Jijibora Tie-In — How Hotel Packages Map to the Existing Smart-City Framework
Audience: Product, platform, and implementation teams
Purpose: Show how the hotel feature packages reuse the existing Jijibora building/reflex/community infrastructure rather than building a new vertical
Sources:docs/platform-map/jijibora/,docs/playbooks/,docs/platform-map/system/
1. The Core Idea
Jijibora is the platform's smart-city/community framework: buildings react to their own state through declarative reflex rules, sourcing, and governance. A hotel is a managed building with residents (guests), staff, vendors, and compliance obligations — exactly the shape Jijibora already models. The hotel packages do not build a new vertical; they configure the existing Jijibora primitives (claims, truth graph, reflex rules, scenario packs, starter packs) for hotel-specific CNS types and lookups.
2. Direct Mappings — Hotel Domain → Jijibora Primitive
| Hotel Package | Jijibora Equivalent | Reuse Point |
|---|---|---|
| PK-01 Front Office & Reservations | Building reflex: space occupancy; mall-tenancy.rule.json (occupancy tracking on space entities) | Room = space entity; occupancy = lease; checkout triggers housekeeping reflex |
| PK-02 Housekeeping & Staff | Community sourcing rule; reflex rule with SoD gate | Turnover task = sourcing requirement; inspector sign-off = separation-of-duties (lookup.claims.sod.v1) |
| PK-03 Engineering & Maintenance | Building safety inspections scenario; public-space rounds rule | Fault = inspection stage; work order = rounds ticket; expert sign-off = expert_signoff_required_for_certificate guard |
| PK-04 Restaurant & F&B | Community sourcing + solver (basket split) | Requisition = sourcing requirement; vendor split = procurement.basket_split@1 solver |
| PK-05 Events & Banquets | Mood board / creative review; meeting notes & decision records | Event design = cns://creative/mood_board; BEO = cns://knowledge/meeting_note |
| PK-06 Staff & Workforce | Identity plane; APF; scope governance | Staff = cns://truth/node/person; shifts = truth edges; permissions = APF resolve_effective |
| PK-07 Procurement & Group Purchasing | Record federation (s184); federated PoCE escrow | Group procurement = cns://federation/procurement; per-property quota = BBS+ selective disclosure |
| PK-09 Compliance & Safety | Building safety inspections scenario (7-stage chain); compliance gates (s350) | Fire/health/accessibility = gate stages; expert sign-off = mandatory gate guard |
3. Reused Jijibora Artifacts
| Jijibora Artifact | Hotel Use |
|---|---|
mall-tenancy.rule.json (jijibora-facilities) | Room/staff occupancy tracking; stall/board analogue → room/function-space booking |
building-safety-inspections.scenario.json | Fire, health, accessibility, building-safety inspection chain with expert sign-off |
rent-lease-register.rule.json | Room lease register; occupancy history append-only |
lookup.claims.sod.v1 | Housekeeping cleaner ≠ inspector; folio approver ≠ requester |
lookup.claims.threshold.v1 / .procurement.v1 | Folio adjustment tiers; PO approval routing |
Solver Gateway procurement.basket_split@1 | F&B basket split across vendors |
s184_record_federation | Multi-property group procurement bindings |
s142_scope_governance_authority | Regional → property → department delegation chains |
s230_app_permissions (APF) | Role-based access per property (front desk vs. housekeeping vs. manager) |
s131-s150 PoCE lifecycle | Check-in, clean sign-off, work-order close, PO approval receipts |
Starter pack model (jijibora-starter-packs/) | Hotel starter packs: Front Desk, Housekeeping, Maintenance, Finance, Events |
4. What the Hotel Reuses vs. What Is New
| Reused (no new code) | New for hotels (config only) |
|---|---|
| Reflex rule engine (criteria → match.fired) | Hotel CNS types: cns://claim/type/hotel/* |
| Solver Gateway + branch_and_bound | Hotel lookup values (checklists, thresholds, escalation ladders) |
| PoCE session + receipt | Hotel playbook scenario packs (H-1..H-10) |
| Record federation (s184) | Starter-pack dictionary entries for hotel SKUs |
| APF role resolution | Guest BBS+ selective-disclosure credential templates |
| Compliance gates (s350) | Event mood-board PDF export route (already exists in playbooks) |
No new tables. No new schema. No bespoke hotel vertical. The hotel packages are declarative configuration (CNS types, lookups, scenario packs, starter packs) on top of the same substrate Jijibora already runs on.
5. Example — Housekeeping Turnover Reuses the Building Reflex
Jijibora's building reflex ("when a space entity's state changes, evaluate rules and actuate the next step") maps directly:
- Jijibora: drain/road segment state changes → page the right desk → open a case → PoCE record
- Hotel: room departure (occupancy lease ends) → create housekeeping task → assign attendant → cleaner works checklist → inspector signs off → room READY → PoCE record
Same engine, same reflex shape, different CNS type and lookup values.
6. Example — Group Procurement Reuses Record Federation
Jijibora's cross-org federation (cooperatives aggregating fertilizer demand) maps directly:
- Jijibora: Coop A + Coop B aggregate fertilizer → federated requisition → BBS+ quota signatures → shared PoCE escrow → release on delivery
- Hotel group: Property 1 + Property 2 aggregate F&B → federated requisition → BBS+ quota signatures (margins hidden) → shared PoCE escrow → release on multi-property delivery
Same engine, same federation, different domain.
7. Implementation Consequence
Because hotels reuse Jijibora infrastructure:
- Deployment: same
surreal importstrata order; no new schema deployments - Seeding: hotel CNS types + lookups added to
datasets/lookups/anddatasets/scenarios/; seeded viascripts/seed-nats-kv-declarative.mjs - Testing: same verify scripts (NATS judge + Surreal cross-checks); no new test surface
- Operations: same starter-pack bring-up, Soft-first, live-gate ritual
8. Positioning for Hotel Buyers
Tell a hotel: "You are not buying a hotel system. You are activating the same building-operations backbone that powers smart communities — rooms instead of parcels, housekeeping instead of waste rounds, F&B procurement instead of community sourcing — with the same audit, federation, and fail-closed guarantees."