Business Flows (BF) — Cross-EPIC User Journeys
Cross-EPIC narrated journeys. Each BF doc walks a single end-to-end user journey step-by-step, naming the user story that owns each step, the code path that runs it, the closest automated test, and any catalog gaps surfaced as
[SME-PROPOSED]candidates.Authored during the RTM Reconciliation Pilot (2026-05-24) and scaled out across the remaining 12 flows on 2026-05-25. BF-001 is the template; BF-002 through BF-013 follow the same structure.
Index
| # | Flow | Status | Primary EPICs | Highlights |
|---|---|---|---|---|
| BF-001 | Tenant + Property Onboarding | DRAFTED 2026-05-24 | EP-001, EP-002 | 14 steps · 8 failure modes · 7 drifts |
| BF-002 | Guest Booking | DRAFTED 2026-05-25 | EP-003, EP-011, EP-004, EP-015 | 11 steps · 10 failure modes · 12 drifts · 4-service payment seam |
| BF-003 | Check-in (Indian + International + C-Form) | DRAFTED 2026-05-25 | EP-005A, EP-004, EP-006 | LAUNCH BLOCKER · 12 steps · 13 failure modes · 21 drifts (8 P0) |
| BF-004 | POS Order → Folio | DRAFTED 2026-05-25 | EP-007, EP-005B | LAUNCH BLOCKER · 10 steps · 11 failure modes · 8 drifts (6 P0) |
| BF-005 | Check-out + e-invoice | DRAFTED 2026-05-25 | EP-005A, EP-005B, EP-012C | LAUNCH BLOCKER · 12 steps · 13 failure modes · 7 P0 |
| BF-006 | Night Audit | DRAFTED 2026-05-25 | EP-005C | 12 steps · 10 failure modes · 12 drifts · missing reconciliation invariant |
| BF-007 | OTA Channel Sync | DRAFTED 2026-05-25 | EP-009, EP-003 | 12 steps · 10 failure modes · 11 drifts (4 P0) |
| BF-008 | Payment Capture + Refund | DRAFTED 2026-05-25 | EP-015, EP-005B | 12 steps · 10 failure modes · 9 drifts (4 P0) |
| BF-009 | Housekeeping Lifecycle | DRAFTED 2026-05-25 | EP-006 | 13 steps · 22 [SME-PROPOSED] · UTC vs IST midnight bug |
| BF-010 | Banquet Event | DRAFTED 2026-05-25 | EP-008 | 11 steps · banquet→folio→IRN handoff entirely missing |
| BF-011 | Spa Booking | DRAFTED 2026-05-25 | EP-016 | 11 steps · 9 failure modes · 14 drifts |
| BF-012 | Reporting & Compliance Export | DRAFTED 2026-05-25 | EP-012B, EP-012C, EP-012D | 12 steps · 11 failure modes · 12 drifts (8 P0) highest concentration |
| BF-013 | DSAR / GDPR Erasure | DRAFTED 2026-05-25 | EP-004, EP-014, EP-015 | 12 steps · 12 failure modes · 11 drifts · CBIC/RBI retention violation |
Conventions
- Catalog gap tag:
[SME-PROPOSED]marks a step whose user story does not exist in03-epic-catalog/01-epic-catalog.mddespite shipped code. - File paths: always absolute repo-relative (e.g.
hmp-auth-service/src/auth/auth.controller.ts:58). - Test status: PASS / FAIL / SKIPPED / TBD (sourced from
hmp-docs/docs/platform-registry/2026-05-16-13-flow-demo-readiness.mduntil Task 12 re-measures). - Drift IDs: locally numbered per BF doc (
D-001,D-002, …); roll up to the platform-wide drift register at reconciliation Task 6.
How to author a new BF doc
- Pick a cross-EPIC user journey from the index above.
- Read the source map for the EPICs it touches (
_scratch/source-map.mdif a reconciliation is in progress, otherwise the per-EPIC RTM files). - Walk the journey step-by-step. For each step name:
- The owning story (or
[SME-PROPOSED]if a catalog gap). - The primary code path (file:line).
- The closest automated test (file :: scenario — pass status).
- Pre-conditions + post-conditions.
- Notes on kill-switches, flags, drift, etc.
- The owning story (or
- Add a "Failure modes worth testing" table (target: 6-10 rows).
- Add a "Day-2" section listing what the hotel tackles post-go-live.
- Add a "Drift summary" table for issues surfaced by the walk.
- Cross-link the doc from this README's index.