Loading…
Open-Policy Exchange
~4 min to deploy
Hospitality & Travel Pack
Overbooking, rate-parity, and comp gates — stop oversold rooms, off-parity rates, and over-limit comps before a booking confirms.
For: Hotels, restaurants, OTAs, booking platforms
SOC 2 CC8.1PCI DSS 4.0Folio evidence trail
What it enforces
Overbooking Guard
Blocks a booking that would oversell the room-type inventory.
Rate-Parity Guard
Blocks published-rate overrides that breach a parity agreement.
Comp & Refund Ceiling
Holds comps or refunds above the folio limit for a manager approval key.
hospitality-travel-pack.yaml
# Hospitality & Travel Pack
# Fork: the three gates from the hospitality starter pack.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: hospitality-travel-pack
surface: sdk
policy_pack_id: hospitality
standards: [SOC2-CC8.1, PCI-DSS-4.0]
defaults:
mode: shadow
emit_dossier: true
rules:
- name: overbooking_guard
when: "action == 'booking.confirm'"
decision: |
BLOCK IF rooms_requested > rooms_available
ALLOW OTHERWISE
reason_code: room_type_oversold
- name: rate_parity_guard
when: "action == 'rate.publish'"
decision: |
BLOCK IF published_rate < parity_agreement.floor_rate
ESCALATE IF channel not in parity_agreement.channels
ALLOW OTHERWISE
reason_code: rate_breaches_parity
- name: comp_and_refund_ceiling
when: "action in ['folio.comp', 'folio.refund']"
decision: |
ESCALATE IF amount_usd > folio.comp_limit_usd
ALLOW OTHERWISE
reason_code: comp_over_folio_limit
Fork it, change the thresholds to match your environment, and deploy in shadow mode first — it defaults to listen-only so nothing in your live pipeline changes.
How to install it
Follow the install path for this surface, then paste the forked YAML as your policy config.
What to do next
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.