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.
T13 · Exact-version approval and sole-owner self-approval
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | Unit · API · database |
| Priority | P0 |
| Gates | A04, A05 |
| Build step | Step-04-Opportunities-Versions-Approvals |
| Decisions | Q02 |
Given
A sole entitled owner/admin authors a draft; a contributor and unrelated viewer also try approval. B prepares interest E1.
When
Self-approve exact revision/action explicitly; publish/submit it; try the same commands as contributor/viewer.
Then / oracle
Proposed default permits entitled owner/admin self-approval with explicit action and actor/revision audit. Contributor/viewer cannot self-authorise. Approval binds immutable content and intended action; no substitution or cross-action reuse. Configurable four-eyes approval is separately scoped outside Balanced.
Evidence required
Approval/action/revision records; audit; one approved publication or EOI.
Decision dependency (verbatim)
Q02: DG must approve self-approval default and role matrix; no four-eyes switch is promised.
Source: TDD rev 1.3 (PDF); machine-readable in 10-Sources/tdd-bundle/. Back to Scenario-Index · Traceability-Matrix · integration dependencies in Dependency-and-Regression-Table.