# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T15:12:50Z", "synthesisSha256": "4320ed3a7a27cfd3602b0b5f276e7446959348f27e95aa0bd877456b4cee0acc", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ECO-023", "registryId": "vr.wm-eco-023", "name": "Reservation / Booking", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ECO.RSV" ], "tags": [ "reservation", "booking", "soc.eco.rsv" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-eco-023-reservation-booking/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-eco-023", "model": { "registry_id": "vr.wm-eco-023", "model_id": "WM-ECO-023", "name": "Reservation / Booking", "entry_kind": "aggregate", "purpose": "Represent one governed request, hold and confirmation lifecycle for scarce or scheduled capacity so agents can understand what is sought, for whom, from which provider, under which terms, at what time and place, and with what operational evidence without confusing the reservation with inventory, contract, order, ticket, payment or fulfilment.", "scope_statement": "Owns reservation identity, versions, profiles and lifecycle; requester, booker, provider, beneficiary, broker, payer and contact bindings; reserved subject and external offering, inventory, availability and capacity references; segments, sub-reservations, units, quantities, party composition, preferences, accessibility needs, alternatives and dependencies; rate, price, tax, deposit, guarantee, cancellation, change, no-show and refund policy references; external offer, contract, order, ticket, entitlement, invoice and payment bindings; request, hold, waitlist, confirmation, modification, rebooking, split, merge, transfer, cancellation, expiry, no-show, correction and dispute assertions; desired, offered, held, confirmed, service, cancellation, check-in, fulfilment, observation and knowledge times; locations, routes, check-in and fulfilment evidence; provenance, privacy, retention, validation and loss-aware projections. External party, offering, inventory, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain authoritative.", "in_scope": [ "Reservation identity, versions, profiles, parties, reserved subject, availability and capacity references, composition, quantities, preferences and dependencies", "Terms, guarantee and financial references, request, hold, confirmation, modification, cancellation, time, place, check-in and fulfilment evidence, governance, privacy, retention and projections" ], "out_of_scope": [ "Owning Party, Account, Offering, Product, Service, Resource, Inventory, Availability, Capacity Ledger, Schedule, Calendar Event, Location, Offer, Contract, Order, Ticket, Entitlement, Invoice, Payment, Check-in, Fulfilment or Records masters", "Treating requested, held, confirmed, paid, ticketed, checked-in, fulfilled, cancelled or expired status as universal proof of legal validity, capacity allocation, attendance, service completion, refund or release", "Autonomous scarce-capacity commitment, contract acceptance, charging, refunding, ticketing, transfer, cancellation, sensitive disclosure or physical record disposition" ], "boundary_notes": [ { "neighbor": "WM-ECO-006 Commercial Contract", "distinction": "The unfrozen parent agreement establishes obligations and legal terms. The reservation records capacity-seeking and booking lifecycle assertions and does not prove contract formation.", "source_refs": [ "SRC-003", "SRC-010", "SRC-011" ] }, { "neighbor": "Availability, inventory, capacity and allocation", "distinction": "Availability is an observation and inventory systems own pools, quotas, units and allocation. The reservation stores source-qualified bindings and observed hold or release results.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-008", "SRC-009" ] }, { "neighbor": "Appointment, calendar event and reserved service", "distinction": "An appointment or calendar event represents scheduled interaction and the service owns execution. The reservation owns booking intent, terms and confirmation bindings.", "source_refs": [ "SRC-004", "SRC-008", "SRC-012" ] }, { "neighbor": "Offer, contract, order, ticket, entitlement, invoice and payment", "distinction": "Each external commercial or fulfilment record has independent identity, state and authority; confirmation does not collapse or replace them.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ] }, { "neighbor": "UN/EDIFACT, Schema.org, IATA, TM Forum, EU law, RFC, PROV, ODRL, DQV, ISO 4217 and OpenAPI", "distinction": "Each representation has a distinct scope; every mapping is version-pinned, profile-qualified and loss-declaring.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ] }, "sources": [ { "id": "SRC-001", "title": "UN/EDIFACT Reservation request interactive message", "organization": "United Nations Economic Commission for Europe", "url": "https://service.unece.org/trade/untdid/d01c/timd/resreq_c.htm", "version_or_date": "UN/EDIFACT D.01C RESREQ", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines interactive travel, tourism and leisure reservation requests, originator, control references, units, services, dates, parties, payment and modification or cancellation actions." }, { "id": "SRC-002", "title": "UN/EDIFACT Reservation response interactive message", "organization": "United Nations Economic Commission for Europe", "url": "https://service.unece.org/trade/untdid/d98b/timd/resrsp_c.htm", "version_or_date": "UN/EDIFACT D.98B RESRSP revision 3", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines responses to initial, modification, cancellation and display requests and carries industry, originator and reservation-control context." }, { "id": "SRC-003", "title": "UN/EDIFACT Firm booking message", "organization": "United Nations Economic Commission for Europe", "url": "https://service.unece.org/trade/untdid/d09b/trmd/iftmbf_c.htm", "version_or_date": "UN/EDIFACT D.09B IFTMBF revision 11", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines a firm transport-service booking for one consignment and its conditions, parties, movement and transport requirements." }, { "id": "SRC-004", "title": "Reservation", "organization": "Schema.org Community Group", "url": "https://schema.org/Reservation", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines a generic reservation with identifier, status, booking and modification time, provider, beneficiary, reserved subject, ticket, price and broker." }, { "id": "SRC-005", "title": "ReservationStatusType", "organization": "Schema.org Community Group", "url": "https://schema.org/ReservationStatusType", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Provides pending, hold, confirmed and cancelled public reservation states." }, { "id": "SRC-006", "title": "ReservationPackage", "organization": "Schema.org Community Group", "url": "https://schema.org/ReservationPackage", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines a group of sub-reservations with common values and preserves child reservation identities." }, { "id": "SRC-007", "title": "Fulfilling with Orders: ONE Order Factsheet", "organization": "International Air Transport Association", "url": "https://www.iata.org/en/iata-repository/pressroom/fact-sheets/fact-sheet-one-order/", "version_or_date": "Factsheet accessed 6 September 2026", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Explains the airline transition from fragmented reservation, ticket and accounting records to an order while showing why reservation and order identities require explicit profiles and mappings." }, { "id": "SRC-008", "title": "Appointment Management API TMF646", "organization": "TM Forum", "url": "https://www.tmforum.org/open-digital-architecture/open-apis/TMF646", "version_or_date": "TMF646 v4.0 directory entry, release 1 July 2021, page update 7 November 2024", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines free-slot search and appointment creation with nature and place, useful for the appointment profile while appointment execution remains external." }, { "id": "SRC-009", "title": "Open API Directory", "organization": "TM Forum", "url": "https://www.tmforum.org/open-digital-architecture/open-apis", "version_or_date": "Directory accessed 6 September 2026; includes TMF716 v4 Resource Reservation", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Registers appointment, resource reservation, catalog, inventory, order, payment, privacy and related API boundaries." }, { "id": "SRC-010", "title": "Directive EU 2015/2302 on package travel and linked travel arrangements", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/dir/2015/2302/oj", "version_or_date": "Official Journal text 25 November 2015; amendments and national transposition remain profile-specific", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines booking-process, pre-contract information, confirmation, transfer, alteration, termination, assistance and linked-arrangement duties in EU package-travel scope." }, { "id": "SRC-011", "title": "Directive 2011/83/EU on consumer rights", "organization": "European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32011L0083", "version_or_date": "Consolidated context current at access; national implementation remains profile-specific", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines distance-contract information, payment, performance and withdrawal rules plus scoped exclusions for dated accommodation, transport, car rental, catering and leisure services." }, { "id": "SRC-012", "title": "Internet Calendaring and Scheduling Core Object Specification", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc5545.html", "version_or_date": "RFC 5545 September 2009", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines events, start, end, duration, recurrence, timezone, status and scheduling identifiers for calendar projections." }, { "id": "SRC-013", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339 July 2002, updated by RFC 9557", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines interoperable timestamps with seconds and explicit UTC relationship." }, { "id": "SRC-014", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines entities, activities, agents, attribution, generation, derivation, revision and qualified provenance." }, { "id": "SRC-015", "title": "ODRL Information Model 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "W3C Recommendation 15 February 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines policy offers, agreements, parties, assets, permissions, prohibitions, duties and constraints for policy projection." }, { "id": "SRC-016", "title": "Data on the Web Best Practices: Data Quality Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-dqv/", "version_or_date": "W3C Working Group Note 15 December 2016", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines quality dimensions, metrics, measurements, annotations, policies and certificates." }, { "id": "SRC-017", "title": "Global Financial Data Standards: ISO 4217 Currency Codes", "organization": "SIX Financial Information", "url": "https://www.six-group.com/en/products-services/financial-information/market-reference-data/data-standards.html", "version_or_date": "ISO 4217 Maintenance Agency lists current at access", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Provides maintained currency identifiers and minor units for quoted prices, deposits, fees, charges and refunds." }, { "id": "SRC-018", "title": "OpenAPI Specification 3.1.1", "organization": "OpenAPI Initiative", "url": "https://spec.openapis.org/oas/v3.1.1.html", "version_or_date": "Version 3.1.1, 24 October 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:08:00Z", "relevance": "Defines HTTP API operations, schemas, responses, security and reusable components for reservation service projections." } ], "structure": { "bundles": [ { "id": "identity-intent-parties-and-authority", "name": "Identity, intent, parties and authority", "description": "Groups reservation context for identity, intent, parties and authority.", "rationale": "Identify the reservation and its intent without absorbing party, offering or contract masters", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-010", "SRC-011", "SRC-014" ], "layers": [ { "id": "reservation-root-identity-version-profile-and-status", "name": "Reservation root identity, version, profile and status", "description": "Groups source-qualified reservation context for reservation root identity, version, profile and status.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-014" ], "findings": [ { "id": "reservation-id-version-head-alias-profile-status-and-master-system", "name": "Reservation ID, version head, alias, profile, status and master system", "description": "Records reservation id, version head, alias, profile, status and master system as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-014" ], "questions": [ { "id": "reservation-id-version-head-alias-profile-status-and-master-system-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish reservation id, version head, alias, profile, status and master system?", "kind": "identity", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "reservation-id-version-head-alias-profile-status-and-master-system-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on reservation id, version head, alias, profile, status and master system, for which purpose and under what authority?", "kind": "authority", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "reservation-id-version-head-alias-profile-status-and-master-system-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify reservation id, version head, alias, profile, status and master system?", "kind": "security", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "reservation-id-version-head-alias-profile-status-and-master-system-data", "name": "Reservation ID, version head, alias, profile, status and master system data", "description": "Typed reservation data for reservation id, version head, alias, profile, status and master system, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-014" ] } ], "artifacts": [ { "id": "reservation-id-version-head-alias-profile-status-and-master-system-record", "name": "Reservation ID, version head, alias, profile, status and master system record", "description": "Immutable or successor-versioned reservation evidence for reservation id, version head, alias, profile, status and master system.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for reservation-id-version-head-alias-profile-status-and-master-system; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "requested-held-confirmed-waitlisted-cancelled-expired-noshow-and-disputed-classification", "name": "Requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification", "description": "Records requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-014" ], "questions": [ { "id": "requested-held-confirmed-waitlisted-cancelled-expired-noshow-and-disputed-classification-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification?", "kind": "classification", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "requested-held-confirmed-waitlisted-cancelled-expired-noshow-and-disputed-classification-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification, for which purpose and under what authority?", "kind": "requirement", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "requested-held-confirmed-waitlisted-cancelled-expired-noshow-and-disputed-classification-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification?", "kind": "privacy", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "requested-held-confirmed-waitlisted-cancelled-expired-noshow-and-disputed-classification-data", "name": "Requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification data", "description": "Typed reservation data for requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-014" ] } ], "artifacts": [ { "id": "requested-held-confirmed-waitlisted-cancelled-expired-noshow-and-disputed-classification-record", "name": "Requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification record", "description": "Immutable or successor-versioned reservation evidence for requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for requested-held-confirmed-waitlisted-cancelled-expired-noshow-and-disputed-classification; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-014" ] } ], "inline_only_rationale": null } ] }, { "id": "purpose-parties-roles-contact-and-authority", "name": "Purpose, parties, roles, contact and authority", "description": "Groups source-qualified reservation context for purpose, parties, roles, contact and authority.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014" ], "findings": [ { "id": "requester-booker-holder-beneficiary-provider-broker-payer-contact-and-operator-role", "name": "Requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role", "description": "Records requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014" ], "questions": [ { "id": "requester-booker-holder-beneficiary-provider-broker-payer-contact-and-operator-role-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role?", "kind": "relationship", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "requester-booker-holder-beneficiary-provider-broker-payer-contact-and-operator-role-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role, for which purpose and under what authority?", "kind": "constraint", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "requester-booker-holder-beneficiary-provider-broker-payer-contact-and-operator-role-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role?", "kind": "retention", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "requester-booker-holder-beneficiary-provider-broker-payer-contact-and-operator-role-data", "name": "Requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role data", "description": "Typed reservation data for requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014" ] } ], "artifacts": [ { "id": "requester-booker-holder-beneficiary-provider-broker-payer-contact-and-operator-role-record", "name": "Requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role record", "description": "Immutable or successor-versioned reservation evidence for requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for requester-booker-holder-beneficiary-provider-broker-payer-contact-and-operator-role; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "purpose-authorization-delegation-consent-acknowledgement-reliance-and-restriction", "name": "Purpose, authorization, delegation, consent, acknowledgement, reliance and restriction", "description": "Records purpose, authorization, delegation, consent, acknowledgement, reliance and restriction as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014" ], "questions": [ { "id": "purpose-authorization-delegation-consent-acknowledgement-reliance-and-restriction-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish purpose, authorization, delegation, consent, acknowledgement, reliance and restriction?", "kind": "authority", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "purpose-authorization-delegation-consent-acknowledgement-reliance-and-restriction-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on purpose, authorization, delegation, consent, acknowledgement, reliance and restriction, for which purpose and under what authority?", "kind": "process", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "purpose-authorization-delegation-consent-acknowledgement-reliance-and-restriction-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify purpose, authorization, delegation, consent, acknowledgement, reliance and restriction?", "kind": "access", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "purpose-authorization-delegation-consent-acknowledgement-reliance-and-restriction-data", "name": "Purpose, authorization, delegation, consent, acknowledgement, reliance and restriction data", "description": "Typed reservation data for purpose, authorization, delegation, consent, acknowledgement, reliance and restriction, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014" ] } ], "artifacts": [ { "id": "purpose-authorization-delegation-consent-acknowledgement-reliance-and-restriction-record", "name": "Purpose, authorization, delegation, consent, acknowledgement, reliance and restriction record", "description": "Immutable or successor-versioned reservation evidence for purpose, authorization, delegation, consent, acknowledgement, reliance and restriction.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for purpose-authorization-delegation-consent-acknowledgement-reliance-and-restriction; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "availability-capacity-composition-and-preferences", "name": "Availability, capacity, composition and preferences", "description": "Groups reservation context for availability, capacity, composition and preferences.", "rationale": "Represent what is sought and held while external inventory remains authoritative", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-009" ], "layers": [ { "id": "availability-offering-slot-capacity-and-allocation", "name": "Availability, offering, slot, capacity and allocation", "description": "Groups source-qualified reservation context for availability, offering, slot, capacity and allocation.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-009" ], "findings": [ { "id": "availability-query-observation-offering-resource-slot-class-channel-and-source", "name": "Availability query, observation, offering, resource, slot, class, channel and source", "description": "Records availability query, observation, offering, resource, slot, class, channel and source as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-009" ], "questions": [ { "id": "availability-query-observation-offering-resource-slot-class-channel-and-source-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish availability query, observation, offering, resource, slot, class, channel and source?", "kind": "measurement", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "availability-query-observation-offering-resource-slot-class-channel-and-source-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on availability query, observation, offering, resource, slot, class, channel and source, for which purpose and under what authority?", "kind": "event", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "availability-query-observation-offering-resource-slot-class-channel-and-source-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify availability query, observation, offering, resource, slot, class, channel and source?", "kind": "exception", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "availability-query-observation-offering-resource-slot-class-channel-and-source-data", "name": "Availability query, observation, offering, resource, slot, class, channel and source data", "description": "Typed reservation data for availability query, observation, offering, resource, slot, class, channel and source, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "availability-query-observation-offering-resource-slot-class-channel-and-source-record", "name": "Availability query, observation, offering, resource, slot, class, channel and source record", "description": "Immutable or successor-versioned reservation evidence for availability query, observation, offering, resource, slot, class, channel and source.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for availability-query-observation-offering-resource-slot-class-channel-and-source; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "inventory-pool-quota-capacity-unit-hold-allocation-guarantee-overbooking-and-release", "name": "Inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release", "description": "Records inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-009" ], "questions": [ { "id": "inventory-pool-quota-capacity-unit-hold-allocation-guarantee-overbooking-and-release-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release?", "kind": "constraint", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "inventory-pool-quota-capacity-unit-hold-allocation-guarantee-overbooking-and-release-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release, for which purpose and under what authority?", "kind": "measurement", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "inventory-pool-quota-capacity-unit-hold-allocation-guarantee-overbooking-and-release-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release?", "kind": "interoperability", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "inventory-pool-quota-capacity-unit-hold-allocation-guarantee-overbooking-and-release-data", "name": "Inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release data", "description": "Typed reservation data for inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "inventory-pool-quota-capacity-unit-hold-allocation-guarantee-overbooking-and-release-record", "name": "Inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release record", "description": "Immutable or successor-versioned reservation evidence for inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for inventory-pool-quota-capacity-unit-hold-allocation-guarantee-overbooking-and-release; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "segments-units-party-composition-preferences-and-dependencies", "name": "Segments, units, party composition, preferences and dependencies", "description": "Groups source-qualified reservation context for segments, units, party composition, preferences and dependencies.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-008" ], "findings": [ { "id": "segment-leg-stay-session-subevent-subreservation-package-sequence-and-link", "name": "Segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link", "description": "Records segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-008" ], "questions": [ { "id": "segment-leg-stay-session-subevent-subreservation-package-sequence-and-link-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link?", "kind": "composition", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "segment-leg-stay-session-subevent-subreservation-package-sequence-and-link-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link, for which purpose and under what authority?", "kind": "evidence", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "segment-leg-stay-session-subevent-subreservation-package-sequence-and-link-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link?", "kind": "decision", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "segment-leg-stay-session-subevent-subreservation-package-sequence-and-link-data", "name": "Segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link data", "description": "Typed reservation data for segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "segment-leg-stay-session-subevent-subreservation-package-sequence-and-link-record", "name": "Segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link record", "description": "Immutable or successor-versioned reservation evidence for segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for segment-leg-stay-session-subevent-subreservation-package-sequence-and-link; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "quantity-party-composition-seat-room-table-slot-accessibility-preference-alternative-and-dependency", "name": "Quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency", "description": "Records quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-008" ], "questions": [ { "id": "quantity-party-composition-seat-room-table-slot-accessibility-preference-alternative-and-dependency-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency?", "kind": "composition", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "quantity-party-composition-seat-room-table-slot-accessibility-preference-alternative-and-dependency-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency, for which purpose and under what authority?", "kind": "quality", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "quantity-party-composition-seat-room-table-slot-accessibility-preference-alternative-and-dependency-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency?", "kind": "identity", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "quantity-party-composition-seat-room-table-slot-accessibility-preference-alternative-and-dependency-data", "name": "Quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency data", "description": "Typed reservation data for quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "quantity-party-composition-seat-room-table-slot-accessibility-preference-alternative-and-dependency-record", "name": "Quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency record", "description": "Immutable or successor-versioned reservation evidence for quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for quantity-party-composition-seat-room-table-slot-accessibility-preference-alternative-and-dependency; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "terms-economics-guarantees-and-external-commerce", "name": "Terms, economics, guarantees and external commerce", "description": "Groups reservation context for terms, economics, guarantees and external commerce.", "rationale": "Preserve reservation-specific terms while offers, contracts, orders, tickets and payments keep independent identity", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-015", "SRC-017" ], "layers": [ { "id": "rate-price-tax-deposit-guarantee-and-charge-policy", "name": "Rate, price, tax, deposit, guarantee and charge policy", "description": "Groups source-qualified reservation context for rate, price, tax, deposit, guarantee and charge policy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-015", "SRC-017" ], "findings": [ { "id": "rate-plan-quoted-price-currency-tax-fee-discount-validity-and-source", "name": "Rate plan, quoted price, currency, tax, fee, discount, validity and source", "description": "Records rate plan, quoted price, currency, tax, fee, discount, validity and source as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-015", "SRC-017" ], "questions": [ { "id": "rate-plan-quoted-price-currency-tax-fee-discount-validity-and-source-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish rate plan, quoted price, currency, tax, fee, discount, validity and source?", "kind": "measurement", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "rate-plan-quoted-price-currency-tax-fee-discount-validity-and-source-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on rate plan, quoted price, currency, tax, fee, discount, validity and source, for which purpose and under what authority?", "kind": "validation", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "rate-plan-quoted-price-currency-tax-fee-discount-validity-and-source-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify rate plan, quoted price, currency, tax, fee, discount, validity and source?", "kind": "classification", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "rate-plan-quoted-price-currency-tax-fee-discount-validity-and-source-data", "name": "Rate plan, quoted price, currency, tax, fee, discount, validity and source data", "description": "Typed reservation data for rate plan, quoted price, currency, tax, fee, discount, validity and source, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-015", "SRC-017" ] } ], "artifacts": [ { "id": "rate-plan-quoted-price-currency-tax-fee-discount-validity-and-source-record", "name": "Rate plan, quoted price, currency, tax, fee, discount, validity and source record", "description": "Immutable or successor-versioned reservation evidence for rate plan, quoted price, currency, tax, fee, discount, validity and source.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for rate-plan-quoted-price-currency-tax-fee-discount-validity-and-source; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-015", "SRC-017" ] } ], "inline_only_rationale": null }, { "id": "deposit-payment-guarantee-cancellation-noshow-change-refund-and-penalty-policy", "name": "Deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy", "description": "Records deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-015", "SRC-017" ], "questions": [ { "id": "deposit-payment-guarantee-cancellation-noshow-change-refund-and-penalty-policy-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy?", "kind": "requirement", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "deposit-payment-guarantee-cancellation-noshow-change-refund-and-penalty-policy-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy, for which purpose and under what authority?", "kind": "security", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "deposit-payment-guarantee-cancellation-noshow-change-refund-and-penalty-policy-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy?", "kind": "composition", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "deposit-payment-guarantee-cancellation-noshow-change-refund-and-penalty-policy-data", "name": "Deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy data", "description": "Typed reservation data for deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-015", "SRC-017" ] } ], "artifacts": [ { "id": "deposit-payment-guarantee-cancellation-noshow-change-refund-and-penalty-policy-record", "name": "Deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy record", "description": "Immutable or successor-versioned reservation evidence for deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for deposit-payment-guarantee-cancellation-noshow-change-refund-and-penalty-policy; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-015", "SRC-017" ] } ], "inline_only_rationale": null } ] }, { "id": "offer-contract-order-ticket-payment-and-eligibility-bindings", "name": "Offer, contract, order, ticket, payment and eligibility bindings", "description": "Groups source-qualified reservation context for offer, contract, order, ticket, payment and eligibility bindings.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ], "findings": [ { "id": "offer-quote-contract-order-ticket-entitlement-invoice-payment-and-refund-reference", "name": "Offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference", "description": "Records offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "offer-quote-contract-order-ticket-entitlement-invoice-payment-and-refund-reference-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference?", "kind": "relationship", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "offer-quote-contract-order-ticket-entitlement-invoice-payment-and-refund-reference-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference, for which purpose and under what authority?", "kind": "privacy", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "offer-quote-contract-order-ticket-entitlement-invoice-payment-and-refund-reference-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference?", "kind": "relationship", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "offer-quote-contract-order-ticket-entitlement-invoice-payment-and-refund-reference-data", "name": "Offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference data", "description": "Typed reservation data for offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "offer-quote-contract-order-ticket-entitlement-invoice-payment-and-refund-reference-record", "name": "Offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference record", "description": "Immutable or successor-versioned reservation evidence for offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for offer-quote-contract-order-ticket-entitlement-invoice-payment-and-refund-reference; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "eligibility-identity-document-membership-loyalty-voucher-promotion-and-verification", "name": "Eligibility, identity document, membership, loyalty, voucher, promotion and verification", "description": "Records eligibility, identity document, membership, loyalty, voucher, promotion and verification as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "eligibility-identity-document-membership-loyalty-voucher-promotion-and-verification-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish eligibility, identity document, membership, loyalty, voucher, promotion and verification?", "kind": "validation", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "eligibility-identity-document-membership-loyalty-voucher-promotion-and-verification-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on eligibility, identity document, membership, loyalty, voucher, promotion and verification, for which purpose and under what authority?", "kind": "retention", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "eligibility-identity-document-membership-loyalty-voucher-promotion-and-verification-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify eligibility, identity document, membership, loyalty, voucher, promotion and verification?", "kind": "state", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "eligibility-identity-document-membership-loyalty-voucher-promotion-and-verification-data", "name": "Eligibility, identity document, membership, loyalty, voucher, promotion and verification data", "description": "Typed reservation data for eligibility, identity document, membership, loyalty, voucher, promotion and verification, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "eligibility-identity-document-membership-loyalty-voucher-promotion-and-verification-record", "name": "Eligibility, identity document, membership, loyalty, voucher, promotion and verification record", "description": "Immutable or successor-versioned reservation evidence for eligibility, identity document, membership, loyalty, voucher, promotion and verification.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for eligibility-identity-document-membership-loyalty-voucher-promotion-and-verification; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "request-hold-confirmation-change-and-cancellation", "name": "Request, hold, confirmation, change and cancellation", "description": "Groups reservation context for request, hold, confirmation, change and cancellation.", "rationale": "Model the reservation lifecycle without treating messages or financial events as equivalent states", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-014" ], "layers": [ { "id": "request-response-hold-waitlist-confirmation-and-state-axes", "name": "Request, response, hold, waitlist, confirmation and state axes", "description": "Groups source-qualified reservation context for request, response, hold, waitlist, confirmation and state axes.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009" ], "findings": [ { "id": "request-action-correlation-response-decision-reason-confirmation-code-and-evidence", "name": "Request action, correlation, response, decision, reason, confirmation code and evidence", "description": "Records request action, correlation, response, decision, reason, confirmation code and evidence as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009" ], "questions": [ { "id": "request-action-correlation-response-decision-reason-confirmation-code-and-evidence-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish request action, correlation, response, decision, reason, confirmation code and evidence?", "kind": "process", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "request-action-correlation-response-decision-reason-confirmation-code-and-evidence-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on request action, correlation, response, decision, reason, confirmation code and evidence, for which purpose and under what authority?", "kind": "access", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "request-action-correlation-response-decision-reason-confirmation-code-and-evidence-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify request action, correlation, response, decision, reason, confirmation code and evidence?", "kind": "lifecycle", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "request-action-correlation-response-decision-reason-confirmation-code-and-evidence-data", "name": "Request action, correlation, response, decision, reason, confirmation code and evidence data", "description": "Typed reservation data for request action, correlation, response, decision, reason, confirmation code and evidence, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "request-action-correlation-response-decision-reason-confirmation-code-and-evidence-record", "name": "Request action, correlation, response, decision, reason, confirmation code and evidence record", "description": "Immutable or successor-versioned reservation evidence for request action, correlation, response, decision, reason, confirmation code and evidence.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for request-action-correlation-response-decision-reason-confirmation-code-and-evidence; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "commercial-capacity-hold-booking-payment-ticket-checkin-and-fulfilment-state-axis", "name": "Commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis", "description": "Records commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009" ], "questions": [ { "id": "commercial-capacity-hold-booking-payment-ticket-checkin-and-fulfilment-state-axis-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis?", "kind": "state", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "commercial-capacity-hold-booking-payment-ticket-checkin-and-fulfilment-state-axis-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis, for which purpose and under what authority?", "kind": "exception", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "commercial-capacity-hold-booking-payment-ticket-checkin-and-fulfilment-state-axis-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis?", "kind": "temporal", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "commercial-capacity-hold-booking-payment-ticket-checkin-and-fulfilment-state-axis-data", "name": "Commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis data", "description": "Typed reservation data for commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "commercial-capacity-hold-booking-payment-ticket-checkin-and-fulfilment-state-axis-record", "name": "Commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis record", "description": "Immutable or successor-versioned reservation evidence for commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for commercial-capacity-hold-booking-payment-ticket-checkin-and-fulfilment-state-axis; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "modify-rebook-split-merge-transfer-cancel-expire-and-release", "name": "Modify, rebook, split, merge, transfer, cancel, expire and release", "description": "Groups source-qualified reservation context for modify, rebook, split, merge, transfer, cancel, expire and release.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-011", "SRC-014" ], "findings": [ { "id": "modification-rebook-substitution-upgrade-downgrade-split-merge-transfer-and-successor", "name": "Modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor", "description": "Records modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-011", "SRC-014" ], "questions": [ { "id": "modification-rebook-substitution-upgrade-downgrade-split-merge-transfer-and-successor-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor?", "kind": "lifecycle", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "modification-rebook-substitution-upgrade-downgrade-split-merge-transfer-and-successor-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor, for which purpose and under what authority?", "kind": "interoperability", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "modification-rebook-substitution-upgrade-downgrade-split-merge-transfer-and-successor-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor?", "kind": "spatial", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "modification-rebook-substitution-upgrade-downgrade-split-merge-transfer-and-successor-data", "name": "Modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor data", "description": "Typed reservation data for modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-011", "SRC-014" ] } ], "artifacts": [ { "id": "modification-rebook-substitution-upgrade-downgrade-split-merge-transfer-and-successor-record", "name": "Modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor record", "description": "Immutable or successor-versioned reservation evidence for modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for modification-rebook-substitution-upgrade-downgrade-split-merge-transfer-and-successor; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-011", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "cancel-request-cancel-effective-expiry-noshow-release-refund-dispute-and-correction", "name": "Cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction", "description": "Records cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-011", "SRC-014" ], "questions": [ { "id": "cancel-request-cancel-effective-expiry-noshow-release-refund-dispute-and-correction-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction?", "kind": "event", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "cancel-request-cancel-effective-expiry-noshow-release-refund-dispute-and-correction-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction, for which purpose and under what authority?", "kind": "decision", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "cancel-request-cancel-effective-expiry-noshow-release-refund-dispute-and-correction-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction?", "kind": "provenance", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "cancel-request-cancel-effective-expiry-noshow-release-refund-dispute-and-correction-data", "name": "Cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction data", "description": "Typed reservation data for cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-011", "SRC-014" ] } ], "artifacts": [ { "id": "cancel-request-cancel-effective-expiry-noshow-release-refund-dispute-and-correction-record", "name": "Cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction record", "description": "Immutable or successor-versioned reservation evidence for cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for cancel-request-cancel-effective-expiry-noshow-release-refund-dispute-and-correction; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-011", "SRC-014" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "time-place-checkin-fulfilment-and-outcome", "name": "Time, place, check-in, fulfilment and outcome", "description": "Groups reservation context for time, place, check-in, fulfilment and outcome.", "rationale": "Keep intended schedule and location separate from actual arrival, admission and service evidence", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-016" ], "layers": [ { "id": "schedule-timezone-location-route-and-cutoffs", "name": "Schedule, timezone, location, route and cutoffs", "description": "Groups source-qualified reservation context for schedule, timezone, location, route and cutoffs.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-012", "SRC-013" ], "findings": [ { "id": "desired-offered-held-confirmed-start-end-duration-recurrence-timezone-and-exception", "name": "Desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception", "description": "Records desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-012", "SRC-013" ], "questions": [ { "id": "desired-offered-held-confirmed-start-end-duration-recurrence-timezone-and-exception-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception?", "kind": "temporal", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "desired-offered-held-confirmed-start-end-duration-recurrence-timezone-and-exception-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception, for which purpose and under what authority?", "kind": "identity", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "desired-offered-held-confirmed-start-end-duration-recurrence-timezone-and-exception-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception?", "kind": "ownership", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "desired-offered-held-confirmed-start-end-duration-recurrence-timezone-and-exception-data", "name": "Desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception data", "description": "Typed reservation data for desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "desired-offered-held-confirmed-start-end-duration-recurrence-timezone-and-exception-record", "name": "Desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception record", "description": "Immutable or successor-versioned reservation evidence for desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for desired-offered-held-confirmed-start-end-duration-recurrence-timezone-and-exception; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "origin-destination-venue-place-resource-position-route-zone-and-jurisdiction-reference", "name": "Origin, destination, venue, place, resource position, route, zone and jurisdiction reference", "description": "Records origin, destination, venue, place, resource position, route, zone and jurisdiction reference as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-012", "SRC-013" ], "questions": [ { "id": "origin-destination-venue-place-resource-position-route-zone-and-jurisdiction-reference-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish origin, destination, venue, place, resource position, route, zone and jurisdiction reference?", "kind": "spatial", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "origin-destination-venue-place-resource-position-route-zone-and-jurisdiction-reference-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on origin, destination, venue, place, resource position, route, zone and jurisdiction reference, for which purpose and under what authority?", "kind": "classification", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "origin-destination-venue-place-resource-position-route-zone-and-jurisdiction-reference-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify origin, destination, venue, place, resource position, route, zone and jurisdiction reference?", "kind": "authority", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "origin-destination-venue-place-resource-position-route-zone-and-jurisdiction-reference-data", "name": "Origin, destination, venue, place, resource position, route, zone and jurisdiction reference data", "description": "Typed reservation data for origin, destination, venue, place, resource position, route, zone and jurisdiction reference, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "origin-destination-venue-place-resource-position-route-zone-and-jurisdiction-reference-record", "name": "Origin, destination, venue, place, resource position, route, zone and jurisdiction reference record", "description": "Immutable or successor-versioned reservation evidence for origin, destination, venue, place, resource position, route, zone and jurisdiction reference.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for origin-destination-venue-place-resource-position-route-zone-and-jurisdiction-reference; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "arrival-checkin-admission-handover-fulfilment-noshow-and-outcome", "name": "Arrival, check-in, admission, handover, fulfilment, no-show and outcome", "description": "Groups source-qualified reservation context for arrival, check-in, admission, handover, fulfilment, no-show and outcome.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-010", "SRC-014", "SRC-016" ], "findings": [ { "id": "arrival-checkin-identity-check-admission-boarding-pickup-handover-and-attendance-reference", "name": "Arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference", "description": "Records arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-010", "SRC-014", "SRC-016" ], "questions": [ { "id": "arrival-checkin-identity-check-admission-boarding-pickup-handover-and-attendance-reference-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference?", "kind": "event", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "arrival-checkin-identity-check-admission-boarding-pickup-handover-and-attendance-reference-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference, for which purpose and under what authority?", "kind": "composition", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "arrival-checkin-identity-check-admission-boarding-pickup-handover-and-attendance-reference-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference?", "kind": "requirement", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "arrival-checkin-identity-check-admission-boarding-pickup-handover-and-attendance-reference-data", "name": "Arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference data", "description": "Typed reservation data for arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-010", "SRC-014", "SRC-016" ] } ], "artifacts": [ { "id": "arrival-checkin-identity-check-admission-boarding-pickup-handover-and-attendance-reference-record", "name": "Arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference record", "description": "Immutable or successor-versioned reservation evidence for arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for arrival-checkin-identity-check-admission-boarding-pickup-handover-and-attendance-reference; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-010", "SRC-014", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "service-start-completion-partial-fulfilment-noshow-failure-complaint-remedy-and-evidence", "name": "Service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence", "description": "Records service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-010", "SRC-014", "SRC-016" ], "questions": [ { "id": "service-start-completion-partial-fulfilment-noshow-failure-complaint-remedy-and-evidence-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence?", "kind": "evidence", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "service-start-completion-partial-fulfilment-noshow-failure-complaint-remedy-and-evidence-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence, for which purpose and under what authority?", "kind": "relationship", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "service-start-completion-partial-fulfilment-noshow-failure-complaint-remedy-and-evidence-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence?", "kind": "constraint", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "service-start-completion-partial-fulfilment-noshow-failure-complaint-remedy-and-evidence-data", "name": "Service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence data", "description": "Typed reservation data for service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-010", "SRC-014", "SRC-016" ] } ], "artifacts": [ { "id": "service-start-completion-partial-fulfilment-noshow-failure-complaint-remedy-and-evidence-record", "name": "Service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence record", "description": "Immutable or successor-versioned reservation evidence for service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for service-start-completion-partial-fulfilment-noshow-failure-complaint-remedy-and-evidence; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-010", "SRC-014", "SRC-016" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-provenance-privacy-validation-and-interoperability", "name": "Governance, provenance, privacy, validation and interoperability", "description": "Groups reservation context for governance, provenance, privacy, validation and interoperability.", "rationale": "Preserve authority, history, access and loss-aware projections across reservation domains", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "layers": [ { "id": "ownership-source-revision-access-privacy-and-retention", "name": "Ownership, source, revision, access, privacy and retention", "description": "Groups source-qualified reservation context for ownership, source, revision, access, privacy and retention.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014", "SRC-016" ], "findings": [ { "id": "owner-steward-source-system-channel-actor-derivation-revision-conflict-and-audit", "name": "Owner, steward, source system, channel, actor, derivation, revision, conflict and audit", "description": "Records owner, steward, source system, channel, actor, derivation, revision, conflict and audit as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014", "SRC-016" ], "questions": [ { "id": "owner-steward-source-system-channel-actor-derivation-revision-conflict-and-audit-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish owner, steward, source system, channel, actor, derivation, revision, conflict and audit?", "kind": "provenance", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "owner-steward-source-system-channel-actor-derivation-revision-conflict-and-audit-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on owner, steward, source system, channel, actor, derivation, revision, conflict and audit, for which purpose and under what authority?", "kind": "state", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "owner-steward-source-system-channel-actor-derivation-revision-conflict-and-audit-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify owner, steward, source system, channel, actor, derivation, revision, conflict and audit?", "kind": "process", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "owner-steward-source-system-channel-actor-derivation-revision-conflict-and-audit-data", "name": "Owner, steward, source system, channel, actor, derivation, revision, conflict and audit data", "description": "Typed reservation data for owner, steward, source system, channel, actor, derivation, revision, conflict and audit, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014", "SRC-016" ] } ], "artifacts": [ { "id": "owner-steward-source-system-channel-actor-derivation-revision-conflict-and-audit-record", "name": "Owner, steward, source system, channel, actor, derivation, revision, conflict and audit record", "description": "Immutable or successor-versioned reservation evidence for owner, steward, source system, channel, actor, derivation, revision, conflict and audit.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for owner-steward-source-system-channel-actor-derivation-revision-conflict-and-audit; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "purpose-contact-itinerary-access-confidentiality-disclosure-retention-legalhold-and-tombstone", "name": "Purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone", "description": "Records purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014", "SRC-016" ], "questions": [ { "id": "purpose-contact-itinerary-access-confidentiality-disclosure-retention-legalhold-and-tombstone-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone?", "kind": "privacy", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "purpose-contact-itinerary-access-confidentiality-disclosure-retention-legalhold-and-tombstone-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone, for which purpose and under what authority?", "kind": "lifecycle", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "purpose-contact-itinerary-access-confidentiality-disclosure-retention-legalhold-and-tombstone-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone?", "kind": "event", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "purpose-contact-itinerary-access-confidentiality-disclosure-retention-legalhold-and-tombstone-data", "name": "Purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone data", "description": "Typed reservation data for purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014", "SRC-016" ] } ], "artifacts": [ { "id": "purpose-contact-itinerary-access-confidentiality-disclosure-retention-legalhold-and-tombstone-record", "name": "Purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone record", "description": "Immutable or successor-versioned reservation evidence for purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for purpose-contact-itinerary-access-confidentiality-disclosure-retention-legalhold-and-tombstone; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-014", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "validation-events-clocks-and-loss-aware-projections", "name": "Validation, events, clocks and loss-aware projections", "description": "Groups source-qualified reservation context for validation, events, clocks and loss-aware projections.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "findings": [ { "id": "request-hold-confirm-modify-cancel-expire-checkin-fulfil-observation-ingestion-and-knowledge-time", "name": "Request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time", "description": "Records request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "request-hold-confirm-modify-cancel-expire-checkin-fulfil-observation-ingestion-and-knowledge-time-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time?", "kind": "temporal", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "request-hold-confirm-modify-cancel-expire-checkin-fulfil-observation-ingestion-and-knowledge-time-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time, for which purpose and under what authority?", "kind": "temporal", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "request-hold-confirm-modify-cancel-expire-checkin-fulfil-observation-ingestion-and-knowledge-time-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time?", "kind": "measurement", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "request-hold-confirm-modify-cancel-expire-checkin-fulfil-observation-ingestion-and-knowledge-time-data", "name": "Request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time data", "description": "Typed reservation data for request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "request-hold-confirm-modify-cancel-expire-checkin-fulfil-observation-ingestion-and-knowledge-time-record", "name": "Request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time record", "description": "Immutable or successor-versioned reservation evidence for request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for request-hold-confirm-modify-cancel-expire-checkin-fulfil-observation-ingestion-and-knowledge-time; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "identity-capacity-state-term-arithmetic-policy-privacy-unedifact-schemaorg-iata-tmf-rfc-prov-and-api-validation", "name": "Identity, capacity, state, term, arithmetic, policy, privacy, UN/EDIFACT, Schema.org, IATA, TMF, RFC, PROV and API validation", "description": "Records identity, capacity, state, term, arithmetic, policy, privacy, un/edifact, schema.org, iata, tmf, rfc, prov and api validation as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "identity-capacity-state-term-arithmetic-policy-privacy-unedifact-schemaorg-iata-tmf-rfc-prov-and-api-validation-q01", "text": "What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish identity, capacity, state, term, arithmetic, policy, privacy, un/edifact, schema.org, iata, tmf, rfc, prov and api validation?", "kind": "interoperability", "answer_data": [ "reservation, version, request, segment, unit, party, subject and master identifiers", "travel, stay, appointment, event, dining, rental, facility, resource, group or package profile and schema version", "unknown, pending, held, waitlisted, confirmed, cancelled, expired, disputed and not-applicable states" ] }, { "id": "identity-capacity-state-term-arithmetic-policy-privacy-unedifact-schemaorg-iata-tmf-rfc-prov-and-api-validation-q02", "text": "Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on identity, capacity, state, term, arithmetic, policy, privacy, un/edifact, schema.org, iata, tmf, rfc, prov and api validation, for which purpose and under what authority?", "kind": "spatial", "answer_data": [ "requester, booker, holder, beneficiary, provider, broker, payer, operator, verifier and source system", "purpose, delegation, consent, terms, policy, access, confidentiality, retention and jurisdiction", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "identity-capacity-state-term-arithmetic-policy-privacy-unedifact-schemaorg-iata-tmf-rfc-prov-and-api-validation-q03", "text": "Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify identity, capacity, state, term, arithmetic, policy, privacy, un/edifact, schema.org, iata, tmf, rfc, prov and api validation?", "kind": "evidence", "answer_data": [ "distinct desired, availability, hold, confirmation, service, cancellation, fulfilment, observation and knowledge times", "inventory, offer, policy, message, ticket, payment, check-in, fulfilment, evidence, quality and uncertainty references", "timezone, exception, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "identity-capacity-state-term-arithmetic-policy-privacy-unedifact-schemaorg-iata-tmf-rfc-prov-and-api-validation-data", "name": "Identity, capacity, state, term, arithmetic, policy, privacy, UN/EDIFACT, Schema.org, IATA, TMF, RFC, PROV and API validation data", "description": "Typed reservation data for identity, capacity, state, term, arithmetic, policy, privacy, un/edifact, schema.org, iata, tmf, rfc, prov and api validation, qualified by version, party authority, capacity source, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "identity-capacity-state-term-arithmetic-policy-privacy-unedifact-schemaorg-iata-tmf-rfc-prov-and-api-validation-record", "name": "Identity, capacity, state, term, arithmetic, policy, privacy, UN/EDIFACT, Schema.org, IATA, TMF, RFC, PROV and API validation record", "description": "Immutable or successor-versioned reservation evidence for identity, capacity, state, term, arithmetic, policy, privacy, un/edifact, schema.org, iata, tmf, rfc, prov and api validation.", "media_or_form": [ "logical reservation specification assertion", "request, hold, confirmation, segment, term, lifecycle, time, check-in, evidence, validation or projection record" ], "serial": true, "identity_strategy": "Reservation ID plus independent version, request, segment, unit, hold, confirmation or event ID and artifact kind for identity-capacity-state-term-arithmetic-policy-privacy-unedifact-schemaorg-iata-tmf-rfc-prov-and-api-validation; party, date, place, price, filename or digest never identifies a reservation alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "draft-reservation-request", "name": "Draft reservation request", "description": "Governed operation to draft reservation request without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.", "inputs": [ "reservation intent", "party roles", "reserved subject and desired time" ], "outputs": [ "versioned non-binding request draft" ], "preconditions": [ "purpose, subject, authority, profile, time, quantity and privacy checks pass" ], "effects": [ "no capacity, contract, ticket or payment is committed" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "id": "evaluate-availability-reference", "name": "Evaluate availability reference", "description": "Governed operation to evaluate availability reference without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.", "inputs": [ "request", "source-qualified availability observations" ], "outputs": [ "ranked feasible options with freshness and uncertainty" ], "preconditions": [ "inventory source, slot, quantity, class, time, location and freshness pass" ], "effects": [ "external inventory remains authoritative and unchanged" ], "source_refs": [ "SRC-001", "SRC-008", "SRC-009", "SRC-016" ] }, { "id": "place-provisional-hold", "name": "Place provisional hold", "description": "Governed operation to place provisional hold without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.", "inputs": [ "authorized request", "capacity-system operation reference", "hold policy" ], "outputs": [ "hold request and observed hold assertion" ], "preconditions": [ "authority, capacity, expiry, terms, idempotency and source checks pass" ], "effects": [ "hold request and external allocation result remain distinct" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-009" ] }, { "id": "confirm-booking", "name": "Confirm booking", "description": "Governed operation to confirm booking without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.", "inputs": [ "reservation head", "provider confirmation evidence", "accepted terms" ], "outputs": [ "immutable confirmation assertion and successor version" ], "preconditions": [ "authority, terms, capacity, identifiers, notices and evidence pass" ], "effects": [ "confirmation does not prove payment, ticket, entitlement or fulfilment" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010" ] }, { "id": "compose-or-split-reservation", "name": "Compose or split reservation", "description": "Governed operation to compose or split reservation without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.", "inputs": [ "reservation versions", "segments or sub-reservations", "composition rules" ], "outputs": [ "package, split or merge successor graph" ], "preconditions": [ "identity, sequence, shared terms, dependency and party checks pass" ], "effects": [ "child identities, external orders and tickets remain intact" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-010" ] }, { "id": "modify-or-rebook", "name": "Modify or rebook", "description": "Governed operation to modify or rebook without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.", "inputs": [ "reservation head", "authorized change request", "availability and term evidence" ], "outputs": [ "change assertion and linked successor" ], "preconditions": [ "authority, capacity, price, policy, notice, compatibility and effect checks pass" ], "effects": [ "the prior record stays immutable and financial execution remains external" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-010", "SRC-011" ] }, { "id": "cancel-expire-or-request-release", "name": "Cancel, expire or request release", "description": "Governed operation to cancel, expire or request release without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.", "inputs": [ "reservation", "authorized cancellation or expiry trigger", "release policy" ], "outputs": [ "cancellation or expiry assertion and release request reference" ], "preconditions": [ "authority, deadline, charge, refund, dependency, notice and external release evidence pass" ], "effects": [ "cancelled state does not itself prove capacity release or refund" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-010", "SRC-011" ] }, { "id": "record-checkin-noshow-or-fulfilment-reference", "name": "Record check-in, no-show or fulfilment reference", "description": "Governed operation to record check-in, no-show or fulfilment reference without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.", "inputs": [ "reservation", "external arrival, admission or service evidence" ], "outputs": [ "source-qualified operational observation" ], "preconditions": [ "subject, actor, event time, source, status, confidence and privacy pass" ], "effects": [ "actual operational lifecycle stays external" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-014", "SRC-016" ] }, { "id": "validate-and-reconcile-reservation", "name": "Validate and reconcile reservation", "description": "Governed operation to validate and reconcile reservation without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.", "inputs": [ "reservation version", "rules and external observations" ], "outputs": [ "validation findings and reconciliation evidence" ], "preconditions": [ "identity, capacity, state, time, terms, arithmetic, privacy and lifecycle checks execute" ], "effects": [ "errors are reported without autonomous commercial action" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-013", "SRC-016", "SRC-017" ] }, { "id": "query-project-retain-and-audit", "name": "Query, project, retain and audit", "description": "Governed operation to query, project, retain and audit without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.", "inputs": [ "reservation", "purpose-bound access", "target profile", "records policy" ], "outputs": [ "filtered view, loss-declaring projection, retention result or audit event" ], "preconditions": [ "purpose, authority, privacy, mapping, digest, lifecycle and legal-hold checks pass" ], "effects": [ "projections never replace the canonical reservation and disposition stays external" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "composition": [ { "target": "WM-ECO-006", "relation": "REFERENCE", "purpose": "Resolve the commercial agreement when one exists without granting reservation-owned mutation or cascade authority.", "required": false, "source_refs": [ "SRC-003", "SRC-010", "SRC-011" ] }, { "target": "Party, Offering, Inventory, Availability, Capacity, Schedule, Location, Contract, Order, Ticket, Entitlement, Invoice, Payment, Check-in, Fulfilment and Records models", "relation": "REFERENCE", "purpose": "Resolve authoritative external identities, states, events and evidence without duplicating their lifecycles.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-014" ] }, { "target": "UN/EDIFACT RESREQ, RESRSP and IFTMBF; Schema.org Reservation; IATA ONE Order; TMF646 and TMF716; EU booking profiles; RFC 5545 and RFC 3339; PROV-O; ODRL; DQV; ISO 4217; OpenAPI 3.1.1", "relation": "ALIGN", "purpose": "Project version-pinned booking, transport, discovery, airline, resource, legal, temporal, provenance, policy, quality, currency and API views with declared loss.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension owner, namespace authority, accountable reservation owner and delegated commercial, capacity, operational and legal authorities", "Authoritative Party, Offering, Inventory, Availability, Contract, Order, Ticket, Entitlement, Payment, Calendar, Location, Fulfilment and Records registries", "Approved sector, jurisdiction, capacity, rate, guarantee, cancellation, no-show, privacy, retention and interoperability profiles", "Role, delegation, consent, scarce-capacity, modification, cancellation, transfer, disclosure and agent-operation policies" ], "namespace_guidance": "Mint reservation, version, request, segment, unit binding, hold, confirmation, lifecycle, evidence, validation and projection IDs; preserve every external master identifier.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative reservation identifier, provider namespace and version head, never by party name, date, confirmation code, ticket, place, price or digest alone.", "Keep reservation, availability, capacity allocation, appointment, calendar event, offer, contract, order, ticket, entitlement, invoice, payment, check-in and fulfilment independently identifiable." ], "patch_rules": [ "Extensions declare profile, identity, parties, reserved subject, capacity, composition, terms, lifecycle, time, place, privacy and interoperability effects.", "Issued versions are immutable; modifications, rebookings, splits, merges and transfers create linked successors with reason, authority, impacts and compatibility.", "Never silently change provider, beneficiary, reserved subject, capacity, time, place, rate, guarantee, cancellation rule, ticket, payment, authority or privacy term." ], "compatibility_rules": [ "Ignore additive fields only when identity, version, parties, subject, capacity, segments, terms, states, times, authority, access and provenance survive.", "Every projection pins specification version and declares loss in capacity, composition, policy, lifecycle, time, authority and evidence semantics." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier for reservation, version, request, segment, hold, confirmation, lifecycle event or artifact, qualified by provider namespace and record kind.", "Governed globally resolvable reservation or artifact IRI.", "Dimension UUID or ULID when neither preceding identifier exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; distinguish desired, availability, request, hold, confirmation, service, modification, cancellation, expiry, check-in, fulfilment, observation, ingestion and knowledge times whenever they differ.", "serial_naming_rule": "Use {reservation-id}--{version-id}--{request-segment-hold-confirmation-or-event-id}--{artifact-kind}--{revision-id}.", "integrity_rule": "Store digest, media type, record kind, reservation and version IDs, profile, provider, actor, timezone, distinct event and knowledge times, confidentiality marking and provenance." }, "policies": [ "The reservation owns booking context but not external party, offering, inventory, contract, order, ticket, payment, calendar, location, fulfilment or records masters.", "Request, availability, hold, confirmation, contract, payment, ticket, allocation, check-in and fulfilment states and clocks remain distinct.", "Confirmed, paid, ticketed, checked-in or completed status never alone proves legal validity, capacity guarantee, attendance, fulfilment or fitness.", "Agents cannot autonomously commit scarce capacity, accept terms, charge or refund, issue tickets, transfer, cancel, disclose sensitive itinerary or dispose records without delegated authority." ], "crud": { "read": [ "Resolve reservation head, versions, parties, reserved subject, capacity, composition, terms, lifecycle, times, place, operational evidence, access and projection loss under the permitted view." ], "create": [ "Bind identity, provider, requester, beneficiary, purpose, profile, reserved subject, source authority, desired schedule and initial state before reservation assertions are accepted." ], "update": [ "Append successor composition, terms, hold, confirmation, modification, cancellation, check-in, fulfilment, correction and lifecycle assertions with reason, authority, event time and knowledge time." ], "delete": [ "Apply legal hold, operational, consumer, financial, privacy and adopting-Dimension retention policy; tombstone only the catalogue view without cascading to external masters, and let authoritative systems execute physical disposition." ] }, "roles": [ { "name": "Reservation owner", "responsibilities": [ "Own purpose, scope, profile, lifecycle, compatibility and accountable use." ] }, { "name": "Capacity and inventory steward", "responsibilities": [ "Own availability, pool, quota, allocation, overbooking and release-system bindings." ] }, { "name": "Commercial and policy owner", "responsibilities": [ "Own rates, terms, guarantees, cancellation, no-show, change and refund policy references." ] }, { "name": "Provider and operations steward", "responsibilities": [ "Own confirmation, check-in, admission, handover, fulfilment and exception bindings." ] }, { "name": "Privacy and legal authority", "responsibilities": [ "Own consent, notice, transfer, itinerary data, access, jurisdiction and retention limitations." ] }, { "name": "Reviewer and approving authority", "responsibilities": [ "Own validation, exceptions, segregation of duties and authorization for consequential changes." ] }, { "name": "Interoperability and records steward", "responsibilities": [ "Own mappings, conformance evidence, declared loss, legal hold and disposition policy." ] } ], "access": { "default_rule": "Deny passenger, guest, attendee, patient, itinerary, accessibility, identity-document, loyalty, payment, location, contact, negotiated-rate and dispute data unless a purpose-bound policy permits the minimum necessary view.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Declared operational, support, emergency, legal, financial, audit, regulatory or subject-rights access must cite authority, scope, purpose and time limit and must be logged." ], "audit_requirements": [ "Log actor, agent, role, purpose, reservation and version, operation, authority, policy, RFC 3339 time, affected subject or terms, source revision and outcome without duplicating restricted personal data." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension namespace, reservation, commercial, capacity, privacy, retention and agent policies.", "Read this reservation and linked party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records models before mutation." ] } }, "coverage": { "claim": "WM-ECO-023 covers one governed reservation from request and availability through hold, confirmation, composition, terms, modification, cancellation, time, place, check-in, fulfilment evidence, governance and loss-aware projections. Sector and jurisdiction profiles, legal determinations, capacity-system conformance and independent external review remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Identity is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "classification and direct properties", "status": "covered", "notes": "Classification and direct properties is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Recognition and observation is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Capabilities and possible actions is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "composition", "status": "covered", "notes": "Composition is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "lifecycle", "status": "covered", "notes": "Lifecycle is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "relationships", "status": "covered", "notes": "Relationships is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "temporal", "status": "covered", "notes": "Temporal is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "spatial", "status": "covered", "notes": "Spatial is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "provenance", "status": "covered", "notes": "Provenance is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "ownership", "status": "covered", "notes": "Ownership is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "validation", "status": "covered", "notes": "Validation is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "access", "status": "covered", "notes": "Access is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Retention and deletion is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "interoperability", "status": "covered", "notes": "Interoperability is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." }, { "dimension": "authority and ethics", "status": "covered", "notes": "Authority and ethics is explicit; sector, jurisdiction, legal-effect, capacity-source and external-review profiles remain held where applicable." } ], "known_omissions": [ "Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.", "The WM-ECO-006 parent signal has no frozen approved relation and grants no cascade authority.", "Airline, rail, hotel, restaurant, medical, event, rental, logistics, facility and other domain profiles need separate rules and code lists.", "National contract, consumer, identity, accessibility, payment, privacy, emergency-access and records rules require jurisdiction and sector profiles.", "UN/EDIFACT, Schema.org, IATA and TM Forum sources are loss-aware projections and do not universally define legal booking effect or capacity truth." ], "conflicts": [ "Reservation, availability observation, provisional hold, appointment, calendar event, offer, contract, order, ticket, entitlement, payment, allocation and fulfilment are related but not interchangeable.", "Pending, held, waitlisted, confirmed, paid, ticketed, checked-in, fulfilled, cancelled, expired and no-show states belong to separate axes.", "Desired, offered, held, confirmed, service, cancellation, release, observation, ingestion and knowledge times must not be collapsed.", "A cancellation, expiry or no-show assertion does not itself prove capacity release, charge, refund, entitlement revocation or record deletion." ], "regional_assumptions": [ "Booking confirmation, transfer, cancellation, withdrawal, no-show, accessibility, identity, tax, fees, refunds and retention depend on governing law, sector, provider policy and party type.", "EU package-travel and consumer rules are scoped profiles, not universal governing law; UN/EDIFACT transport and travel messages do not establish contract effect by themselves." ], "adversarial_checks": [ "Reject a reservation that collapses into availability, inventory, contract, order, ticket, payment, calendar or fulfilment masters.", "Reject a confirmed state without authoritative provider, confirmation evidence, reserved subject, capacity source, time, terms and version.", "Reject a capacity claim without source, unit, pool or class, validity interval, freshness, uncertainty and external allocation status.", "Reject cancellation as proof of release or refund and keep request, effective, expiry, no-show, release and financial events distinct.", "Reject autonomous commitment, acceptance, charging, refunding, ticketing, transfer, cancellation, disclosure or disposition without delegated authority.", "Reject a projection that hides composition, state-axis, timezone, policy, authority, provenance or information loss." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "aggregate", "status": "accepted-with-profile-boundary", "rationale": "The root is a reservation or booking lifecycle aggregate. Party, offering, inventory, availability, capacity allocation, appointment, calendar event, contract, order, ticket, entitlement, invoice, payment, check-in, fulfilment and records remain external masters." }, "decisions": [ { "concept": "Reservation, booking, availability and hold", "disposition": "accepted-with-explicit-boundary", "rationale": "Reservation and booking name the governed aggregate; availability is a source-qualified observation and a hold is a temporary external allocation assertion with its own expiry and authority." }, { "concept": "WM-ECO-006 parent signal", "disposition": "accepted-as-unapproved-reference", "rationale": "Commercial Contract is a plausible parent reference when a booking forms or implements an agreement, but no frozen canonical relation grants ownership, mutation or cascade authority." }, { "concept": "Party roles and beneficiaries", "disposition": "accepted", "rationale": "Requester, booker, holder, beneficiary, provider, broker, payer, contact and operator remain separate, source-qualified roles and may be different parties." }, { "concept": "Capacity, inventory, composition and preferences", "disposition": "accepted-with-external-master-boundary", "rationale": "The reservation records referenced pool, class, slot, quota, segment, unit, party composition, accessibility and preference assertions while inventory and allocation systems retain authority." }, { "concept": "Terms and financial bindings", "disposition": "accepted", "rationale": "Rate, price, tax, deposit, guarantee, cancellation, no-show, change and refund rules are versioned bindings; offers, contracts, invoices, payments and refunds retain separate execution and evidence." }, { "concept": "Request, confirmation and operational state axes", "disposition": "accepted", "rationale": "Request, capacity, hold, booking, payment, ticket, check-in and fulfilment states preserve independent sources, authority and time; one state cannot prove another." }, { "concept": "Modification, cancellation, expiry, no-show and release", "disposition": "accepted", "rationale": "Change and rebooking create successors; cancellation request, effective cancellation, expiry, no-show, capacity release, charge, refund and disposition remain separately attributable." }, { "concept": "Temporal and spatial semantics", "disposition": "accepted", "rationale": "Desired, observed, offered, held, confirmed, service, modification, cancellation, release, check-in, fulfilment and knowledge times remain distinct with timezone and location context." }, { "concept": "Interoperability projections", "disposition": "accepted-with-loss-declaration", "rationale": "UN/EDIFACT, Schema.org, IATA, TM Forum, EU profiles, RFC, PROV, ODRL, DQV, ISO 4217 and OpenAPI cover different facets and never replace the canonical aggregate." }, { "concept": "Single-provider waiver and no-tools audit", "disposition": "accepted-with-mandatory-hold", "rationale": "One bounded Claude Sonnet and one bounded Grok attempt each timed out after 120 seconds. Codex separately audited the frozen validated result and comparison without new research facts; assurance remains reviewable-draft." } ], "publicationHolds": [ "Absence-of-external-review hold: one Claude Sonnet and one Grok attempt for WM-ECO-023 each timed out after 120 seconds; no external research result was admitted.", "Relation hold: WM-ECO-006 is only a parent signal and no model relation is canonically approved for this aggregate.", "Boundary hold: reservation, availability, inventory, capacity allocation, appointment, calendar event, offer, contract, order, ticket, entitlement, invoice, payment, check-in, fulfilment and records must retain separate identities.", "State-axis hold: request, capacity, hold, booking, payment, ticket, check-in and fulfilment states and clocks must never be silently collapsed.", "Capacity hold: every availability, quota, hold, overbooking, allocation and release assertion requires authoritative source, unit or class, interval, freshness, uncertainty and observed external state.", "Temporal hold: desired, availability, request, hold, confirmation, service, modification, cancellation, expiry, release, check-in, fulfilment, observation, ingestion and knowledge time remain distinct; timestamps require seconds and timezone offset.", "Cancellation hold: request, effective cancellation, expiry, no-show, capacity release, charge, refund, entitlement effect and record disposition require separate evidence and authority.", "Authority hold: capacity commitment, term acceptance, charging, refunding, ticketing, transfer, cancellation, disclosure and disposition require delegated accountable authority.", "Jurisdiction hold: EU package-travel and consumer rules are scoped profiles; national, sector and provider rules require separate validation.", "Interoperability hold: every UN/EDIFACT, Schema.org, IATA, TM Forum, RFC, PROV, ODRL, DQV, ISO 4217 and OpenAPI projection requires version pins, conformance evidence and information-loss declarations.", "Privacy hold: passenger, guest, attendee, patient, itinerary, location, accessibility, identity-document, loyalty, payment and contact data require purpose-bound access, minimization and retention controls.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Canonically approve the WM-ECO-006 relation and register Party, Offering, Inventory, Availability, Capacity, Schedule, Location, Contract, Order, Ticket, Entitlement, Payment, Check-in, Fulfilment and Records edges.", "Create airline, rail, hotel, restaurant, medical, event, rental, logistics, facility and jurisdiction-specific profiles and code lists.", "Conformance-test request, hold, confirmation, modification, cancellation, release, time, composition and projection mappings against concrete implementations.", "Validate organization-specific capacity, overbooking, guarantee, cancellation, no-show, transfer, accessibility, privacy, retention and emergency-access policies.", "Obtain authorized legal, consumer, financial and sector review before making jurisdiction-specific or contract-effect claims.", "Obtain independent external research review before promoting beyond reviewable-draft assurance." ] }, "statistics": { "sources": 18, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }