This section is the engineering picture of DomiDo. It describes how the universal customer-facing application, the backend service, the data model, the external integrations, and the security and operations posture combine into a single working platform that supports a phased rollout — public interest beta first, then no-capture pre-orders, then real fulfilment, with a designer marketplace expansion to follow. The section is written so a newcomer can read its pages top to bottom without prior knowledge of the project's internal documents: detailed implementation rules are captured directly on these pages, and the requirements section remains the canonical functional contract that those pages sit on top of. Together, the pages below form a complete picture of how the platform is built today, what it has been designed to grow into, and where the boundaries lie between the engineering shape of the system and the business and legal shape of the product.
The System overview describes the whole platform on one page — the universal application, the Go backend, the worker loop, the database, the search index, and the external providers DomiDo depends on, with the phase-governed delivery model that controls what runs when.
The Application architecture page describes how the universal application is structured. One React Native and Expo codebase is rendered as a Web Progressive Web App today and packaged for iOS and Android when those phases open.
The Backend page describes the Go service that owns the API, the workers, and the business logic — its service shape, runtime processes, internal package boundaries, configuration model, and the rules that handlers, jobs, and transactions follow.
The Domain and data page describes the canonical entities (interest reservation, pre-order, order, listing, designer, payout account, job, localised text, and others), their relationships, the MongoDB collections that store them, and the read models that drive the user interface.
The Integrations page describes the external systems DomiDo talks to: Stripe, the OAuth providers, AI generation providers, the language-model translation provider, media storage, the Docusaurus help projection, email and support, analytics, and fulfilment partners.
The Security and operations page describes authentication, authorisation, payment and payout safety, privacy and data protection, audit, observability, backup and recovery, and the small-team operating model.
The Infrastructure page describes the dev, test, staging, and production environments that run the platform — application compute, orchestration, database, object storage, edge, observability, and the promotion pipeline that moves a build through them.
The API traceability audit is the route-by-route, element-by-element check that every visible UI surface is backed by a real API contract or an explicit phase gate, with the resolved API gaps and remaining frontend corrections recorded for the Phase A launch.
The Architecture choices page records the architectural choices that shape every other engineering page: the universal React Native application, the canonical application-programming-interface, the phase model as a boundary, the three commerce aggregates (interest reservation, pre-order, order), the Go and MongoDB Atlas backend, and backend-owned translation.