The rest of this library is written for the people running trials. This section is for the people running the software. Each page says what is built, what is not, and what a reviewer should ask.
The shape of the system
- Architecture: the parts, the modules in each, how a request flows, what runs in the background, and the gaps.
- Data and tenancy: the 72 tables, how organizations are separated, how UAT and Live data are kept apart, and what makes the records tamper-evident.
- The database: the two database roles, the one-table-per-migration schema, the commands, and how a database is reset.
- Environments and versioning: the study states, the workspaces and the versions, and what each state allows.
- API and integrations: the API surface, and what can and cannot be integrated today.
- AI: the two optional helpers, where their data goes, and how they are gated.
Running and checking it
- Running it: what you deploy, how a deployment goes, backups, alerts, and the operational gaps to plan for.
- Configuration: every setting of the data plane and the control plane, generated from the code.
- Testing and quality: the automated suites, the gates a revision passes, the load tests, and what is not a validation.
- Architecture decisions: the twenty records behind the design, with their status.
For security controls and the split between what the application provides and what your infrastructure must, see Security and hosting. For what the system does and does not do for each regulation, see Compliance.