# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T20:04:02Z", "synthesisSha256": "53c689298de30fbc08dcc2182995a9a3a28e72af6246dac09e555299f4aa862b", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-FLW-009", "registryId": "vr.wm-flw-009", "name": "Journey / Trip", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.FLW.MOB" ], "tags": [ "journey", "trip", "phy.flw.mob" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-flw-009-journey-trip/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-flw-009", "model": { "registry_id": "vr.wm-flw-009", "model_id": "WM-FLW-009", "name": "Journey / Trip", "entry_kind": "aggregate", "purpose": "Represent one governed planned or actual movement of a person or vehicle between declared endpoints with ordered legs, typed clocks, observations and correction lineage without becoming its route, itinerary, service, subject or booking.", "scope_statement": "Owns journey and revision identity, kind and boundary; subject and journey-role bindings; origin, destination, calls and journey-scoped endpoint assertions; ordered leg or stage composition; purpose and wider-travel relationships; requested, planned, target, estimated, predicted, observed and actual clocks; selected-plan references and journey constraints; lifecycle and progress assertions; position and trajectory evidence links; disruption, outcome, measurement, provenance, reconciliation, access, retention and loss-aware projections. Person, vehicle, organization, route, itinerary, network, place, stop, service, schedule, booking, ticket, fare, shipment, incident, weather, payment, sensor, evidence and document masters remain external.", "in_scope": [ "Journey identity, revision, kind, subject roles, origin, destination, purpose, wider travel and subtrip relationships", "Ordered legs, stages, modes, calls, route and service references, selected plan, typed times, execution state, progress and trajectory evidence", "Deviations, outcomes, derived measures, reconciliation, provenance, privacy, access, retention and interoperability" ], "out_of_scope": [ "Owning person, organization, vehicle, route, itinerary, network, place, stop, service, schedule, booking, ticket, fare, shipment, incident, weather, payment, sensor, evidence or document master lifecycles", "Equating a person trip with a vehicle journey, a route with an itinerary, a plan with actual movement, a position fix with a trajectory, boarding with a whole trip or a statistical count with operational truth", "Autonomous consequential rerouting, safety intervention, passenger-rights determination, border or regulatory decision, protected live-location disclosure or irreversible deletion" ], "boundary_notes": [ { "neighbor": "WM-FLW-007 Passenger Mobility / Transit", "distinction": "Passenger Mobility owns transit networks, services, schedules, fares and aggregate mobility context. Journey / Trip owns one movement episode and may reference transit service or passenger-trip views without assuming inheritance.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ] }, { "neighbor": "WM-FLW-010 Route / Itinerary", "distinction": "A route is a reusable or selected spatial path and an itinerary is a planning result or ordered visit plan. A journey is the identity-bearing intended or undertaken movement that references them and preserves actual divergence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-010", "SRC-014", "SRC-015" ] }, { "neighbor": "Person, Vehicle, Organization and Transport Service", "distinction": "The journey assigns journey-scoped roles and references. Subject identity, vehicle lifecycle, operator authority, network, schedule and service operation remain externally mastered.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005" ] }, { "neighbor": "WM-FLW-011 Shipment / Consignment", "distinction": "A shipment may reference one or more transport journeys. Cargo, consignment, custody and logistics lifecycle remain shipment-owned and do not become journey composition.", "source_refs": [ "SRC-010", "SRC-011" ] }, { "neighbor": "Observation, Sensor, Incident and Evidence", "distinction": "The journey binds source-qualified position, passing, disruption and completion assertions. Sensor streams, generic incidents and evidentiary records retain independent identity and authority.", "source_refs": [ "SRC-005", "SRC-006", "SRC-008", "SRC-009", "SRC-019" ] }, { "neighbor": "Travel, Tour and Tourism Trip", "distinction": "A wider travel episode or return journey may contain multiple one-way trips and activities. Tourism status depends on purpose, destination, usual environment and duration under a statistical profile.", "source_refs": [ "SRC-011", "SRC-012", "SRC-013" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Transmodel v6.2 Data Dictionary", "organization": "CEN Transmodel", "url": "https://transmodel-cen.eu/wp-content/uploads/2024/09/Transmodel-v6.2-Data-Dictionary.pdf", "version_or_date": "Transmodel v6.2, September 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Defines passenger trips, trip patterns, legs, vehicle journeys, service journeys, calls and related transport concepts." }, { "id": "SRC-002", "title": "Passenger Information Tutorial", "organization": "CEN Transmodel", "url": "https://transmodel-cen.eu/index.php/passenger-information-tutorial/", "version_or_date": "Tutorial accessed 2026-09-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Explains that a passenger trip is movement between places, may contain consecutive legs and differs from a vehicle journey." }, { "id": "SRC-003", "title": "Transmodel at a glance", "organization": "CEN Transmodel", "url": "https://transmodel-cen.eu/index.php/transmodel-at-a-glance/", "version_or_date": "Transmodel v6 overview accessed 2026-09-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Separates service journey, vehicle journey, dead run, journey pattern and operating block." }, { "id": "SRC-004", "title": "GTFS Schedule Reference", "organization": "MobilityData", "url": "https://gtfs.org/documentation/schedule/reference/", "version_or_date": "Living specification accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Defines routes, trips, service dates, stops, stop sequences, shapes, frequencies and scheduled passing times." }, { "id": "SRC-005", "title": "GTFS Realtime Reference", "organization": "MobilityData", "url": "https://gtfs.org/documentation/realtime/reference/", "version_or_date": "GTFS Realtime 2.0, accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Defines trip updates, vehicle positions, stop-time predictions, schedule relationships, service alerts and observation timestamps." }, { "id": "SRC-006", "title": "GTFS Realtime Trip Updates", "organization": "MobilityData", "url": "https://gtfs.org/documentation/realtime/feed-entities/trip-updates/", "version_or_date": "Guidance accessed 2026-09-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Distinguishes scheduled trips, predictions, measured past events, cancellation, addition, rerouting and uncertainty." }, { "id": "SRC-007", "title": "OGC Moving Features standards", "organization": "Open Geospatial Consortium", "url": "https://www.ogc.org/standards/movingfeatures/", "version_or_date": "Standards catalogue accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Catalogues format-neutral movement concepts and XML, CSV, JSON and API projections." }, { "id": "SRC-008", "title": "OGC API Moving Features Part 1 Core", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/22-003r3/22-003r3.html", "version_or_date": "OGC 22-003r3, version 1.0, 24 October 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Defines moving-feature collections, static identity and access to temporal geometry and temporal properties." }, { "id": "SRC-009", "title": "OGC Moving Features Access", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/16-120r3/16-120r3.html", "version_or_date": "OGC 16-120r3, version 1.0, 2017", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Defines trajectory operations including position, time and velocity queries and conformance tests." }, { "id": "SRC-010", "title": "ISO 19141 Geographic information - Schema for moving features", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/41445.html", "version_or_date": "ISO 19141:2008, confirmed 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Defines geometric movement, planned-route deviation and moving-feature interactions while excluding non-spatial lifecycle change." }, { "id": "SRC-011", "title": "Glossary for Transport Statistics, sixth edition", "organization": "UNECE, Eurostat and International Transport Forum", "url": "https://unece.org/info/Transport/pub/411667", "version_or_date": "Sixth edition, February 2026", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Provides current harmonized transport terminology and statistical definitions across modes." }, { "id": "SRC-012", "title": "National Travel Survey 2024: notes and definitions", "organization": "United Kingdom Department for Transport", "url": "https://www.gov.uk/government/statistics/national-travel-survey-2024/nts-2024-notes-and-definitions", "version_or_date": "Accredited Official Statistics, 2024 release", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Defines a trip as one-way travel with one main purpose and stages by mode or vehicle change." }, { "id": "SRC-013", "title": "International Recommendations for Tourism Statistics 2008", "organization": "United Nations Statistics Division", "url": "https://unstats.un.org/unsd/tradeserv/IRTS%202008%20edited%20whitecover.pdf", "version_or_date": "ST/ESA/STAT/SER.M/83/Rev.1, 2010", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Defines tourism-trip purpose, origin, destination, duration, mode, travel party and the boundary between travel and tourism." }, { "id": "SRC-014", "title": "Commission Delegated Regulation (EU) 2024/490", "organization": "European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32024R0490", "version_or_date": "29 November 2023, published 13 February 2024", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Amends EU multimodal travel-information rules and distinguishes static, historic, observed and dynamic data." }, { "id": "SRC-015", "title": "Trip", "organization": "Schema.org Community Group", "url": "https://schema.org/Trip", "version_or_date": "Vocabulary page accessed 2026-09-06", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Provides a lightweight web alignment for trip, itinerary, subtrip, provider, departure and arrival." }, { "id": "SRC-016", "title": "GeoSPARQL", "organization": "Open Geospatial Consortium", "url": "https://www.ogc.org/standards/geosparql/", "version_or_date": "GeoSPARQL 1.1, OGC 22-047r1", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Defines interoperable geospatial feature, geometry and query semantics for place and path projections." }, { "id": "SRC-017", "title": "Time Ontology in OWL", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/owl-time/", "version_or_date": "Candidate Recommendation Draft, 15 November 2022", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Defines instants, intervals, duration, ordering, temporal position, reference systems and precision." }, { "id": "SRC-018", "title": "RFC 3339: Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Defines interoperable timestamps with seconds and explicit offsets for journey event and observation clocks." }, { "id": "SRC-019", "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-06T19:58:00Z", "relevance": "Defines attribution, derivation, revision, invalidation and delegation for journey assertions and evidence." }, { "id": "SRC-020", "title": "Data Quality Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-dqv/", "version_or_date": "W3C Working Group Note, 15 December 2016", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Defines quality measurements, annotations, policies and provenance for schedule, trajectory and reconciliation data." }, { "id": "SRC-021", "title": "ODRL Information Model 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "W3C Recommendation, 15 February 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T19:58:00Z", "relevance": "Defines permissions, prohibitions, duties and constraints for sensitive trip and live-location data." } ], "structure": { "bundles": [ { "id": "journey-identity-class-and-subject", "name": "Journey identity, class and subject", "description": "Groups the governed Journey / Trip concern for journey identity, class and subject.", "rationale": "Establish one movement episode without collapsing traveller, vehicle, route, itinerary or service masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-019", "SRC-003", "SRC-012", "SRC-013" ], "layers": [ { "id": "identity-scope-and-version", "name": "Identity, scope and version", "description": "Groups Journey / Trip context for identity, scope and version without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-019" ], "findings": [ { "id": "journey-identity-namespace-version-and-successor", "name": "Journey identity, namespace, version and successor", "description": "Records journey identity, namespace, version and successor as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-019" ], "questions": [ { "id": "journey-identity-namespace-version-and-successor-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish journey identity, namespace, version and successor?", "kind": "identity", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "journey-identity-namespace-version-and-successor-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access journey identity, namespace, version and successor, and under what role or authority?", "kind": "provenance", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "journey-identity-namespace-version-and-successor-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify journey identity, namespace, version and successor?", "kind": "quality", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "journey-identity-namespace-version-and-successor-data", "name": "Journey identity, namespace, version and successor data", "description": "Typed journey-scoped values and references needed to answer the governed questions for journey identity, namespace, version and successor.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-019" ] } ], "artifacts": [ { "id": "journey-identity-namespace-version-and-successor-artifact", "name": "Journey identity, namespace, version and successor evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting journey identity, namespace, version and successor.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-019" ] } ], "inline_only_rationale": null }, { "id": "journey-boundary-origin-destination-and-completion-rule", "name": "Journey boundary, origin, destination and completion rule", "description": "Records journey boundary, origin, destination and completion rule as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-019" ], "questions": [ { "id": "journey-boundary-origin-destination-and-completion-rule-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish journey boundary, origin, destination and completion rule?", "kind": "definition", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "journey-boundary-origin-destination-and-completion-rule-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access journey boundary, origin, destination and completion rule, and under what role or authority?", "kind": "ownership", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "journey-boundary-origin-destination-and-completion-rule-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify journey boundary, origin, destination and completion rule?", "kind": "validation", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "journey-boundary-origin-destination-and-completion-rule-data", "name": "Journey boundary, origin, destination and completion rule data", "description": "Typed journey-scoped values and references needed to answer the governed questions for journey boundary, origin, destination and completion rule.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-019" ] } ], "artifacts": [ { "id": "journey-boundary-origin-destination-and-completion-rule-artifact", "name": "Journey boundary, origin, destination and completion rule evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting journey boundary, origin, destination and completion rule.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-019" ] } ], "inline_only_rationale": null } ] }, { "id": "kind-subject-purpose-and-grouping", "name": "Kind, subject, purpose and grouping", "description": "Groups Journey / Trip context for kind, subject, purpose and grouping without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013" ], "findings": [ { "id": "person-trip-vehicle-journey-service-journey-and-dead-run-kind", "name": "Person trip, vehicle journey, service journey and dead run kind", "description": "Records person trip, vehicle journey, service journey and dead run kind as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013" ], "questions": [ { "id": "person-trip-vehicle-journey-service-journey-and-dead-run-kind-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish person trip, vehicle journey, service journey and dead run kind?", "kind": "classification", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "person-trip-vehicle-journey-service-journey-and-dead-run-kind-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access person trip, vehicle journey, service journey and dead run kind, and under what role or authority?", "kind": "authority", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "person-trip-vehicle-journey-service-journey-and-dead-run-kind-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify person trip, vehicle journey, service journey and dead run kind?", "kind": "security", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "person-trip-vehicle-journey-service-journey-and-dead-run-kind-data", "name": "Person trip, vehicle journey, service journey and dead run kind data", "description": "Typed journey-scoped values and references needed to answer the governed questions for person trip, vehicle journey, service journey and dead run kind.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "person-trip-vehicle-journey-service-journey-and-dead-run-kind-artifact", "name": "Person trip, vehicle journey, service journey and dead run kind evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting person trip, vehicle journey, service journey and dead run kind.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "traveller-vehicle-trip-purpose-wider-travel-and-subtrip", "name": "Traveller, vehicle, trip purpose, wider travel and subtrip", "description": "Records traveller, vehicle, trip purpose, wider travel and subtrip as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013" ], "questions": [ { "id": "traveller-vehicle-trip-purpose-wider-travel-and-subtrip-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish traveller, vehicle, trip purpose, wider travel and subtrip?", "kind": "relationship", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "traveller-vehicle-trip-purpose-wider-travel-and-subtrip-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access traveller, vehicle, trip purpose, wider travel and subtrip, and under what role or authority?", "kind": "constraint", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "traveller-vehicle-trip-purpose-wider-travel-and-subtrip-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify traveller, vehicle, trip purpose, wider travel and subtrip?", "kind": "privacy", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "traveller-vehicle-trip-purpose-wider-travel-and-subtrip-data", "name": "Traveller, vehicle, trip purpose, wider travel and subtrip data", "description": "Typed journey-scoped values and references needed to answer the governed questions for traveller, vehicle, trip purpose, wider travel and subtrip.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "traveller-vehicle-trip-purpose-wider-travel-and-subtrip-artifact", "name": "Traveller, vehicle, trip purpose, wider travel and subtrip evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting traveller, vehicle, trip purpose, wider travel and subtrip.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "places-paths-legs-and-modes", "name": "Places, paths, legs and modes", "description": "Groups the governed Journey / Trip concern for places, paths, legs and modes.", "rationale": "Represent ordered movement composition while places, routes, networks and transport assets retain external authority.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-016", "SRC-011", "SRC-012" ], "layers": [ { "id": "endpoints-calls-and-path", "name": "Endpoints, calls and path", "description": "Groups Journey / Trip context for endpoints, calls and path without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-016" ], "findings": [ { "id": "origin-destination-via-place-stop-call-and-activity-place", "name": "Origin, destination, via place, stop, call and activity place", "description": "Records origin, destination, via place, stop, call and activity place as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-016" ], "questions": [ { "id": "origin-destination-via-place-stop-call-and-activity-place-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish origin, destination, via place, stop, call and activity place?", "kind": "spatial", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "origin-destination-via-place-stop-call-and-activity-place-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access origin, destination, via place, stop, call and activity place, and under what role or authority?", "kind": "process", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "origin-destination-via-place-stop-call-and-activity-place-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify origin, destination, via place, stop, call and activity place?", "kind": "retention", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "origin-destination-via-place-stop-call-and-activity-place-data", "name": "Origin, destination, via place, stop, call and activity place data", "description": "Typed journey-scoped values and references needed to answer the governed questions for origin, destination, via place, stop, call and activity place.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-016" ] } ], "artifacts": [ { "id": "origin-destination-via-place-stop-call-and-activity-place-artifact", "name": "Origin, destination, via place, stop, call and activity place evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting origin, destination, via place, stop, call and activity place.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "route-journey-pattern-shape-trajectory-and-deviation-reference", "name": "Route, journey pattern, shape, trajectory and deviation reference", "description": "Records route, journey pattern, shape, trajectory and deviation reference as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-016" ], "questions": [ { "id": "route-journey-pattern-shape-trajectory-and-deviation-reference-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish route, journey pattern, shape, trajectory and deviation reference?", "kind": "relationship", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "route-journey-pattern-shape-trajectory-and-deviation-reference-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access route, journey pattern, shape, trajectory and deviation reference, and under what role or authority?", "kind": "event", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "route-journey-pattern-shape-trajectory-and-deviation-reference-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify route, journey pattern, shape, trajectory and deviation reference?", "kind": "access", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "route-journey-pattern-shape-trajectory-and-deviation-reference-data", "name": "Route, journey pattern, shape, trajectory and deviation reference data", "description": "Typed journey-scoped values and references needed to answer the governed questions for route, journey pattern, shape, trajectory and deviation reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-016" ] } ], "artifacts": [ { "id": "route-journey-pattern-shape-trajectory-and-deviation-reference-artifact", "name": "Route, journey pattern, shape, trajectory and deviation reference evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting route, journey pattern, shape, trajectory and deviation reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "ordered-legs-modes-and-transfers", "name": "Ordered legs, modes and transfers", "description": "Groups Journey / Trip context for ordered legs, modes and transfers without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-012" ], "findings": [ { "id": "leg-stage-sequence-mode-vehicle-service-and-predecessor", "name": "Leg, stage, sequence, mode, vehicle, service and predecessor", "description": "Records leg, stage, sequence, mode, vehicle, service and predecessor as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-012" ], "questions": [ { "id": "leg-stage-sequence-mode-vehicle-service-and-predecessor-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish leg, stage, sequence, mode, vehicle, service and predecessor?", "kind": "composition", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "leg-stage-sequence-mode-vehicle-service-and-predecessor-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access leg, stage, sequence, mode, vehicle, service and predecessor, and under what role or authority?", "kind": "measurement", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "leg-stage-sequence-mode-vehicle-service-and-predecessor-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify leg, stage, sequence, mode, vehicle, service and predecessor?", "kind": "exception", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "leg-stage-sequence-mode-vehicle-service-and-predecessor-data", "name": "Leg, stage, sequence, mode, vehicle, service and predecessor data", "description": "Typed journey-scoped values and references needed to answer the governed questions for leg, stage, sequence, mode, vehicle, service and predecessor.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "leg-stage-sequence-mode-vehicle-service-and-predecessor-artifact", "name": "Leg, stage, sequence, mode, vehicle, service and predecessor evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting leg, stage, sequence, mode, vehicle, service and predecessor.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "access-egress-transfer-connection-wait-and-interchange", "name": "Access, egress, transfer, connection, wait and interchange", "description": "Records access, egress, transfer, connection, wait and interchange as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-012" ], "questions": [ { "id": "access-egress-transfer-connection-wait-and-interchange-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish access, egress, transfer, connection, wait and interchange?", "kind": "process", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "access-egress-transfer-connection-wait-and-interchange-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access access, egress, transfer, connection, wait and interchange, and under what role or authority?", "kind": "evidence", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "access-egress-transfer-connection-wait-and-interchange-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify access, egress, transfer, connection, wait and interchange?", "kind": "interoperability", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "access-egress-transfer-connection-wait-and-interchange-data", "name": "Access, egress, transfer, connection, wait and interchange data", "description": "Typed journey-scoped values and references needed to answer the governed questions for access, egress, transfer, connection, wait and interchange.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "access-egress-transfer-connection-wait-and-interchange-artifact", "name": "Access, egress, transfer, connection, wait and interchange evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting access, egress, transfer, connection, wait and interchange.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "plan-time-and-traveller-constraints", "name": "Plan, time and traveller constraints", "description": "Groups the governed Journey / Trip concern for plan, time and traveller constraints.", "rationale": "Keep plans and time assertions typed so a prediction or routing result cannot overwrite observed movement.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-017", "SRC-018", "SRC-002", "SRC-012", "SRC-014", "SRC-015" ], "layers": [ { "id": "time-basis-passing-and-duration", "name": "Time basis, passing and duration", "description": "Groups Journey / Trip context for time basis, passing and duration without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-017", "SRC-018" ], "findings": [ { "id": "operating-day-time-zone-start-end-passing-and-duration", "name": "Operating day, time zone, start, end, passing and duration", "description": "Records operating day, time zone, start, end, passing and duration as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-017", "SRC-018" ], "questions": [ { "id": "operating-day-time-zone-start-end-passing-and-duration-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish operating day, time zone, start, end, passing and duration?", "kind": "temporal", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "operating-day-time-zone-start-end-passing-and-duration-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access operating day, time zone, start, end, passing and duration, and under what role or authority?", "kind": "quality", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "operating-day-time-zone-start-end-passing-and-duration-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify operating day, time zone, start, end, passing and duration?", "kind": "decision", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "operating-day-time-zone-start-end-passing-and-duration-data", "name": "Operating day, time zone, start, end, passing and duration data", "description": "Typed journey-scoped values and references needed to answer the governed questions for operating day, time zone, start, end, passing and duration.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "operating-day-time-zone-start-end-passing-and-duration-artifact", "name": "Operating day, time zone, start, end, passing and duration evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting operating day, time zone, start, end, passing and duration.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "requested-planned-target-estimated-predicted-observed-and-actual-time", "name": "Requested, planned, target, estimated, predicted, observed and actual time", "description": "Records requested, planned, target, estimated, predicted, observed and actual time as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-017", "SRC-018" ], "questions": [ { "id": "requested-planned-target-estimated-predicted-observed-and-actual-time-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish requested, planned, target, estimated, predicted, observed and actual time?", "kind": "classification", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "requested-planned-target-estimated-predicted-observed-and-actual-time-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access requested, planned, target, estimated, predicted, observed and actual time, and under what role or authority?", "kind": "validation", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "requested-planned-target-estimated-predicted-observed-and-actual-time-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify requested, planned, target, estimated, predicted, observed and actual time?", "kind": "identity", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "requested-planned-target-estimated-predicted-observed-and-actual-time-data", "name": "Requested, planned, target, estimated, predicted, observed and actual time data", "description": "Typed journey-scoped values and references needed to answer the governed questions for requested, planned, target, estimated, predicted, observed and actual time.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "requested-planned-target-estimated-predicted-observed-and-actual-time-artifact", "name": "Requested, planned, target, estimated, predicted, observed and actual time evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting requested, planned, target, estimated, predicted, observed and actual time.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null } ] }, { "id": "plan-choice-and-constraints", "name": "Plan choice and constraints", "description": "Groups Journey / Trip context for plan choice and constraints without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012", "SRC-014", "SRC-015" ], "findings": [ { "id": "journey-request-routing-result-selected-plan-itinerary-and-alternative", "name": "Journey request, routing result, selected plan, itinerary and alternative", "description": "Records journey request, routing result, selected plan, itinerary and alternative as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012", "SRC-014", "SRC-015" ], "questions": [ { "id": "journey-request-routing-result-selected-plan-itinerary-and-alternative-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish journey request, routing result, selected plan, itinerary and alternative?", "kind": "decision", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "journey-request-routing-result-selected-plan-itinerary-and-alternative-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access journey request, routing result, selected plan, itinerary and alternative, and under what role or authority?", "kind": "security", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "journey-request-routing-result-selected-plan-itinerary-and-alternative-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify journey request, routing result, selected plan, itinerary and alternative?", "kind": "classification", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "journey-request-routing-result-selected-plan-itinerary-and-alternative-data", "name": "Journey request, routing result, selected plan, itinerary and alternative data", "description": "Typed journey-scoped values and references needed to answer the governed questions for journey request, routing result, selected plan, itinerary and alternative.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "journey-request-routing-result-selected-plan-itinerary-and-alternative-artifact", "name": "Journey request, routing result, selected plan, itinerary and alternative evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting journey request, routing result, selected plan, itinerary and alternative.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "accessibility-preference-party-luggage-mode-and-transfer-constraint", "name": "Accessibility, preference, party, luggage, mode and transfer constraint", "description": "Records accessibility, preference, party, luggage, mode and transfer constraint as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012", "SRC-014", "SRC-015" ], "questions": [ { "id": "accessibility-preference-party-luggage-mode-and-transfer-constraint-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish accessibility, preference, party, luggage, mode and transfer constraint?", "kind": "constraint", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "accessibility-preference-party-luggage-mode-and-transfer-constraint-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access accessibility, preference, party, luggage, mode and transfer constraint, and under what role or authority?", "kind": "privacy", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "accessibility-preference-party-luggage-mode-and-transfer-constraint-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify accessibility, preference, party, luggage, mode and transfer constraint?", "kind": "composition", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "accessibility-preference-party-luggage-mode-and-transfer-constraint-data", "name": "Accessibility, preference, party, luggage, mode and transfer constraint data", "description": "Typed journey-scoped values and references needed to answer the governed questions for accessibility, preference, party, luggage, mode and transfer constraint.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "accessibility-preference-party-luggage-mode-and-transfer-constraint-artifact", "name": "Accessibility, preference, party, luggage, mode and transfer constraint evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting accessibility, preference, party, luggage, mode and transfer constraint.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "execution-progress-and-observation", "name": "Execution, progress and observation", "description": "Groups the governed Journey / Trip concern for execution, progress and observation.", "rationale": "Record what was reported or observed during the journey while operational services and sensors remain external masters.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-019", "SRC-007", "SRC-008", "SRC-009", "SRC-010" ], "layers": [ { "id": "lifecycle-state-and-progress", "name": "Lifecycle state and progress", "description": "Groups Journey / Trip context for lifecycle state and progress without importing neighboring master lifecycles.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-019" ], "findings": [ { "id": "proposed-confirmed-ready-started-in-progress-arrived-and-completed-state", "name": "Proposed, confirmed, ready, started, in-progress, arrived and completed state", "description": "Records proposed, confirmed, ready, started, in-progress, arrived and completed state as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-019" ], "questions": [ { "id": "proposed-confirmed-ready-started-in-progress-arrived-and-completed-state-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish proposed, confirmed, ready, started, in-progress, arrived and completed state?", "kind": "lifecycle", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "proposed-confirmed-ready-started-in-progress-arrived-and-completed-state-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access proposed, confirmed, ready, started, in-progress, arrived and completed state, and under what role or authority?", "kind": "retention", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "proposed-confirmed-ready-started-in-progress-arrived-and-completed-state-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify proposed, confirmed, ready, started, in-progress, arrived and completed state?", "kind": "relationship", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "proposed-confirmed-ready-started-in-progress-arrived-and-completed-state-data", "name": "Proposed, confirmed, ready, started, in-progress, arrived and completed state data", "description": "Typed journey-scoped values and references needed to answer the governed questions for proposed, confirmed, ready, started, in-progress, arrived and completed state.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-019" ] } ], "artifacts": [ { "id": "proposed-confirmed-ready-started-in-progress-arrived-and-completed-state-artifact", "name": "Proposed, confirmed, ready, started, in-progress, arrived and completed state evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting proposed, confirmed, ready, started, in-progress, arrived and completed state.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-019" ] } ], "inline_only_rationale": null }, { "id": "current-leg-call-stop-sequence-progress-and-completion-evidence", "name": "Current leg, call, stop sequence, progress and completion evidence", "description": "Records current leg, call, stop sequence, progress and completion evidence as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-019" ], "questions": [ { "id": "current-leg-call-stop-sequence-progress-and-completion-evidence-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish current leg, call, stop sequence, progress and completion evidence?", "kind": "state", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "current-leg-call-stop-sequence-progress-and-completion-evidence-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access current leg, call, stop sequence, progress and completion evidence, and under what role or authority?", "kind": "access", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "current-leg-call-stop-sequence-progress-and-completion-evidence-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify current leg, call, stop sequence, progress and completion evidence?", "kind": "state", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "current-leg-call-stop-sequence-progress-and-completion-evidence-data", "name": "Current leg, call, stop sequence, progress and completion evidence data", "description": "Typed journey-scoped values and references needed to answer the governed questions for current leg, call, stop sequence, progress and completion evidence.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-019" ] } ], "artifacts": [ { "id": "current-leg-call-stop-sequence-progress-and-completion-evidence-artifact", "name": "Current leg, call, stop sequence, progress and completion evidence evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting current leg, call, stop sequence, progress and completion evidence.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-011", "SRC-019" ] } ], "inline_only_rationale": null } ] }, { "id": "movement-observation-and-trajectory", "name": "Movement observation and trajectory", "description": "Groups Journey / Trip context for movement observation and trajectory without importing neighboring master lifecycles.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-019" ], "findings": [ { "id": "position-fix-bearing-speed-odometer-observation-time-and-device", "name": "Position fix, bearing, speed, odometer, observation time and device", "description": "Records position fix, bearing, speed, odometer, observation time and device as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-019" ], "questions": [ { "id": "position-fix-bearing-speed-odometer-observation-time-and-device-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish position fix, bearing, speed, odometer, observation time and device?", "kind": "measurement", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "position-fix-bearing-speed-odometer-observation-time-and-device-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access position fix, bearing, speed, odometer, observation time and device, and under what role or authority?", "kind": "exception", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "position-fix-bearing-speed-odometer-observation-time-and-device-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify position fix, bearing, speed, odometer, observation time and device?", "kind": "lifecycle", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "position-fix-bearing-speed-odometer-observation-time-and-device-data", "name": "Position fix, bearing, speed, odometer, observation time and device data", "description": "Typed journey-scoped values and references needed to answer the governed questions for position fix, bearing, speed, odometer, observation time and device.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-019" ] } ], "artifacts": [ { "id": "position-fix-bearing-speed-odometer-observation-time-and-device-artifact", "name": "Position fix, bearing, speed, odometer, observation time and device evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting position fix, bearing, speed, odometer, observation time and device.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-019" ] } ], "inline_only_rationale": null }, { "id": "actual-trajectory-temporal-geometry-gap-interpolation-and-confidence", "name": "Actual trajectory, temporal geometry, gap, interpolation and confidence", "description": "Records actual trajectory, temporal geometry, gap, interpolation and confidence as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-019" ], "questions": [ { "id": "actual-trajectory-temporal-geometry-gap-interpolation-and-confidence-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish actual trajectory, temporal geometry, gap, interpolation and confidence?", "kind": "evidence", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "actual-trajectory-temporal-geometry-gap-interpolation-and-confidence-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access actual trajectory, temporal geometry, gap, interpolation and confidence, and under what role or authority?", "kind": "interoperability", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "actual-trajectory-temporal-geometry-gap-interpolation-and-confidence-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify actual trajectory, temporal geometry, gap, interpolation and confidence?", "kind": "temporal", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "actual-trajectory-temporal-geometry-gap-interpolation-and-confidence-data", "name": "Actual trajectory, temporal geometry, gap, interpolation and confidence data", "description": "Typed journey-scoped values and references needed to answer the governed questions for actual trajectory, temporal geometry, gap, interpolation and confidence.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-019" ] } ], "artifacts": [ { "id": "actual-trajectory-temporal-geometry-gap-interpolation-and-confidence-artifact", "name": "Actual trajectory, temporal geometry, gap, interpolation and confidence evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting actual trajectory, temporal geometry, gap, interpolation and confidence.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-019" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "deviation-outcome-and-measures", "name": "Deviation, outcome and measures", "description": "Groups the governed Journey / Trip concern for deviation, outcome and measures.", "rationale": "Preserve disruption, outcome and measurement evidence without converting estimates into facts or incidents into journey identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-014", "SRC-019", "SRC-009", "SRC-011", "SRC-012", "SRC-013", "SRC-020" ], "layers": [ { "id": "disruption-change-and-outcome", "name": "Disruption, change and outcome", "description": "Groups Journey / Trip context for disruption, change and outcome without importing neighboring master lifecycles.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-014", "SRC-019" ], "findings": [ { "id": "delay-cancellation-diversion-interruption-missed-connection-and-recovery", "name": "Delay, cancellation, diversion, interruption, missed connection and recovery", "description": "Records delay, cancellation, diversion, interruption, missed connection and recovery as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-014", "SRC-019" ], "questions": [ { "id": "delay-cancellation-diversion-interruption-missed-connection-and-recovery-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish delay, cancellation, diversion, interruption, missed connection and recovery?", "kind": "exception", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "delay-cancellation-diversion-interruption-missed-connection-and-recovery-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access delay, cancellation, diversion, interruption, missed connection and recovery, and under what role or authority?", "kind": "decision", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "delay-cancellation-diversion-interruption-missed-connection-and-recovery-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify delay, cancellation, diversion, interruption, missed connection and recovery?", "kind": "spatial", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "delay-cancellation-diversion-interruption-missed-connection-and-recovery-data", "name": "Delay, cancellation, diversion, interruption, missed connection and recovery data", "description": "Typed journey-scoped values and references needed to answer the governed questions for delay, cancellation, diversion, interruption, missed connection and recovery.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-014", "SRC-019" ] } ], "artifacts": [ { "id": "delay-cancellation-diversion-interruption-missed-connection-and-recovery-artifact", "name": "Delay, cancellation, diversion, interruption, missed connection and recovery evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting delay, cancellation, diversion, interruption, missed connection and recovery.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-014", "SRC-019" ] } ], "inline_only_rationale": null }, { "id": "boarding-alighting-no-show-abandonment-partial-completion-and-arrival-outcome", "name": "Boarding, alighting, no-show, abandonment, partial completion and arrival outcome", "description": "Records boarding, alighting, no-show, abandonment, partial completion and arrival outcome as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-014", "SRC-019" ], "questions": [ { "id": "boarding-alighting-no-show-abandonment-partial-completion-and-arrival-outcome-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish boarding, alighting, no-show, abandonment, partial completion and arrival outcome?", "kind": "event", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "boarding-alighting-no-show-abandonment-partial-completion-and-arrival-outcome-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access boarding, alighting, no-show, abandonment, partial completion and arrival outcome, and under what role or authority?", "kind": "identity", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "boarding-alighting-no-show-abandonment-partial-completion-and-arrival-outcome-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify boarding, alighting, no-show, abandonment, partial completion and arrival outcome?", "kind": "provenance", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "boarding-alighting-no-show-abandonment-partial-completion-and-arrival-outcome-data", "name": "Boarding, alighting, no-show, abandonment, partial completion and arrival outcome data", "description": "Typed journey-scoped values and references needed to answer the governed questions for boarding, alighting, no-show, abandonment, partial completion and arrival outcome.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-014", "SRC-019" ] } ], "artifacts": [ { "id": "boarding-alighting-no-show-abandonment-partial-completion-and-arrival-outcome-artifact", "name": "Boarding, alighting, no-show, abandonment, partial completion and arrival outcome evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting boarding, alighting, no-show, abandonment, partial completion and arrival outcome.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-014", "SRC-019" ] } ], "inline_only_rationale": null } ] }, { "id": "distance-performance-and-impact", "name": "Distance, performance and impact", "description": "Groups Journey / Trip context for distance, performance and impact without importing neighboring master lifecycles.", "source_refs": [ "SRC-005", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-020" ], "findings": [ { "id": "travelled-network-and-straight-line-distance-duration-wait-and-speed", "name": "Travelled, network and straight-line distance, duration, wait and speed", "description": "Records travelled, network and straight-line distance, duration, wait and speed as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-005", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-020" ], "questions": [ { "id": "travelled-network-and-straight-line-distance-duration-wait-and-speed-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish travelled, network and straight-line distance, duration, wait and speed?", "kind": "measurement", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "travelled-network-and-straight-line-distance-duration-wait-and-speed-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access travelled, network and straight-line distance, duration, wait and speed, and under what role or authority?", "kind": "classification", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "travelled-network-and-straight-line-distance-duration-wait-and-speed-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify travelled, network and straight-line distance, duration, wait and speed?", "kind": "ownership", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "travelled-network-and-straight-line-distance-duration-wait-and-speed-data", "name": "Travelled, network and straight-line distance, duration, wait and speed data", "description": "Typed journey-scoped values and references needed to answer the governed questions for travelled, network and straight-line distance, duration, wait and speed.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-020" ] } ], "artifacts": [ { "id": "travelled-network-and-straight-line-distance-duration-wait-and-speed-artifact", "name": "Travelled, network and straight-line distance, duration, wait and speed evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting travelled, network and straight-line distance, duration, wait and speed.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-020" ] } ], "inline_only_rationale": null }, { "id": "occupancy-cost-energy-emissions-accessibility-and-service-quality-view", "name": "Occupancy, cost, energy, emissions, accessibility and service-quality view", "description": "Records occupancy, cost, energy, emissions, accessibility and service-quality view as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-005", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-020" ], "questions": [ { "id": "occupancy-cost-energy-emissions-accessibility-and-service-quality-view-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish occupancy, cost, energy, emissions, accessibility and service-quality view?", "kind": "quality", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "occupancy-cost-energy-emissions-accessibility-and-service-quality-view-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access occupancy, cost, energy, emissions, accessibility and service-quality view, and under what role or authority?", "kind": "composition", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "occupancy-cost-energy-emissions-accessibility-and-service-quality-view-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify occupancy, cost, energy, emissions, accessibility and service-quality view?", "kind": "authority", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "occupancy-cost-energy-emissions-accessibility-and-service-quality-view-data", "name": "Occupancy, cost, energy, emissions, accessibility and service-quality view data", "description": "Typed journey-scoped values and references needed to answer the governed questions for occupancy, cost, energy, emissions, accessibility and service-quality view.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-020" ] } ], "artifacts": [ { "id": "occupancy-cost-energy-emissions-accessibility-and-service-quality-view-artifact", "name": "Occupancy, cost, energy, emissions, accessibility and service-quality view evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting occupancy, cost, energy, emissions, accessibility and service-quality view.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-020" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-provenance-and-interoperability", "name": "Governance, provenance and interoperability", "description": "Groups the governed Journey / Trip concern for governance, provenance and interoperability.", "rationale": "Make journey memory correctable, privacy-aware and safely projectable across incompatible vocabularies.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-001", "SRC-007", "SRC-008", "SRC-014", "SRC-015", "SRC-016", "SRC-021" ], "layers": [ { "id": "provenance-reconciliation-and-lineage", "name": "Provenance, reconciliation and lineage", "description": "Groups Journey / Trip context for provenance, reconciliation and lineage without importing neighboring master lifecycles.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ], "findings": [ { "id": "source-actor-method-event-time-record-time-ingestion-time-and-assurance", "name": "Source, actor, method, event time, record time, ingestion time and assurance", "description": "Records source, actor, method, event time, record time, ingestion time and assurance as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ], "questions": [ { "id": "source-actor-method-event-time-record-time-ingestion-time-and-assurance-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish source, actor, method, event time, record time, ingestion time and assurance?", "kind": "provenance", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "source-actor-method-event-time-record-time-ingestion-time-and-assurance-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access source, actor, method, event time, record time, ingestion time and assurance, and under what role or authority?", "kind": "relationship", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "source-actor-method-event-time-record-time-ingestion-time-and-assurance-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify source, actor, method, event time, record time, ingestion time and assurance?", "kind": "constraint", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "source-actor-method-event-time-record-time-ingestion-time-and-assurance-data", "name": "Source, actor, method, event time, record time, ingestion time and assurance data", "description": "Typed journey-scoped values and references needed to answer the governed questions for source, actor, method, event time, record time, ingestion time and assurance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ] } ], "artifacts": [ { "id": "source-actor-method-event-time-record-time-ingestion-time-and-assurance-artifact", "name": "Source, actor, method, event time, record time, ingestion time and assurance evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting source, actor, method, event time, record time, ingestion time and assurance.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ] } ], "inline_only_rationale": null }, { "id": "schedule-observation-conflict-correction-split-merge-and-successor", "name": "Schedule-observation conflict, correction, split, merge and successor", "description": "Records schedule-observation conflict, correction, split, merge and successor as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ], "questions": [ { "id": "schedule-observation-conflict-correction-split-merge-and-successor-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish schedule-observation conflict, correction, split, merge and successor?", "kind": "validation", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "schedule-observation-conflict-correction-split-merge-and-successor-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access schedule-observation conflict, correction, split, merge and successor, and under what role or authority?", "kind": "state", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "schedule-observation-conflict-correction-split-merge-and-successor-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify schedule-observation conflict, correction, split, merge and successor?", "kind": "process", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "schedule-observation-conflict-correction-split-merge-and-successor-data", "name": "Schedule-observation conflict, correction, split, merge and successor data", "description": "Typed journey-scoped values and references needed to answer the governed questions for schedule-observation conflict, correction, split, merge and successor.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ] } ], "artifacts": [ { "id": "schedule-observation-conflict-correction-split-merge-and-successor-artifact", "name": "Schedule-observation conflict, correction, split, merge and successor evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting schedule-observation conflict, correction, split, merge and successor.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ] } ], "inline_only_rationale": null } ] }, { "id": "access-retention-and-projections", "name": "Access, retention and projections", "description": "Groups Journey / Trip context for access, retention and projections without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ], "findings": [ { "id": "traveller-location-sensitivity-consent-purpose-access-legal-hold-and-retention", "name": "Traveller location sensitivity, consent, purpose, access, legal hold and retention", "description": "Records traveller location sensitivity, consent, purpose, access, legal hold and retention as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ], "questions": [ { "id": "traveller-location-sensitivity-consent-purpose-access-legal-hold-and-retention-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish traveller location sensitivity, consent, purpose, access, legal hold and retention?", "kind": "privacy", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "traveller-location-sensitivity-consent-purpose-access-legal-hold-and-retention-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access traveller location sensitivity, consent, purpose, access, legal hold and retention, and under what role or authority?", "kind": "lifecycle", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "traveller-location-sensitivity-consent-purpose-access-legal-hold-and-retention-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify traveller location sensitivity, consent, purpose, access, legal hold and retention?", "kind": "event", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "traveller-location-sensitivity-consent-purpose-access-legal-hold-and-retention-data", "name": "Traveller location sensitivity, consent, purpose, access, legal hold and retention data", "description": "Typed journey-scoped values and references needed to answer the governed questions for traveller location sensitivity, consent, purpose, access, legal hold and retention.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ] } ], "artifacts": [ { "id": "traveller-location-sensitivity-consent-purpose-access-legal-hold-and-retention-artifact", "name": "Traveller location sensitivity, consent, purpose, access, legal hold and retention evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting traveller location sensitivity, consent, purpose, access, legal hold and retention.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ] } ], "inline_only_rationale": null }, { "id": "transmodel-gtfs-moving-features-statistical-schema-org-time-and-provenance-projection", "name": "Transmodel, GTFS, Moving Features, statistical, Schema.org, time and provenance projection", "description": "Records transmodel, gtfs, moving features, statistical, schema.org, time and provenance projection as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ], "questions": [ { "id": "transmodel-gtfs-moving-features-statistical-schema-org-time-and-provenance-projection-q01", "text": "Which journey identity, class, subject, endpoint, leg, time basis and source establish transmodel, gtfs, moving features, statistical, schema.org, time and provenance projection?", "kind": "interoperability", "answer_data": [ "journey and revision identifier, namespace, kind and lifecycle status", "traveller, vehicle, operator, service, route, place and leg references", "planned, predicted, observed and actual time with source and confidence" ] }, { "id": "transmodel-gtfs-moving-features-statistical-schema-org-time-and-provenance-projection-q02", "text": "Who planned, undertook, operated, observed, asserted, corrected or may access transmodel, gtfs, moving features, statistical, schema.org, time and provenance projection, and under what role or authority?", "kind": "temporal", "answer_data": [ "traveller, driver, operator, planner, observer, steward and authority roles", "delegation, consent, purpose, access scope, jurisdiction and applicable policy", "assertion owner, evidence issuer, reviewer, correction actor and disputed state" ] }, { "id": "transmodel-gtfs-moving-features-statistical-schema-org-time-and-provenance-projection-q03", "text": "Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify transmodel, gtfs, moving features, statistical, schema.org, time and provenance projection?", "kind": "measurement", "answer_data": [ "origin, destination, calls, stages, modes, connections, sequence and dependencies", "distance, duration, waiting, speed, occupancy, gap, tolerance and uncertainty", "source snapshot, digest, event and ingestion clocks, conflict, correction and semantic-loss declaration" ] } ], "data_elements": [ { "id": "transmodel-gtfs-moving-features-statistical-schema-org-time-and-provenance-projection-data", "name": "Transmodel, GTFS, Moving Features, statistical, Schema.org, time and provenance projection data", "description": "Typed journey-scoped values and references needed to answer the governed questions for transmodel, gtfs, moving features, statistical, schema.org, time and provenance projection.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ] } ], "artifacts": [ { "id": "transmodel-gtfs-moving-features-statistical-schema-org-time-and-provenance-projection-artifact", "name": "Transmodel, GTFS, Moving Features, statistical, Schema.org, time and provenance projection evidence manifest", "description": "Digest-addressed manifest of plans, observations, mappings, corrections and external records supporting transmodel, gtfs, moving features, statistical, schema.org, time and provenance projection.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative journey master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-journey", "name": "Register journey", "description": "Create one governed journey identity and boundary.", "inputs": [ "subject and role references", "origin and destination", "journey kind and time basis" ], "outputs": [ "journey identifier", "initial revision" ], "preconditions": [ "active Dimension", "create authority" ], "effects": [ "journey identity and explicit unknowns are appended" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-019" ] }, { "id": "bind-participants", "name": "Bind participants", "description": "Bind traveller, driver, operator, vehicle and service roles without importing their lifecycles.", "inputs": [ "journey identifier", "party, vehicle and service references", "role intervals" ], "outputs": [ "typed participant bindings" ], "preconditions": [ "resolved master identities" ], "effects": [ "role-qualified references are appended" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "compose-legs", "name": "Compose ordered legs", "description": "Append stages, modes, endpoints, calls and connection dependencies.", "inputs": [ "journey identifier", "leg definitions", "route and place references" ], "outputs": [ "validated ordered leg graph" ], "preconditions": [ "stable journey revision" ], "effects": [ "leg composition is versioned without mutating route masters" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012" ] }, { "id": "record-plan", "name": "Record selected plan", "description": "Record requested, proposed or selected movement plan and alternatives.", "inputs": [ "journey request", "routing result", "selection rationale" ], "outputs": [ "typed plan assertion", "successor relation" ], "preconditions": [ "planner authority", "time and accessibility constraints" ], "effects": [ "plan is appended and remains distinct from actual movement" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-014" ] }, { "id": "record-observation", "name": "Record journey observation", "description": "Append calls, passing times, position fixes and other journey-scoped observations.", "inputs": [ "journey identifier", "observation", "source and clocks" ], "outputs": [ "immutable observation assertion" ], "preconditions": [ "recognized subject", "source provenance" ], "effects": [ "evidence is appended without erasing plan or prediction" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-008", "SRC-019" ] }, { "id": "derive-progress", "name": "Derive progress and state", "description": "Derive current leg, progress and lifecycle state from qualified evidence.", "inputs": [ "journey revision", "plans", "observations" ], "outputs": [ "derived state view", "derivation trace" ], "preconditions": [ "deterministic state policy" ], "effects": [ "view is refreshed without rewriting evidence" ], "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-019" ] }, { "id": "reconcile-times", "name": "Reconcile journey times", "description": "Compare requested, planned, predicted, observed and actual times.", "inputs": [ "time assertions", "operating-day basis", "tolerance policy" ], "outputs": [ "reconciliation result", "conflict set" ], "preconditions": [ "timezone and source known" ], "effects": [ "differences and precedence are recorded" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-017", "SRC-018", "SRC-020" ] }, { "id": "handle-deviation", "name": "Handle deviation", "description": "Register disruption, impact, recovery, diversion or successor plan without overwriting history.", "inputs": [ "journey identifier", "exception evidence", "authorized response" ], "outputs": [ "exception record", "successor plan reference" ], "preconditions": [ "response authority", "affected scope" ], "effects": [ "deviation and recovery lineage are appended" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-010", "SRC-014", "SRC-019" ] }, { "id": "calculate-measures", "name": "Calculate journey measures", "description": "Calculate qualified distance, duration, wait, speed and impact views.", "inputs": [ "trajectory or leg data", "method", "units and uncertainty" ], "outputs": [ "versioned measurement view" ], "preconditions": [ "declared method and source coverage" ], "effects": [ "measurements remain derivations rather than journey identity" ], "source_refs": [ "SRC-009", "SRC-010", "SRC-011", "SRC-020" ] }, { "id": "project-journey", "name": "Project journey", "description": "Produce minimum-necessary standards-aligned or stakeholder views.", "inputs": [ "journey revision", "target profile", "access purpose" ], "outputs": [ "versioned projection", "semantic-loss declaration" ], "preconditions": [ "authorized recipient", "pinned target version" ], "effects": [ "projection is logged and source identity is preserved" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-019", "SRC-020", "SRC-021" ] } ], "composition": [ { "target": "WM-FLW-007 Passenger Mobility / Transit", "relation": "REFERENCE", "purpose": "Resolve transit network, service, schedule, fare and mobility context without inheriting the broader model's lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005" ] }, { "target": "WM-FLW-010 Route / Itinerary", "relation": "REFERENCE", "purpose": "Resolve reusable paths and planning results while preserving journey identity and actual divergence.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-010", "SRC-014", "SRC-015" ] }, { "target": "Person, Vehicle, Organization, Place, Service, Schedule, Booking, Ticket, Shipment, Incident, Sensor and Evidence models", "relation": "REFERENCE", "purpose": "Resolve external masters without duplicating their identity, authority or lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-008", "SRC-010", "SRC-019" ] }, { "target": "Transmodel v6.2 and GTFS Schedule and Realtime", "relation": "ALIGN", "purpose": "Project passenger-trip and vehicle-journey views with explicit vocabulary and version mappings.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] }, { "target": "OGC and ISO Moving Features and GeoSPARQL", "relation": "ALIGN", "purpose": "Project actual movement, temporal geometry and spatial-query views with CRS, gap and conformance controls.", "required": false, "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-016" ] }, { "target": "UNECE transport statistics, UN tourism statistics and Schema.org Trip", "relation": "ALIGN", "purpose": "Project statistical and web-discovery views without treating their trip boundaries as universal.", "required": false, "source_refs": [ "SRC-011", "SRC-012", "SRC-013", "SRC-015" ] }, { "target": "OWL-Time, RFC 3339, PROV-O, DQV and ODRL", "relation": "ALIGN", "purpose": "Project temporal, provenance, quality and access semantics with exact pins and semantic-loss declarations.", "required": false, "source_refs": [ "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the Dimension owner, responsible stewards and authority for personal, organizational, fleet and public-service journey records.", "Register authoritative person, vehicle, operator, route, itinerary, service, schedule, place, booking, ticket, shipment, incident, sensor and evidence masters.", "Publish journey, relation, event, identifier, access, retention, assurance and interoperability registries.", "Pin mode, region, operating-day, time-zone, accessibility, privacy, safety and exchange profiles." ], "namespace_guidance": "Mint journey, revision, leg, observation, exception and projection identifiers only in the adopting Dimension namespace; preserve person, vehicle, operator, route, itinerary, service, schedule, place, booking, ticket, shipment, incident and sensor identities as typed external references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local journey, identifier, event, access, retention and provenance registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by registry ID, model version, authoritative journey master ID, immutable revision, journey kind, subject, origin, destination and time basis; never use date, route, ticket, vehicle, filename or hash alone as identity.", "Keep person trip, vehicle journey, service journey, route, itinerary, leg, stage, call, position observation, trajectory and wider travel distinct and preserve corrections and successors." ], "patch_rules": [ "Additive extensions use a Dimension-owned namespace and declare target node, mode or jurisdiction profile, authority, source, rationale, access, time and interoperability impact.", "Breaking changes require a new version, migration and crosswalk maps, compatibility declaration and continued resolution of prior journey revisions and identifiers." ], "compatibility_rules": [ "Consumers may ignore unknown additive fields only when journey identity, kind, subject, endpoints, leg order, time kind, status, authority, provenance and access meaning remain intact.", "Transmodel, GTFS, Moving Features, statistical, Schema.org, GeoSPARQL, OWL-Time and provenance mappings pin source and target versions and declare transformed, omitted or non-round-trippable values." ] }, "artifact_rules": { "identity_priority": [ "Authoritative journey master-system identifier and immutable revision identifier.", "Governed globally resolvable journey, leg or observation IRI.", "Adopting-Dimension UUID or ULID when no authoritative external identifier exists." ], "timestamp_rule": "Record event timestamps in RFC 3339 with seconds and an explicit UTC offset or Z; keep requested, planned, target, estimated, predicted, observed, actual, record, correction and ingestion times distinct.", "serial_naming_rule": "Name serial artifacts as {journey-id}--{artifact-kind}--{revision-or-event-id}; never use a date, route, place, vehicle, traveller, ticket, filename or hash alone as journey identity.", "integrity_rule": "Store digest, media type, byte length, issuer, source and vocabulary versions, journey scope, event and record times, provenance, assurance and access marking for each retained serial artifact." }, "policies": [ "The adopting Dimension declares who may create, plan, bind, observe, correct, derive, disclose, retain and tombstone journey records.", "Every journey assertion requires journey and revision identity, kind, subject or vehicle, endpoint or leg scope, time kind, source, authority, confidence, status and lineage as applicable.", "Agents never infer actual movement, passenger presence, boarding, completion, incident causality or entitlement from a plan, prediction, ticket, position fix or status label alone.", "Route, itinerary, person, vehicle, service, schedule, place, booking, ticket, shipment, incident, payment, sensor and evidence masters remain external.", "Automated agents may append low-risk observations, reconciliations and projections under delegation, but consequential rerouting, safety action, protected live-location disclosure and irreversible deletion require accountable authority." ], "crud": { "read": [ "Resolve active Dimension, purpose, role, journey kind, subject scope, time horizon, requested revision, assurance, freshness and access policy; return the minimum permitted projection." ], "create": [ "Create stable journey identity, kind, subject, origin, destination, temporal basis, source, authority and explicit unknowns before adding plans or observations." ], "update": [ "Append an immutable plan, observation, state or correction revision with actor, authority, reason, RFC 3339 effective time and predecessor; validate composition, clocks, evidence and access." ], "delete": [ "Apply privacy, safety, dispute, audit, retention and legal-hold policy; tombstone eligible Journey-owned records or withdraw projections while preserving identity, material provenance and non-cascading external references. The adopting Dimension retention policy owns execution." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Own namespace, mastership, delegation, access, retention and federation rules." ] }, { "name": "Journey steward", "responsibilities": [ "Own journey boundary, composition, plan assertions, status derivation and reconciliation." ] }, { "name": "Traveller or vehicle steward", "responsibilities": [ "Maintain authoritative subject identity, consent, role and permitted journey linkage." ] }, { "name": "Transport operator", "responsibilities": [ "Own service, schedule, vehicle-journey and operational observations it performs." ] }, { "name": "Observation or data steward", "responsibilities": [ "Govern devices, sources, clocks, quality, mappings and correction lineage." ] }, { "name": "Safety or regulatory authority", "responsibilities": [ "Own restrictions, interventions and jurisdictional decisions outside Journey mastership." ] }, { "name": "Reviewer or auditor", "responsibilities": [ "Review evidence, conflicts, corrections and protected use without rewriting originals." ] }, { "name": "Disclosure authority", "responsibilities": [ "Approve recipient, purpose, location exposure, redaction and publication timing." ] } ], "access": { "default_rule": "Deny mutation and sensitive disclosure unless the active Dimension, role, purpose, journey kind, subject, location sensitivity and field policy grant the action; expose the minimum necessary projection.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency access must be time-limited, purpose-bound, attributable, independently reviewed and unable to erase immutable journey, correction or legal-hold evidence." ], "audit_requirements": [ "Log actor, role, purpose, journey and revision identity, action, decision, policy and vocabulary versions, RFC 3339 timestamp with offset, affected fields, source evidence and outcome for privileged mutation or disclosure." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read the nearest Dimension-owner AGENTS.md, journey authority, active mode, jurisdiction, time, access, retention and disclosure policies.", "Read this model AGENTS.md, pinned spec.yaml and required person, vehicle, route, itinerary, service, schedule, place, booking, ticket, shipment, incident, sensor and evidence model instructions before mutation." ] } }, "coverage": { "claim": "WM-FLW-009 covers one governed Journey / Trip as an identity-bearing intended or undertaken movement of a person or vehicle with endpoints, ordered legs, typed plans and clocks, progress, observations, trajectory evidence, deviations, outcomes, measures, provenance, access and loss-aware projections. Mode, jurisdiction, trip-segmentation, route and itinerary split, privacy, implementation-conformance and independent-review questions remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Journey, revision, wider travel, subtrip, leg, call, observation, exception and projection identities remain distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Person trip, vehicle journey, service journey, dead run, wider travel and statistical profiles are typed rather than merged." }, { "dimension": "direct properties", "status": "covered", "notes": "Journey-owned kind, endpoints, composition, time assertions, state and outcome are covered while external masters retain their direct properties." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Plan, prediction, report, measured position, passing event, actual trajectory and correction are distinguished by type, source and clocks." }, { "dimension": "lifecycle", "status": "covered", "notes": "Proposed, selected, confirmed, ready, started, in-progress, interrupted, diverted, cancelled, arrived, completed, corrected and tombstoned states preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Subjects, parties, vehicles, services, routes, itineraries, places, legs, bookings, tickets, shipments, incidents, sensors and evidence use typed bindings." }, { "dimension": "temporal", "status": "covered", "notes": "Operating day, time zone, requested, planned, target, predicted, observed, actual, record, correction and ingestion clocks remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Origin, destination, via places, stops, calls, paths, shapes, trajectories, CRS, gaps and uncertainty are explicit." }, { "dimension": "provenance", "status": "covered", "notes": "Sources, actors, methods, evidence snapshots, derivations, revisions and invalidations are linked." }, { "dimension": "ownership", "status": "covered", "notes": "Dimension owner, journey steward, traveller or vehicle steward, operator, data steward, authority, reviewer and disclosure authority have separate responsibilities." }, { "dimension": "validation", "status": "covered", "notes": "Identity, leg order, endpoint continuity, clock, route, schedule, trajectory, state, correction and crosswalk checks are explicit." }, { "dimension": "access", "status": "covered", "notes": "Role, purpose, consent, delegation, location sensitivity, minimum projection, emergency access and audit are represented." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Immutable observations, corrections, disputes, legal hold, withdrawal and tombstones are explicit and non-cascading." }, { "dimension": "interoperability", "status": "covered", "notes": "Transmodel, GTFS, OGC, ISO, statistical, Schema.org, GeoSPARQL, OWL-Time, PROV, DQV and ODRL mappings pin versions and disclose loss." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Registration, binding, composition, planning, observation, state derivation, time reconciliation, deviation handling, measurement and projection functions declare controlled effects." } ], "known_omissions": [ "Mode, jurisdiction, safety, immigration, border, accessibility, passenger-rights, employment-travel, privacy and retention profiles require exact current rules and competent review.", "Person, organization, vehicle, route, itinerary, network, place, service, schedule, booking, ticket, fare, shipment, incident, payment, sensor and evidence lifecycles remain in neighboring masters.", "Certified field crosswalks, trajectory-matching algorithms, trip-segmentation rules, prediction benchmarks and legal proof requirements remain future work." ], "conflicts": [ "Trip and journey have different meanings across Transmodel, GTFS, transport statistics, tourism and ordinary language; the model requires an explicit journey kind and source profile.", "A person trip, passenger boarding, vehicle journey, service journey and wider return journey cannot share one count or identity without declared aggregation semantics.", "Planned route, routing result, selected itinerary, scheduled service, predicted movement, position samples and actual trajectory are different assertion classes." ], "regional_assumptions": [ "EU multimodal information rules and UK travel-survey definitions are regional profiles, not universal journey law.", "Transmodel and GTFS primarily describe passenger transport and service data; private, pedestrian, freight-linked and non-service vehicle journeys need explicit profiles.", "Tourism-statistics purpose and duration definitions apply only when the relevant statistical population and usual-environment tests are satisfied." ], "adversarial_checks": [ "Reject a journey without stable identity or declared composite key, kind, subject, origin, destination, temporal basis, source and revision lineage.", "Reject a route, itinerary, booking, ticket, vehicle, service or position fix represented as the journey itself.", "Reject planned, target, predicted, observed and actual times collapsed into one timestamp or interpreted without operating-day and timezone rules.", "Reject a passenger boarding or vehicle run counted as a whole personal trip without declared aggregation and purpose semantics.", "Reject last-write-wins when schedule and observations conflict; preserve source, event time, record time, uncertainty, correction and precedence.", "Reject protected live-location disclosure, consequential rerouting or record destruction outside delegated authority and retention policy." ] }, "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": "The model owns one journey identity, journey-scoped composition, assertions, state and correction lineage. Person, vehicle, organization, route, itinerary, network, place, service, schedule, booking, ticket, shipment, incident, sensor and evidence remain external masters." }, "decisions": [ { "concept": "Journey / Trip boundary", "disposition": "accepted-as-movement-episode-aggregate", "rationale": "A stable journey groups one intended or undertaken movement and its stages, typed clocks, observations and corrections without becoming a route, itinerary, service or subject." }, { "concept": "Person trip and vehicle journey", "disposition": "accepted-as-distinct-journey-kinds", "rationale": "Transmodel and GTFS demonstrate that passenger movement and a vehicle service run may be related but need separate identities, participants and counting rules." }, { "concept": "Journey, travel and return journey", "disposition": "accepted-as-profiled-aggregation", "rationale": "A one-way purpose-bounded trip, a public-transport boarding and a wider journey away from home are not interchangeable without an explicit statistical or domain profile." }, { "concept": "Route and itinerary", "disposition": "accepted-as-external-plan-and-path-masters", "rationale": "The journey references reusable paths and selected planning results, preserving actual deviation and successor plans without importing route or itinerary lifecycle." }, { "concept": "Leg, stage, call and boarding", "disposition": "accepted-as-distinct-composition-and-event-concepts", "rationale": "A stage is generally mode-specific movement, a call is a visit to a point and a boarding is an event; none alone is the whole journey." }, { "concept": "Requested, planned, predicted, observed and actual time", "disposition": "accepted-as-independent-assertion-classes", "rationale": "Each clock has its own source, authority, operating-day and timezone basis and must survive reconciliation rather than last-write-wins." }, { "concept": "Position fix and actual trajectory", "disposition": "accepted-as-evidence-versus-derived-path", "rationale": "A position sample is an observation; a trajectory is a time-qualified geometry that may include gaps and interpolation and cannot prove journey completion by itself." }, { "concept": "WM-FLW-007 candidate parent", "disposition": "held-as-compositional-reference", "rationale": "Passenger Mobility / Transit is narrower by traveller and broader by networks, services and fares, so inheritance is not approved." }, { "concept": "WM-FLW-011 incoming reference", "disposition": "accepted-with-non-ownership-rule", "rationale": "A shipment may cite transport journeys, while cargo, consignment and custody remain shipment-owned." }, { "concept": "Disruption and journey lifecycle", "disposition": "accepted-as-related-but-independent-records", "rationale": "Delay, cancellation, diversion, interruption and missed connection qualify journey outcome but generic incident identity and authority remain external." }, { "concept": "Standards and statistical projections", "disposition": "accepted-as-versioned-loss-aware-alignments", "rationale": "Transmodel, GTFS, OGC, ISO, UNECE, tourism statistics and Schema.org use different trip boundaries, vocabularies and conformance expectations." }, { "concept": "Single-provider waiver and local no-tools audit", "disposition": "accepted-with-mandatory-hold", "rationale": "One bounded Claude Sonnet and one bounded Grok attempt each timed out after 120 seconds. Codex separately audited the frozen validated result and comparison without acquiring new facts, so assurance remains reviewable-draft." } ], "publicationHolds": [ "Absence-of-external-review hold: one Claude Sonnet and one Grok attempt for WM-FLW-009 each timed out after 120 seconds; no external result was admitted.", "Boundary hold: Journey owns one movement episode and its journey-scoped assertions while route, itinerary, person, vehicle, service, schedule, booking, ticket, shipment, incident, sensor and evidence masters remain external.", "Relation hold: WM-FLW-007 remains a candidate compositional reference rather than an approved parent because its transit boundary does not equal generic Journey / Trip.", "Neighbor hold: WM-FLW-010 currently combines Route / Itinerary; its reusable-route and planning-result boundaries need independent research and may require a future split.", "Terminology hold: trip, journey, stage, leg, call, boarding, tour and travel have profile-specific meanings and require an explicit vocabulary profile.", "Mode hold: pedestrian, bicycle, road, rail, maritime, aviation, private, shared, public, on-demand, freight-linked and autonomous-vehicle journeys need independently validated profiles.", "Jurisdiction hold: safety, accessibility, passenger rights, border movement, privacy, employment travel, retention and evidence rules depend on region and context.", "Segmentation hold: purpose changes, mode changes, vehicle changes, stopovers, overnight stays, loops, series of calls, interrupted trips and return journeys require profile-specific split and merge rules.", "Observation hold: map matching, trajectory gaps, interpolation, sensor accuracy, identity matching and completion inference require tested methods and confidence thresholds.", "Prediction hold: delay, ETA, rerouting and recovery views require model, input-cutoff, uncertainty, freshness and benchmark evidence.", "Privacy hold: personal trips and live locations need purpose limitation, minimization, consent or other authority, protected access and deletion profiles.", "Interoperability hold: every Transmodel, GTFS, OGC, ISO, statistical, Schema.org, GeoSPARQL, OWL-Time, PROV, DQV and ODRL projection needs exact release pins, conformance evidence and semantic-loss declarations.", "Review hold: transport operations, mobility planning, geospatial, statistics, tourism, accessibility, safety, privacy, data governance, records and independent external review are outstanding.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Approve or reject the WM-FLW-007 relation after generic Journey / Trip and Passenger Mobility / Transit boundaries are jointly reviewed.", "Research WM-FLW-010 and decide whether reusable Route and selected Itinerary need separate model identities.", "Create independently validated person-trip, vehicle-journey, service-journey, pedestrian, road, rail, maritime, aviation, private, shared, public and on-demand profiles.", "Benchmark trip segmentation, identity matching, endpoint continuity, time reconciliation, map matching, trajectory reconstruction, completion inference, ETA and disruption handling.", "Pin exact external releases and licensing conditions and obtain independent transport, geospatial, statistics, safety, accessibility, privacy, data and records review before promotion beyond reviewable-draft assurance." ] }, "statistics": { "sources": 21, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }