# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T20:21:13Z", "synthesisSha256": "9ad82f5b7b98fbaac99599e5dbc2b156a15726aeb68617471f6da97a4b552094", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-FLW-010", "registryId": "vr.wm-flw-010", "name": "Route / Itinerary", "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": [ "route", "itinerary", "phy.flw.mob" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-flw-010-route-itinerary/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-flw-010", "model": { "registry_id": "vr.wm-flw-010", "model_id": "WM-FLW-010", "name": "Route / Itinerary", "entry_kind": "aggregate", "purpose": "Represent one governed reusable or computed route, or one candidate or selected itinerary, with ordered structure, constraints, plan clocks, alternatives and successor lineage without becoming its journey, network, schedule, resource or routing engine.", "scope_statement": "Owns mandatory route-or-itinerary kind; object and revision identity; endpoints, ordered waypoints, segments, legs, visits and transfers; route topology and geometry references; itinerary composition; requested and applied constraints; objectives, candidates, ranking and selection rationale; planned clocks and validity; service, schedule, mode and resource references; plan lifecycle, validation, replanning and actual-journey divergence references; estimates, quality, provenance, access, retention and loss-aware projections. Journey execution, networks, places, schedules, services, people, vehicles, bookings, tickets, fares, activities, shipments, incidents, weather, routing engines, source datasets and evidence masters remain external.", "in_scope": [ "Route or itinerary identity, revision, mandatory kind, boundary, ownership and successor lineage", "Ordered route path or itinerary composition, constraints, objectives, alternatives, selected plan, clocks and external bindings", "Validation, disruption, replanning, estimates, provenance, privacy, access, retention and interoperability" ], "out_of_scope": [ "Owning journey, network, place, schedule, service, person, vehicle, booking, ticket, fare, activity, shipment, incident, weather, routing-engine, dataset, evidence or document lifecycles", "Equating route with itinerary, route or itinerary with journey, line with route, segment with leg, waypoint with visit, plan with actual movement or estimate with commitment", "Performing routing computation, autonomous consequential rerouting, safety or legal permission decisions, protected location disclosure or irreversible deletion" ], "boundary_notes": [ { "neighbor": "WM-FLW-009 Journey / Trip", "distinction": "Journey owns the planned or actual movement episode, observations and outcomes. Route / Itinerary owns reusable or computed path and planning-result structure; a journey references a selected plan and may diverge from it.", "source_refs": [ "SRC-001", "SRC-004", "SRC-012", "SRC-013", "SRC-015" ] }, { "neighbor": "Network, Place and Stop", "distinction": "Route / Itinerary orders typed references and may carry snapshot geometry. Network topology, place identity, facilities, restrictions and authoritative geometry remain externally mastered.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-009", "SRC-010", "SRC-011" ] }, { "neighbor": "Line, Journey Pattern, Service and Schedule", "distinction": "A line groups service presentation, a route describes a path, a journey pattern orders scheduled points, and a scheduled trip instantiates service. Their identities and lifecycles remain distinct.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ] }, { "neighbor": "Routing Engine, Algorithm and Computation Job", "distinction": "The model records requests, parameters, versions and results. Execution, resource use, optimization implementation and job control remain owned by external computation masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] }, { "neighbor": "Booking, Ticket, Fare, Activity and Resource", "distinction": "An itinerary may reference entitlements, offers, reservations, activities, vehicles and facilities, but does not own or imply their availability, validity or lifecycle.", "source_refs": [ "SRC-003", "SRC-004", "SRC-013", "SRC-015" ] }, { "neighbor": "Trajectory and Moving Feature", "distinction": "Route / Itinerary describes intended path or plan. Actual temporal geometry and movement observations remain journey or moving-feature evidence and are compared rather than merged.", "source_refs": [ "SRC-012", "SRC-021" ] } ] }, "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-06T20:18:00Z", "relevance": "Defines ROUTE, LINK SEQUENCE, JOURNEY PATTERN, journey and timing concepts." }, { "id": "SRC-002", "title": "Transmodel at a glance", "organization": "CEN Transmodel", "url": "https://www.transmodel-cen.eu/wp-content/uploads/2015/01/Transmodel_at_a_-glance-1.pdf", "version_or_date": "Overview accessed 2026-09-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:18:00Z", "relevance": "Explains route points, physical path projection and ordered journey patterns." }, { "id": "SRC-003", "title": "NeTEx", "organization": "CEN NeTEx", "url": "https://netex-cen.eu/", "version_or_date": "CEN TS 16614 family, site accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:18:00Z", "relevance": "Official European exchange family for public-transport networks, schedules and related route structures." }, { "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-06T20:18:00Z", "relevance": "Defines routes, trips, stop times, shapes, calendars and transfers, with semantics distinct from Transmodel." }, { "id": "SRC-005", "title": "OGC API - Routes overview", "organization": "Open Geospatial Consortium", "url": "https://ogcapi.ogc.org/routes/overview.html", "version_or_date": "Developing specification accessed 2026-09-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:18:00Z", "relevance": "Describes engine-independent route requests, parameters, asynchronous execution and route profiles." }, { "id": "SRC-006", "title": "OGC Routing Pilot Engineering Report", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/per/19-041r3.html", "version_or_date": "OGC 19-041r3, 2020", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:18:00Z", "relevance": "Defines a pilot Route Exchange Model with definition, overview, segments, endpoints and status." }, { "id": "SRC-007", "title": "WPS Routing API Engineering Report", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/per/19-040.html", "version_or_date": "OGC 19-040, 2020", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:18:00Z", "relevance": "Defines route computation inputs including waypoints, temporal, height, load, obstacle, engine, algorithm and dataset choices." }, { "id": "SRC-008", "title": "OGC Standards Roadmap", "organization": "Open Geospatial Consortium", "url": "https://portal.ogc.org/public_ogc/standards/standards_workflow.php?bg=1", "version_or_date": "Roadmap accessed 2026-09-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:18:00Z", "relevance": "Shows OGC Route Exchange Model 21-001 as proposed rather than an approved standard." }, { "id": "SRC-009", "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-06T20:18:00Z", "relevance": "Defines interoperable feature, geometry, spatial-relation and query semantics." }, { "id": "SRC-010", "title": "RFC 7946: The GeoJSON Format", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc7946.html", "version_or_date": "RFC 7946, August 2016", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:18:00Z", "relevance": "Defines portable point, line, feature and feature-collection geometry encoding." }, { "id": "SRC-011", "title": "ISO 19133 Geographic information - Location-based services - Tracking and navigation", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/32500.html", "version_or_date": "ISO 19133:2005", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:18:00Z", "relevance": "Defines conceptual schemas for tracking and navigation services and network-based routing." }, { "id": "SRC-012", "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-06T20:18:00Z", "relevance": "Provides the boundary between planned route and actual moving-feature trajectory." }, { "id": "SRC-013", "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", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:18:00Z", "relevance": "Defines machine-readable travel itineraries, handover points and static, historic, observed and dynamic travel data." }, { "id": "SRC-014", "title": "Multimodal travel information services", "organization": "European Commission", "url": "https://transport.ec.europa.eu/transport-themes/intelligent-transport-systems/road/action-plan-and-directive/multimodal-travel-information-services_en", "version_or_date": "Policy page accessed 2026-09-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T20:18:00Z", "relevance": "Provides EU multimodal journey-planning and data-access context." }, { "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-06T20:18:00Z", "relevance": "Provides lightweight web alignment for itinerary, subtrip, provider, departure and arrival." }, { "id": "SRC-016", "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-06T20:18:00Z", "relevance": "Defines instants, intervals, duration, ordering, temporal position and reference systems." }, { "id": "SRC-017", "title": "RFC 3339: Date and Time on the Internet", "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-06T20:18:00Z", "relevance": "Defines timestamps with seconds and explicit offsets." }, { "id": "SRC-018", "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-06T20:18:00Z", "relevance": "Defines attribution, derivation, revision, invalidation and delegation." }, { "id": "SRC-019", "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-06T20:18:00Z", "relevance": "Defines quality measurements, annotations, policies and provenance." }, { "id": "SRC-020", "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-06T20:18:00Z", "relevance": "Defines permissions, prohibitions, duties and constraints for sensitive itinerary data." }, { "id": "SRC-021", "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-06T20:18:00Z", "relevance": "Catalogues movement representations used to keep route plans distinct from actual trajectories." } ], "structure": { "bundles": [ { "id": "identity-kind-and-boundary", "name": "Identity, kind and boundary", "description": "Groups the governed Route / Itinerary concern for identity, kind and boundary.", "rationale": "Make route and itinerary jointly discoverable without collapsing their different identities or lifecycles.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-018", "SRC-002", "SRC-004", "SRC-013", "SRC-015" ], "layers": [ { "id": "identity-version-and-successor", "name": "Identity, version and successor", "description": "Groups Route / Itinerary context for identity, version and successor without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-018" ], "findings": [ { "id": "route-or-itinerary-identity-namespace-version-and-kind", "name": "Route or itinerary identity, namespace, version and mandatory kind", "description": "Records route or itinerary identity, namespace, version and mandatory kind as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-018" ], "questions": [ { "id": "route-or-itinerary-identity-namespace-version-and-kind-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish route or itinerary identity, namespace, version and mandatory kind?", "kind": "identity", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "route-or-itinerary-identity-namespace-version-and-kind-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access route or itinerary identity, namespace, version and mandatory kind, and under which authority or policy?", "kind": "ownership", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "route-or-itinerary-identity-namespace-version-and-kind-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify route or itinerary identity, namespace, version and mandatory kind?", "kind": "validation", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "route-or-itinerary-identity-namespace-version-and-kind-data", "name": "Route or itinerary identity, namespace, version and mandatory kind data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for route or itinerary identity, namespace, version and mandatory kind.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-018" ] } ], "artifacts": [ { "id": "route-or-itinerary-identity-namespace-version-and-kind-artifact", "name": "Route or itinerary identity, namespace, version and mandatory kind evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting route or itinerary identity, namespace, version and mandatory kind.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "revision-predecessor-successor-effective-period-and-status", "name": "Revision, predecessor, successor, effective period and status", "description": "Records revision, predecessor, successor, effective period and status as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-018" ], "questions": [ { "id": "revision-predecessor-successor-effective-period-and-status-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish revision, predecessor, successor, effective period and status?", "kind": "lifecycle", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "revision-predecessor-successor-effective-period-and-status-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access revision, predecessor, successor, effective period and status, and under which authority or policy?", "kind": "authority", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "revision-predecessor-successor-effective-period-and-status-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify revision, predecessor, successor, effective period and status?", "kind": "security", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "revision-predecessor-successor-effective-period-and-status-data", "name": "Revision, predecessor, successor, effective period and status data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for revision, predecessor, successor, effective period and status.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-018" ] } ], "artifacts": [ { "id": "revision-predecessor-successor-effective-period-and-status-artifact", "name": "Revision, predecessor, successor, effective period and status evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting revision, predecessor, successor, effective period and status.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-018" ] } ], "inline_only_rationale": null } ] }, { "id": "scope-owner-and-plan-boundary", "name": "Scope, owner and plan boundary", "description": "Groups Route / Itinerary context for scope, owner and plan boundary without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-013", "SRC-015" ], "findings": [ { "id": "reusable-route-computed-route-itinerary-and-combined-plan", "name": "Reusable route, computed route, itinerary and combined-plan boundary", "description": "Records reusable route, computed route, itinerary and combined-plan boundary as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-013", "SRC-015" ], "questions": [ { "id": "reusable-route-computed-route-itinerary-and-combined-plan-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish reusable route, computed route, itinerary and combined-plan boundary?", "kind": "classification", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "reusable-route-computed-route-itinerary-and-combined-plan-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access reusable route, computed route, itinerary and combined-plan boundary, and under which authority or policy?", "kind": "constraint", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "reusable-route-computed-route-itinerary-and-combined-plan-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify reusable route, computed route, itinerary and combined-plan boundary?", "kind": "privacy", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "reusable-route-computed-route-itinerary-and-combined-plan-data", "name": "Reusable route, computed route, itinerary and combined-plan boundary data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for reusable route, computed route, itinerary and combined-plan boundary.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-013", "SRC-015" ] } ], "artifacts": [ { "id": "reusable-route-computed-route-itinerary-and-combined-plan-artifact", "name": "Reusable route, computed route, itinerary and combined-plan boundary evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting reusable route, computed route, itinerary and combined-plan boundary.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary 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-013", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "planner-operator-traveller-vehicle-cargo-and-authority-roles", "name": "Planner, operator, traveller, vehicle, cargo and authority roles", "description": "Records planner, operator, traveller, vehicle, cargo and authority roles as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-013", "SRC-015" ], "questions": [ { "id": "planner-operator-traveller-vehicle-cargo-and-authority-roles-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish planner, operator, traveller, vehicle, cargo and authority roles?", "kind": "ownership", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "planner-operator-traveller-vehicle-cargo-and-authority-roles-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access planner, operator, traveller, vehicle, cargo and authority roles, and under which authority or policy?", "kind": "process", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "planner-operator-traveller-vehicle-cargo-and-authority-roles-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify planner, operator, traveller, vehicle, cargo and authority roles?", "kind": "retention", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "planner-operator-traveller-vehicle-cargo-and-authority-roles-data", "name": "Planner, operator, traveller, vehicle, cargo and authority roles data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for planner, operator, traveller, vehicle, cargo and authority roles.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-013", "SRC-015" ] } ], "artifacts": [ { "id": "planner-operator-traveller-vehicle-cargo-and-authority-roles-artifact", "name": "Planner, operator, traveller, vehicle, cargo and authority roles evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting planner, operator, traveller, vehicle, cargo and authority roles.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary 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-013", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "network-path-and-ordered-structure", "name": "Network path and ordered structure", "description": "Groups the governed Route / Itinerary concern for network path and ordered structure.", "rationale": "Represent traversal and plan composition while external networks, places and schedules retain mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ], "layers": [ { "id": "endpoints-waypoints-and-network-path", "name": "Endpoints, waypoints and network path", "description": "Groups Route / Itinerary context for endpoints, waypoints and network path without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ], "findings": [ { "id": "origin-destination-via-waypoint-node-link-and-zone-reference", "name": "Origin, destination, via waypoint, node, link and zone reference", "description": "Records origin, destination, via waypoint, node, link and zone reference as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "origin-destination-via-waypoint-node-link-and-zone-reference-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish origin, destination, via waypoint, node, link and zone reference?", "kind": "spatial", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "origin-destination-via-waypoint-node-link-and-zone-reference-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access origin, destination, via waypoint, node, link and zone reference, and under which authority or policy?", "kind": "event", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "origin-destination-via-waypoint-node-link-and-zone-reference-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify origin, destination, via waypoint, node, link and zone reference?", "kind": "access", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "origin-destination-via-waypoint-node-link-and-zone-reference-data", "name": "Origin, destination, via waypoint, node, link and zone reference data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for origin, destination, via waypoint, node, link and zone reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "origin-destination-via-waypoint-node-link-and-zone-reference-artifact", "name": "Origin, destination, via waypoint, node, link and zone reference evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting origin, destination, via waypoint, node, link and zone reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "directed-segment-sequence-topology-geometry-and-crs", "name": "Directed segment sequence, topology, geometry and CRS", "description": "Records directed segment sequence, topology, geometry and crs as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "directed-segment-sequence-topology-geometry-and-crs-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish directed segment sequence, topology, geometry and crs?", "kind": "composition", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "directed-segment-sequence-topology-geometry-and-crs-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access directed segment sequence, topology, geometry and crs, and under which authority or policy?", "kind": "measurement", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "directed-segment-sequence-topology-geometry-and-crs-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify directed segment sequence, topology, geometry and crs?", "kind": "exception", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "directed-segment-sequence-topology-geometry-and-crs-data", "name": "Directed segment sequence, topology, geometry and CRS data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for directed segment sequence, topology, geometry and crs.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "directed-segment-sequence-topology-geometry-and-crs-artifact", "name": "Directed segment sequence, topology, geometry and CRS evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting directed segment sequence, topology, geometry and crs.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] }, { "id": "legs-stages-visits-and-transfers", "name": "Legs, stages, visits and transfers", "description": "Groups Route / Itinerary context for legs, stages, visits and transfers without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ], "findings": [ { "id": "itinerary-leg-stage-call-visit-activity-and-order", "name": "Itinerary leg, stage, call, visit, activity and order", "description": "Records itinerary leg, stage, call, visit, activity and order as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ], "questions": [ { "id": "itinerary-leg-stage-call-visit-activity-and-order-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish itinerary leg, stage, call, visit, activity and order?", "kind": "composition", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "itinerary-leg-stage-call-visit-activity-and-order-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access itinerary leg, stage, call, visit, activity and order, and under which authority or policy?", "kind": "evidence", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "itinerary-leg-stage-call-visit-activity-and-order-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify itinerary leg, stage, call, visit, activity and order?", "kind": "interoperability", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "itinerary-leg-stage-call-visit-activity-and-order-data", "name": "Itinerary leg, stage, call, visit, activity and order data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for itinerary leg, stage, call, visit, activity and order.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ] } ], "artifacts": [ { "id": "itinerary-leg-stage-call-visit-activity-and-order-artifact", "name": "Itinerary leg, stage, call, visit, activity and order evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting itinerary leg, stage, call, visit, activity and order.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "access-egress-transfer-handover-connection-and-wait", "name": "Access, egress, transfer, handover, connection and wait", "description": "Records access, egress, transfer, handover, connection and wait as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ], "questions": [ { "id": "access-egress-transfer-handover-connection-and-wait-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish access, egress, transfer, handover, connection and wait?", "kind": "relationship", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "access-egress-transfer-handover-connection-and-wait-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access access, egress, transfer, handover, connection and wait, and under which authority or policy?", "kind": "quality", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "access-egress-transfer-handover-connection-and-wait-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify access, egress, transfer, handover, connection and wait?", "kind": "decision", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "access-egress-transfer-handover-connection-and-wait-data", "name": "Access, egress, transfer, handover, connection and wait data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for access, egress, transfer, handover, connection and wait.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ] } ], "artifacts": [ { "id": "access-egress-transfer-handover-connection-and-wait-artifact", "name": "Access, egress, transfer, handover, connection and wait evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting access, egress, transfer, handover, connection and wait.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "constraints-criteria-and-selection", "name": "Constraints, criteria and selection", "description": "Groups the governed Route / Itinerary concern for constraints, criteria and selection.", "rationale": "Preserve what was requested, what was feasible and why one alternative was selected.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-013", "SRC-014", "SRC-019" ], "layers": [ { "id": "request-and-feasibility-constraints", "name": "Request and feasibility constraints", "description": "Groups Route / Itinerary context for request and feasibility constraints without importing neighboring master lifecycles.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-013", "SRC-014" ], "findings": [ { "id": "mode-accessibility-vehicle-cargo-height-load-and-safety-constraint", "name": "Mode, accessibility, vehicle, cargo, height, load and safety constraint", "description": "Records mode, accessibility, vehicle, cargo, height, load and safety constraint as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-013", "SRC-014" ], "questions": [ { "id": "mode-accessibility-vehicle-cargo-height-load-and-safety-constraint-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish mode, accessibility, vehicle, cargo, height, load and safety constraint?", "kind": "constraint", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "mode-accessibility-vehicle-cargo-height-load-and-safety-constraint-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access mode, accessibility, vehicle, cargo, height, load and safety constraint, and under which authority or policy?", "kind": "validation", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "mode-accessibility-vehicle-cargo-height-load-and-safety-constraint-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify mode, accessibility, vehicle, cargo, height, load and safety constraint?", "kind": "identity", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "mode-accessibility-vehicle-cargo-height-load-and-safety-constraint-data", "name": "Mode, accessibility, vehicle, cargo, height, load and safety constraint data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for mode, accessibility, vehicle, cargo, height, load and safety constraint.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-013", "SRC-014" ] } ], "artifacts": [ { "id": "mode-accessibility-vehicle-cargo-height-load-and-safety-constraint-artifact", "name": "Mode, accessibility, vehicle, cargo, height, load and safety constraint evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting mode, accessibility, vehicle, cargo, height, load and safety constraint.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary 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-011", "SRC-013", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "avoid-prefer-must-pass-time-window-permission-and-policy-constraint", "name": "Avoid, prefer, must-pass, time-window, permission and policy constraint", "description": "Records avoid, prefer, must-pass, time-window, permission and policy constraint as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-013", "SRC-014" ], "questions": [ { "id": "avoid-prefer-must-pass-time-window-permission-and-policy-constraint-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish avoid, prefer, must-pass, time-window, permission and policy constraint?", "kind": "constraint", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "avoid-prefer-must-pass-time-window-permission-and-policy-constraint-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access avoid, prefer, must-pass, time-window, permission and policy constraint, and under which authority or policy?", "kind": "security", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "avoid-prefer-must-pass-time-window-permission-and-policy-constraint-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify avoid, prefer, must-pass, time-window, permission and policy constraint?", "kind": "classification", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "avoid-prefer-must-pass-time-window-permission-and-policy-constraint-data", "name": "Avoid, prefer, must-pass, time-window, permission and policy constraint data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for avoid, prefer, must-pass, time-window, permission and policy constraint.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-013", "SRC-014" ] } ], "artifacts": [ { "id": "avoid-prefer-must-pass-time-window-permission-and-policy-constraint-artifact", "name": "Avoid, prefer, must-pass, time-window, permission and policy constraint evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting avoid, prefer, must-pass, time-window, permission and policy constraint.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary 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-011", "SRC-013", "SRC-014" ] } ], "inline_only_rationale": null } ] }, { "id": "objective-alternatives-and-choice", "name": "Objective, alternatives and choice", "description": "Groups Route / Itinerary context for objective, alternatives and choice without importing neighboring master lifecycles.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-013", "SRC-019" ], "findings": [ { "id": "distance-time-cost-emissions-energy-risk-and-comfort-objective", "name": "Distance, time, cost, emissions, energy, risk and comfort objective", "description": "Records distance, time, cost, emissions, energy, risk and comfort objective as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-013", "SRC-019" ], "questions": [ { "id": "distance-time-cost-emissions-energy-risk-and-comfort-objective-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish distance, time, cost, emissions, energy, risk and comfort objective?", "kind": "decision", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "distance-time-cost-emissions-energy-risk-and-comfort-objective-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access distance, time, cost, emissions, energy, risk and comfort objective, and under which authority or policy?", "kind": "privacy", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "distance-time-cost-emissions-energy-risk-and-comfort-objective-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify distance, time, cost, emissions, energy, risk and comfort objective?", "kind": "composition", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "distance-time-cost-emissions-energy-risk-and-comfort-objective-data", "name": "Distance, time, cost, emissions, energy, risk and comfort objective data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for distance, time, cost, emissions, energy, risk and comfort objective.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-013", "SRC-019" ] } ], "artifacts": [ { "id": "distance-time-cost-emissions-energy-risk-and-comfort-objective-artifact", "name": "Distance, time, cost, emissions, energy, risk and comfort objective evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting distance, time, cost, emissions, energy, risk and comfort objective.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary 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-013", "SRC-019" ] } ], "inline_only_rationale": null }, { "id": "candidate-alternative-ranking-selection-rejection-and-rationale", "name": "Candidate alternative, ranking, selection, rejection and rationale", "description": "Records candidate alternative, ranking, selection, rejection and rationale as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-013", "SRC-019" ], "questions": [ { "id": "candidate-alternative-ranking-selection-rejection-and-rationale-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish candidate alternative, ranking, selection, rejection and rationale?", "kind": "decision", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "candidate-alternative-ranking-selection-rejection-and-rationale-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access candidate alternative, ranking, selection, rejection and rationale, and under which authority or policy?", "kind": "retention", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "candidate-alternative-ranking-selection-rejection-and-rationale-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify candidate alternative, ranking, selection, rejection and rationale?", "kind": "relationship", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "candidate-alternative-ranking-selection-rejection-and-rationale-data", "name": "Candidate alternative, ranking, selection, rejection and rationale data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for candidate alternative, ranking, selection, rejection and rationale.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-013", "SRC-019" ] } ], "artifacts": [ { "id": "candidate-alternative-ranking-selection-rejection-and-rationale-artifact", "name": "Candidate alternative, ranking, selection, rejection and rationale evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting candidate alternative, ranking, selection, rejection and rationale.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary 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-013", "SRC-019" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "temporal-service-and-resource-plan", "name": "Temporal, service and resource plan", "description": "Groups the governed Route / Itinerary concern for temporal, service and resource plan.", "rationale": "Bind plan clocks and external operational resources without treating estimates as commitments.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-013", "SRC-016", "SRC-017", "SRC-003", "SRC-015" ], "layers": [ { "id": "validity-planned-time-and-continuity", "name": "Validity, planned time and continuity", "description": "Groups Route / Itinerary context for validity, planned time and continuity without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-013", "SRC-016", "SRC-017" ], "findings": [ { "id": "operating-day-validity-departure-arrival-duration-and-time-zone", "name": "Operating day, validity, departure, arrival, duration and time zone", "description": "Records operating day, validity, departure, arrival, duration and time zone as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-013", "SRC-016", "SRC-017" ], "questions": [ { "id": "operating-day-validity-departure-arrival-duration-and-time-zone-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish operating day, validity, departure, arrival, duration and time zone?", "kind": "temporal", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "operating-day-validity-departure-arrival-duration-and-time-zone-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access operating day, validity, departure, arrival, duration and time zone, and under which authority or policy?", "kind": "access", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "operating-day-validity-departure-arrival-duration-and-time-zone-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify operating day, validity, departure, arrival, duration and time zone?", "kind": "state", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "operating-day-validity-departure-arrival-duration-and-time-zone-data", "name": "Operating day, validity, departure, arrival, duration and time zone data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for operating day, validity, departure, arrival, duration and time zone.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-013", "SRC-016", "SRC-017" ] } ], "artifacts": [ { "id": "operating-day-validity-departure-arrival-duration-and-time-zone-artifact", "name": "Operating day, validity, departure, arrival, duration and time zone evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting operating day, validity, departure, arrival, duration and time zone.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary 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-013", "SRC-016", "SRC-017" ] } ], "inline_only_rationale": null }, { "id": "requested-planned-estimated-predicted-committed-and-slack-time", "name": "Requested, planned, estimated, predicted, committed and slack time", "description": "Records requested, planned, estimated, predicted, committed and slack time as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-013", "SRC-016", "SRC-017" ], "questions": [ { "id": "requested-planned-estimated-predicted-committed-and-slack-time-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish requested, planned, estimated, predicted, committed and slack time?", "kind": "classification", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "requested-planned-estimated-predicted-committed-and-slack-time-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access requested, planned, estimated, predicted, committed and slack time, and under which authority or policy?", "kind": "exception", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "requested-planned-estimated-predicted-committed-and-slack-time-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify requested, planned, estimated, predicted, committed and slack time?", "kind": "lifecycle", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "requested-planned-estimated-predicted-committed-and-slack-time-data", "name": "Requested, planned, estimated, predicted, committed and slack time data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for requested, planned, estimated, predicted, committed and slack time.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-013", "SRC-016", "SRC-017" ] } ], "artifacts": [ { "id": "requested-planned-estimated-predicted-committed-and-slack-time-artifact", "name": "Requested, planned, estimated, predicted, committed and slack time evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting requested, planned, estimated, predicted, committed and slack time.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary 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-013", "SRC-016", "SRC-017" ] } ], "inline_only_rationale": null } ] }, { "id": "mode-service-schedule-and-resource-bindings", "name": "Mode, service, schedule and resource bindings", "description": "Groups Route / Itinerary context for mode, service, schedule and resource bindings without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ], "findings": [ { "id": "mode-line-route-pattern-service-trip-and-schedule-reference", "name": "Mode, line, route pattern, service trip and schedule reference", "description": "Records mode, line, route pattern, service trip and schedule reference as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ], "questions": [ { "id": "mode-line-route-pattern-service-trip-and-schedule-reference-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish mode, line, route pattern, service trip and schedule reference?", "kind": "relationship", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "mode-line-route-pattern-service-trip-and-schedule-reference-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access mode, line, route pattern, service trip and schedule reference, and under which authority or policy?", "kind": "interoperability", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "mode-line-route-pattern-service-trip-and-schedule-reference-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify mode, line, route pattern, service trip and schedule reference?", "kind": "temporal", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "mode-line-route-pattern-service-trip-and-schedule-reference-data", "name": "Mode, line, route pattern, service trip and schedule reference data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for mode, line, route pattern, service trip and schedule reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ] } ], "artifacts": [ { "id": "mode-line-route-pattern-service-trip-and-schedule-reference-artifact", "name": "Mode, line, route pattern, service trip and schedule reference evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting mode, line, route pattern, service trip and schedule reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "vehicle-seat-booking-ticket-fare-activity-and-facility-reference", "name": "Vehicle, seat, booking, ticket, fare, activity and facility reference", "description": "Records vehicle, seat, booking, ticket, fare, activity and facility reference as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ], "questions": [ { "id": "vehicle-seat-booking-ticket-fare-activity-and-facility-reference-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish vehicle, seat, booking, ticket, fare, activity and facility reference?", "kind": "relationship", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "vehicle-seat-booking-ticket-fare-activity-and-facility-reference-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access vehicle, seat, booking, ticket, fare, activity and facility reference, and under which authority or policy?", "kind": "decision", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "vehicle-seat-booking-ticket-fare-activity-and-facility-reference-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify vehicle, seat, booking, ticket, fare, activity and facility reference?", "kind": "spatial", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "vehicle-seat-booking-ticket-fare-activity-and-facility-reference-data", "name": "Vehicle, seat, booking, ticket, fare, activity and facility reference data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for vehicle, seat, booking, ticket, fare, activity and facility reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ] } ], "artifacts": [ { "id": "vehicle-seat-booking-ticket-fare-activity-and-facility-reference-artifact", "name": "Vehicle, seat, booking, ticket, fare, activity and facility reference evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting vehicle, seat, booking, ticket, fare, activity and facility reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-change-and-evaluation", "name": "Lifecycle, change and evaluation", "description": "Groups the governed Route / Itinerary concern for lifecycle, change and evaluation.", "rationale": "Make computation, selection, invalidation and replanning auditable while preserving history.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-013", "SRC-018", "SRC-009", "SRC-011", "SRC-019" ], "layers": [ { "id": "plan-state-disruption-and-replanning", "name": "Plan state, disruption and replanning", "description": "Groups Route / Itinerary context for plan state, disruption and replanning without importing neighboring master lifecycles.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-013", "SRC-018" ], "findings": [ { "id": "draft-requested-computing-candidate-selected-confirmed-and-cancelled-state", "name": "Draft, requested, computing, candidate, selected, confirmed and cancelled state", "description": "Records draft, requested, computing, candidate, selected, confirmed and cancelled state as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-013", "SRC-018" ], "questions": [ { "id": "draft-requested-computing-candidate-selected-confirmed-and-cancelled-state-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish draft, requested, computing, candidate, selected, confirmed and cancelled state?", "kind": "lifecycle", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "draft-requested-computing-candidate-selected-confirmed-and-cancelled-state-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access draft, requested, computing, candidate, selected, confirmed and cancelled state, and under which authority or policy?", "kind": "identity", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "draft-requested-computing-candidate-selected-confirmed-and-cancelled-state-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify draft, requested, computing, candidate, selected, confirmed and cancelled state?", "kind": "provenance", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "draft-requested-computing-candidate-selected-confirmed-and-cancelled-state-data", "name": "Draft, requested, computing, candidate, selected, confirmed and cancelled state data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for draft, requested, computing, candidate, selected, confirmed and cancelled state.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-013", "SRC-018" ] } ], "artifacts": [ { "id": "draft-requested-computing-candidate-selected-confirmed-and-cancelled-state-artifact", "name": "Draft, requested, computing, candidate, selected, confirmed and cancelled state evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting draft, requested, computing, candidate, selected, confirmed and cancelled state.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary 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-013", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "disruption-invalidity-reroute-difference-successor-and-actual-divergence", "name": "Disruption, invalidity, reroute, difference, successor and actual divergence", "description": "Records disruption, invalidity, reroute, difference, successor and actual divergence as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-013", "SRC-018" ], "questions": [ { "id": "disruption-invalidity-reroute-difference-successor-and-actual-divergence-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish disruption, invalidity, reroute, difference, successor and actual divergence?", "kind": "exception", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "disruption-invalidity-reroute-difference-successor-and-actual-divergence-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access disruption, invalidity, reroute, difference, successor and actual divergence, and under which authority or policy?", "kind": "classification", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "disruption-invalidity-reroute-difference-successor-and-actual-divergence-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify disruption, invalidity, reroute, difference, successor and actual divergence?", "kind": "ownership", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "disruption-invalidity-reroute-difference-successor-and-actual-divergence-data", "name": "Disruption, invalidity, reroute, difference, successor and actual divergence data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for disruption, invalidity, reroute, difference, successor and actual divergence.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-013", "SRC-018" ] } ], "artifacts": [ { "id": "disruption-invalidity-reroute-difference-successor-and-actual-divergence-artifact", "name": "Disruption, invalidity, reroute, difference, successor and actual divergence evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting disruption, invalidity, reroute, difference, successor and actual divergence.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary 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-013", "SRC-018" ] } ], "inline_only_rationale": null } ] }, { "id": "measures-uncertainty-and-quality", "name": "Measures, uncertainty and quality", "description": "Groups Route / Itinerary context for measures, uncertainty and quality without importing neighboring master lifecycles.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-011", "SRC-019" ], "findings": [ { "id": "distance-duration-cost-toll-energy-emissions-and-risk-estimate", "name": "Distance, duration, cost, toll, energy, emissions and risk estimate", "description": "Records distance, duration, cost, toll, energy, emissions and risk estimate as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-011", "SRC-019" ], "questions": [ { "id": "distance-duration-cost-toll-energy-emissions-and-risk-estimate-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish distance, duration, cost, toll, energy, emissions and risk estimate?", "kind": "measurement", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "distance-duration-cost-toll-energy-emissions-and-risk-estimate-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access distance, duration, cost, toll, energy, emissions and risk estimate, and under which authority or policy?", "kind": "composition", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "distance-duration-cost-toll-energy-emissions-and-risk-estimate-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify distance, duration, cost, toll, energy, emissions and risk estimate?", "kind": "authority", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "distance-duration-cost-toll-energy-emissions-and-risk-estimate-data", "name": "Distance, duration, cost, toll, energy, emissions and risk estimate data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for distance, duration, cost, toll, energy, emissions and risk estimate.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-011", "SRC-019" ] } ], "artifacts": [ { "id": "distance-duration-cost-toll-energy-emissions-and-risk-estimate-artifact", "name": "Distance, duration, cost, toll, energy, emissions and risk estimate evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting distance, duration, cost, toll, energy, emissions and risk estimate.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-011", "SRC-019" ] } ], "inline_only_rationale": null }, { "id": "coverage-freshness-precision-confidence-uncertainty-and-validation", "name": "Coverage, freshness, precision, confidence, uncertainty and validation", "description": "Records coverage, freshness, precision, confidence, uncertainty and validation as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-011", "SRC-019" ], "questions": [ { "id": "coverage-freshness-precision-confidence-uncertainty-and-validation-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish coverage, freshness, precision, confidence, uncertainty and validation?", "kind": "quality", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "coverage-freshness-precision-confidence-uncertainty-and-validation-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access coverage, freshness, precision, confidence, uncertainty and validation, and under which authority or policy?", "kind": "relationship", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "coverage-freshness-precision-confidence-uncertainty-and-validation-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify coverage, freshness, precision, confidence, uncertainty and validation?", "kind": "constraint", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "coverage-freshness-precision-confidence-uncertainty-and-validation-data", "name": "Coverage, freshness, precision, confidence, uncertainty and validation data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for coverage, freshness, precision, confidence, uncertainty and validation.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-011", "SRC-019" ] } ], "artifacts": [ { "id": "coverage-freshness-precision-confidence-uncertainty-and-validation-artifact", "name": "Coverage, freshness, precision, confidence, uncertainty and validation evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting coverage, freshness, precision, confidence, uncertainty and validation.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-011", "SRC-019" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "provenance-access-and-interoperability", "name": "Provenance, access and interoperability", "description": "Groups the governed Route / Itinerary concern for provenance, access and interoperability.", "rationale": "Make every plan reproducible, governable and safely projectable across incompatible route vocabularies.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-018", "SRC-019", "SRC-001", "SRC-003", "SRC-004", "SRC-009", "SRC-010", "SRC-013", "SRC-015", "SRC-016", "SRC-017", "SRC-020", "SRC-021" ], "layers": [ { "id": "source-engine-algorithm-and-lineage", "name": "Source, engine, algorithm and lineage", "description": "Groups Route / Itinerary context for source, engine, algorithm and lineage without importing neighboring master lifecycles.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-018", "SRC-019" ], "findings": [ { "id": "network-dataset-version-engine-algorithm-parameter-and-job-reference", "name": "Network dataset version, engine, algorithm, parameter and job reference", "description": "Records network dataset version, engine, algorithm, parameter and job reference as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-018", "SRC-019" ], "questions": [ { "id": "network-dataset-version-engine-algorithm-parameter-and-job-reference-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish network dataset version, engine, algorithm, parameter and job reference?", "kind": "provenance", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "network-dataset-version-engine-algorithm-parameter-and-job-reference-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access network dataset version, engine, algorithm, parameter and job reference, and under which authority or policy?", "kind": "state", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "network-dataset-version-engine-algorithm-parameter-and-job-reference-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify network dataset version, engine, algorithm, parameter and job reference?", "kind": "process", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "network-dataset-version-engine-algorithm-parameter-and-job-reference-data", "name": "Network dataset version, engine, algorithm, parameter and job reference data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for network dataset version, engine, algorithm, parameter and job reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-018", "SRC-019" ] } ], "artifacts": [ { "id": "network-dataset-version-engine-algorithm-parameter-and-job-reference-artifact", "name": "Network dataset version, engine, algorithm, parameter and job reference evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting network dataset version, engine, algorithm, parameter and job reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary 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-018", "SRC-019" ] } ], "inline_only_rationale": null }, { "id": "assertion-derivation-correction-invalidation-review-and-evidence", "name": "Assertion, derivation, correction, invalidation, review and evidence", "description": "Records assertion, derivation, correction, invalidation, review and evidence as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-018", "SRC-019" ], "questions": [ { "id": "assertion-derivation-correction-invalidation-review-and-evidence-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish assertion, derivation, correction, invalidation, review and evidence?", "kind": "evidence", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "assertion-derivation-correction-invalidation-review-and-evidence-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access assertion, derivation, correction, invalidation, review and evidence, and under which authority or policy?", "kind": "lifecycle", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "assertion-derivation-correction-invalidation-review-and-evidence-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify assertion, derivation, correction, invalidation, review and evidence?", "kind": "event", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "assertion-derivation-correction-invalidation-review-and-evidence-data", "name": "Assertion, derivation, correction, invalidation, review and evidence data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for assertion, derivation, correction, invalidation, review and evidence.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-018", "SRC-019" ] } ], "artifacts": [ { "id": "assertion-derivation-correction-invalidation-review-and-evidence-artifact", "name": "Assertion, derivation, correction, invalidation, review and evidence evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting assertion, derivation, correction, invalidation, review and evidence.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary 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-018", "SRC-019" ] } ], "inline_only_rationale": null } ] }, { "id": "access-retention-and-crosswalks", "name": "Access, retention and crosswalks", "description": "Groups Route / Itinerary context for access, retention and crosswalks without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ], "findings": [ { "id": "location-sensitivity-purpose-consent-access-retention-and-license", "name": "Location sensitivity, purpose, consent, access, retention and license", "description": "Records location sensitivity, purpose, consent, access, retention and license as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ], "questions": [ { "id": "location-sensitivity-purpose-consent-access-retention-and-license-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish location sensitivity, purpose, consent, access, retention and license?", "kind": "privacy", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "location-sensitivity-purpose-consent-access-retention-and-license-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access location sensitivity, purpose, consent, access, retention and license, and under which authority or policy?", "kind": "temporal", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "location-sensitivity-purpose-consent-access-retention-and-license-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify location sensitivity, purpose, consent, access, retention and license?", "kind": "measurement", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "location-sensitivity-purpose-consent-access-retention-and-license-data", "name": "Location sensitivity, purpose, consent, access, retention and license data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for location sensitivity, purpose, consent, access, retention and license.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ] } ], "artifacts": [ { "id": "location-sensitivity-purpose-consent-access-retention-and-license-artifact", "name": "Location sensitivity, purpose, consent, access, retention and license evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting location sensitivity, purpose, consent, access, retention and license.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ] } ], "inline_only_rationale": null }, { "id": "transmodel-netex-gtfs-ogc-geojson-schema-org-time-and-provenance-crosswalk", "name": "Transmodel, NeTEx, GTFS, OGC, GeoJSON, Schema.org, time and provenance crosswalk", "description": "Records transmodel, netex, gtfs, ogc, geojson, schema.org, time and provenance crosswalk as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ], "questions": [ { "id": "transmodel-netex-gtfs-ogc-geojson-schema-org-time-and-provenance-crosswalk-q01", "text": "Which route or itinerary identity, kind, revision, ordered component, time basis and source establish transmodel, netex, gtfs, ogc, geojson, schema.org, time and provenance crosswalk?", "kind": "interoperability", "answer_data": [ "route or itinerary identifier, mandatory kind, namespace, revision and lifecycle state", "origin, destination, ordered waypoint, segment, leg, visit or transfer references", "validity, planned clocks, source profile, confidence and external master references" ] }, { "id": "transmodel-netex-gtfs-ogc-geojson-schema-org-time-and-provenance-crosswalk-q02", "text": "Who requested, computed, selected, owns, reviewed, corrected or may access transmodel, netex, gtfs, ogc, geojson, schema.org, time and provenance crosswalk, and under which authority or policy?", "kind": "spatial", "answer_data": [ "planner, requester, operator, traveller, asset steward, routing provider and reviewer roles", "delegation, purpose, constraint, jurisdiction, permission, license and access scope", "assertion owner, algorithm or method, reviewer, correction actor and disputed state" ] }, { "id": "transmodel-netex-gtfs-ogc-geojson-schema-org-time-and-provenance-crosswalk-q03", "text": "Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify transmodel, netex, gtfs, ogc, geojson, schema.org, time and provenance crosswalk?", "kind": "evidence", "answer_data": [ "requested and applied constraints, objectives, candidate ranking and selection rationale", "distance, duration, cost, energy, emissions, risk, tolerance and uncertainty", "network snapshot, engine and algorithm version, digest, successor, invalidation and semantic-loss declaration" ] } ], "data_elements": [ { "id": "transmodel-netex-gtfs-ogc-geojson-schema-org-time-and-provenance-crosswalk-data", "name": "Transmodel, NeTEx, GTFS, OGC, GeoJSON, Schema.org, time and provenance crosswalk data", "description": "Typed route- or itinerary-scoped values and references required to answer the governed questions for transmodel, netex, gtfs, ogc, geojson, schema.org, time and provenance crosswalk.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ] } ], "artifacts": [ { "id": "transmodel-netex-gtfs-ogc-geojson-schema-org-time-and-provenance-crosswalk-artifact", "name": "Transmodel, NeTEx, GTFS, OGC, GeoJSON, Schema.org, time and provenance crosswalk evidence manifest", "description": "Digest-addressed manifest of definitions, requests, alternatives, selections, validations, corrections and external records supporting transmodel, netex, gtfs, ogc, geojson, schema.org, time and provenance crosswalk.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative route or itinerary master-system identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-plan-object", "name": "Register route or itinerary", "description": "Create one governed route or itinerary identity with a mandatory kind and boundary.", "inputs": [ "kind discriminator", "origin and destination", "owner and source" ], "outputs": [ "plan-object identifier", "initial revision" ], "preconditions": [ "active Dimension", "create authority" ], "effects": [ "identity and explicit unknowns are appended" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-018" ] }, { "id": "define-route", "name": "Define directed route", "description": "Append ordered waypoints, nodes, links, segments, topology and geometry references.", "inputs": [ "route identifier", "ordered path components", "network and geometry references" ], "outputs": [ "validated route definition" ], "preconditions": [ "route kind", "network profile known" ], "effects": [ "route definition is versioned without importing network mastership" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-009", "SRC-010", "SRC-011" ] }, { "id": "compose-itinerary", "name": "Compose itinerary", "description": "Append ordered legs, stages, visits, calls, transfers and activity references.", "inputs": [ "itinerary identifier", "ordered components", "route, place and service references" ], "outputs": [ "validated itinerary composition" ], "preconditions": [ "itinerary kind", "stable component references" ], "effects": [ "composition and continuity checks are recorded" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ] }, { "id": "bind-constraints", "name": "Bind request constraints", "description": "Record hard, soft, accessibility, operational, safety and permission constraints.", "inputs": [ "plan-object identifier", "constraint set", "authority and purpose" ], "outputs": [ "typed constraint profile" ], "preconditions": [ "constraint semantics and units known" ], "effects": [ "requested and applied constraints remain separately auditable" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-013" ] }, { "id": "record-candidates", "name": "Record candidate alternatives", "description": "Register external routing request, parameters and candidate results without owning the routing engine.", "inputs": [ "routing request reference", "engine, algorithm and dataset versions", "candidate results" ], "outputs": [ "candidate set", "comparison view" ], "preconditions": [ "external computation completed", "source snapshot available" ], "effects": [ "alternatives and estimates are appended with provenance" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-018", "SRC-019" ] }, { "id": "select-plan", "name": "Select route or itinerary", "description": "Record selection, ranking, rejection rationale and any confirmation state.", "inputs": [ "candidate set", "objective weights", "decision authority" ], "outputs": [ "selected revision", "decision trace" ], "preconditions": [ "candidates valid for the same request" ], "effects": [ "selection is appended without deleting alternatives" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-013", "SRC-019" ] }, { "id": "bind-services-resources", "name": "Bind services and resources", "description": "Bind modes, schedules, services, vehicles, facilities, bookings and activities as external references.", "inputs": [ "itinerary revision", "service and resource references", "planned times" ], "outputs": [ "typed bindings" ], "preconditions": [ "external identities resolvable" ], "effects": [ "plan bindings are versioned without importing external lifecycles" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-013", "SRC-015" ] }, { "id": "validate-plan", "name": "Validate continuity and feasibility", "description": "Validate order, topology, geometry, clocks, transfers, constraints, resource bindings and source freshness.", "inputs": [ "route or itinerary revision", "validation profile", "external snapshots" ], "outputs": [ "validation report", "blocking and non-blocking issues" ], "preconditions": [ "pinned profile and tolerance rules" ], "effects": [ "validation evidence is appended; the plan is not silently repaired" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-016", "SRC-017", "SRC-019" ] }, { "id": "supersede-replan", "name": "Supersede or replan", "description": "Create a successor after disruption, invalidity, changed constraint or better alternative.", "inputs": [ "current revision", "change evidence", "replacement definition" ], "outputs": [ "successor revision", "difference and invalidation trace" ], "preconditions": [ "change authority", "affected scope known" ], "effects": [ "prior plan remains resolvable and immutable" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-018" ] }, { "id": "project-plan", "name": "Project route or itinerary", "description": "Produce minimum-necessary standards-aligned or stakeholder views.", "inputs": [ "plan 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-003", "SRC-004", "SRC-005", "SRC-009", "SRC-010", "SRC-013", "SRC-015", "SRC-016", "SRC-018", "SRC-019", "SRC-020" ] } ], "composition": [ { "target": "WM-FLW-009 Journey / Trip", "relation": "REFERENCE", "purpose": "Bind a selected plan to intended or actual movement while preserving execution observations and outcomes in Journey.", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-012", "SRC-013", "SRC-015" ] }, { "target": "Network, Place, Stop, Service, Schedule, Person, Vehicle, Booking, Ticket, Activity, Shipment, Incident, Engine, Dataset and Evidence models", "relation": "REFERENCE", "purpose": "Resolve external masters without duplicating their identity, authority or lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-018" ] }, { "target": "Transmodel v6.2 and NeTEx", "relation": "ALIGN", "purpose": "Project European public-transport route and journey-pattern views with explicit type and version mappings.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "target": "GTFS Schedule", "relation": "ALIGN", "purpose": "Project routes, trips, stop-time sequences, shapes, calendars and transfers without adopting GTFS terminology as universal.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "OGC API Routes, Route Exchange Model, GeoSPARQL and GeoJSON", "relation": "ALIGN", "purpose": "Project engine-independent route requests and geometry while pinning developing OGC drafts and declared conformance.", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010" ] }, { "target": "ISO 19133, ISO 19141 and OGC Moving Features", "relation": "ALIGN", "purpose": "Align navigation and planned-route concepts while keeping actual moving-feature trajectory external.", "required": false, "source_refs": [ "SRC-011", "SRC-012", "SRC-021" ] }, { "target": "EU multimodal travel information and Schema.org Trip", "relation": "ALIGN", "purpose": "Project regional machine-readable itinerary and lightweight web-discovery views with explicit limitations.", "required": false, "source_refs": [ "SRC-013", "SRC-014", "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-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the Dimension owner, route and itinerary stewards, routing authorities and accountable decision roles.", "Register authoritative network, place, service, schedule, person, vehicle, booking, ticket, activity, shipment, incident, routing-engine and evidence masters.", "Publish route, itinerary, relation, constraint, identifier, access, retention, quality and interoperability registries.", "Pin mode, region, network, geometry, operating-day, timezone, accessibility, safety, privacy, licensing and exchange profiles." ], "namespace_guidance": "Mint route, itinerary, revision, leg, segment, constraint, candidate and projection identifiers only in the adopting Dimension namespace; preserve network, place, service, schedule, person, vehicle, booking, ticket, activity, shipment, incident, engine and dataset identities as typed external references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local route, itinerary, constraint, identifier, access, retention and provenance registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by registry ID, model version, mandatory route-or-itinerary kind, authoritative master ID, immutable revision, endpoints, effective period and source profile; never use date, filename, geometry hash or endpoint pair alone as identity.", "Keep reusable route, computed route, itinerary, journey, line, journey pattern, segment, leg, waypoint, call, visit, computation job and trajectory distinct and preserve alternatives, 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 plan revisions and identifiers." ], "compatibility_rules": [ "Consumers may ignore unknown additive fields only when kind, identity, endpoints, order, topology, clocks, constraint, state, provenance and access meaning remain intact.", "Transmodel, NeTEx, GTFS, OGC, GeoJSON, 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 route or itinerary master-system identifier and immutable revision.", "Governed globally resolvable route, itinerary, segment or leg 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 request, computation, planned, estimated, predicted, committed, selection, invalidation, correction and ingestion times distinct.", "serial_naming_rule": "Name serial artifacts as {route-or-itinerary-id}--{artifact-kind}--{revision-or-event-id}; never use a date, endpoint, route number, traveller, vehicle, filename or hash alone as identity.", "integrity_rule": "Store digest, media type, byte length, issuer, source and vocabulary versions, plan scope, event and record times, provenance, assurance, license and access marking for each retained serial artifact." }, "policies": [ "The adopting Dimension declares who may create, compute, select, confirm, bind, validate, supersede, disclose, retain and tombstone route or itinerary records.", "Every assertion requires object kind, identity and revision, path or itinerary scope, time kind, source, authority, confidence, status and lineage as applicable.", "Agents never infer actual movement, passenger presence, legal permission, reservation, feasibility or safety from a route, itinerary, estimate, ticket or routing status alone.", "Journeys, networks, places, services, schedules, people, vehicles, bookings, tickets, fares, activities, shipments, incidents, weather, engines, datasets and evidence remain external masters.", "Automated agents may add low-risk candidates, validations and projections under delegation, but consequential rerouting, safety decisions, protected location disclosure and irreversible deletion require accountable authority." ], "crud": { "read": [ "Resolve active Dimension, purpose, role, mandatory kind, requested revision, time horizon, assurance, freshness, license and access policy; return the minimum permitted projection." ], "create": [ "Create stable identity, mandatory kind, endpoints or itinerary boundary, temporal basis, source, authority and explicit unknowns before adding path components or constraints." ], "update": [ "Append an immutable definition, constraint, candidate, selection, binding, validation or correction revision with actor, authority, reason, RFC 3339 effective time and predecessor." ], "delete": [ "Apply privacy, safety, dispute, audit, retention and legal-hold policy; tombstone eligible Route / Itinerary-owned records or withdraw projections while preserving identity, material provenance and non-cascading external references." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Own namespace, mastership, delegation, access, retention and federation rules." ] }, { "name": "Route steward", "responsibilities": [ "Own reusable or computed path boundary, topology, geometry references and revision lineage." ] }, { "name": "Itinerary steward", "responsibilities": [ "Own ordered planning result, alternatives, selection and successor history." ] }, { "name": "Network or schedule steward", "responsibilities": [ "Own referenced network, place, service and schedule masters." ] }, { "name": "Routing provider", "responsibilities": [ "Own engine, algorithm, dataset, computation job and result assertions it issues." ] }, { "name": "Traveller, operator or asset authority", "responsibilities": [ "Supply applicable preferences, constraints, permissions and accountable decisions." ] }, { "name": "Reviewer or auditor", "responsibilities": [ "Review feasibility, 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, object kind, location sensitivity, license 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 plan, correction or legal-hold evidence." ], "audit_requirements": [ "Log actor, role, purpose, object 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, route and itinerary authority, active mode, jurisdiction, time, access, retention, license and disclosure policies.", "Read this model AGENTS.md, pinned spec.yaml and required journey, network, place, service, schedule, person, vehicle, booking, ticket, activity, shipment, incident, engine, dataset and evidence model instructions before mutation." ] } }, "coverage": { "claim": "WM-FLW-010 covers a governed Route / Itinerary aggregate family with a mandatory kind discriminator, ordered path or itinerary composition, constraints, objectives, alternatives, selection, planned clocks, external operational bindings, validation, successor planning, estimates, provenance, access and loss-aware projections. Mode, jurisdiction, aggregate-split, routing-algorithm, implementation-conformance and independent-review questions remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Route, itinerary, combined-plan, revision, segment, leg, candidate and projection identities remain distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Mandatory kind separates reusable route, computed route, itinerary and combined planning views." }, { "dimension": "direct properties", "status": "covered", "notes": "Endpoints, order, topology, geometry, constraints, clocks, selection and plan state are covered without importing external masters." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Definition, request, computation result, selection, validation and actual-journey divergence are typed assertions." }, { "dimension": "lifecycle", "status": "covered", "notes": "Draft, requested, computing, candidate, selected, confirmed, invalid, superseded and cancelled states preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Networks, places, services, schedules, people, vehicles, resources, bookings, journeys and evidence use typed references." }, { "dimension": "temporal", "status": "covered", "notes": "Operating day, validity, requested, computation, planned, estimated, predicted, committed, selection and correction clocks remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Origin, destination, waypoints, nodes, links, segments, geometry, topology, direction, CRS and precision are explicit." }, { "dimension": "provenance", "status": "covered", "notes": "Network dataset, engine, algorithm, parameters, computation, assertions, derivations, revisions and invalidations are linked." }, { "dimension": "ownership", "status": "covered", "notes": "Dimension, route, itinerary, network, routing-provider, subject, reviewer and disclosure roles are separated." }, { "dimension": "validation", "status": "covered", "notes": "Identity, kind, order, topology, geometry, time, transfer, constraint, resource, freshness and crosswalk checks are explicit." }, { "dimension": "access", "status": "covered", "notes": "Role, purpose, consent, license, location sensitivity, minimum projection, emergency access and audit are represented." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Alternatives, decisions, corrections, disputes, legal hold, withdrawal and tombstones are explicit and non-cascading." }, { "dimension": "interoperability", "status": "covered", "notes": "Transmodel, NeTEx, GTFS, OGC, GeoJSON, ISO, EU, Schema.org, GeoSPARQL, OWL-Time, PROV, DQV and ODRL mappings disclose loss." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Registration, path definition, itinerary composition, constraints, candidates, selection, bindings, validation, replanning and projection declare controlled effects." } ], "known_omissions": [ "Mode, region, safety, accessibility, border, traffic-law, passenger-rights, privacy, licensing and retention profiles require exact current rules and competent review.", "Network, place, journey, service, schedule, person, vehicle, booking, ticket, fare, activity, shipment, incident, weather, routing-engine, dataset and evidence lifecycles remain in neighboring masters.", "Certified field crosswalks, routing algorithms, map matching, traffic prediction, feasibility solvers and legal proof requirements remain future work.", "The aggregate family may require a future breaking split into separate Route and Itinerary specifications after wider implementation evidence." ], "conflicts": [ "Route, trip, journey pattern and itinerary have different meanings across Transmodel, GTFS, OGC, EU law and ordinary language; a mandatory kind and source profile are required.", "A reusable path, computed route, candidate itinerary, selected plan, scheduled service and actual journey cannot share one lifecycle or truth status.", "OGC API Routes and Route Exchange Model are developing or proposed material as of 2026-09-06, not approved OGC standards; implementations must pin exact drafts." ], "regional_assumptions": [ "EU multimodal travel-information rules are a regional profile, not universal route or itinerary law.", "Transmodel, NeTEx and GTFS primarily describe public passenger transport; private, freight, pedestrian, indoor, maritime, aviation and off-network plans need explicit profiles.", "Network restrictions, permits, accessibility, safety and privacy requirements depend on jurisdiction, mode and operating context." ], "adversarial_checks": [ "Reject an object without stable identity, mandatory route-or-itinerary kind, revision, boundary, source and lineage.", "Reject a route represented as an itinerary or journey, or an itinerary represented as actual movement evidence.", "Reject unordered path components, broken topology, unqualified CRS, infeasible transfers or planned clocks without operating-day and timezone basis.", "Reject a candidate, estimate, routing job status or ticket interpreted as a selected, feasible or legally permitted plan.", "Reject last-write-wins when constraints, alternatives, selections or source datasets change; preserve difference, invalidation and successor history.", "Reject a claim that OGC API Routes or Route Exchange Model is an approved OGC standard without checking the current OGC roadmap.", "Reject protected 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-with-split-hold", "rationale": "Catalogue convenience justifies one aggregate family only when every instance declares route, itinerary or combined-plan. Journey execution, networks, places, schedules, resources, engines and evidence remain external masters, and a future major version may split Route and Itinerary." }, "decisions": [ { "concept": "Route / Itinerary aggregate boundary", "disposition": "accepted-with-mandatory-kind-and-split-hold", "rationale": "Route is a reusable or computed directed path; itinerary is an ordered planning result. The aggregate is valid only with an explicit discriminator and separable identities." }, { "concept": "Journey / Trip relation", "disposition": "held-as-compositional-reference", "rationale": "Journey owns intended or actual movement and observations; Route / Itinerary owns path and plan structure, alternatives and successor history." }, { "concept": "Reusable and computed route", "disposition": "accepted-as-distinct-route-profiles", "rationale": "A reusable route may outlive computations, while a computed route is qualified by request, source dataset, engine, algorithm and parameters." }, { "concept": "Itinerary composition", "disposition": "accepted-as-ordered-legs-stages-visits-and-transfers", "rationale": "An itinerary may combine multiple routes, modes, off-network legs, activities and handover points without becoming the journey itself." }, { "concept": "Network and geometry ownership", "disposition": "accepted-as-external-master-with-versioned-snapshot", "rationale": "The plan records ordered references and optional geometry snapshots, while authoritative topology, places, restrictions and geometry remain external." }, { "concept": "Constraints, objectives and alternatives", "disposition": "accepted-as-separate-assertion-classes", "rationale": "Requested, applied, violated or waived constraints and candidate ranking or selection rationale must not collapse into one outcome." }, { "concept": "Plan clocks and commitments", "disposition": "accepted-as-independent-time-kinds", "rationale": "Requested, planned, estimated, predicted and committed clocks require independent source, authority, operating-day and timezone semantics." }, { "concept": "Routing engine and computation job", "disposition": "accepted-as-external-masters", "rationale": "The model records request, versions, parameters and results but does not own optimization implementation or execution lifecycle." }, { "concept": "OGC API Routes and Route Exchange Model", "disposition": "accepted-as-developing-loss-aware-alignment", "rationale": "OGC material is useful for route exchange but remains developing or proposed as of 2026-09-06 and must not be presented as approved conformance." }, { "concept": "Transmodel, NeTEx and GTFS", "disposition": "accepted-as-profiled-crosswalks", "rationale": "Their route, line, journey-pattern, trip, stop-time and shape terms differ and require exact versioned mappings." }, { "concept": "Actual trajectory", "disposition": "accepted-as-external-execution-evidence", "rationale": "Actual temporal geometry belongs to Journey or Moving Feature evidence and may be compared with a route or itinerary without rewriting the plan." }, { "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-010 each timed out after 120 seconds; no external result was admitted.", "Aggregate hold: every instance must declare route, itinerary or combined-plan, and a future major version may split the aggregate into linked models.", "Boundary hold: journey execution, networks, places, schedules, services, people, vehicles, bookings, activities, shipments, incidents, routing engines, source datasets and evidence remain external.", "Terminology hold: route, line, journey pattern, trip, itinerary, segment, leg, waypoint, stop, call and visit have profile-specific meanings.", "Standards-status hold: OGC API Routes and Route Exchange Model are developing or proposed material as of 2026-09-06, not approved OGC standards.", "Mode hold: pedestrian, bicycle, road, rail, maritime, aviation, indoor, private, public, shared, freight and autonomous-route profiles need independent validation.", "Jurisdiction hold: safety, accessibility, traffic, border, passenger-rights, privacy, licensing and retention rules depend on region and operating context.", "Computation hold: routing and optimization algorithms, traffic prediction, feasibility solvers and benchmarks remain external implementation concerns.", "Feasibility hold: a computed or selected plan does not prove resource availability, reservation, legal permission, safety or successful execution.", "Privacy hold: personal itineraries and precise locations need purpose limitation, minimization, consent or other authority, protected access and deletion profiles.", "Interoperability hold: every Transmodel, NeTEx, GTFS, OGC, ISO, EU, Schema.org, GeoSPARQL, GeoJSON, OWL-Time, PROV, DQV and ODRL projection needs exact release pins, conformance evidence and semantic-loss declarations.", "Review hold: transport planning, geospatial, accessibility, safety, privacy, optimization, 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": [ "Decide whether Route and Itinerary should split into separate registry models after paired implementation and query-pattern review.", "Create independently validated pedestrian, bicycle, road, rail, maritime, aviation, indoor, multimodal, freight, evacuation and autonomous-route profiles.", "Benchmark path continuity, transfer feasibility, map matching, traffic prediction, routing algorithms, multi-objective ranking, replanning and actual-plan divergence.", "Pin exact external releases and licensing conditions and obtain independent transport, geospatial, accessibility, safety, privacy, optimization, 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 } }