Requirements Reconciliation
This folder holds the platform-wide Requirements Traceability Matrix (RTM) — the
link layer between requirements (../epics/, ../01-epic-catalog.md),
use cases (../../platform-registry/_data/use-cases/), running code, and tests.
First reconciliation (BF-001 Tenant + Property Onboarding) landed 2026-05-24 as the pilot. The pattern is now ready to scale to BF-002 through BF-013 — see
PLAYBOOK.md.
Files in this folder
| File / folder | What it contains | Authored / updated |
|---|---|---|
RTM-DASHBOARD.md | Top-level roll-up: one row per EPIC, summary metrics (Catalog %Built, Verified %Built, Tested, Pass-rate, Drift count, SME refinements). EP-001 + EP-002 populated by the pilot; EP-003..EP-022 scaffolded. | Pilot 2026-05-24 |
P0-DRIFT-TRIAGE-2026-05-25.md | 11-cluster engineering triage of the 29 launch-critical P0 drifts. Each cluster carries owner, effort, sprint placement, master-tracker linkage, and operator accept/defer decision row. 75% of these P0s are brand-new — not in the master pending tracker. | 2026-05-25 |
EP-001-rtm.md | Per-EPIC matrix for the 7 EP-001 stories that participate in BF-001 (Tenant + Property Onboarding). PARTIAL RTM — the other 9 EP-001 stories ship with a future auth-flow reconciliation. | Pilot 2026-05-24 |
EP-002-rtm.md | Per-EPIC matrix for all 14 EP-002 stories. FULL RTM. | Pilot 2026-05-24 |
01-epic-catalog-SME-PROPOSED.md | Sidecar with proposed status corrections to the live catalog using the new 5-state vocabulary (Built / Built-Untested / Partial / Stub / Not Started). Covers EP-001 + EP-002; includes 5 proposed new stories. | Pilot 2026-05-24 |
use-case-proposals/ | Sidecar folder with proposed UC changes — 2 enhancing-existing + 5 NEW UC proposals from the pilot. Each closes a specific drift finding. | Pilot 2026-05-24 |
PLAYBOOK.md | How to author a new RTM reconciliation. Captures what worked, what to change, drift criteria, SME operating rules, recommended order for BF-002..BF-013. | Pilot 2026-05-24 |
README.md | This file — folder index + reading order. | Pilot 2026-05-24 |
How to read these files
Three entry points by audience:
1. Engineering leadership / audit reviewer
Start at RTM-DASHBOARD.md. The roll-up table tells
you at a glance which EPICs have been reconciled, which still rely on stale
catalog status, and where drift counts are concentrated. Cross-reference the
"Last reconciled" column against the live demo-readiness snapshot
(../platform-registry/2026-05-16-13-flow-demo-readiness.md) to gauge
freshness.
2. Developer / SME working a specific EPIC
Open the matching EP-NNN-rtm.md. Each story carries
code paths, test files, pass-rate, SME notes, and drift findings — sufficient
to start a remediation PR without re-reading the source EPIC + 5 review files.
For a cross-EPIC user journey, open the matching
../business-flows/BF-NNN-*.md — the BF doc is the
load-bearing artifact that surfaces gaps no single EPIC owns.
3. Operator reviewing proposed changes
The *-SME-PROPOSED* files are the operator review queue:
01-epic-catalog-SME-PROPOSED.md— proposed catalog status corrections + 5 proposed new stories. Accept / reject / amend per row, then merge accepted rows into the live catalog and delete the sidecar.use-case-proposals/uc-*-SME-PROPOSED.yaml— proposed UC changes / NEW UCs. Each file's header states which class (existing vs NEW) and which drift ID it closes.
The [SME-PROPOSED] tag also appears inline within each per-EPIC RTM, each
business-flow doc, and the appended sections of per-story review files
(../reviews/EP-NNN/US-NNN-NNN-review.md). Inline refinements
are advisory until the operator promotes them into the live story body.
Status of the artifacts
| Artifact | Status (2026-05-24) | Next step |
|---|---|---|
| Pilot: BF-001 Tenant + Property Onboarding (EP-001 partial + EP-002) | DONE — landed 2026-05-24 across the 11 pilot tasks | Operator review of sidecars + acceptance of 5 proposed new stories |
| BF-002 Guest Booking (search → confirmation) | not yet started | Schedule per PLAYBOOK § Next flows recommended order (position 6) |
| BF-003 Check-in (Indian + International + C-Form) | not yet started | Recommended NEXT — Property #1 launch-blocker (position 2) |
| BF-004 POS Order → Folio | not yet started | Property #1 launch-blocker (position 4) |
| BF-005 Check-out + e-invoice | not yet started | Property #1 launch-blocker (position 3) |
| BF-006 through BF-013 | not yet started | See PLAYBOOK § Next flows recommended order |
| Phase 4 automation (script-driven mechanical RTM populator) | not yet started | Recommended after BF-003..BF-005 land — by then the mechanical patterns are stable enough to script |
Related folders
../epics/— EPIC source docs (live, authoritative for story body)../reviews/— per-story implementation review files (in-place enhanced by the pilot with Tests/Drift/SME sections)../business-flows/— cross-EPIC user-journey narratives (BF-001 created by the pilot; template for BF-002..BF-013)../01-epic-catalog.md— live catalog (3-state vocabulary; the SME-PROPOSED sidecar in this folder proposes a 5-state expansion)../../superpowers/specs/2026-05-24-rtm-reconciliation-pilot-design.md— pilot spec../../superpowers/plans/2026-05-24-rtm-reconciliation-pilot.md— pilot plan (11 tasks)