Appendix A — Hotel CNS Type Hierarchy
Status: Reference
Sources: D-06 — Ontology Pack for Developers, S-03 — Glossary (plain language),docs/cns/, Comprehensive Business Processes Specification
CNS (Canonical Naming System) URIs identify every hotel entity and claim type. CNS types are declarative (registered in cns_type_catalog), never invented in code.
1. Claim Types (cns://claim/type/hotel/...)
| CNS URI | Description | Traits | Primary Use |
|---|---|---|---|
cns://claim/type/hotel/reservation | Guest reservation / booking | [booking_confirmed, poce_governed] | Front desk reservation lifecycle (H-1) |
cns://claim/type/hotel/folio_line | Folio / invoice charge line | [charge_posted, poce_governed] | Folio line items, adjustments |
cns://claim/type/hotel/event | Function / banquet booking | [event_booked, deposit_required] | Events & banquets (H-5) |
cns://claim/type/hotel/incident | Security / safety incident | [incident_reported, escalated] | Incident & security reports (H-8) |
cns://claim/type/hotel/identity | Guest / staff identity record | [identity_verified, kyc] | Guest identity & access (H-10) |
cns://federation/procurement | Federated group requisition | [federated, escrow_governed] | Multi-property group procurement (H-9) |
cns://creative/mood_board | Event design board | [visual_assets_pinned, approval_required] | Event design (H-6) |
cns://collaboration/discussion | Staff discussion thread | [thread_active] | Staff communication (H-7) |
2. Workflow & Operation Types
| CNS URI | Description | Primary Use |
|---|---|---|
cns://workflow/task | Task / checklist item | Housekeeping, inspections, rounds (H-2) |
cns://workflow/requisition | Purchase requisition | F&B & procurement (H-4) |
cns://workflow/schedule | Schedule / booking | Reservations, function space, shifts (H-5/H-3) |
cns://operations/work_order | Maintenance work order | Engineering (H-3) |
cns://operations/incident | Operational incident | Fault intake (H-3/H-8) |
cns://knowledge/meeting_note | Meeting / decision record | BEOs, shift handovers (Process 4) |
3. Resource Types (cns://resource/...)
| CNS URI | Description | Primary Use |
|---|---|---|
cns://resource/room | Hotel room / unit | Occupancy, housekeeping, maintenance |
cns://resource/function_space | Banquet hall, boardroom | Event space booking |
cns://resource/equipment | AV, projector, laundry | Equipment reservation |
cns://resource/inventory | Linen, amenities, F&B stock | Procurement, par levels |
cns://resource/budget | Budget pool (cost center) | Threshold gating, spend control |
4. Truth Node Types (cns://truth/node/...)
| CNS URI | Description |
|---|---|
cns://truth/node/person | Guest or staff profile |
cns://truth/node/organization | Vendor, supplier, corporate client |
cns://truth/node/property | Hotel property (for group scope) |
5. Edge Types (truth_edge.edge_type)
| Edge Type | Semantics | Example |
|---|---|---|
occupies | guest → room (lease, time-bounded) | guest_G123 occupies room_405 |
has_claim | node → claim | guest_G123 has_claim reservation_RES-001 |
assigned_to | task → staff | housekeeping_HK-405 assigned_to attendant_9 |
services | task → room | housekeeping_HK-405 services room_405 |
maintains | work order → asset | workorder_WO-88 maintains asset_hvac_lobby |
charges_budget | claim → budget | requisition_REQ-77 charges_budget budget_fnb_q4 |
requires_gate | claim → approval gate | requisition_REQ-77 requires_gate approval_gate_tiered |
submitted_by | claim → person | requisition_REQ-77 submitted_by staff_procurement_3 |
bound_to | resource → lease | room_405 bound_to occupancy_lease_L1 |
6. Registration Pattern
Hotel CNS types are registered declaratively via fn::cns::register_type / fn::cns::register_entry (s185) or the playbook dictionary (dictionary.v1.json). Do not hardcode CNS URIs in application code — read them from governed NATS KV lookups at runtime.
Example registration shape (offline seed, not runtime):
json
{
"cns_type": "cns://claim/type/hotel/reservation",
"traits": ["booking_confirmed", "poce_governed"],
"schema_ref": "claims.hotel.reservation.v1",
"version": "1.0.0"
}