JJijibora
Docs & Product Guide
On this page (5 sections)

Deployment & Starter Packs — Hotel Rollout

Status: Implementation & Operations
Sources: S-07 — Starter Packs for Stakeholders, A-04 — Starter Packs for Administrators, D-05 — Starter Packs for Developers, D-07 — Starter Bundles for Developers, A-01 — Jijibora Deployment (Administrator Operations)


1. Deployment Posture — Soft First

Per AGENTS.md — Sovereign OS / Cosmic Circuit and the Jijibora deployment model, every hotel playbook ships Soft-first (validation + plan, zero live writes) until a live gate ritual is performed. A pack never self-declares live_gate_met. Rollout stays in Soft mode until the hotel confirms:

  • Which 3–5 problems to solve first (e.g., housekeeping sign-off, procurement approval, maintenance work orders)
  • Which citizen/staff languages and phone numbers receive reports and updates
  • Who holds funds and who taps "Approve" on photo proof
  • Which personal details are kept out of receipts/dashboards; how long emergency access lasts
  • Service promises (max hours a room may stay out of order, max response time for faults)

2. Hotel Starter Packs

Starter packs bind to existing scenario/lookup keys (never invent new namespaces) and emerge as dictionary SKU rows.

Starter PackContentsHotel Day-1 Scope
Front Desk DeskH-1 Reservation & Folio, H-10 IdentityReservations, check-in/check-out, folio, guest identity
Housekeeping DeskH-2 Housekeeping, H-7 Staff CommsRoom turnover, checklists, inspector sign-off, staff chat
Maintenance DeskH-3 Maintenance, H-8 IncidentFault intake, OpenMAINT work orders, expert sign-off
Finance DeskH-4 Procurement, ERPNext syncRequisitions, approval tiers, PO sync, three-way match
Events DeskH-5 Events, H-6 Mood BoardFunction bookings, BEOs, event design, PDF export
Full Hotel BundleAll H-1..H-10 + federationComplete property operations backbone

3. Bring-Up Sequence (Per Pack)

  1. Ensure lookups/scenarios exist in NATS KV (datasets/lookups/, datasets/scenarios/ are seed sources; runtime reads KV, never filesystem).
  2. Seed one family at a time with its targeted seeder (scripts/seed-nats-kv-declarative.mjs); record revision in datasets/lookups/kv-manifest.json.
  3. Run the family verify script (NATS judge + Surreal cross-checks); never fabricate a passing verdict.
  4. Re-run scripts/render-fragments-manifest.mjs after any fragment change.
  5. Perform the live gate ritual to move a pack from Soft to LIVE.

4. Technical Stack (Local Dev)

ServicePortRole
SurrealDB:8000State of record (RocksDB, NS africa, DB community_os)
NATS:4222Event spine / JetStream KV
Apache Camel:8181Protocol mediation, EIP routes
Kestra:8180Macro-DAG orchestration
Agent BFF:3030Runtime BFF, playbook runner proxy
Truth BFF:3031Truth graph / DDE proxy
ERPNext:8000 (API)Fiscal GL / PO
OpenMAINT:8080CMMS / work orders
Synapse:8008Matrix chat
Plane.io:8091Task boards
MinIO:9000Object storage
Gotenberg:3094PDF generation
Keycloak:8081Identity / OIDC
Solver Gateway:3070Optimisation
Fleetbase:9002Logistics

Local start: surreal start --user root --pass root --bind 127.0.0.1:8000 rocksdb:/data/surreal-data; then DEV_SKIP_AUTH=1 SURREAL_URL=http://127.0.0.1:8000 node apps/agent-bff/src/index.js.


5. Phased Rollout (Hotel Group)

PhaseScopeExit Criteria
Pilot (1 property)Front Desk + Housekeeping starter packs, Soft modeLive gate passed; PoCE receipts verified; staff trained
Expand (1 property)Add Maintenance + Finance packsERPNext 3-way match live; OpenMAINT WOs synced
Group (multi-property)Add Events + federation (H-9)Cross-property procurement live; BBS+ selective disclosure
Scale (N properties)Full bundle + optimisationSolver-gateway use cases live; dashboards from live data only