15. Traceability and release scope
- Repository
- bloque-app/aledgent
- Commit
5ca6b8a- Version
- 0.4.27
- Status
- draft
- Rendered
- 2026-10-17T19:30:18Z
Every story maps to at least one requirement, invariant or error. Work that traces to nothing here is invalid. This specification MUST NOT contain a requirement that serves no story.
Cross-cutting requirements serve every epic, not just one: REQ-AR-1–REQ-AR-7, REQ-PN-1, REQ-OP-1, REQ-OP-3, REQ-OP-4, REQ-OP-6–REQ-OP-8, REQ-OP-10–REQ-OP-12,
REQ-ER-1, REQ-ER-2, and the runtime and kernel capability contracts REQ-RT-* and REQ-KER-*. Every story
depends on these, and no story names them individually. Epic L is withdrawn. Its identifier is not
reused.
Release scope
Section titled “Release scope”V0 is the first release. It is a deployment with one operator, one settlement layer, both custody modes and the switch between them, and every surface of §7. It is not the release that delivers every property in this document.
| Epic | V0 | Beyond V0 |
|---|---|---|
| A — Identity and accounts | US-A1, US-A2, US-A4–US-A9 |
— |
| B — Internal transfers | US-B1–US-B3 |
— |
| C — Reservations | US-C1–US-C4, US-C6 |
US-C5 (encumbrance — DEF-11) |
| D — Inbound | US-D1–US-D3 |
— |
| E — Outbound | US-E1, US-E3, US-E4 |
— |
| F — Multi-asset | US-F1, US-F3–US-F5 |
— |
| G — Agents | US-G1–US-G3 |
US-G4 (window allowances) |
| H — Querying | US-H1–US-H5 |
— |
| I — Privacy and disclosure | US-I1, US-I4 |
US-I2, US-I3 (disclosures — DEF-3) |
| J — Provability | US-J1, US-J3 |
US-J2 (third-party detection of revision) |
| K — Operations and recovery | US-K1–US-K7 |
— |
| M — Integration | US-M2–US-M8 |
— |
| N — Migration | US-N1, US-N2 |
— |
A requirement, invariant or error that serves only a beyond-V0 story does not bind V0. Three exceptions bind V0 even though their stories do not:
REQ-PR-1andREQ-PR-7, so that anchoring starts from the first entry, not from the first disclosure;REQ-RC-3, so that an upgrade path exists before it is needed;REQ-AR-5, so that no claim goes beyond what V0 enforces.
V0’s exit criteria are NFR-9’s three reconciliation axes at exactly zero divergence, sustained, and
REQ-RC-4’s zero-divergence rule for any initial state. Nothing else in this document may be traded
against them.
© 2026 Pagos Cube LLC · Code: Apache-2.0 OR MIT · agents/: AGPL-3.0-or-later · Docs: CC-BY-4.0