Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
Vault engineering schema
How this vault is organised for engineering work. Update this note when the workflow changes, not when a fact changes.
Three layers
| Layer | Folders | Rule |
|---|---|---|
| Evidence | 00-Start-Here.md, 01–11, 99-Validation | Read-only. Consolidated, validated revision 1.3. History is superseded by a new versioned record, never edited (Document-Lineage). A hook blocks edits. |
| Engineering | 12-Development/ | Written by engineers and AI assistants. Cites evidence, never restates it. Everything here is Proposed until code and tests exist at a named revision. |
| Planning | 12-Development/Planning/, 12-Development/Research/ | Issue plans and cited research notes. Working material; superseded freely. |
Ingest (adding knowledge)
- Decide the layer. DG policy or product fact: it belongs in evidence and only the owner changes it (
GGA_VAULT_EVIDENCE_EDIT=1, recorded with DG’s approver and date). - Engineering fact: write or update one note under
12-Development/, following Documentation-Template. - Link to the owning evidence note with a wikilink. A fact lives in exactly one place.
- Add a line to log and, if a new note, to Development-Index.
- Run
python 11-Tooling/validate_vault.py . --selftestfrom the vault root. Fix links; never edit the validator or evidence to make it pass.
Query (finding knowledge)
Start at Development-Index. Read the module’s Minimal Context Set (Modules/), then only the cited sections. Skip 10-Sources/. Use the brain-researcher agent for cited answers.
Authority
See operating-contract section 2. Conflicts are recorded, not resolved by newest timestamp.
Change history
| Date | Change |
|---|---|
| 2026-10-20 | Created (bootstrap Phase 2) |