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.
Documentation template
Every note in 12-Development/ (except generated tables and ADRs) follows this shape. Keep sections short; delete a section only by writing “None” so the absence is visible.
- Purpose: one or two sentences.
- Scope: what the note covers and what it deliberately does not.
- Source notes: wikilinks to the evidence notes that own the facts.
- Current state: Proposed (specification) or Implemented (code and tests exist at a named revision). Nothing is Implemented until then.
- Contracts: interfaces, endpoints, events, tables, stated as the vault states them.
- Invariants: rules that must always hold.
- Scenarios: stable IDs (T##, DG##) and gates (A##, S##) that exercise this note.
- Open decisions: Qnn that block behaviour, written as Blocked by Qnn.
- Known limitations.
- Change history: date and change.
Front matter: title, tags, status: proposed, vault_revision: "1.3", updated, sources. Begin with the vault’s one-line status banner.
Wording rules the validator enforces: no unnegated claim that tests passed or that DG approved anything; no exactly-once delivery claim; every wikilink resolves.
Change history
| Date | Change |
|---|---|
| 2026-10-20 | Created (bootstrap Phase 2) |