Appendix C — Hotel Implementation Roadmap

Status: Planning
Sources: A-01 — Jijibora Deployment (Administrator Operations), A-04 — Starter Packs for Administrators, D-07 — Starter Bundles for Developers, S-07 — Starter Packs for Stakeholders, MASTER PRODUCTION PLAN — Sovereign OS / Jamii Online Console & Vertical Ecosystem

1. Phase 0 — Foundations (Weeks 0–2)

Deploy Sovereign OS core strata (SurrealDB :8000, NATS :4222, Camel :8181, Kestra :8180, Agent BFF :3030, Truth BFF :3031)
Deploy canonical primitives: claim, truth_node, truth_edge, resource, resource_edge, integration_entity (s356)
Deploy APF (s230), PoCE (s131-s150), federation (s184), compliance gates (s350)
Deploy hotel starter pack dependencies (Keycloak :8081, ERPNext, OpenMAINT :8080, Synapse :8008, Plane :8091, MinIO :9000, Gotenberg :3094, Solver Gateway :3070)
Seed base NATS KV lookups (SOVEREIGN_LOOKUPS)

Exit: Health checks green; fn::integration::health_check_kuratibu / equivalent passes; no schema changes beyond canonical strata.

2. Phase 1 — Pilot Property (Weeks 3–8)

Starter packs: Front Desk Desk (H-1, H-10) + Housekeeping Desk (H-2, H-7), Soft mode.

Register hotel CNS types (cns://claim/type/hotel/*)
Declare hotel NATS KV lookups (thresholds, SoD, checklists, SLAs)
Wire PMS webhooks → reservation claims; ERPNext → folio/PO sync
Housekeeping: task claims, photo evidence (MinIO), inspector sign-off, PoCE receipts
Staff chat: Synapse rooms ↔ discussion claims
Live gate ritual: move Front Desk + Housekeeping packs to LIVE

Exit: Pilot property running live on reservations, check-in/check-out, folio, housekeeping sign-off; auditors can verify PoCE receipts.

3. Phase 2 — Full Property (Weeks 9–16)

Add: Maintenance Desk (H-3, H-8) + Finance Desk (H-4), LIVE.

OpenMAINT work order integration; fault intake → WO → technician dispatch → parts deduction → expert sign-off
Procurement: requisitions → threshold tiers → dual-custody PoCE → ERPNext PO → three-way match
Incident & security reports with escalation ladder
Solver-gateway: F&B basket split (procurement.basket_split@1), housekeeping route proposals

Exit: Full property operations on Sovereign OS; ERPNext 3-way match live; OpenMAINT WOs synced; solver proposals reviewed by humans.

4. Phase 3 — Events & Group (Weeks 17–24)

Add: Events Desk (H-5, H-6) + Group Federation (H-9), LIVE.

Function space booking, BEOs, event design mood boards, Gotenberg PDF export
Multi-property federation: group procurement with BBS+ selective disclosure, federated PoCE escrow
Scope governance & delegation (s142): property GM ↔ department heads ↔ regional office

Exit: Hotel group operating cross-property procurement; events revenue on platform; delegation chains auditable.

5. Phase 4 — Scale & Optimize (Month 7+)

Solver-gateway housekeeping route optimization (live, human-confirmed)
Maintenance crew routing; linen/laundry replenishment planning
Additional properties onboarded as new scopes
Compliance gates live: health, fire, accessibility, building safety inspections
Dashboards from live data only (no hardcoded metrics)

6. Success Metrics (Live Data Only)

All metrics computed from live backend API responses / SurrealDB queries — never hardcoded:

Reservations processed via PoCE (count, from claim table)
Housekeeping turnovers completed with inspector sign-off (count, from PoCE steps)
Maintenance WOs closed with expert sign-off (count, from claim + OpenMAINT mirror)
POs approved via dual-custody (count, from PoCE sessions)
Cross-property federated requisitions (count, from s184_record_federation)
Compliance gate evaluations passed/failed (from compliance_gate_eval)

Honesty rule: If a metric is not yet computed, the dashboard renders an honest empty state or skeleton — never a synthetic number.

7. What to Confirm with the Hotel (Pilot Kickoff)

Which 3–5 problems to solve first (housekeeping sign-off? procurement approval? maintenance WOs?)
Which staff/guest languages and phone numbers receive reports/updates
Who holds funds and who taps "Approve" on photo proof (name the propose-vs-dispose line)
Which personal details stay out of receipts/dashboards; emergency access TTL
Service promises: max hours a room may stay out of order; max fault response time (which properties may choose faster)