This page is the complete table of contents for the DomiDo wiki. It lists every page currently published, grouped by section, with a one-line summary so newcomers can scan the whole landscape from a single screen. DomiDo is an AI-assisted modular outdoor construction platform built by Avvyland Limited (United Kingdom), and the company sells universal blocks and fasteners only — every construction shown on the platform is a user-generated design. Use this index as the starting point for any wider exploration of the project: if you do not yet know which section a topic lives in, scan here first. If you are reading the wiki for the first time and want a guided path rather than a flat list, Start here lays out a recommended reading order tailored to your role.
The wiki's three orientation pages sit above any section.
- DomiDo — Project documentation hub for DomiDo and pointer to every section.
- Start here — A guided path through the wiki for newcomers, with a recommended reading order.
- Glossary — Every DomiDo-specific term, abbreviation, and concept explained in one place.
The Overview section introduces the project in plain language — what it is, where it is headed, how the pipeline that delivers it works, and the business shape of the venture.
- Overview — Index for the Overview section.
- What is DomiDo? — The DomiDo project explained in plain language: the problem, the solution, the four pillars, and the product family.
- Product vision — The DomiDo vision and mission, the two creation modes, what is in the first release, and the longer-term roadmap.
- How it works — The DomiDo pipeline end to end: idea, 3D model, kit of blocks, box at the door.
- Executive summary — The DomiDo business in one document: recommendation, five-dimension assessment, top risks, top opportunities, and conditions for going ahead.
The Product section describes strategy, scope, and the customer side of the proposition.
- Product — Index for the Product section.
- Minimum viable product scope — The slice of DomiDo being built first: what ships at Phase A pre-order launch, what is out, and the known gaps.
- Personas and the jobs they hire DomiDo to do — The customer types DomiDo is designed for, what they are trying to get done, and the mental models behind it.
- Use cases and user journeys — The end-to-end stories of how people discover DomiDo, design, order, receive, and assemble.
- User stories — The full catalogue of testable behavioural requirements organised by epic.
- Task analysis — A close-up look at each major task, with steps, decisions, failure modes, and time budgets.
- Business model — How DomiDo creates and captures value across kits, the designer marketplace, AI design credits, and network effects.
- Pricing and economics — The conceptual unit economics behind kit pricing and AI credit pricing.
- Product strategy — Block-system constraints, market filters, scoring framework, and use-case categories the platform enables.
- Go-to-market — How DomiDo reaches its first customers across social, content, influencer, community, and PR mechanics.
- Competitive landscape — Who already serves outdoor structures, modular kits, and creator-driven product platforms.
- Competitive user-experience comparison — A like-for-like comparison of how competitor products feel to use.
The Requirements section is the full software-requirements baseline.
- Requirements — Index for the Requirements section.
- Software overview — Master software specification framing what the system must do across the phased rollout.
- Functional requirements — Detailed behaviour across authentication, catalogue, design, checkout, fulfilment, and marketplace.
- Non-functional requirements — Quality attributes: accessibility, responsiveness, reliability, performance, privacy, observability, maintainability.
- Data requirements — Logical data model: entities, fields, lifecycle, classifications, quality rules.
- Interface requirements — REST API surface, enums, and error contracts.
- Security — Identity, authentication, authorisation, payment, upload, and operational security controls.
- Audit and logging — Audit events captured by the platform: event shape, coverage, retention, and access.
- Business rules — Catalogue of rules governing pricing, commerce, returns, payouts, marketplace, and content.
- Acceptance criteria — Conditions every feature must satisfy before shipping.
- User roles and permissions — Roles, capabilities, and access matrices for every user type.
- Engineering requirements — Architecture, frontend, API, media, commerce, and quality-engineering requirements.
- Traceability — Mapping from mock surfaces and product decisions through requirements to APIs and acceptance criteria.
- Web app mock requirements — Mock-derived requirements for the public web app, with overrides where the mock conflicts with product decisions.
- Payment architecture — Deep dive into payment flows, including SetupIntent, PaymentIntent, in-app billing, Connect payouts, strong customer authentication, and tax.
The Architecture section is the technical-design view of the platform.
- Architecture — Index for the Architecture section.
- System overview — The whole platform on one page: app, backend, worker, database, search index, external providers, and phase model.
- Application architecture — How the universal app is structured: one codebase rendered to web today, packageable for iOS and Android later.
- Domain and data — Canonical entities, the relationships between them, the MongoDB collections, and the read models the universal app consumes.
- Backend — The Go backend specification: service shape, runtime processes, internal package boundaries, configuration, transactions, jobs, observability, recovery, and testing.
- Integrations — How the platform connects to Stripe, OAuth providers, AI generation, translation, media, publication, support, analytics, and fulfilment partners.
- Security and operations — Authentication, authorisation, payment safety, privacy, audit, observability, backup and recovery, and the small-team operating model.
- API traceability audit — Route-by-route check that every visible surface is backed by a real backend contract, a client-only behaviour, an external link, or a phase gate.
- Architecture choices — The current architectural choices that shape every other engineering page.
The Operations section covers manufacturing, fulfilment, quality, risk, and the operating cadence.
- Operations — Index for the Operations section.
- Manufacturing and fulfilment — How blocks and fasteners are tooled, moulded, kitted, packed, and delivered.
- Quality assurance — Standards, sampling, inspection, traceability, and corrective action that keep blocks correct, sound, and durable.
- Delivery plan — The phased delivery plan: Phase A public interest beta, Phase A.5 gated no-capture pre-orders, Phase B fulfilment.
- Phase A backlog — The developer-ready work breakdown from foundations through public beta to pre-order conversion.
- Beta launch checklist — Hard launch gates, no-go conditions, smoke-test script, launch-day operating room, and evidence pack.
- Risks, decisions, and cuts — Locked decisions, explicit cuts, top risks, kill-and-pivot signals, and the first-customer plan.
- Risk analysis — Full risk catalogue across technical, IP, market, manufacturing, financial, regulatory, team, competitive, and operational categories.
- Observability — Product analytics, logging, metrics, tracing, error tracking, alerting, and performance monitoring.
- Support and telemetry — Support workflow, event dictionary, alert table, and the data-class boundaries that let a small team learn from real users.
- Sustainability — Material choices, circular-economy positioning, manufacturing sustainability, carbon, packaging, and roadmap.
- Architecture options — Current technology stack, key architecture choices, infrastructure cost model, build-versus-buy, scaling path, and architecture risks.
The Technology section holds the specialised technical research that supports the rest of the wiki.
- Technology — Index for the Technology section.
- Block design — Engineering of the block: dimensions, interlocking mechanism, materials, structural performance, and manufacturability.
- 3D and AR — Viewer libraries, assembly visualisation, AR placement, glTF/GLB pipelines, performance, and accessibility.
- Assembly instructions — Instruction generation, visual conventions, interactive UX, animated sequences, accessibility, and formats.
- Payment systems — Stripe usage across phases: SetupIntent, PaymentIntent, Billing, Connect Express, tax, refunds, fraud, and reconciliation.
- Product scoring — Signals, model structure, freshness handling, anti-gaming, and the relationship to merchandising.
The Reference section is this section: the orientation layer.