Hospitality Targeting — Sovereign OS for Hotels

Status: Document Set Index
Target Vertical: Hotels & Hospitality (independent properties, groups, managed portfolios)
Substrate: Sovereign OS / Community Weave Platform
Version: 1.0.0 | Date: 2026-11-09

Purpose

This document set describes how the Sovereign OS / Community Weave Platform infrastructure can target hotels. It is compiled entirely from existing work in the repository — playbooks, processes, integrations, architecture mandates, and canonical primitives — with zero bespoke tables, zero schema changes, and zero synthetic fallbacks.

Hotels are multi-system operations (reservations, housekeeping, maintenance, procurement, F&B, events, revenue, compliance, security) that today run on siloed point solutions. Sovereign OS replaces the silo stack with one declarative, auditable, integration-native state of record built on five canonical primitives (claim, truth_node, truth_edge, resource, resource_edge, integration_entity) and cryptographic Proof of Correct Execution (PoCE).

Document Set

#	Document	Audience	What it covers
00	EXECUTIVE-SUMMARY	Leadership, sales	Why hotels are a prime target; value proposition; positioning
01	ARCHITECTURE-MAPPING	Architects, CTOs	Hotel operations → canonical primitives; truth edges; multi-property; PoCE integration; honesty limits
02	PLAYBOOKS-FOR-HOTELS	Product, ops leads	10 hotel playbooks (H-1..H-10); flows, guard rails, evidence; authoring recipe
03	PROCESSES-AND-WORKFLOWS	Operations managers	The 8 canonical process families mapped to hotel functions
04	INTEGRATIONS-FOR-HOTELS	Integration engineers	PMS, ERPNext, OpenMAINT, Plane, Synapse, Fleetbase, MinIO, Gotenberg, Keycloak, Solver Gateway, NATS; SoR boundaries; fail-closed
05	POCE-AND-COMPLIANCE	Compliance, audit, risk	PoCE lifecycle; hotel trigger points; SoD & quorum; compliance gates (s350); federation (s184); scope governance (s142); claims we can/cannot make
06	SOURCING-AND-OPTIMIZATION	Revenue, procurement, housekeeping	Solver-gateway (`:3070`); machines propose/rules dispose; F&B basket split, housekeeping routing, maintenance dispatch; verdict contract; failure guards
07	UI-GUEST-EXPERIENCE	Product, frontend	Schema-driven UI; strict frontend rules; hotel component blueprints; real-time NATS streaming; honest states; branding
08	DEPLOYMENT-AND-STARTER-PACKS	IT, implementation	Soft-first rollout; starter packs; bring-up sequence; tech stack; phased rollout
09	GOVERNANCE-AND-FEDERATION	Hotel group leadership	Property-as-scope; APF; delegation & authority (s142); record federation (s184); BBS+ selective disclosure; community governance (s165)
A	CNS TYPES	Architects, implementers	Hotel CNS type hierarchy (claim, workflow, resource, truth node, edge types)
B	NATS KV LOOKUPS	Implementers	Declarative lookup keys; hotel-specific lookups to declare; declaration pattern
C	ROADMAP	Leadership, PMs	4-phase rollout; pilot→property→group→scale; success metrics; pilot kickoff questions

How to Read This Set

Start with 00 (Executive Summary) for the value proposition and positioning.
Architects should read 01 (Architecture Mapping) + appendices A & B (CNS types, lookups).
Product/ops leads should read 02 (Playbooks) + 03 (Processes).
Integration engineers should read 04 (Integrations) + 06 (Sourcing & Optimization).
Compliance/audit should read 05 (PoCE & Compliance) + 09 (Governance & Federation).
Frontend/product should read 07 (UI & Guest Experience).
Implementation/PM should read 08 (Deployment & Starter Packs) + appendix C (Roadmap).

Core Architectural Mandates (Applied Throughout)

Zero bespoke tables — all hotel entities map to claim, truth_node, truth_edge, resource, resource_edge, integration_entity. No room_reservation, housekeeping_task, guest_folio tables.
Declarative-first — business logic is config/lookup in NATS JetStream KV (SOVEREIGN_SCENARIOS, SOVEREIGN_LOOKUPS, SOVEREIGN_TEMPLATES), never filesystem reads at runtime and never hardcoded in code.
Fail closed — if an external peer (ERPNext, OpenMAINT, solver-gateway, PMS) is unavailable, the platform returns 502/503 with a typed error. No synthetic OPTIMAL, no dummy IDs, no mock fallback.
Zero synthetic adapter payloads — no dummy coordinates, dummy suppliers, hardcoded org IDs, or Array.from() fake routes.
Machines propose, rules dispose — sourcing/solving/optimization suggest; a named approver confirms via PoCE.
No hardcoded metrics — UI cards/dashboards render live data or honest skeleton/empty states; no fake 98.4% or 12 active rooms.
PoCE audit — every critical state transition produces a cryptographically verifiable receipt.

Next Steps

Read 00-EXECUTIVE-SUMMARY.md to confirm the value proposition fits your hotel group.
Run a pilot kickoff using the questions in appendix C (§7) and 05 (§9).
Select 3–5 first problems and a pilot property; begin with the Front Desk Desk and Housekeeping Desk starter packs in Soft mode.
Execute the live gate ritual to move packs from Soft to LIVE (see Deployment & Starter Packs — Hotel Rollout).