Welcome to the DomiDo project wiki. This page is the recommended first stop for anyone landing here for the first time — a guided tour rather than a checklist. Read it through if you want a complete picture, or jump straight to the section that matches your role. DomiDo is an AI-assisted modular outdoor construction marketplace developed by Avvyland Limited (United Kingdom): customers describe what they want to build outdoors or upload a 3D model, and the platform produces a physical kit of universal interlocking blocks plus the fasteners and instructions to assemble the object at home. The company sells universal blocks and fasteners only; every construction shown on the platform is a user-generated design. The pages below walk a newcomer from the product idea, through the pipeline that delivers it, into the role-specific documentation that goes deeper.
DomiDo lives at the intersection of artificial intelligence (turning a description or reference into a 3D model), computational geometry (turning that 3D model into a layout of universal interlocking blocks), and physical manufacturing (turning the layout into a real kit at the customer's door). The platform reaches its final form in four phased rollouts. Phase A is the public interest beta: customers browse the gallery, save designs, and register non-binding interest in a kit, and no money moves anywhere on the platform. Phase A.5 opens an invited pre-order step in which a customer's card is verified through Stripe but never charged, the order sitting in a "cleared to build" queue. Phase B captures payment once a manufacturing batch is queued, ships the kit, and supports the customer through assembly with the digital build companion. Phase C opens the full designer marketplace, where designers publish their own kits, earn royalties on each pre-order, and protect their work with embedding-based uniqueness controls.
If you have ten minutes and want a complete answer to "what is this project?", read these four pages in order. What is DomiDo? introduces the project concept in plain language. How it works traces the end-to-end pipeline from "I have an idea" to "I have built it". Product vision describes where the product is headed. Executive summary gives the business in one document. By the end you will know what the product is, who it is for, how it is delivered, and where it sits in the market.
Begin with Overview and then move through the Product section in order. MVP scope describes what is being built first and what is explicitly deferred. Personas and jobs names the customers the product is designed for and the jobs they hire the platform to do. Use cases and user journeys traces the end-to-end flows. The commercial picture is in Business model and Pricing and economics; the strategic shape is in Product strategy; the launch plan, channels, and viral mechanics are in Go-to-market; and Competitive landscape explains who else plays in this space.
After the Overview, head into the Architecture and Requirements sections. System overview is the high-altitude architecture picture; Application architecture describes the universal React Native and Expo app; Backend specification covers the Go services, MongoDB Atlas, and Atlas Vector Search; Domain and data architecture lays out the canonical entities and their ownership; Integrations lists the third-party services the platform depends on; Security and operations describes the security posture, audit, observability, and backup; Architecture decisions records why the system is built the way it is; and Payment architecture is the full Stripe SetupIntent and PaymentIntent design. Then read the requirements set, beginning with Software overview.
Start in Design and UX. The umbrella UX document is Baseline report; the app's content structure is in Information architecture; diagram-led walkthroughs of each customer journey are in User flows; the tokens, components, typography, and colour palette are in Design system; repeating UI behaviours are in Interaction patterns; the accessibility position is in Accessibility; and the formal UX reviews are in Heuristic evaluation and Cognitive walkthrough. Cross-reference with the Product section to align user-experience work with strategy.
On the operational side, Manufacturing and fulfilment describes how kits are made and shipped, Quality assurance covers defect handling and test strategy, Delivery plan is the startup execution schedule, Beta launch checklist lists what has to be true to go live, Risks, decisions, and cuts records the trade-offs already made and the known risks, Observability holds the metrics, logs, and alerts, and Support and telemetry describes how customer behaviour is captured. The compliance picture comes from Product safety for UKCA, CE, and conformity assessment; Marketplace compliance for Phase C duties; Tax and customs for VAT, import duties, and cross-border concerns; Data and privacy for GDPR and adjacent regimes; Intellectual property for patent strategy and designer rights; and Legal overview for the consolidated legal landscape.
The business in one document is Executive summary. The commercial mechanics behind the marketplace are in Business model, and the pricing structure and unit-economics shape are in Pricing and economics. The high-level business case — milestones, target market, cost categories — is in Feasibility summary, and the material risks and mitigations are catalogued in Risk analysis.
Every page ends with a See also footer that links to related topics, so you can navigate laterally as well as hierarchically. The Document index lists every page by section with a one-line summary, and the Glossary explains every project-specific term. Sections are folders: opening a section name in the address bar (for example /domido/architecture) lands on the section index, which lists all child pages with a short description of each.