The docs live next to the code.

1. 01Gateway model deliveryThe server-side provider-routing contract, supported OpenRouter path, key boundaries, and conditions required before any live activation.docs/GATEWAY_MODEL_DELIVERY.md
2. 02SpiderMesh archiveThe preserved distributed-compute design and the explicit reactivation boundary while contribution and execution remain paused.docs/SPIDERMESH_ARCHIVE.md
3. 03Operating policy and evaluation planThe versioned system-policy path, behavior evaluation gates, and truthful distinction between policy operation and model training.docs/VERITY_OPERATING_POLICY_TRAINING_PLAN.md
4. 04Single BrainThe tenant-scoped deterministic reminder foundation, explicit consent API, privacy screen, withdrawal boundary, and deferred universal-learning work.docs/SINGLE_BRAIN.md
5. 05Office quality loopThe evidence-backed 98% completion gate, bounded revision passes, review and continuation states, and currently deferred quality-progress interface.docs/OFFICE_QUALITY_LOOP.md
6. 06Research and Work TraceThe persisted evidence trail, review-state report, and visible activity records that will support the dedicated Research Canvas.docs/RESEARCH_AND_WORK_TRACE.md
7. 07Deployment runbookContainer images for each service, the public/private compose split, TLS and CSP templates, and the mTLS certificate tooling. Start here if you intend to run Verity yourself.docs/DEPLOY.md
8. 08StatusWhat is verified, what is in flight, and which test gates were green at the last snapshot. Written to be checked, not to reassure.docs/STATUS.md
9. 09Competitor gap auditVerity measured against the strongest comparable products, with a file-and-line citation behind every claim about Verity and a severity on every gap. Includes the places Verity is behind.docs/COMPETITOR_GAPS.md
10. 10Gap closure planThe ranked sequencing of that audit: owner service, effort, dependencies.docs/COMPETITOR_GAPS_PLAN.md
11. 11Codebase auditA point-in-time read of the tree: what exists, what is stubbed, what the tests actually cover.docs/AUDIT_2026-07-25.md
12. 12Master planThe milestone structure the build follows, and the design rules the interface is held to.docs/MASTER_PLAN.md
13. 13Scale backlogProduction hardening and scale-out work that is known, scoped and deliberately not done yet.docs/SCALE_BACKLOG.md
14. 14API surfacestaleThe service and route inventory. Read it with care: the gap audit flags this file as stale, listing shipped routes as planned. The code is the authority.docs/API_SURFACE.md

BoundDocumentation is not the specification. Where a document and the source disagree, the source is right and the document is a bug, which is why the gap audit refuses to cite anything but file:line.