Hospitality Targeting — Executive Summary
Status: Strategic Positioning Document
Target Vertical: Hotels & Hospitality (independent properties, groups, and managed portfolios)
Substrate: Sovereign OS / Community Weave Platform (SurrealDB 3.0.5, NATS JetStream 2.10, Apache Camel:8181, Kestra:8180, PoCEs131-s150, Record Federations184)
Version: 1.0.0 | Date: 2026-11-09
Sources: Sovereign OS Playbook Architecture: Common Business Workflows, Playbook Engine Architecture & Runtime Execution Model,docs/platform-map/jijibora/, Integration Matrix & System Adapters Specification
1. Why Hotels Are a Prime Target for Our Infrastructure
A hotel is not a single application. It is a tightly coupled stack of operational systems that today live in silos:
| Hotel Function | Typical Silo Today | Our Canonical Replacement |
|---|---|---|
| Reservations & front desk | Property Management System (PMS) | claim + truth_edge (occupancy binding) |
| Housekeeping & room attendants | Task sheets / whiteboards | claim (task checklist) + PoCE sign-off |
| Engineering & maintenance | CMMS / spreadsheets | resource + OpenMAINT mediation |
| Procurement & F&B purchasing | Email + ERPNext fragments | claim (requisition) → ERPNext via Camel |
| Events & banquets | Contracts + mood boards | claim (event booking) + cns://creative/mood_board |
| Staff communication | WhatsApp groups | Synapse Matrix rooms ↔ cns://collaboration/discussion |
| Finance & folios | Accounting package | ERPNext SoR boundary (fiscal ledger) |
| Guest & staff identity | PMS logins / paper files | Keycloak + APF + BBS+ selective disclosure |
The opportunity: Hotels buy point solutions (PMS, RMS, CRS, CRM, POS, CMMS) that do not talk to each other, have no shared audit trail, and force staff to re-key data across systems. Sovereign OS replaces the silo stack with one declarative state of record built on five canonical primitives (claim, truth_node, truth_edge, resource, resource_edge, integration_entity), zero bespoke tables, and cryptographic Proof of Correct Execution (PoCE) for every state transition.
2. Core Value Proposition for Hotels
| Capability | What the hotel gains | Platform basis |
|---|---|---|
| Single source of truth | One record for a guest, room, asset, or requisition that every desk sees | claim + truth_node + integration_entity (Stratum 356) |
| Cryptographic audit | Every check-in, housekeeping sign-off, maintenance close, and PO approval is an immutable, verifiable PoCE receipt | s131-s150 PoCE sessions |
| Declarative playbooks, no new tables | New hotel SOPs (e.g., "turn-down service", "late checkout gate") are configured as lookups + scenario packs, never new SQL tables | SOVEREIGN_SCENARIOS / SOVEREIGN_LOOKUPS KV buckets |
| Fail-closed operations | If PMS, ERPNext, or the solver is unavailable, the platform refuses with a typed error — never invents a fake room assignment, rate, or "optimal" plan | Mandate 6 (zero silent fallbacks) |
| Cross-property federation | Hotel groups share procurement, staff, and vendor records across properties without merging databases | s184_record_federation + APF |
| Optimization that proposes, humans dispose | Housekeeping routes, procurement basket splits, and maintenance crew dispatch are suggested by the solver-gateway (:3070) and confirmed by a named approver | solver-gateway, procurement.basket_split@1, branch_and_bound |
3. Positioning Statement
Sovereign OS gives hotels a declarative, auditable, integration-native operations backbone that keeps existing frontends (PMS, POS, staff apps) as optional consumers while moving durable logic — identity, claims, leases, escrows, optimisation, event delivery — into headless engines. Hotels consume through REST, WebSocket, WhatsApp, or USSD without replacing their guest-facing UIs.
Entry point: Start with one problem (e.g., housekeeping sign-off or procurement approval) in Soft mode, then expand to the full hotel playbook catalog. No bespoke tables. No schema changes. No synthetic fallbacks.
4. Document Set Roadmap
| # | Document | Audience | Purpose |
|---|---|---|---|
| 01 | Architecture Mapping | Architects, CTOs | Map hotel operations to canonical primitives |
| 02 | Playbooks for Hotels | Product, Ops leads | Hotel-specific declarative playbooks |
| 03 | Processes & Workflows | Operations managers | Detailed process specs per hotel function |
| 04 | Integrations for Hotels | Integration engineers | PMS, ERPNext, OpenMAINT, Plane, Synapse, Fleetbase, etc. |
| 05 | PoCE & Compliance | Compliance, audit, risk | Cryptographic audit, SoD, health & safety gates |
| 06 | Sourcing & Optimization | Revenue, procurement, housekeeping leads | Solver-gateway use cases |
| 07 | UI & Guest Experience | Product, frontend | Schema-driven UI, honest states, branding |
| 08 | Deployment & Starter Packs | IT, implementation | Rollout, Soft mode, starter packs |
| 09 | Governance & Federation | Hotel group leadership | Multi-property governance, APF, federation |
| A | CNS Type Hierarchy | Architects, implementers | Hotel CNS URI registry |
| B | NATS KV Lookups | Implementers | Declarative lookup definitions |
| C | Implementation Roadmap | Leadership, PMs | Phased rollout plan |