Technical
The mechanism, with names.
Eight short pages for whoever has to sign off on putting a record in here. Each names the functions, tables and tests involved and says where to look. No pitch.
- 1Architecture at a glanceA Next.js application over one PostgreSQL database, where the database is the boundary and the application is a client of it.
- 2The enforcement modelA step is a typed demand for evidence; the database refuses to satisfy it without that evidence and refuses to close a case with a required step open.
- 3Tenant isolationRow-level security on every table, keyed by org_id and project_id, with the role checks as security-definer functions the policies call.
- 4The audit spine and the hash chainOne append-only events table per organization, each row sealed with a SHA-256 digest of the row before it, verifiable end to end by a single function.
- 5The AI workforceTen agents that are people in the data model, act only through a permission-checked tool registry, and hand anything consequential to a named human.
- 6Field capture, offline, and location proofA tablet on site queues what it captures, replays it when it has signal, and the same database rules apply when it lands.
- 7Data model, export and APIOrganizations own projects; projects own sites, assets, cases and documents; everything you own leaves as CSV and files on demand.
- 8Deployment, migrations and testsChecksummed migrations that can be re-run, a test suite that runs the real database offline, and crons that fail closed.
Terms used here are defined in the glossary. The public readiness register is on the security page.