{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-flw-010","code":"wm-flw-010-route-itinerary","url":"https://ver.cy/models/wm-flw-010-route-itinerary/","name":"Route / Itinerary","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Physical world and living systems","entryKind":"aggregate","plane":"","domain":["PHY.FLW.MOB"],"industry":["Cross-industry"],"navPath":"NAV.PHY.FLW.MOB","tags":["route","itinerary","phy.flw.mob"],"facets":{}},"whatItIs":"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.","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":{"in":["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":["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"],"boundaries":[{"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."},{"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."},{"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."},{"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."},{"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."},{"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."}]},"distinguishingFeatures":["A route is a directed path through a network; an itinerary is a plan of legs, visits and transfers.","Neither proves movement; actual movement belongs to the journey model.","Candidates, ranking and selection rationale are kept, not just the chosen option.","Routing engines compute routes; this model records them."],"structure":{"bundles":[{"id":"identity-kind-and-boundary","name":"Identity, kind and boundary","description":"Groups the governed Route / Itinerary concern for identity, kind and boundary.","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.","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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish route or itinerary identity, namespace, version and mandatory kind?","id":"route-or-itinerary-identity-namespace-version-and-kind-q01","kind":"identity"},{"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?","id":"route-or-itinerary-identity-namespace-version-and-kind-q02","kind":"ownership"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify route or itinerary identity, namespace, version and mandatory kind?","id":"route-or-itinerary-identity-namespace-version-and-kind-q03","kind":"validation"}]},{"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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish revision, predecessor, successor, effective period and status?","id":"revision-predecessor-successor-effective-period-and-status-q01","kind":"lifecycle"},{"text":"Who requested, computed, selected, owns, reviewed, corrected or may access revision, predecessor, successor, effective period and status, and under which authority or policy?","id":"revision-predecessor-successor-effective-period-and-status-q02","kind":"authority"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify revision, predecessor, successor, effective period and status?","id":"revision-predecessor-successor-effective-period-and-status-q03","kind":"security"}]}]},{"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.","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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish reusable route, computed route, itinerary and combined-plan boundary?","id":"reusable-route-computed-route-itinerary-and-combined-plan-q01","kind":"classification"},{"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?","id":"reusable-route-computed-route-itinerary-and-combined-plan-q02","kind":"constraint"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify reusable route, computed route, itinerary and combined-plan boundary?","id":"reusable-route-computed-route-itinerary-and-combined-plan-q03","kind":"privacy"}]},{"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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish planner, operator, traveller, vehicle, cargo and authority roles?","id":"planner-operator-traveller-vehicle-cargo-and-authority-roles-q01","kind":"ownership"},{"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?","id":"planner-operator-traveller-vehicle-cargo-and-authority-roles-q02","kind":"process"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify planner, operator, traveller, vehicle, cargo and authority roles?","id":"planner-operator-traveller-vehicle-cargo-and-authority-roles-q03","kind":"retention"}]}]}]},{"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.","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.","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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish origin, destination, via waypoint, node, link and zone reference?","id":"origin-destination-via-waypoint-node-link-and-zone-reference-q01","kind":"spatial"},{"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?","id":"origin-destination-via-waypoint-node-link-and-zone-reference-q02","kind":"event"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify origin, destination, via waypoint, node, link and zone reference?","id":"origin-destination-via-waypoint-node-link-and-zone-reference-q03","kind":"access"}]},{"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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish directed segment sequence, topology, geometry and crs?","id":"directed-segment-sequence-topology-geometry-and-crs-q01","kind":"composition"},{"text":"Who requested, computed, selected, owns, reviewed, corrected or may access directed segment sequence, topology, geometry and crs, and under which authority or policy?","id":"directed-segment-sequence-topology-geometry-and-crs-q02","kind":"measurement"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify directed segment sequence, topology, geometry and crs?","id":"directed-segment-sequence-topology-geometry-and-crs-q03","kind":"exception"}]}]},{"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.","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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish itinerary leg, stage, call, visit, activity and order?","id":"itinerary-leg-stage-call-visit-activity-and-order-q01","kind":"composition"},{"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?","id":"itinerary-leg-stage-call-visit-activity-and-order-q02","kind":"evidence"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify itinerary leg, stage, call, visit, activity and order?","id":"itinerary-leg-stage-call-visit-activity-and-order-q03","kind":"interoperability"}]},{"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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish access, egress, transfer, handover, connection and wait?","id":"access-egress-transfer-handover-connection-and-wait-q01","kind":"relationship"},{"text":"Who requested, computed, selected, owns, reviewed, corrected or may access access, egress, transfer, handover, connection and wait, and under which authority or policy?","id":"access-egress-transfer-handover-connection-and-wait-q02","kind":"quality"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify access, egress, transfer, handover, connection and wait?","id":"access-egress-transfer-handover-connection-and-wait-q03","kind":"decision"}]}]}]},{"id":"constraints-criteria-and-selection","name":"Constraints, criteria and selection","description":"Groups the governed Route / Itinerary concern for constraints, criteria and selection.","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.","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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish mode, accessibility, vehicle, cargo, height, load and safety constraint?","id":"mode-accessibility-vehicle-cargo-height-load-and-safety-constraint-q01","kind":"constraint"},{"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?","id":"mode-accessibility-vehicle-cargo-height-load-and-safety-constraint-q02","kind":"validation"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify mode, accessibility, vehicle, cargo, height, load and safety constraint?","id":"mode-accessibility-vehicle-cargo-height-load-and-safety-constraint-q03","kind":"identity"}]},{"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.","questions":[{"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?","id":"avoid-prefer-must-pass-time-window-permission-and-policy-constraint-q01","kind":"constraint"},{"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?","id":"avoid-prefer-must-pass-time-window-permission-and-policy-constraint-q02","kind":"security"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify avoid, prefer, must-pass, time-window, permission and policy constraint?","id":"avoid-prefer-must-pass-time-window-permission-and-policy-constraint-q03","kind":"classification"}]}]},{"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.","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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish distance, time, cost, emissions, energy, risk and comfort objective?","id":"distance-time-cost-emissions-energy-risk-and-comfort-objective-q01","kind":"decision"},{"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?","id":"distance-time-cost-emissions-energy-risk-and-comfort-objective-q02","kind":"privacy"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify distance, time, cost, emissions, energy, risk and comfort objective?","id":"distance-time-cost-emissions-energy-risk-and-comfort-objective-q03","kind":"composition"}]},{"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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish candidate alternative, ranking, selection, rejection and rationale?","id":"candidate-alternative-ranking-selection-rejection-and-rationale-q01","kind":"decision"},{"text":"Who requested, computed, selected, owns, reviewed, corrected or may access candidate alternative, ranking, selection, rejection and rationale, and under which authority or policy?","id":"candidate-alternative-ranking-selection-rejection-and-rationale-q02","kind":"retention"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify candidate alternative, ranking, selection, rejection and rationale?","id":"candidate-alternative-ranking-selection-rejection-and-rationale-q03","kind":"relationship"}]}]}]},{"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.","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.","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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish operating day, validity, departure, arrival, duration and time zone?","id":"operating-day-validity-departure-arrival-duration-and-time-zone-q01","kind":"temporal"},{"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?","id":"operating-day-validity-departure-arrival-duration-and-time-zone-q02","kind":"access"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify operating day, validity, departure, arrival, duration and time zone?","id":"operating-day-validity-departure-arrival-duration-and-time-zone-q03","kind":"state"}]},{"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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish requested, planned, estimated, predicted, committed and slack time?","id":"requested-planned-estimated-predicted-committed-and-slack-time-q01","kind":"classification"},{"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?","id":"requested-planned-estimated-predicted-committed-and-slack-time-q02","kind":"exception"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify requested, planned, estimated, predicted, committed and slack time?","id":"requested-planned-estimated-predicted-committed-and-slack-time-q03","kind":"lifecycle"}]}]},{"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.","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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish mode, line, route pattern, service trip and schedule reference?","id":"mode-line-route-pattern-service-trip-and-schedule-reference-q01","kind":"relationship"},{"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?","id":"mode-line-route-pattern-service-trip-and-schedule-reference-q02","kind":"interoperability"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify mode, line, route pattern, service trip and schedule reference?","id":"mode-line-route-pattern-service-trip-and-schedule-reference-q03","kind":"temporal"}]},{"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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish vehicle, seat, booking, ticket, fare, activity and facility reference?","id":"vehicle-seat-booking-ticket-fare-activity-and-facility-reference-q01","kind":"relationship"},{"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?","id":"vehicle-seat-booking-ticket-fare-activity-and-facility-reference-q02","kind":"decision"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify vehicle, seat, booking, ticket, fare, activity and facility reference?","id":"vehicle-seat-booking-ticket-fare-activity-and-facility-reference-q03","kind":"spatial"}]}]}]},{"id":"lifecycle-change-and-evaluation","name":"Lifecycle, change and evaluation","description":"Groups the governed Route / Itinerary concern for lifecycle, change and evaluation.","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.","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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish draft, requested, computing, candidate, selected, confirmed and cancelled state?","id":"draft-requested-computing-candidate-selected-confirmed-and-cancelled-state-q01","kind":"lifecycle"},{"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?","id":"draft-requested-computing-candidate-selected-confirmed-and-cancelled-state-q02","kind":"identity"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify draft, requested, computing, candidate, selected, confirmed and cancelled state?","id":"draft-requested-computing-candidate-selected-confirmed-and-cancelled-state-q03","kind":"provenance"}]},{"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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish disruption, invalidity, reroute, difference, successor and actual divergence?","id":"disruption-invalidity-reroute-difference-successor-and-actual-divergence-q01","kind":"exception"},{"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?","id":"disruption-invalidity-reroute-difference-successor-and-actual-divergence-q02","kind":"classification"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify disruption, invalidity, reroute, difference, successor and actual divergence?","id":"disruption-invalidity-reroute-difference-successor-and-actual-divergence-q03","kind":"ownership"}]}]},{"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.","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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish distance, duration, cost, toll, energy, emissions and risk estimate?","id":"distance-duration-cost-toll-energy-emissions-and-risk-estimate-q01","kind":"measurement"},{"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?","id":"distance-duration-cost-toll-energy-emissions-and-risk-estimate-q02","kind":"composition"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify distance, duration, cost, toll, energy, emissions and risk estimate?","id":"distance-duration-cost-toll-energy-emissions-and-risk-estimate-q03","kind":"authority"}]},{"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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish coverage, freshness, precision, confidence, uncertainty and validation?","id":"coverage-freshness-precision-confidence-uncertainty-and-validation-q01","kind":"quality"},{"text":"Who requested, computed, selected, owns, reviewed, corrected or may access coverage, freshness, precision, confidence, uncertainty and validation, and under which authority or policy?","id":"coverage-freshness-precision-confidence-uncertainty-and-validation-q02","kind":"relationship"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify coverage, freshness, precision, confidence, uncertainty and validation?","id":"coverage-freshness-precision-confidence-uncertainty-and-validation-q03","kind":"constraint"}]}]}]},{"id":"provenance-access-and-interoperability","name":"Provenance, access and interoperability","description":"Groups the governed Route / Itinerary concern for provenance, access and interoperability.","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.","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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish network dataset version, engine, algorithm, parameter and job reference?","id":"network-dataset-version-engine-algorithm-parameter-and-job-reference-q01","kind":"provenance"},{"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?","id":"network-dataset-version-engine-algorithm-parameter-and-job-reference-q02","kind":"state"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify network dataset version, engine, algorithm, parameter and job reference?","id":"network-dataset-version-engine-algorithm-parameter-and-job-reference-q03","kind":"process"}]},{"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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish assertion, derivation, correction, invalidation, review and evidence?","id":"assertion-derivation-correction-invalidation-review-and-evidence-q01","kind":"evidence"},{"text":"Who requested, computed, selected, owns, reviewed, corrected or may access assertion, derivation, correction, invalidation, review and evidence, and under which authority or policy?","id":"assertion-derivation-correction-invalidation-review-and-evidence-q02","kind":"lifecycle"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify assertion, derivation, correction, invalidation, review and evidence?","id":"assertion-derivation-correction-invalidation-review-and-evidence-q03","kind":"event"}]}]},{"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.","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.","questions":[{"text":"Which route or itinerary identity, kind, revision, ordered component, time basis and source establish location sensitivity, purpose, consent, access, retention and license?","id":"location-sensitivity-purpose-consent-access-retention-and-license-q01","kind":"privacy"},{"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?","id":"location-sensitivity-purpose-consent-access-retention-and-license-q02","kind":"temporal"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify location sensitivity, purpose, consent, access, retention and license?","id":"location-sensitivity-purpose-consent-access-retention-and-license-q03","kind":"measurement"}]},{"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.","questions":[{"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?","id":"transmodel-netex-gtfs-ogc-geojson-schema-org-time-and-provenance-crosswalk-q01","kind":"interoperability"},{"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?","id":"transmodel-netex-gtfs-ogc-geojson-schema-org-time-and-provenance-crosswalk-q02","kind":"spatial"},{"text":"Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify transmodel, netex, gtfs, ogc, geojson, schema.org, time and provenance crosswalk?","id":"transmodel-netex-gtfs-ogc-geojson-schema-org-time-and-provenance-crosswalk-q03","kind":"evidence"}]}]}]}]},"agentConduct":{"may":["Register candidate routes and itineraries with constraints.","Validate continuity and connection times.","Present alternatives with rationale.","Supersede a plan on disruption."],"mustNot":["Present a route as legally permitted or safe without evidence.","Book or ticket on behalf of a traveller without consent.","Reroute consequentially without authority.","Disclose protected locations."],"requiresHuman":["Selecting routes for hazardous loads or vulnerable travellers.","Rerouting during safety incidents."]},"ethics":{"considerations":["Routes for vulnerable travellers must respect accessibility needs.","Itineraries reveal plans and locations.","Routing choices can push traffic into residential areas."],"affectedParties":["Travellers","Residents along routes","Operators","Emergency services"]},"owners":{"steward":"Declare the Dimension owner, route and itinerary stewards, routing authorities and accountable decision roles.","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."]}],"masterSystems":[]},"relations":[{"target":"WM-FLW-009 Journey / Trip","type":"references","note":"Bind a selected plan to intended or actual movement while preserving execution observations and outcomes in Journey."},{"target":"Network, Place, Stop, Service, Schedule, Person, Vehicle, Booking, Ticket, Activity, Shipment, Incident, Engine, Dataset and Evidence models","type":"references","note":"Resolve external masters without duplicating their identity, authority or lifecycle."},{"target":"Transmodel v6.2 and NeTEx","type":"aligned","note":"Project European public-transport route and journey-pattern views with explicit type and version mappings."},{"target":"GTFS Schedule","type":"aligned","note":"Project routes, trips, stop-time sequences, shapes, calendars and transfers without adopting GTFS terminology as universal."},{"target":"OGC API Routes, Route Exchange Model, GeoSPARQL and GeoJSON","type":"aligned","note":"Project engine-independent route requests and geometry while pinning developing OGC drafts and declared conformance."},{"target":"ISO 19133, ISO 19141 and OGC Moving Features","type":"aligned","note":"Align navigation and planned-route concepts while keeping actual moving-feature trajectory external."},{"target":"EU multimodal travel information and Schema.org Trip","type":"aligned","note":"Project regional machine-readable itinerary and lightweight web-discovery views with explicit limitations."},{"target":"OWL-Time, RFC 3339, PROV-O, DQV and ODRL","type":"aligned","note":"Project temporal, provenance, quality and access semantics with exact pins and semantic-loss declarations."},{"target":"WM-FLW-009 Journey / Trip","type":"neighbor","note":"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."},{"target":"Network, Place and Stop","type":"neighbor","note":"Route / Itinerary orders typed references and may carry snapshot geometry. Network topology, place identity, facilities, restrictions and authoritative geometry remain externally mastered."},{"target":"Line, Journey Pattern, Service and Schedule","type":"neighbor","note":"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."},{"target":"Routing Engine, Algorithm and Computation Job","type":"neighbor","note":"The model records requests, parameters, versions and results. Execution, resource use, optimization implementation and job control remain owned by external computation masters."},{"target":"Booking, Ticket, Fare, Activity and Resource","type":"neighbor","note":"An itinerary may reference entitlements, offers, reservations, activities, vehicles and facilities, but does not own or imply their availability, validity or lifecycle."},{"target":"Trajectory and Moving Feature","type":"neighbor","note":"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."},{"target":"WM-FLW-009","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["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."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"required","items":["A route has ordered waypoints or segments with geometry; an itinerary has ordered legs with times and services.","Often confused with a journey (actual movement), a line (service pattern) and a schedule."]},"capabilities":{"applicability":"required","items":["Register route or itinerary: Create one governed route or itinerary identity with a mandatory kind and boundary.","Define directed route: Append ordered waypoints, nodes, links, segments, topology and geometry references.","Compose itinerary: Append ordered legs, stages, visits, calls, transfers and activity references.","Bind request constraints: Record hard, soft, accessibility, operational, safety and permission constraints.","Record candidate alternatives: Register external routing request, parameters and candidate results without owning the routing engine.","Select route or itinerary: Record selection, ranking, rejection rationale and any confirmation state.","Bind services and resources: Bind modes, schedules, services, vehicles, facilities, bookings and activities as external references.","Validate continuity and feasibility: Validate order, topology, geometry, clocks, transfers, constraints, resource bindings and source freshness.","Supersede or replan: Create a successor after disruption, invalidity, changed constraint or better alternative.","Project route or itinerary: Produce minimum-necessary standards-aligned or stakeholder views."]},"hazards":{"applicability":"required","items":["Infeasible connections stranding travellers.","Routes violating restrictions such as weight or height.","Exposure of planned locations.","Stale plans after disruption."]},"interfaces":{"applicability":"required","items":["OGC API Routes.","GTFS static schedule format.","CEN Transmodel and NeTEx.","GeoJSON (IETF RFC 7946)."]},"context":{"applicability":"required","items":["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."]}},"sources":[{"title":"Transmodel v6.2 Data Dictionary","url":"https://transmodel-cen.eu/wp-content/uploads/2024/09/Transmodel-v6.2-Data-Dictionary.pdf","note":"CEN Transmodel"},{"title":"Transmodel at a glance","url":"https://www.transmodel-cen.eu/wp-content/uploads/2015/01/Transmodel_at_a_-glance-1.pdf","note":"CEN Transmodel"},{"title":"NeTEx","url":"https://netex-cen.eu/","note":"CEN NeTEx"},{"title":"GTFS Schedule Reference","url":"https://gtfs.org/documentation/schedule/reference/","note":"MobilityData"},{"title":"OGC API - Routes overview","url":"https://ogcapi.ogc.org/routes/overview.html","note":"Open Geospatial Consortium"},{"title":"OGC Routing Pilot Engineering Report","url":"https://docs.ogc.org/per/19-041r3.html","note":"Open Geospatial Consortium"},{"title":"WPS Routing API Engineering Report","url":"https://docs.ogc.org/per/19-040.html","note":"Open Geospatial Consortium"},{"title":"OGC Standards Roadmap","url":"https://portal.ogc.org/public_ogc/standards/standards_workflow.php?bg=1","note":"Open Geospatial Consortium"},{"title":"GeoSPARQL","url":"https://www.ogc.org/standards/geosparql/","note":"Open Geospatial Consortium"},{"title":"RFC 7946: The GeoJSON Format","url":"https://www.rfc-editor.org/rfc/rfc7946.html","note":"Internet Engineering Task Force"},{"title":"ISO 19133 Geographic information - Location-based services - Tracking and navigation","url":"https://www.iso.org/standard/32500.html","note":"International Organization for Standardization"},{"title":"ISO 19141 Geographic information - Schema for moving features","url":"https://www.iso.org/standard/41445.html","note":"International Organization for Standardization"},{"title":"Commission Delegated Regulation (EU) 2024/490","url":"https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32024R0490","note":"European Union"},{"title":"Multimodal travel information services","url":"https://transport.ec.europa.eu/transport-themes/intelligent-transport-systems/road/action-plan-and-directive/multimodal-travel-information-services_en","note":"European Commission"},{"title":"Trip","url":"https://schema.org/Trip","note":"Schema.org Community Group"},{"title":"Time Ontology in OWL","url":"https://www.w3.org/TR/owl-time/","note":"World Wide Web Consortium"},{"title":"RFC 3339: Date and Time on the Internet","url":"https://www.rfc-editor.org/rfc/rfc3339.html","note":"Internet Engineering Task Force"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Data Quality Vocabulary","url":"https://www.w3.org/TR/vocab-dqv/","note":"World Wide Web Consortium"},{"title":"ODRL Information Model 2.2","url":"https://www.w3.org/TR/odrl-model/","note":"World Wide Web Consortium"},{"title":"OGC Moving Features standards","url":"https://www.ogc.org/standards/movingfeatures/","note":"Open Geospatial Consortium"}],"openQuestions":["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.","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."],"resources":{"spec":"/models/wm-flw-010-route-itinerary/spec.yaml","agents":"/models/wm-flw-010-route-itinerary/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-flw-010"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-flw-010-route-itinerary/spec.yaml","ver-cy/world-models/card-supplements/wm-flw-010-route-itinerary.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T20:21:13Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"A route is planned geometry and sequence; its length is derived data, not a property of a physical body.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}