# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T05:06:40Z", "synthesisSha256": "7f63d44ff87ef1c56a397b409cd51b9cde398915bc39ab32e05ac705bd1f783d", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-026", "registryId": "vr.wm-act-026", "name": "Appointment / Reservation Event", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.APT" ], "tags": [ "appointment", "reservation", "event", "act.apt" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-026-appointment-reservation-event/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-026", "model": { "registry_id": "vr.wm-act-026", "model_id": "WM-ACT-026", "name": "Appointment / Reservation Event", "entry_kind": "aggregate", "purpose": "Represent a proposed, held or confirmed allocation of time, capacity, service, place or resource among participants without owning availability, actual encounter, service order or payment lifecycles.", "scope_statement": "Owns booking identity and lineage, request purpose and preferences, planned interval and recurrence, allocation references, booking-scoped party roles and responses, proposals and confirmation basis, booking lifecycle events, terms references, booking-specific communications and evidence, projections, access and retention. Party, resource, service, schedule, slot, place, order, payment, entitlement, message, encounter, generic evidence and audit masters remain external.", "in_scope": [ "Appointment and reservation identity, request, proposed or held allocation, participants, service or resource references, time, recurrence and capacity observation", "Proposal, response, confirmation, waitlist, modification, reschedule, cancellation, expiry, no-show and fulfilment assertions with authority and lineage", "Terms and commerce references, communications, provenance, validation, role views, privacy, retention, interoperability and safe agent operations" ], "out_of_scope": [ "Party, resource, service, location, schedule, slot, order, payment, entitlement, message, encounter, generic evidence or audit-log master lifecycle", "Proving actual attendance, service performance, resource availability, payment settlement, legal entitlement or party identity merely from booking status", "Implementing scheduler, optimization, routing, conferencing, payment, messaging or sector-specific protocol engines and claiming lossless cross-format equivalence" ], "boundary_notes": [ { "neighbor": "Schedule / Slot / Availability", "distinction": "The booking references source-qualified availability and allocated slots; schedules and slots keep their own identity, capacity and availability lifecycle.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011" ] }, { "neighbor": "Encounter / Event occurrence", "distinction": "The booking describes planned allocation; an actual encounter or real-world event keeps separate observations and outcome evidence.", "source_refs": [ "SRC-001", "SRC-010" ] }, { "neighbor": "Order / Payment / Entitlement", "distinction": "The booking can reference commercial or authorization records, but confirmation does not itself settle payment or grant entitlement.", "source_refs": [ "SRC-009", "SRC-011" ] }, { "neighbor": "Party / Resource / Service / Place", "distinction": "Booking-scoped roles and allocation references are owned here; external subject masters and their lifecycles are not copied.", "source_refs": [ "SRC-001", "SRC-009", "SRC-010" ] }, { "neighbor": "Calendar message / Notification", "distinction": "The booking owns the intended state and records communication references; delivery of an invitation or confirmation is not acceptance.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ] }, "sources": [ { "id": "SRC-001", "title": "FHIR R5 Appointment", "organization": "Health Level Seven International", "url": "https://www.hl7.org/fhir/appointment.html", "version_or_date": "FHIR R5 5.0.0", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:05:00Z", "relevance": "Defines healthcare appointment scope, actors, services, requested periods, recurrence, participant responses and lifecycle states, and distinguishes appointment from encounter." }, { "id": "SRC-002", "title": "FHIR R5 Slot", "organization": "Health Level Seven International", "url": "https://www.hl7.org/fhir/slot.html", "version_or_date": "FHIR R5 5.0.0", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:05:00Z", "relevance": "Defines a schedule slot, start and end, free, busy and tentative status, overbooking and service classifications." }, { "id": "SRC-003", "title": "FHIR R5 Schedule", "organization": "Health Level Seven International", "url": "https://www.hl7.org/fhir/schedule.html", "version_or_date": "FHIR R5 5.0.0", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:05:00Z", "relevance": "Defines the availability container for a service or resource and explicitly excludes actual appointment information." }, { "id": "SRC-004", "title": "FHIR R5 AppointmentResponse", "organization": "Health Level Seven International", "url": "https://www.hl7.org/fhir/appointmentresponse.html", "version_or_date": "FHIR R5 5.0.0", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:05:00Z", "relevance": "Defines participant acceptance, decline, tentative and needs-action responses, including proposed times and recurrence-wide or occurrence-specific response." }, { "id": "SRC-005", "title": "Internet Calendaring and Scheduling Core Object Specification", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc5545", "version_or_date": "RFC 5545, September 2009", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:05:00Z", "relevance": "Defines VEVENT, UID, organizer, attendee, date-time, duration, location, resources, recurrence rules, recurrence identifiers, sequence and free-busy data." }, { "id": "SRC-006", "title": "iCalendar Transport-Independent Interoperability Protocol", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc5546", "version_or_date": "RFC 5546, December 2009", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:05:00Z", "relevance": "Defines scheduling methods including request, reply, add, cancel, refresh, counter and decline-counter and their security and concurrency concerns." }, { "id": "SRC-007", "title": "JSCalendar: A JSON Representation of Calendar Data", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc8984", "version_or_date": "RFC 8984, July 2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:05:00Z", "relevance": "Defines JSON calendar events, participants, locations, time zones, recurrence rules, recurrence overrides, alerts and links." }, { "id": "SRC-008", "title": "Date and Time on the Internet: Timestamps with Additional Information", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc9557", "version_or_date": "RFC 9557, April 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:05:00Z", "relevance": "Defines timestamp extensions for named time zones and documents why offset, time zone and future local-time intent are distinct." }, { "id": "SRC-009", "title": "Reservation", "organization": "Schema.org Community Group", "url": "https://schema.org/Reservation", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-06T05:05:00Z", "relevance": "Defines cross-sector reservation identity, booking and modification times, provider, beneficiary, reserved subject, status, ticket and price." }, { "id": "SRC-010", "title": "Event", "organization": "Schema.org Community Group", "url": "https://schema.org/Event", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-06T05:05:00Z", "relevance": "Defines event time, location, organizer, attendee, attendance mode, capacity, schedule, status and previous start dates." }, { "id": "SRC-011", "title": "TMF646 Appointment Management API REST Specification", "organization": "TM Forum", "url": "https://www.tmforum.org/resources/specifications/tmf646-appointment-management-api-rest-specification-r19-0-0/", "version_or_date": "TMF646 v4.0.1, November 2019", "source_type": "standard", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-06T05:05:00Z", "relevance": "Defines cross-industry appointment search, free-slot selection, creation and appointment characteristics for customer and service operations." }, { "id": "SRC-012", "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-06T05:05:00Z", "relevance": "Defines entities, activities, agents, attribution, derivation, revision and generation for booking provenance and corrections." } ], "structure": { "bundles": [ { "id": "booking-definition-identity-and-boundary", "name": "Booking definition, identity and boundary", "description": "Defines the scheduled allocation and its authoritative identity.", "rationale": "A booking is a planned or held allocation. It is not availability, an actual encounter, a service order or proof that participation occurred.", "source_refs": [ "SRC-001", "SRC-005", "SRC-009", "SRC-011" ], "layers": [ { "id": "concept-type-and-instance-identity", "name": "Concept, type and instance identity", "description": "Separates appointment and reservation semantics from each booking instance and representation.", "source_refs": [ "SRC-001", "SRC-005", "SRC-009", "SRC-011" ], "findings": [ { "id": "appointment-reservation-hold-event-and-encounter-distinction", "name": "Appointment, reservation, hold, event and encounter distinction", "description": "Definition, inclusion and exclusion rules, planned allocation kind and external actual-occurrence reference.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-009", "SRC-010" ], "questions": [ { "id": "appointment-reservation-hold-event-and-encounter-distinction-q01", "text": "What identity, type, role, scope, version and values define appointment, reservation, hold, event and encounter distinction?", "kind": "identity", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "appointment-reservation-hold-event-and-encounter-distinction-q02", "text": "Which authority, source, observation, evidence and event or effective time support appointment, reservation, hold, event and encounter distinction?", "kind": "evidence", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "appointment-reservation-hold-event-and-encounter-distinction-q03", "text": "How is appointment, reservation, hold, event and encounter distinction validated, shared, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "appointment-reservation-hold-event-and-encounter-distinction-data", "name": "Appointment, reservation, hold, event and encounter distinction data", "description": "Structured appointment or reservation data for appointment, reservation, hold, event and encounter distinction.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "appointment-reservation-hold-event-and-encounter-distinction-record", "name": "Appointment, reservation, hold, event and encounter distinction record", "description": "Versioned evidence-bearing booking record for appointment, reservation, hold, event and encounter distinction with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus appointment-reservation-hold-event-and-encounter-distinction assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "booking-identifier-type-version-channel-source-and-lineage", "name": "Booking identifier, type, version, channel, source and lineage", "description": "Authoritative booking ID, local and external IDs, class, profile version, booking channel, source system and predecessor or successor.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009", "SRC-012" ], "questions": [ { "id": "booking-identifier-type-version-channel-source-and-lineage-q01", "text": "What identity, type, role, scope, version and values define booking identifier, type, version, channel, source and lineage?", "kind": "definition", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "booking-identifier-type-version-channel-source-and-lineage-q02", "text": "Which authority, source, observation, evidence and event or effective time support booking identifier, type, version, channel, source and lineage?", "kind": "authority", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "booking-identifier-type-version-channel-source-and-lineage-q03", "text": "How is booking identifier, type, version, channel, source and lineage validated, shared, changed, contested, corrected and retained?", "kind": "interoperability", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "booking-identifier-type-version-channel-source-and-lineage-data", "name": "Booking identifier, type, version, channel, source and lineage data", "description": "Structured appointment or reservation data for booking identifier, type, version, channel, source and lineage.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009", "SRC-012" ] } ], "artifacts": [ { "id": "booking-identifier-type-version-channel-source-and-lineage-record", "name": "Booking identifier, type, version, channel, source and lineage record", "description": "Versioned evidence-bearing booking record for booking identifier, type, version, channel, source and lineage with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus booking-identifier-type-version-channel-source-and-lineage assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009", "SRC-012" ] } ], "inline_only_rationale": null } ] }, { "id": "purpose-request-and-preferences", "name": "Purpose, request and preferences", "description": "Captures why allocation is sought and the bounded request that preceded it.", "source_refs": [ "SRC-001", "SRC-009", "SRC-011" ], "findings": [ { "id": "requester-purpose-service-need-priority-and-request-event", "name": "Requester, purpose, service need, priority and request event", "description": "Requester reference, stated purpose, requested service or resource, priority, referral or order reference and request provenance.", "source_refs": [ "SRC-001", "SRC-011", "SRC-012" ], "questions": [ { "id": "requester-purpose-service-need-priority-and-request-event-q01", "text": "What identity, type, role, scope, version and values define requester, purpose, service need, priority and request event?", "kind": "relationship", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "requester-purpose-service-need-priority-and-request-event-q02", "text": "Which authority, source, observation, evidence and event or effective time support requester, purpose, service need, priority and request event?", "kind": "temporal", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "requester-purpose-service-need-priority-and-request-event-q03", "text": "How is requester, purpose, service need, priority and request event validated, shared, changed, contested, corrected and retained?", "kind": "access", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "requester-purpose-service-need-priority-and-request-event-data", "name": "Requester, purpose, service need, priority and request event data", "description": "Structured appointment or reservation data for requester, purpose, service need, priority and request event.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "requester-purpose-service-need-priority-and-request-event-record", "name": "Requester, purpose, service need, priority and request event record", "description": "Versioned evidence-bearing booking record for requester, purpose, service need, priority and request event with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus requester-purpose-service-need-priority-and-request-event assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "preferred-time-location-participant-resource-and-flexibility", "name": "Preferred time, location, participant, resource and flexibility", "description": "Requested windows, time zone, acceptable locations, participants, resources, duration, flexibility and alternatives.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-011" ], "questions": [ { "id": "preferred-time-location-participant-resource-and-flexibility-q01", "text": "What identity, type, role, scope, version and values define preferred time, location, participant, resource and flexibility?", "kind": "requirement", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "preferred-time-location-participant-resource-and-flexibility-q02", "text": "Which authority, source, observation, evidence and event or effective time support preferred time, location, participant, resource and flexibility?", "kind": "decision", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "preferred-time-location-participant-resource-and-flexibility-q03", "text": "How is preferred time, location, participant, resource and flexibility validated, shared, changed, contested, corrected and retained?", "kind": "exception", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "preferred-time-location-participant-resource-and-flexibility-data", "name": "Preferred time, location, participant, resource and flexibility data", "description": "Structured appointment or reservation data for preferred time, location, participant, resource and flexibility.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-011" ] } ], "artifacts": [ { "id": "preferred-time-location-participant-resource-and-flexibility-record", "name": "Preferred time, location, participant, resource and flexibility record", "description": "Versioned evidence-bearing booking record for preferred time, location, participant, resource and flexibility with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus preferred-time-location-participant-resource-and-flexibility assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "time-recurrence-availability-and-capacity", "name": "Time, recurrence, availability and capacity", "description": "Defines the promised interval and references the external availability from which it was allocated.", "rationale": "Time-zone intent, recurrence identity, slot state and booking commitment are distinct and must not be inferred from a display string.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-007", "SRC-008" ], "layers": [ { "id": "temporal-commitment-and-recurrence", "name": "Temporal commitment and recurrence", "description": "Represents one interval or a recurrence template with explicit exceptions.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008" ], "findings": [ { "id": "start-end-duration-time-zone-window-and-deadline", "name": "Start, end, duration, time zone, window and deadline", "description": "Planned start and end, duration, offset, named time zone, permissible window, arrival window, hold expiry and response deadline.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008" ], "questions": [ { "id": "start-end-duration-time-zone-window-and-deadline-q01", "text": "What identity, type, role, scope, version and values define start, end, duration, time zone, window and deadline?", "kind": "ownership", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "start-end-duration-time-zone-window-and-deadline-q02", "text": "Which authority, source, observation, evidence and event or effective time support start, end, duration, time zone, window and deadline?", "kind": "provenance", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "start-end-duration-time-zone-window-and-deadline-q03", "text": "How is start, end, duration, time zone, window and deadline validated, shared, changed, contested, corrected and retained?", "kind": "privacy", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "start-end-duration-time-zone-window-and-deadline-data", "name": "Start, end, duration, time zone, window and deadline data", "description": "Structured appointment or reservation data for start, end, duration, time zone, window and deadline.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "start-end-duration-time-zone-window-and-deadline-record", "name": "Start, end, duration, time zone, window and deadline record", "description": "Versioned evidence-bearing booking record for start, end, duration, time zone, window and deadline with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus start-end-duration-time-zone-window-and-deadline assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "recurrence-template-occurrence-identity-exception-and-override", "name": "Recurrence template, occurrence identity, exception and override", "description": "Series ID, recurrence rules and dates, occurrence ID, excluded instances, overrides and series versus occurrence changes.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "recurrence-template-occurrence-identity-exception-and-override-q01", "text": "What identity, type, role, scope, version and values define recurrence template, occurrence identity, exception and override?", "kind": "classification", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "recurrence-template-occurrence-identity-exception-and-override-q02", "text": "Which authority, source, observation, evidence and event or effective time support recurrence template, occurrence identity, exception and override?", "kind": "quality", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "recurrence-template-occurrence-identity-exception-and-override-q03", "text": "How is recurrence template, occurrence identity, exception and override validated, shared, changed, contested, corrected and retained?", "kind": "security", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "recurrence-template-occurrence-identity-exception-and-override-data", "name": "Recurrence template, occurrence identity, exception and override data", "description": "Structured appointment or reservation data for recurrence template, occurrence identity, exception and override.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "recurrence-template-occurrence-identity-exception-and-override-record", "name": "Recurrence template, occurrence identity, exception and override record", "description": "Versioned evidence-bearing booking record for recurrence template, occurrence identity, exception and override with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus recurrence-template-occurrence-identity-exception-and-override assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "schedule-slot-capacity-and-conflict", "name": "Schedule, slot, capacity and conflict", "description": "References availability evidence and preserves the allocation decision that consumed it.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-010", "SRC-011" ], "findings": [ { "id": "schedule-slot-availability-observation-and-freshness-reference", "name": "Schedule, slot, availability observation and freshness reference", "description": "External schedule and slot IDs, availability result, query constraints, source revision, observed time and freshness.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011" ], "questions": [ { "id": "schedule-slot-availability-observation-and-freshness-reference-q01", "text": "What identity, type, role, scope, version and values define schedule, slot, availability observation and freshness reference?", "kind": "composition", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "schedule-slot-availability-observation-and-freshness-reference-q02", "text": "Which authority, source, observation, evidence and event or effective time support schedule, slot, availability observation and freshness reference?", "kind": "measurement", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "schedule-slot-availability-observation-and-freshness-reference-q03", "text": "How is schedule, slot, availability observation and freshness reference validated, shared, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "schedule-slot-availability-observation-and-freshness-reference-data", "name": "Schedule, slot, availability observation and freshness reference data", "description": "Structured appointment or reservation data for schedule, slot, availability observation and freshness reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011" ] } ], "artifacts": [ { "id": "schedule-slot-availability-observation-and-freshness-reference-record", "name": "Schedule, slot, availability observation and freshness reference record", "description": "Versioned evidence-bearing booking record for schedule, slot, availability observation and freshness reference with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus schedule-slot-availability-observation-and-freshness-reference assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "capacity-quantity-hold-allocation-overbooking-and-conflict", "name": "Capacity, quantity, hold, allocation, overbooking and conflict", "description": "Requested and allocated quantity, unit, capacity class, hold, remaining capacity observation, overbooking flag and conflict result.", "source_refs": [ "SRC-002", "SRC-003", "SRC-010", "SRC-011" ], "questions": [ { "id": "capacity-quantity-hold-allocation-overbooking-and-conflict-q01", "text": "What identity, type, role, scope, version and values define capacity, quantity, hold, allocation, overbooking and conflict?", "kind": "state", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "capacity-quantity-hold-allocation-overbooking-and-conflict-q02", "text": "Which authority, source, observation, evidence and event or effective time support capacity, quantity, hold, allocation, overbooking and conflict?", "kind": "lifecycle", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "capacity-quantity-hold-allocation-overbooking-and-conflict-q03", "text": "How is capacity, quantity, hold, allocation, overbooking and conflict validated, shared, changed, contested, corrected and retained?", "kind": "retention", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "capacity-quantity-hold-allocation-overbooking-and-conflict-data", "name": "Capacity, quantity, hold, allocation, overbooking and conflict data", "description": "Structured appointment or reservation data for capacity, quantity, hold, allocation, overbooking and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "capacity-quantity-hold-allocation-overbooking-and-conflict-record", "name": "Capacity, quantity, hold, allocation, overbooking and conflict record", "description": "Versioned evidence-bearing booking record for capacity, quantity, hold, allocation, overbooking and conflict with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus capacity-quantity-hold-allocation-overbooking-and-conflict assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "parties-resources-service-and-place", "name": "Parties, resources, service and place", "description": "Binds external actors and allocatable subjects to booking roles.", "rationale": "A participant response is role-scoped. It does not establish identity, authority, attendance or service delivery by itself.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ], "layers": [ { "id": "organizer-requester-provider-and-participants", "name": "Organizer, requester, provider and participants", "description": "Separates booking responsibility, beneficiary and participation obligations.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-009" ], "findings": [ { "id": "organizer-provider-requester-customer-beneficiary-and-booking-agent", "name": "Organizer, provider, requester, customer, beneficiary and booking agent", "description": "External party references, role, authority, on-behalf-of relationship and contact endpoint.", "source_refs": [ "SRC-001", "SRC-005", "SRC-009", "SRC-011" ], "questions": [ { "id": "organizer-provider-requester-customer-beneficiary-and-booking-agent-q01", "text": "What identity, type, role, scope, version and values define organizer, provider, requester, customer, beneficiary and booking agent?", "kind": "identity", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "organizer-provider-requester-customer-beneficiary-and-booking-agent-q02", "text": "Which authority, source, observation, evidence and event or effective time support organizer, provider, requester, customer, beneficiary and booking agent?", "kind": "evidence", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "organizer-provider-requester-customer-beneficiary-and-booking-agent-q03", "text": "How is organizer, provider, requester, customer, beneficiary and booking agent validated, shared, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "organizer-provider-requester-customer-beneficiary-and-booking-agent-data", "name": "Organizer, provider, requester, customer, beneficiary and booking agent data", "description": "Structured appointment or reservation data for organizer, provider, requester, customer, beneficiary and booking agent.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-009", "SRC-011" ] } ], "artifacts": [ { "id": "organizer-provider-requester-customer-beneficiary-and-booking-agent-record", "name": "Organizer, provider, requester, customer, beneficiary and booking agent record", "description": "Versioned evidence-bearing booking record for organizer, provider, requester, customer, beneficiary and booking agent with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus organizer-provider-requester-customer-beneficiary-and-booking-agent assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-009", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "participant-role-required-status-response-delegation-and-attendance-claim", "name": "Participant role, requirement, status, response, delegation and attendance claim", "description": "Participant or actor reference, required or optional role, response requirement, accepted or declined status, delegation and separately sourced attendance assertion.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "participant-role-required-status-response-delegation-and-attendance-claim-q01", "text": "What identity, type, role, scope, version and values define participant role, requirement, status, response, delegation and attendance claim?", "kind": "definition", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "participant-role-required-status-response-delegation-and-attendance-claim-q02", "text": "Which authority, source, observation, evidence and event or effective time support participant role, requirement, status, response, delegation and attendance claim?", "kind": "authority", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "participant-role-required-status-response-delegation-and-attendance-claim-q03", "text": "How is participant role, requirement, status, response, delegation and attendance claim validated, shared, changed, contested, corrected and retained?", "kind": "interoperability", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "participant-role-required-status-response-delegation-and-attendance-claim-data", "name": "Participant role, requirement, status, response, delegation and attendance claim data", "description": "Structured appointment or reservation data for participant role, requirement, status, response, delegation and attendance claim.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "participant-role-required-status-response-delegation-and-attendance-claim-record", "name": "Participant role, requirement, status, response, delegation and attendance claim record", "description": "Versioned evidence-bearing booking record for participant role, requirement, status, response, delegation and attendance claim with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus participant-role-required-status-response-delegation-and-attendance-claim assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "reserved-subject-service-resource-and-location", "name": "Reserved subject, service, resource and location", "description": "States what is allocated and the conditions needed for use.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ], "findings": [ { "id": "service-product-activity-order-referral-and-fulfilment-target", "name": "Service, product, activity, order, referral and fulfilment target", "description": "Reserved or scheduled subject, requested service, product or activity, external order or referral and intended fulfilment target.", "source_refs": [ "SRC-001", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "service-product-activity-order-referral-and-fulfilment-target-q01", "text": "What identity, type, role, scope, version and values define service, product, activity, order, referral and fulfilment target?", "kind": "relationship", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "service-product-activity-order-referral-and-fulfilment-target-q02", "text": "Which authority, source, observation, evidence and event or effective time support service, product, activity, order, referral and fulfilment target?", "kind": "temporal", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "service-product-activity-order-referral-and-fulfilment-target-q03", "text": "How is service, product, activity, order, referral and fulfilment target validated, shared, changed, contested, corrected and retained?", "kind": "access", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "service-product-activity-order-referral-and-fulfilment-target-data", "name": "Service, product, activity, order, referral and fulfilment target data", "description": "Structured appointment or reservation data for service, product, activity, order, referral and fulfilment target.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "service-product-activity-order-referral-and-fulfilment-target-record", "name": "Service, product, activity, order, referral and fulfilment target record", "description": "Versioned evidence-bearing booking record for service, product, activity, order, referral and fulfilment target with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus service-product-activity-order-referral-and-fulfilment-target assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "resource-place-virtual-endpoint-accessibility-equipment-and-preconditions", "name": "Resource, place, virtual endpoint, accessibility, equipment and preconditions", "description": "External resource and location references, room or device, online endpoint, attendance mode, accessibility needs, equipment and prerequisites.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-010" ], "questions": [ { "id": "resource-place-virtual-endpoint-accessibility-equipment-and-preconditions-q01", "text": "What identity, type, role, scope, version and values define resource, place, virtual endpoint, accessibility, equipment and preconditions?", "kind": "requirement", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "resource-place-virtual-endpoint-accessibility-equipment-and-preconditions-q02", "text": "Which authority, source, observation, evidence and event or effective time support resource, place, virtual endpoint, accessibility, equipment and preconditions?", "kind": "decision", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "resource-place-virtual-endpoint-accessibility-equipment-and-preconditions-q03", "text": "How is resource, place, virtual endpoint, accessibility, equipment and preconditions validated, shared, changed, contested, corrected and retained?", "kind": "exception", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "resource-place-virtual-endpoint-accessibility-equipment-and-preconditions-data", "name": "Resource, place, virtual endpoint, accessibility, equipment and preconditions data", "description": "Structured appointment or reservation data for resource, place, virtual endpoint, accessibility, equipment and preconditions.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-010" ] } ], "artifacts": [ { "id": "resource-place-virtual-endpoint-accessibility-equipment-and-preconditions-record", "name": "Resource, place, virtual endpoint, accessibility, equipment and preconditions record", "description": "Versioned evidence-bearing booking record for resource, place, virtual endpoint, accessibility, equipment and preconditions with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus resource-place-virtual-endpoint-accessibility-equipment-and-preconditions assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "negotiation-confirmation-lifecycle-and-change", "name": "Negotiation, confirmation, lifecycle and change", "description": "Represents proposals, responses and append-only booking transitions.", "rationale": "Current status is derived from attributable events. Reschedule, cancellation, expiry, no-show and fulfilment never silently rewrite prior commitments.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-012" ], "layers": [ { "id": "proposal-response-and-confirmation", "name": "Proposal, response and confirmation", "description": "Preserves the revision each party saw and the basis on which the booking became confirmed.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007", "SRC-011" ], "findings": [ { "id": "proposal-offer-counterproposal-revision-sequence-and-expiry", "name": "Proposal, offer, counterproposal, revision, sequence and expiry", "description": "Proposed allocation, proposing actor, revision and sequence, response deadline, expiry and relation to previous proposal.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012" ], "questions": [ { "id": "proposal-offer-counterproposal-revision-sequence-and-expiry-q01", "text": "What identity, type, role, scope, version and values define proposal, offer, counterproposal, revision, sequence and expiry?", "kind": "ownership", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "proposal-offer-counterproposal-revision-sequence-and-expiry-q02", "text": "Which authority, source, observation, evidence and event or effective time support proposal, offer, counterproposal, revision, sequence and expiry?", "kind": "provenance", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "proposal-offer-counterproposal-revision-sequence-and-expiry-q03", "text": "How is proposal, offer, counterproposal, revision, sequence and expiry validated, shared, changed, contested, corrected and retained?", "kind": "privacy", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "proposal-offer-counterproposal-revision-sequence-and-expiry-data", "name": "Proposal, offer, counterproposal, revision, sequence and expiry data", "description": "Structured appointment or reservation data for proposal, offer, counterproposal, revision, sequence and expiry.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "proposal-offer-counterproposal-revision-sequence-and-expiry-record", "name": "Proposal, offer, counterproposal, revision, sequence and expiry record", "description": "Versioned evidence-bearing booking record for proposal, offer, counterproposal, revision, sequence and expiry with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus proposal-offer-counterproposal-revision-sequence-and-expiry assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "participant-response-confirmation-basis-commitment-and-pending-party", "name": "Participant response, confirmation basis, commitment and pending party", "description": "Response actor, role and revision, accepted, declined, tentative or needs-action state, confirmation rule and outstanding responses.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "participant-response-confirmation-basis-commitment-and-pending-party-q01", "text": "What identity, type, role, scope, version and values define participant response, confirmation basis, commitment and pending party?", "kind": "classification", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "participant-response-confirmation-basis-commitment-and-pending-party-q02", "text": "Which authority, source, observation, evidence and event or effective time support participant response, confirmation basis, commitment and pending party?", "kind": "quality", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "participant-response-confirmation-basis-commitment-and-pending-party-q03", "text": "How is participant response, confirmation basis, commitment and pending party validated, shared, changed, contested, corrected and retained?", "kind": "security", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "participant-response-confirmation-basis-commitment-and-pending-party-data", "name": "Participant response, confirmation basis, commitment and pending party data", "description": "Structured appointment or reservation data for participant response, confirmation basis, commitment and pending party.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "participant-response-confirmation-basis-commitment-and-pending-party-record", "name": "Participant response, confirmation basis, commitment and pending party record", "description": "Versioned evidence-bearing booking record for participant response, confirmation basis, commitment and pending party with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus participant-response-confirmation-basis-commitment-and-pending-party assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "state-transition-reschedule-and-outcome-assertion", "name": "State transition, reschedule and outcome assertion", "description": "Keeps plan lifecycle separate from observations of what happened.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-012" ], "findings": [ { "id": "proposed-held-pending-confirmed-waitlisted-arrived-and-checked-in-event", "name": "Proposed, held, pending, confirmed, waitlisted, arrived and checked-in event", "description": "Typed status event, prior and next state, actor, authority, reason, event time, effective time and evidence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012" ], "questions": [ { "id": "proposed-held-pending-confirmed-waitlisted-arrived-and-checked-in-event-q01", "text": "What identity, type, role, scope, version and values define proposed, held, pending, confirmed, waitlisted, arrived and checked-in event?", "kind": "composition", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "proposed-held-pending-confirmed-waitlisted-arrived-and-checked-in-event-q02", "text": "Which authority, source, observation, evidence and event or effective time support proposed, held, pending, confirmed, waitlisted, arrived and checked-in event?", "kind": "measurement", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "proposed-held-pending-confirmed-waitlisted-arrived-and-checked-in-event-q03", "text": "How is proposed, held, pending, confirmed, waitlisted, arrived and checked-in event validated, shared, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "proposed-held-pending-confirmed-waitlisted-arrived-and-checked-in-event-data", "name": "Proposed, held, pending, confirmed, waitlisted, arrived and checked-in event data", "description": "Structured appointment or reservation data for proposed, held, pending, confirmed, waitlisted, arrived and checked-in event.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012" ] } ], "artifacts": [ { "id": "proposed-held-pending-confirmed-waitlisted-arrived-and-checked-in-event-record", "name": "Proposed, held, pending, confirmed, waitlisted, arrived and checked-in event record", "description": "Versioned evidence-bearing booking record for proposed, held, pending, confirmed, waitlisted, arrived and checked-in event with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus proposed-held-pending-confirmed-waitlisted-arrived-and-checked-in-event assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "modify-reschedule-cancel-expire-no-show-fulfil-correct-and-supersede-event", "name": "Modify, reschedule, cancel, expire, no-show, fulfil, correct and supersede event", "description": "Change scope, prior and new values, authority, reason, original time, release action, no-show or fulfilment assertion source, successor and notification.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-012" ], "questions": [ { "id": "modify-reschedule-cancel-expire-no-show-fulfil-correct-and-supersede-event-q01", "text": "What identity, type, role, scope, version and values define modify, reschedule, cancel, expire, no-show, fulfil, correct and supersede event?", "kind": "state", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "modify-reschedule-cancel-expire-no-show-fulfil-correct-and-supersede-event-q02", "text": "Which authority, source, observation, evidence and event or effective time support modify, reschedule, cancel, expire, no-show, fulfil, correct and supersede event?", "kind": "lifecycle", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "modify-reschedule-cancel-expire-no-show-fulfil-correct-and-supersede-event-q03", "text": "How is modify, reschedule, cancel, expire, no-show, fulfil, correct and supersede event validated, shared, changed, contested, corrected and retained?", "kind": "retention", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "modify-reschedule-cancel-expire-no-show-fulfil-correct-and-supersede-event-data", "name": "Modify, reschedule, cancel, expire, no-show, fulfil, correct and supersede event data", "description": "Structured appointment or reservation data for modify, reschedule, cancel, expire, no-show, fulfil, correct and supersede event.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-012" ] } ], "artifacts": [ { "id": "modify-reschedule-cancel-expire-no-show-fulfil-correct-and-supersede-event-record", "name": "Modify, reschedule, cancel, expire, no-show, fulfil, correct and supersede event record", "description": "Versioned evidence-bearing booking record for modify, reschedule, cancel, expire, no-show, fulfil, correct and supersede event with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus modify-reschedule-cancel-expire-no-show-fulfil-correct-and-supersede-event assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "terms-commerce-communications-evidence-and-provenance", "name": "Terms, commerce, communications, evidence and provenance", "description": "Records booking-specific terms and traceability while referencing external commerce, message and evidence masters.", "rationale": "A booking price or deposit reference does not own payment, refund, invoice or entitlement lifecycle.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-011", "SRC-012" ], "layers": [ { "id": "terms-fees-payment-and-entitlement-references", "name": "Terms, fees, payment and entitlement references", "description": "Connects the booking to the terms that govern confirmation, use and release.", "source_refs": [ "SRC-001", "SRC-009", "SRC-011" ], "findings": [ { "id": "booking-hold-cancellation-no-show-change-and-refund-terms", "name": "Booking, hold, cancellation, no-show, change and refund terms", "description": "Applicable policy versions, acceptance, hold deadline, cancellation window, change rules, no-show terms, refund rule and jurisdiction.", "source_refs": [ "SRC-001", "SRC-009", "SRC-011" ], "questions": [ { "id": "booking-hold-cancellation-no-show-change-and-refund-terms-q01", "text": "What identity, type, role, scope, version and values define booking, hold, cancellation, no-show, change and refund terms?", "kind": "identity", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "booking-hold-cancellation-no-show-change-and-refund-terms-q02", "text": "Which authority, source, observation, evidence and event or effective time support booking, hold, cancellation, no-show, change and refund terms?", "kind": "evidence", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "booking-hold-cancellation-no-show-change-and-refund-terms-q03", "text": "How is booking, hold, cancellation, no-show, change and refund terms validated, shared, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "booking-hold-cancellation-no-show-change-and-refund-terms-data", "name": "Booking, hold, cancellation, no-show, change and refund terms data", "description": "Structured appointment or reservation data for booking, hold, cancellation, no-show, change and refund terms.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-009", "SRC-011" ] } ], "artifacts": [ { "id": "booking-hold-cancellation-no-show-change-and-refund-terms-record", "name": "Booking, hold, cancellation, no-show, change and refund terms record", "description": "Versioned evidence-bearing booking record for booking, hold, cancellation, no-show, change and refund terms with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus booking-hold-cancellation-no-show-change-and-refund-terms assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-009", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "price-deposit-payment-refund-ticket-membership-and-entitlement-reference", "name": "Price, deposit, payment, refund, ticket, membership and entitlement reference", "description": "Quoted price and currency, external price specification, deposit, payment, refund, ticket, membership and entitlement IDs and status observations.", "source_refs": [ "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "price-deposit-payment-refund-ticket-membership-and-entitlement-reference-q01", "text": "What identity, type, role, scope, version and values define price, deposit, payment, refund, ticket, membership and entitlement reference?", "kind": "definition", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "price-deposit-payment-refund-ticket-membership-and-entitlement-reference-q02", "text": "Which authority, source, observation, evidence and event or effective time support price, deposit, payment, refund, ticket, membership and entitlement reference?", "kind": "authority", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "price-deposit-payment-refund-ticket-membership-and-entitlement-reference-q03", "text": "How is price, deposit, payment, refund, ticket, membership and entitlement reference validated, shared, changed, contested, corrected and retained?", "kind": "interoperability", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "price-deposit-payment-refund-ticket-membership-and-entitlement-reference-data", "name": "Price, deposit, payment, refund, ticket, membership and entitlement reference data", "description": "Structured appointment or reservation data for price, deposit, payment, refund, ticket, membership and entitlement reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "price-deposit-payment-refund-ticket-membership-and-entitlement-reference-record", "name": "Price, deposit, payment, refund, ticket, membership and entitlement reference record", "description": "Versioned evidence-bearing booking record for price, deposit, payment, refund, ticket, membership and entitlement reference with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus price-deposit-payment-refund-ticket-membership-and-entitlement-reference assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] }, { "id": "communications-evidence-quality-and-provenance", "name": "Communications, evidence, quality and provenance", "description": "Makes notices, source observations and transformations attributable.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-012" ], "findings": [ { "id": "invitation-confirmation-reminder-change-cancellation-and-delivery-receipt", "name": "Invitation, confirmation, reminder, change, cancellation and delivery receipt", "description": "External message references, audience, purpose, channel, sender, requested response, sent, delivered and acknowledged times and errors.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "invitation-confirmation-reminder-change-cancellation-and-delivery-receipt-q01", "text": "What identity, type, role, scope, version and values define invitation, confirmation, reminder, change, cancellation and delivery receipt?", "kind": "relationship", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "invitation-confirmation-reminder-change-cancellation-and-delivery-receipt-q02", "text": "Which authority, source, observation, evidence and event or effective time support invitation, confirmation, reminder, change, cancellation and delivery receipt?", "kind": "temporal", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "invitation-confirmation-reminder-change-cancellation-and-delivery-receipt-q03", "text": "How is invitation, confirmation, reminder, change, cancellation and delivery receipt validated, shared, changed, contested, corrected and retained?", "kind": "access", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "invitation-confirmation-reminder-change-cancellation-and-delivery-receipt-data", "name": "Invitation, confirmation, reminder, change, cancellation and delivery receipt data", "description": "Structured appointment or reservation data for invitation, confirmation, reminder, change, cancellation and delivery receipt.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "invitation-confirmation-reminder-change-cancellation-and-delivery-receipt-record", "name": "Invitation, confirmation, reminder, change, cancellation and delivery receipt record", "description": "Versioned evidence-bearing booking record for invitation, confirmation, reminder, change, cancellation and delivery receipt with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus invitation-confirmation-reminder-change-cancellation-and-delivery-receipt assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "source-observation-evidence-provenance-confidence-conflict-and-quality", "name": "Source observation, evidence, provenance, confidence, conflict and quality", "description": "Source system and revision, responsible agent, generation or derivation activity, observation and knowledge times, confidence, conflict and validation result.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-012" ], "questions": [ { "id": "source-observation-evidence-provenance-confidence-conflict-and-quality-q01", "text": "What identity, type, role, scope, version and values define source observation, evidence, provenance, confidence, conflict and quality?", "kind": "requirement", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "source-observation-evidence-provenance-confidence-conflict-and-quality-q02", "text": "Which authority, source, observation, evidence and event or effective time support source observation, evidence, provenance, confidence, conflict and quality?", "kind": "decision", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "source-observation-evidence-provenance-confidence-conflict-and-quality-q03", "text": "How is source observation, evidence, provenance, confidence, conflict and quality validated, shared, changed, contested, corrected and retained?", "kind": "exception", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "source-observation-evidence-provenance-confidence-conflict-and-quality-data", "name": "Source observation, evidence, provenance, confidence, conflict and quality data", "description": "Structured appointment or reservation data for source observation, evidence, provenance, confidence, conflict and quality.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-012" ] } ], "artifacts": [ { "id": "source-observation-evidence-provenance-confidence-conflict-and-quality-record", "name": "Source observation, evidence, provenance, confidence, conflict and quality record", "description": "Versioned evidence-bearing booking record for source observation, evidence, provenance, confidence, conflict and quality with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus source-observation-evidence-provenance-confidence-conflict-and-quality assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "interoperability-access-retention-and-agent-operations", "name": "Interoperability, access, retention and agent operations", "description": "Provides loss-aware projections and guarded autonomous operations.", "rationale": "FHIR, iCalendar, JSCalendar, Schema.org and TMF646 overlap but differ in identity, lifecycle, availability, recurrence and outcome semantics.", "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" ], "layers": [ { "id": "validation-concurrency-and-interoperability", "name": "Validation, concurrency and interoperability", "description": "Checks semantic integrity and maps only under pinned profiles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011" ], "findings": [ { "id": "availability-capacity-participant-time-zone-transition-and-concurrency-validation", "name": "Availability, capacity, participant, time-zone, transition and concurrency validation", "description": "Validation checks, expected head or sequence, idempotency key, stale response detection, conflict resolution and structured errors.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-008" ], "questions": [ { "id": "availability-capacity-participant-time-zone-transition-and-concurrency-validation-q01", "text": "What identity, type, role, scope, version and values define availability, capacity, participant, time-zone, transition and concurrency validation?", "kind": "ownership", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "availability-capacity-participant-time-zone-transition-and-concurrency-validation-q02", "text": "Which authority, source, observation, evidence and event or effective time support availability, capacity, participant, time-zone, transition and concurrency validation?", "kind": "provenance", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "availability-capacity-participant-time-zone-transition-and-concurrency-validation-q03", "text": "How is availability, capacity, participant, time-zone, transition and concurrency validation validated, shared, changed, contested, corrected and retained?", "kind": "privacy", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "availability-capacity-participant-time-zone-transition-and-concurrency-validation-data", "name": "Availability, capacity, participant, time-zone, transition and concurrency validation data", "description": "Structured appointment or reservation data for availability, capacity, participant, time-zone, transition and concurrency validation.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "availability-capacity-participant-time-zone-transition-and-concurrency-validation-record", "name": "Availability, capacity, participant, time-zone, transition and concurrency validation record", "description": "Versioned evidence-bearing booking record for availability, capacity, participant, time-zone, transition and concurrency validation with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus availability-capacity-participant-time-zone-transition-and-concurrency-validation assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "fhir-icalendar-jscalendar-schema-org-and-tmf646-crosswalk", "name": "FHIR, iCalendar, JSCalendar, Schema.org and TMF646 crosswalk", "description": "Pinned source and target versions, field and state mappings, recurrence behavior, omissions, conflicts and round-trip class.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "fhir-icalendar-jscalendar-schema-org-and-tmf646-crosswalk-q01", "text": "What identity, type, role, scope, version and values define fhir, icalendar, jscalendar, schema.org and tmf646 crosswalk?", "kind": "classification", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "fhir-icalendar-jscalendar-schema-org-and-tmf646-crosswalk-q02", "text": "Which authority, source, observation, evidence and event or effective time support fhir, icalendar, jscalendar, schema.org and tmf646 crosswalk?", "kind": "quality", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "fhir-icalendar-jscalendar-schema-org-and-tmf646-crosswalk-q03", "text": "How is fhir, icalendar, jscalendar, schema.org and tmf646 crosswalk validated, shared, changed, contested, corrected and retained?", "kind": "security", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "fhir-icalendar-jscalendar-schema-org-and-tmf646-crosswalk-data", "name": "FHIR, iCalendar, JSCalendar, Schema.org and TMF646 crosswalk data", "description": "Structured appointment or reservation data for fhir, icalendar, jscalendar, schema.org and tmf646 crosswalk.", "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-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "fhir-icalendar-jscalendar-schema-org-and-tmf646-crosswalk-record", "name": "FHIR, iCalendar, JSCalendar, Schema.org and TMF646 crosswalk record", "description": "Versioned evidence-bearing booking record for fhir, icalendar, jscalendar, schema.org and tmf646 crosswalk with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus fhir-icalendar-jscalendar-schema-org-and-tmf646-crosswalk assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] }, { "id": "views-access-retention-and-safe-agent-operation", "name": "Views, access, retention and safe agent operation", "description": "Separates audience views and controls mutation, deletion and evidence retention.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-012" ], "findings": [ { "id": "public-participant-requester-provider-operator-auditor-and-agent-view", "name": "Public, participant, requester, provider, operator, auditor and agent view", "description": "Audience, purpose, authority, included fields, redactions, contact and endpoint protection, freshness and expiry.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ], "questions": [ { "id": "public-participant-requester-provider-operator-auditor-and-agent-view-q01", "text": "What identity, type, role, scope, version and values define public, participant, requester, provider, operator, auditor and agent view?", "kind": "composition", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "public-participant-requester-provider-operator-auditor-and-agent-view-q02", "text": "Which authority, source, observation, evidence and event or effective time support public, participant, requester, provider, operator, auditor and agent view?", "kind": "measurement", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "public-participant-requester-provider-operator-auditor-and-agent-view-q03", "text": "How is public, participant, requester, provider, operator, auditor and agent view validated, shared, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "public-participant-requester-provider-operator-auditor-and-agent-view-data", "name": "Public, participant, requester, provider, operator, auditor and agent view data", "description": "Structured appointment or reservation data for public, participant, requester, provider, operator, auditor and agent view.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ] } ], "artifacts": [ { "id": "public-participant-requester-provider-operator-auditor-and-agent-view-record", "name": "Public, participant, requester, provider, operator, auditor and agent view record", "description": "Versioned evidence-bearing booking record for public, participant, requester, provider, operator, auditor and agent view with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus public-participant-requester-provider-operator-auditor-and-agent-view assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "retention-legal-hold-disposition-agent-authority-idempotency-and-audit", "name": "Retention, legal hold, disposition, agent authority, idempotency and audit", "description": "Retention trigger, hold, disposition authority, minimum tombstone, delegated operation, expected revision, rollback and audit evidence.", "source_refs": [ "SRC-001", "SRC-006", "SRC-012" ], "questions": [ { "id": "retention-legal-hold-disposition-agent-authority-idempotency-and-audit-q01", "text": "What identity, type, role, scope, version and values define retention, legal hold, disposition, agent authority, idempotency and audit?", "kind": "state", "answer_data": [ "identifiers", "types and roles", "scope and version", "values and explicit unknowns" ] }, { "id": "retention-legal-hold-disposition-agent-authority-idempotency-and-audit-q02", "text": "Which authority, source, observation, evidence and event or effective time support retention, legal hold, disposition, agent authority, idempotency and audit?", "kind": "lifecycle", "answer_data": [ "authority", "source and evidence", "observation method", "event and effective time", "confidence" ] }, { "id": "retention-legal-hold-disposition-agent-authority-idempotency-and-audit-q03", "text": "How is retention, legal hold, disposition, agent authority, idempotency and audit validated, shared, changed, contested, corrected and retained?", "kind": "retention", "answer_data": [ "validation", "access", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "retention-legal-hold-disposition-agent-authority-idempotency-and-audit-data", "name": "Retention, legal hold, disposition, agent authority, idempotency and audit data", "description": "Structured appointment or reservation data for retention, legal hold, disposition, agent authority, idempotency and audit.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-012" ] } ], "artifacts": [ { "id": "retention-legal-hold-disposition-agent-authority-idempotency-and-audit-record", "name": "Retention, legal hold, disposition, agent authority, idempotency and audit record", "description": "Versioned evidence-bearing booking record for retention, legal hold, disposition, agent authority, idempotency and audit with authority, time, provenance and access marking.", "media_or_form": [ "logical booking assertion", "booking, response, event or evidence reference" ], "serial": true, "identity_strategy": "Booking identifier plus retention-legal-hold-disposition-agent-authority-idempotency-and-audit assertion, artifact or event identifier; party name, display date, timestamp and digest never identify the booking alone.", "source_refs": [ "SRC-001", "SRC-006", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "create-booking-request", "name": "Create booking request", "description": "Record a bounded request for a scheduled service, resource or place.", "inputs": [ "requester", "purpose", "preferences", "service or resource" ], "outputs": [ "booking request" ], "preconditions": [ "requester authority, purpose, scope and privacy validate" ], "effects": [ "a request exists without implying availability or confirmation" ], "source_refs": [ "SRC-001", "SRC-009", "SRC-011" ] }, { "id": "search-and-observe-availability", "name": "Search and observe availability", "description": "Query external schedules and preserve the result and its freshness without owning availability.", "inputs": [ "request constraints", "schedule sources" ], "outputs": [ "availability observation and candidate slots" ], "preconditions": [ "source, constraints, time zone and freshness validate" ], "effects": [ "candidate allocations become comparable but remain unbooked" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011" ] }, { "id": "place-or-release-temporary-hold", "name": "Place or release temporary hold", "description": "Record a time-limited capacity hold and later confirmation, release or expiry.", "inputs": [ "candidate slot", "quantity", "hold policy" ], "outputs": [ "hold event and expiry" ], "preconditions": [ "availability, capacity, authority and idempotency validate" ], "effects": [ "capacity is tentatively allocated until terminal hold action" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-011" ] }, { "id": "propose-respond-and-counter", "name": "Propose, respond and counter", "description": "Exchange revision-qualified proposals and participant responses.", "inputs": [ "proposal", "participants", "response authority" ], "outputs": [ "response or counterproposal" ], "preconditions": [ "identity, revision, authority, deadline and recurrence scope validate" ], "effects": [ "acceptance, decline, tentative or needs-action state is attributable" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "confirm-booking", "name": "Confirm booking", "description": "Commit the allocation after required responses, terms and capacity checks.", "inputs": [ "current proposal", "responses", "terms", "capacity evidence" ], "outputs": [ "confirmed booking and confirmation event" ], "preconditions": [ "expected revision, required participants, terms, capacity and policy validate" ], "effects": [ "a planned allocation is confirmed without asserting occurrence" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-009", "SRC-011" ] }, { "id": "modify-or-reschedule-booking", "name": "Modify or reschedule booking", "description": "Create a successor revision for time, participant, resource, service or location changes.", "inputs": [ "booking", "change request", "authority" ], "outputs": [ "successor revision and change event" ], "preconditions": [ "expected head, authority, availability, recurrence scope and notices validate" ], "effects": [ "current plan changes while prior commitments remain traceable" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ] }, { "id": "cancel-expire-or-release-booking", "name": "Cancel, expire or release booking", "description": "Apply a terminal or hold-expiry transition and release allocated capacity under terms.", "inputs": [ "booking or hold", "authority", "reason" ], "outputs": [ "lifecycle event and release result" ], "preconditions": [ "transition guard, authority, terms, effective time and capacity release validate" ], "effects": [ "current booking state changes without erasing prior history" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-009" ] }, { "id": "record-arrival-no-show-or-fulfilment-assertion", "name": "Record arrival, no-show or fulfilment assertion", "description": "Attach a source-qualified observation about participation or outcome without treating status as proof by default.", "inputs": [ "booking", "observation", "observer authority" ], "outputs": [ "outcome assertion event" ], "preconditions": [ "observer, method, evidence, event time and uncertainty validate" ], "effects": [ "observed outcome is linked but remains distinct from the planned allocation" ], "source_refs": [ "SRC-001", "SRC-010", "SRC-012" ] }, { "id": "project-booking-loss-aware", "name": "Project booking loss-aware", "description": "Map a booking to a pinned interoperability profile with explicit omissions and conflicts.", "inputs": [ "booking revision", "target profile", "purpose" ], "outputs": [ "projection and loss report" ], "preconditions": [ "source and target versions, identity, time zone, recurrence and lifecycle mappings validate" ], "effects": [ "consumer receives a traceable representation with visible limitations" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-011" ] }, { "id": "validate-correct-retain-and-audit", "name": "Validate, correct, retain and audit", "description": "Run semantic checks or create a correction and authorized disposition with preserved lineage.", "inputs": [ "booking lineage", "operation authority", "policy" ], "outputs": [ "validation, successor, disposition or audit event" ], "preconditions": [ "identity, expected head, legal hold, minimum tombstone and post-write checks validate" ], "effects": [ "data changes safely without hiding accountable history" ], "source_refs": [ "SRC-001", "SRC-006", "SRC-008", "SRC-012" ] } ], "composition": [ { "target": "Party, Person, Organization, Agent and Role models", "relation": "REFERENCE", "purpose": "Resolve requester, customer, beneficiary, organizer, provider and participant identities and authority.", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-009" ] }, { "target": "Service, Resource, Place, Schedule, Slot and Availability models", "relation": "REFERENCE", "purpose": "Resolve the allocatable subject and source-qualified capacity without importing its master lifecycle.", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-009", "SRC-010", "SRC-011" ] }, { "target": "Order, Payment, Entitlement, Message, Encounter, Evidence and Audit models", "relation": "REFERENCE", "purpose": "Connect commerce, notices, actual occurrence and provenance while preserving ownership boundaries.", "required": false, "source_refs": [ "SRC-001", "SRC-009", "SRC-010", "SRC-012" ] }, { "target": "HL7 FHIR R5 Appointment, AppointmentResponse, Schedule and Slot", "relation": "ALIGN", "purpose": "Project healthcare scheduling roles, lifecycle, recurrence and availability semantics.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ] }, { "target": "iCalendar, iTIP, JSCalendar, Schema.org and TMF646", "relation": "ALIGN", "purpose": "Project calendar, reservation and service-appointment representations with declared loss.", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension identity, owner, booking governance authority and schedule, privacy and records stewards", "Booking-type, service, resource, location, schedule, terms, lifecycle, interoperability and retention registries", "Master mappings for parties, roles, mandates, services, resources, locations, schedules, orders, payments, messages, encounters and audit logs", "Request, availability, hold, confirmation, change, cancellation, outcome, access, retention and agent-operation policies" ], "namespace_guidance": "Mint stable IDs for booking series, instances, proposals, responses and events. Preserve authoritative booking, schedule and slot IDs and external party, service, resource, location, order and payment identities; never use a party name or display time as identity.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local booking, schedule, resource, service and policy registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize a booking by authoritative source plus booking identifier and current lineage head, not by participant names, subject, time, location or digest.", "Normalize timestamps for comparison while preserving original offset, named time-zone intent, source precision and recurrence identifiers." ], "patch_rules": [ "Extensions declare booking family, target finding, semantics, authority, state-machine, privacy and interoperability impact.", "Confirmed history is append-only. Corrections, reschedules and profile upgrades create successor revisions and preserve prior proposals, responses and events." ], "compatibility_rules": [ "Unknown additive fields may be ignored only when identity, allocation, participants, time, recurrence, lifecycle, authority and provenance remain intact.", "FHIR, iCalendar, JSCalendar, Schema.org and TMF646 mappings pin versions and declare omissions, state conflicts and round-trip limits." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system booking or reservation identifier qualified by source and booking class.", "Governed globally resolvable calendar UID or reservation identifier with source authority.", "Dimension UUID when no authoritative or governed global identifier exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; retain named time-zone intent where recurrence or future local time matters, and separate request, booking, start, end, event, effective, observed and knowledge times.", "serial_naming_rule": "Use {booking-id}--{artifact-kind}--{assertion-or-event-id}; never use participant name, display date, timestamp or digest alone.", "integrity_rule": "Store digest, media type, booking and revision binding, source and profile versions, authority, event and knowledge times, time-zone intent, access marking and provenance." }, "policies": [ "Availability observation, temporary hold, participant acceptance, confirmed booking, actual attendance and service fulfilment are separate attributable states.", "Booking ownership does not transfer ownership of parties, services, resources, schedules, orders, payments, messages, encounters or generic audit records.", "Reschedule, cancellation, expiry, no-show, fulfilment and correction append events and lineage and never silently rewrite earlier commitments.", "Agents may search, validate and project within allowlisted policy, but confirmation, cancellation, destructive release, protected disclosure and disposition require delegated authority and policy-defined controls." ], "crud": { "read": [ "Resolve Dimension policy, booking identity and lineage, participants, allocation, time-zone intent, recurrence, terms, availability evidence, current status, provenance and access purpose." ], "create": [ "Record request, proposal or booking identity, source, purpose, allocation, participants, time, authority, terms and provenance atomically; confirmation requires current capacity and required responses." ], "update": [ "Append proposal, response, confirmation, change, cancellation, expiry, outcome or correction events with actor, authority, reason, event and knowledge time and expected revision; never overwrite committed history." ], "delete": [ "Apply retention, legal-hold and audit policy; release live capacity separately from removing eligible copies, and preserve required booking lineage and minimum tombstone evidence." ] }, "roles": [ { "name": "Booking owner or requester", "responsibilities": [ "States need, preferences and authorized change or cancellation requests." ] }, { "name": "Organizer or provider", "responsibilities": [ "Owns allocation confirmation, delivery coordination and source-qualified outcome assertions." ] }, { "name": "Participant or beneficiary", "responsibilities": [ "Responds for an authorized role and receives minimum necessary booking details." ] }, { "name": "Schedule and resource steward", "responsibilities": [ "Maintains external availability, capacity, holds and release integrity." ] }, { "name": "Booking service operator", "responsibilities": [ "Maintains booking state machine, concurrency, notices and recovery." ] }, { "name": "Privacy and records steward", "responsibilities": [ "Controls protected details, retention, legal hold, disposition and auditability." ] }, { "name": "Interoperability steward", "responsibilities": [ "Owns pinned projections, mappings, loss reports and compatibility tests." ] } ], "access": { "default_rule": "Deny private participant details, contact endpoints, virtual locations, service purpose, payment references and booking history; disclose only purpose-bound minimum fields authorized for the audience.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Participant-self, provider, operator, emergency, auditor, regulator or court access cites authority and remains minimum-necessary, time-limited and separately logged." ], "audit_requirements": [ "Log actor, agent, role, purpose, booking, operation, policy, RFC 3339 time, affected revision or fields, source revision and outcome without copying protected contents unnecessarily." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension booking, schedule, resource, service, access, retention and agent-operation policies.", "Read this model and linked party, resource, service, location, order, payment, message, encounter, evidence and audit models before mutation." ] } }, "coverage": { "claim": "Single-provider codex draft covers the booking aggregate from request and availability observation through temporary hold, proposal, participant response, confirmation, modification, reschedule, cancellation, expiry and outcome assertion, plus terms and commerce references, communications, provenance, validation, access, retention and version-pinned projections. Coverage is broad but explicitly not universal: no approved relation rows exist, sector booking families (transport, lodging, dining, healthcare procedures, hearings, dispatch) are unmodelled, the crosswalk is named but not enumerated field by field, waitlist operations have no function, erasure inside append-only lineage has no rule, and the 72 questions instantiate only three templated shapes across 24 findings.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Booking, series, occurrence, proposal, response, allocation and event identities are distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Appointment, reservation, hold, event and actual encounter boundaries are explicit." }, { "dimension": "direct properties", "status": "covered", "notes": "Purpose, participants, allocation, time, recurrence, status, terms and lineage are first-class." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Availability, conflict, response, attendance and outcome observations are source-qualified." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Request, search, hold, respond, confirm, modify, cancel, observe, project and audit are governed." }, { "dimension": "composition", "status": "covered", "notes": "Parties, resources, services, schedules, orders, payments, messages, encounters and audit masters remain external." }, { "dimension": "lifecycle", "status": "covered", "notes": "Request, proposal, hold, confirmation, waitlist, change, cancellation, expiry and outcome preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Participant roles, reserved subjects, schedule slots, predecessor, successor and external masters use typed links." }, { "dimension": "temporal", "status": "covered", "notes": "Request, booking, start, end, hold, response, event, effective, observed and knowledge times stay distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Physical, virtual and mixed locations and access requirements are referenced." }, { "dimension": "provenance", "status": "covered", "notes": "Requests, proposals, responses, transitions, observations, projections and corrections preserve responsible-agent provenance." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Requester, organizer, participant, provider, schedule, privacy, records and interoperability responsibilities are separated." }, { "dimension": "validation and quality", "status": "covered", "notes": "Identity, revision, time zone, recurrence, participant, availability, capacity, transition and concurrency checks are explicit." }, { "dimension": "access and privacy", "status": "covered", "notes": "Purpose-bound views, protected contacts and locations and deny-by-default history are explicit." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Capacity release, live-state termination, retained lineage, legal hold, copy disposition and tombstones are distinguished." }, { "dimension": "interoperability", "status": "covered", "notes": "FHIR, iCalendar, JSCalendar, Schema.org and TMF646 projections are versioned and loss-aware." } ], "known_omissions": [ "No successful independent Claude or Grok result was available; later scheduling, travel, hospitality, healthcare and legal review is required before canonical promotion.", "No approved relation rows were supplied; proposed links to Encounter and to party, resource, service, location, schedule, order, payment, message, evidence and audit models remain holds.", "Sector-specific booking families such as transport, lodging, dining, healthcare procedures, court hearings and workforce dispatch require separate profiles.", "TMF646 source material used here is v4.0.1; a later TM Forum v5 profile should be reviewed when the full normative artifact is available." ], "conflicts": [ "A confirmed booking can coexist with stale availability, a participant decline, a failed payment or a provider-side cancellation and requires explicit precedence rules.", "FHIR appointment status includes arrived, checked-in, fulfilled and no-show, but these states still need an attributable observation and do not prove all real-world facts.", "Calendar recurrence, named time-zone intent and offset timestamps can diverge after time-zone rule changes or lossy format projection." ], "regional_assumptions": [ "Cancellation rights, deposits, refunds, no-show terms, accessibility obligations, retention and emergency access depend on jurisdiction and sector.", "Healthcare terminology and workflow from FHIR are useful structural inputs but do not make the model healthcare-specific.", "Schema.org and calendar formats support discovery and exchange but do not establish allocation authority, capacity truth or contractual effect." ], "adversarial_checks": [ "Reject confirmation whose booking identity, current revision, participant authority, allocation, time-zone intent or capacity evidence cannot be resolved.", "Reject availability, acceptance, calendar delivery, check-in, no-show or fulfilment represented as proof of another state without a qualified source.", "Reject silent time, recurrence, participant, resource, status or terms mutation and any cancellation or correction without authority and lineage.", "Reject a stale participant response, proposal or update applied to a newer organizer revision without explicit conflict handling.", "Reject an agent operation that confirms, cancels, releases protected capacity, broadens disclosure or destroys held records without delegated authority." ] }, "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", "rationale": "Two axes must not be conflated. On the record plane a registry value such as standalone-mm describes how the model record is stored, versioned and governed in the registry; it is never a subject-model entry kind, and here frozen_context was empty so no frozen registry value could be read at all - that absence is carried as a publication hold rather than silently resolved. On the subject axis the most defensible schema kind is aggregate: the booking has one root identity (authoritative source plus booking identifier plus current lineage head), a transactional confirmation invariant that binds current capacity to required participant responses, and it composes proposals, responses, booking-scoped party roles, status events and booking-specific evidence that have no independent life outside the root, while party, resource, service, place, schedule, slot, order, payment, message, encounter and audit masters remain external references. event is rejected despite the display name because the record is a mutable, revisioned, long-lived commitment whose typed transitions are constituents rather than the root; entity understates the owned composition and append-only lineage; relationship understates independent identity, terms, communications and lifecycle; pattern, mixin, registry and classifier do not describe an instance-bearing subject at all." }, "decisions": [ { "concept": "Entry kind aggregate for WM-ACT-026", "disposition": "accepted", "rationale": "One root identity plus lineage head, an atomic confirmation invariant over capacity and required responses, and owned proposals, responses, roles and status events satisfy aggregate semantics better than entity, event or relationship." }, { "concept": "Display name 'Appointment / Reservation Event'", "disposition": "rejected as an aggregate-root label; rename deferred", "rationale": "The word Event collides with the schema kind event and with the model's own out-of-scope actual occurrence, inviting exactly the confusion the Encounter boundary note tries to prevent. A draft may publish under the current name only with the rename hold visible." }, { "concept": "Record-plane registry value used as subject entry kind", "disposition": "rejected", "rationale": "A record-plane classifier such as standalone-mm answers how the record is governed, not what the subject is; with frozen_context empty there is additionally no verified registry value to copy, so the entry kind is set from subject evidence alone." }, { "concept": "Artifact serial naming rule {booking-id}--{artifact-kind}--{assertion-or-event-id}", "disposition": "rejected as written; occurrence discriminator required", "rationale": "SRC-005 and SRC-007 identify a single occurrence by series identifier plus recurrence identifier. If booking-id resolves to the series, occurrence-scoped artifacts for an overridden or excluded instance are ambiguous, which breaks the model's own artifact identity guarantee." }, { "concept": "Question kind labels across all 72 questions", "disposition": "rejected as semantic metadata; re-typing deferred", "rationale": "The same three templated texts carry rotating kinds - one identical 'What identity, type, role, scope, version and values define X?' shape appears as identity, definition, relationship, requirement, ownership, classification, composition and state. The kind axis is positional, not semantic, and must not be presented as a taxonomy." }, { "concept": "Coverage checklist rows relationships, retention and deletion, interoperability", "disposition": "downgraded from covered to partial", "rationale": "No approved relation rows exist, no redaction rule covers personal data inside append-only lineage, and the crosswalk names five formats without enumerating field or state mappings while TMF646 v5 remains unreviewed. Sixteen of sixteen covered is an overclaim at draft stage." }, { "concept": "Capacity hold ownership between booking and slot or schedule", "disposition": "accepted with an explicit boundary qualifier", "rationale": "SRC-002 and SRC-003 keep capacity, availability and hold expiry with the slot and schedule owners. The booking may record a source-qualified hold reference, deadline and its own expectation, but must not be read as decrementing or enforcing capacity; the function name place-or-release-temporary-hold needs the record-only qualifier its description already states." }, { "concept": "Arrived, checked-in, no-show and fulfilled states inside booking lifecycle", "disposition": "accepted as source-grounded assertions; rejected as proof", "rationale": "SRC-001 carries these in FHIR R5 Appointment status, so their presence is sourced rather than invented, but the declared conflict and adversarial check that status never proves attendance or service performance must survive into every published projection." }, { "concept": "Bundled function validate-correct-retain-and-audit", "disposition": "rejected as one capability; split deferred", "rationale": "It fuses agent-allowlisted validation with authority-gated correction and destructive disposition, contradicting the policy that agents may validate and project freely while disposition requires delegated authority. Under the single-provider waiver add_functions must stay empty, so this is carried as a hold rather than repaired here." }, { "concept": "Missing waitlist enrollment, promotion and expiry function", "disposition": "deferred", "rationale": "Waitlist appears in the purpose, in_scope list and the proposed-held-pending-confirmed-waitlisted status finding, yet no function covers enrollment, position, promotion or lapse. The gap is recorded because no second provider exists to supply the function." }, { "concept": "RFC 3339 timestamp rule with no RFC 3339 source row", "disposition": "rejected as unsourced; pin before promotion", "rationale": "artifact_rules impose a normative RFC 3339 format requirement while the only adjacent source is SRC-008 RFC 9557, which extends rather than defines that format. A normative rule must cite the standard it enforces." }, { "concept": "Uniform artifact media_or_form across all 24 artifacts", "disposition": "accepted for the logical layer; media differentiation deferred", "rationale": "A single logical booking assertion form is coherent at draft, but the crosswalk and communications artifacts claim loss-aware projection and an integrity rule that stores media type, which cannot be tested without concrete serializations such as text/calendar, JSCalendar JSON and FHIR JSON." }, { "concept": "Bundle cohesion of terms, commerce, communications, evidence and provenance", "disposition": "accepted for draft; re-split deferred", "rationale": "The perfectly uniform six-by-two-by-two grid forced commerce terms and provenance or quality into one bundle. The content is sound but the decomposition is template-driven rather than domain-driven and should be revisited before canonical promotion." }, { "concept": "Cross-participant disclosure of responses and contact endpoints", "disposition": "deferred", "rationale": "The access default denies contact endpoints and history, but never adjudicates whether one participant may see another participant's response state or delegation, which SRC-005 and SRC-006 make a live interoperability and privacy decision rather than an implementation detail." }, { "concept": "Erasure of personal data inside append-only confirmed history", "disposition": "deferred", "rationale": "Tombstones, legal hold and disposition authority exist, but no rule governs redaction or pseudonymization of participant identifiers, contacts and free-text purpose embedded in retained proposals, responses and message references, leaving append-only lineage and erasure obligations unreconciled." }, { "concept": "Service layers under the single-provider waiver", "disposition": "passed through unmerged from codex", "rationale": "merge_service_layers stays true only for schema compatibility; with no admitted second provider the deterministic synthesizer has nothing to merge, so the dimension, canon, artifact, policy, CRUD, role, access and bootstrap blocks publish verbatim as single-source content and must be labelled as such." } ], "publicationHolds": [ "Live source and version verification is outstanding for all twelve sources; verify every URL resolves and every pin is exact before promotion, with priority on SRC-009 and SRC-010 Schema.org V30.0 dated 19 March 2026, SRC-011 TMF646 whose URL slug reads r19-0-0 against a declared v4.0.1 of November 2019, and the four FHIR R5 5.0.0 resource anchors.", "Independent second-provider review is absent by explicit repository-owner authorization dated 2026-09-06: Claude was waived after repeated timeouts and Grok was waived as unavailable. This audit is a local no-tools adversarial pass over the codex result and does not constitute external review; the waiver and this limitation must appear in every published artifact.", "The record stays reviewable-draft, never canonical, while the frozen registry record is unavailable - frozen_context was supplied empty, so the record-plane classification, registry lineage and prior entry-kind history for vr.wm-act-026 could not be checked against the published subject kind.", "No approved relation rows were supplied; all neighbor links to Encounter and to party, resource, service, location, schedule, slot, order, payment, message, evidence and audit models publish as proposals under the relationship contract and must not be rendered as accepted edges.", "Artifact identity is not yet normative: the serial naming rule needs an occurrence discriminator for recurring series, and the question-kind axis must be re-typed semantically or demoted to a non-normative rotation marker, before either is cited as a governance guarantee.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Review the current TM Forum appointment management specification, including any v5 profile, against the SRC-011 v4.0.1 material and reconcile state, hold and capacity semantics.", "Enumerate the field-level and state-level crosswalk between FHIR R5 Appointment and AppointmentResponse, RFC 5545 and 5546, RFC 8984 JSCalendar, Schema.org Reservation and TMF646, with a round-trip test corpus and a declared loss class per direction.", "Define a redaction and pseudonymization rule for personal data embedded in append-only proposals, responses, communications references and status events, reconciled with legal hold, tombstone minima and jurisdictional erasure rights.", "Adjudicate cross-participant disclosure: whether a participant may see other participants' response state, delegation chain, contact endpoints or virtual location, grounded in ITIP and JSCalendar participant visibility semantics.", "Specify waitlist enrollment, position, promotion, lapse and notification operations, and split the hold lifecycle authority explicitly between the booking aggregate and the slot or schedule steward.", "Develop sector booking profiles for transport, lodging, dining, healthcare procedures, court hearings and workforce dispatch, and derive the precedence rules for a confirmed booking coexisting with stale availability, a participant decline, a failed payment or a provider-side cancellation.", "Add an explicit source row for the base timestamp standard enforced by artifact_rules and confirm that named time-zone intent survives recurrence expansion after time-zone rule changes." ] }, "statistics": { "sources": 12, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }