HOS Core 0.1
Tenant, Property, Unit, Maintenance window, Reservation, Stay, Task, Guest and Message; opaque identifiers, external references and the four-dimension Unit status model.
Documentation
Inspect the contract, its proof and its current limits.
Documentation is useful from the first public draft. Each item states exactly where it is in the work; unavailable material is not hidden behind a false link.
Published work
Status is part of the documentation.
Draft
HOS Events 0.1
Fifteen CloudEvents-compatible event types in five families, the envelope profile with time bases and actors, snapshots, and delivery, ordering and replay rules.
Event Producer manifest
A declaration of events, authority, snapshots, delivery, replay, retention and limitations, signed by its producer with a published key. Draft schema, signing rules and test vectors published.
Arrival conformance scenarios
Three synthetic scenarios, 42 deliveries: an early arrival to a room not yet released, an assigned room out of order, and a late check-out on a same-day turnover. They cover duplicates, out-of-order and late deliveries, conflicting and mirrored facts, snapshot recovery and a missing capability.
The hos command and the SDK
@hos-ai/cli and @hos-ai/sdk on npm, both alphas: validation, replay, the conformance scenarios for an implementation in any language, the producer check and signed manifests. Their documentation covers install, a ten-minute quickstart, seven guides, the references and troubleshooting.
HOS, HTNG and OpenTravel
What OpenTravel, HTNG and HOS each answer, the six answers HOS writes into the contract, how the three fit together, and where HOS is still behind. Sourced from the public specifications.
Mews mapping
Mews Connector API webhooks and fetched reservations and resources, mapped to HOS Events 0.1 by an unofficial adapter. It replays the arrival scenario to the same expected outcome, and has run read-only against Mews's two public demo enterprises: 3,485 facts, every one valid.
Apaleo mapping
Apaleo webhooks and fetched reservations and units, mapped to HOS Events 0.1 by an unofficial adapter. It replays the arrival scenario to the same expected outcome, and has run read-only against the five sample hotels of an Apaleo developer account: 740 facts, every one valid.
Cloudbeds mapping
Cloudbeds API v1.3 webhooks and fetched reservations and housekeeping status, mapped to HOS Events 0.1 by an unofficial adapter. It replays the arrival scenario to the same expected outcome; two webhook payloads are reconstructed. Its live check is ready but has not run on a real property yet.
Partner-backed and certified mappings
Partner-backed and certified are used only when the evidence exists. No mapping has reached either status.
Tools
Check your work from the command line.
Two npm packages carry the HOS 0.1 schemas and conformance scenarios. They are alphas, as HOS 0.1 is a draft. Passing the scenarios is a self-check, not a certification: no HOS certification exists yet.
@hos-ai/cli
The hos command validates HOS files, replays event streams, runs the conformance scenarios through an implementation in any language, checks what a producer publishes and signs producer manifests. It needs Node.js 22 or later, and works offline.
Terminal
npx @hos-ai/cli --version
npx @hos-ai/cli validate stay.expected.json
npx @hos-ai/cli conformance run --all --level normative --impl "python3 impl.py"
# On Windows, the Python launcher is py:
npx @hos-ai/cli conformance run --all --level normative --impl "py impl.py"@hos-ai/sdk
Types, validation, the HOS Events processing rules, facts with stable ids and signed manifests, for TypeScript in Node or in a browser. The arrival-readiness reference projection comes with it, marked non-normative.
TypeScript
npm install @hos-ai/sdk
import { validate } from "@hos-ai/sdk";
const { valid, errors } = validate(event);
if (!valid) console.log(errors);An implementation in another language gets its verdict through the conformance protocol. Stuck, or found a problem? Open an issue with synthetic data only.
Contribution surface