{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-flw-009","code":"wm-flw-009-journey-trip","url":"https://ver.cy/models/wm-flw-009-journey-trip/","name":"Journey / Trip","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":["journey","trip","phy.flw.mob"],"facets":{}},"whatItIs":"Owns journey and revision identity, kind and boundary; subject and journey-role bindings; origin, destination, calls and journey-scoped endpoint assertions; ordered leg or stage composition; purpose and wider-travel relationships; requested, planned, target, estimated, predicted, observed and actual clocks; selected-plan references and journey constraints; lifecycle and progress assertions; position and trajectory evidence links; disruption, outcome, measurement, provenance, reconciliation, access, retention and loss-aware projections. Person, vehicle, organization, route, itinerary, network, place, stop, service, schedule, booking, ticket, fare, shipment, incident, weather, payment, sensor, evidence and document masters remain external.","purpose":"Represent one governed planned or actual movement of a person or vehicle between declared endpoints with ordered legs, typed clocks, observations and correction lineage without becoming its route, itinerary, service, subject or booking.","scope":{"in":["Journey identity, revision, kind, subject roles, origin, destination, purpose, wider travel and subtrip relationships","Ordered legs, stages, modes, calls, route and service references, selected plan, typed times, execution state, progress and trajectory evidence","Deviations, outcomes, derived measures, reconciliation, provenance, privacy, access, retention and interoperability"],"out":["Owning person, organization, vehicle, route, itinerary, network, place, stop, service, schedule, booking, ticket, fare, shipment, incident, weather, payment, sensor, evidence or document master lifecycles","Equating a person trip with a vehicle journey, a route with an itinerary, a plan with actual movement, a position fix with a trajectory, boarding with a whole trip or a statistical count with operational truth","Autonomous consequential rerouting, safety intervention, passenger-rights determination, border or regulatory decision, protected live-location disclosure or irreversible deletion"],"boundaries":[{"neighbor":"WM-FLW-007 Passenger Mobility / Transit","distinction":"Passenger Mobility owns transit networks, services, schedules, fares and aggregate mobility context. Journey / Trip owns one movement episode and may reference transit service or passenger-trip views without assuming inheritance."},{"neighbor":"WM-FLW-010 Route / Itinerary","distinction":"A route is a reusable or selected spatial path and an itinerary is a planning result or ordered visit plan. A journey is the identity-bearing intended or undertaken movement that references them and preserves actual divergence."},{"neighbor":"Person, Vehicle, Organization and Transport Service","distinction":"The journey assigns journey-scoped roles and references. Subject identity, vehicle lifecycle, operator authority, network, schedule and service operation remain externally mastered."},{"neighbor":"WM-FLW-011 Shipment / Consignment","distinction":"A shipment may reference one or more transport journeys. Cargo, consignment, custody and logistics lifecycle remain shipment-owned and do not become journey composition."},{"neighbor":"Observation, Sensor, Incident and Evidence","distinction":"The journey binds source-qualified position, passing, disruption and completion assertions. Sensor streams, generic incidents and evidentiary records retain independent identity and authority."},{"neighbor":"Travel, Tour and Tourism Trip","distinction":"A wider travel episode or return journey may contain multiple one-way trips and activities. Tourism status depends on purpose, destination, usual environment and duration under a statistical profile."}]},"distinguishingFeatures":["Represents one bounded movement of a traveller or vehicle from origin to destination, not the planned route or itinerary.","A person trip and a vehicle journey are distinct kinds even when they share legs.","Planned, estimated, predicted and observed times are separately recorded.","Booking and ticket are external evidence, not proof of travel."],"structure":{"bundles":[{"id":"journey-identity-class-and-subject","name":"Journey identity, class and subject","description":"Groups the governed Journey / Trip concern for journey identity, class and subject.","layers":[{"id":"identity-scope-and-version","name":"Identity, scope and version","description":"Groups Journey / Trip context for identity, scope and version without importing neighboring master lifecycles.","findings":[{"id":"journey-identity-namespace-version-and-successor","name":"Journey identity, namespace, version and successor","description":"Records journey identity, namespace, version and successor as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish journey identity, namespace, version and successor?","id":"journey-identity-namespace-version-and-successor-q01","kind":"identity"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access journey identity, namespace, version and successor, and under what role or authority?","id":"journey-identity-namespace-version-and-successor-q02","kind":"provenance"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify journey identity, namespace, version and successor?","id":"journey-identity-namespace-version-and-successor-q03","kind":"quality"}]},{"id":"journey-boundary-origin-destination-and-completion-rule","name":"Journey boundary, origin, destination and completion rule","description":"Records journey boundary, origin, destination and completion rule as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish journey boundary, origin, destination and completion rule?","id":"journey-boundary-origin-destination-and-completion-rule-q01","kind":"definition"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access journey boundary, origin, destination and completion rule, and under what role or authority?","id":"journey-boundary-origin-destination-and-completion-rule-q02","kind":"ownership"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify journey boundary, origin, destination and completion rule?","id":"journey-boundary-origin-destination-and-completion-rule-q03","kind":"validation"}]}]},{"id":"kind-subject-purpose-and-grouping","name":"Kind, subject, purpose and grouping","description":"Groups Journey / Trip context for kind, subject, purpose and grouping without importing neighboring master lifecycles.","findings":[{"id":"person-trip-vehicle-journey-service-journey-and-dead-run-kind","name":"Person trip, vehicle journey, service journey and dead run kind","description":"Records person trip, vehicle journey, service journey and dead run kind as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish person trip, vehicle journey, service journey and dead run kind?","id":"person-trip-vehicle-journey-service-journey-and-dead-run-kind-q01","kind":"classification"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access person trip, vehicle journey, service journey and dead run kind, and under what role or authority?","id":"person-trip-vehicle-journey-service-journey-and-dead-run-kind-q02","kind":"authority"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify person trip, vehicle journey, service journey and dead run kind?","id":"person-trip-vehicle-journey-service-journey-and-dead-run-kind-q03","kind":"security"}]},{"id":"traveller-vehicle-trip-purpose-wider-travel-and-subtrip","name":"Traveller, vehicle, trip purpose, wider travel and subtrip","description":"Records traveller, vehicle, trip purpose, wider travel and subtrip as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish traveller, vehicle, trip purpose, wider travel and subtrip?","id":"traveller-vehicle-trip-purpose-wider-travel-and-subtrip-q01","kind":"relationship"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access traveller, vehicle, trip purpose, wider travel and subtrip, and under what role or authority?","id":"traveller-vehicle-trip-purpose-wider-travel-and-subtrip-q02","kind":"constraint"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify traveller, vehicle, trip purpose, wider travel and subtrip?","id":"traveller-vehicle-trip-purpose-wider-travel-and-subtrip-q03","kind":"privacy"}]}]}]},{"id":"places-paths-legs-and-modes","name":"Places, paths, legs and modes","description":"Groups the governed Journey / Trip concern for places, paths, legs and modes.","layers":[{"id":"endpoints-calls-and-path","name":"Endpoints, calls and path","description":"Groups Journey / Trip context for endpoints, calls and path without importing neighboring master lifecycles.","findings":[{"id":"origin-destination-via-place-stop-call-and-activity-place","name":"Origin, destination, via place, stop, call and activity place","description":"Records origin, destination, via place, stop, call and activity place as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish origin, destination, via place, stop, call and activity place?","id":"origin-destination-via-place-stop-call-and-activity-place-q01","kind":"spatial"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access origin, destination, via place, stop, call and activity place, and under what role or authority?","id":"origin-destination-via-place-stop-call-and-activity-place-q02","kind":"process"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify origin, destination, via place, stop, call and activity place?","id":"origin-destination-via-place-stop-call-and-activity-place-q03","kind":"retention"}]},{"id":"route-journey-pattern-shape-trajectory-and-deviation-reference","name":"Route, journey pattern, shape, trajectory and deviation reference","description":"Records route, journey pattern, shape, trajectory and deviation reference as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish route, journey pattern, shape, trajectory and deviation reference?","id":"route-journey-pattern-shape-trajectory-and-deviation-reference-q01","kind":"relationship"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access route, journey pattern, shape, trajectory and deviation reference, and under what role or authority?","id":"route-journey-pattern-shape-trajectory-and-deviation-reference-q02","kind":"event"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify route, journey pattern, shape, trajectory and deviation reference?","id":"route-journey-pattern-shape-trajectory-and-deviation-reference-q03","kind":"access"}]}]},{"id":"ordered-legs-modes-and-transfers","name":"Ordered legs, modes and transfers","description":"Groups Journey / Trip context for ordered legs, modes and transfers without importing neighboring master lifecycles.","findings":[{"id":"leg-stage-sequence-mode-vehicle-service-and-predecessor","name":"Leg, stage, sequence, mode, vehicle, service and predecessor","description":"Records leg, stage, sequence, mode, vehicle, service and predecessor as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish leg, stage, sequence, mode, vehicle, service and predecessor?","id":"leg-stage-sequence-mode-vehicle-service-and-predecessor-q01","kind":"composition"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access leg, stage, sequence, mode, vehicle, service and predecessor, and under what role or authority?","id":"leg-stage-sequence-mode-vehicle-service-and-predecessor-q02","kind":"measurement"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify leg, stage, sequence, mode, vehicle, service and predecessor?","id":"leg-stage-sequence-mode-vehicle-service-and-predecessor-q03","kind":"exception"}]},{"id":"access-egress-transfer-connection-wait-and-interchange","name":"Access, egress, transfer, connection, wait and interchange","description":"Records access, egress, transfer, connection, wait and interchange as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish access, egress, transfer, connection, wait and interchange?","id":"access-egress-transfer-connection-wait-and-interchange-q01","kind":"process"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access access, egress, transfer, connection, wait and interchange, and under what role or authority?","id":"access-egress-transfer-connection-wait-and-interchange-q02","kind":"evidence"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify access, egress, transfer, connection, wait and interchange?","id":"access-egress-transfer-connection-wait-and-interchange-q03","kind":"interoperability"}]}]}]},{"id":"plan-time-and-traveller-constraints","name":"Plan, time and traveller constraints","description":"Groups the governed Journey / Trip concern for plan, time and traveller constraints.","layers":[{"id":"time-basis-passing-and-duration","name":"Time basis, passing and duration","description":"Groups Journey / Trip context for time basis, passing and duration without importing neighboring master lifecycles.","findings":[{"id":"operating-day-time-zone-start-end-passing-and-duration","name":"Operating day, time zone, start, end, passing and duration","description":"Records operating day, time zone, start, end, passing and duration as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish operating day, time zone, start, end, passing and duration?","id":"operating-day-time-zone-start-end-passing-and-duration-q01","kind":"temporal"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access operating day, time zone, start, end, passing and duration, and under what role or authority?","id":"operating-day-time-zone-start-end-passing-and-duration-q02","kind":"quality"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify operating day, time zone, start, end, passing and duration?","id":"operating-day-time-zone-start-end-passing-and-duration-q03","kind":"decision"}]},{"id":"requested-planned-target-estimated-predicted-observed-and-actual-time","name":"Requested, planned, target, estimated, predicted, observed and actual time","description":"Records requested, planned, target, estimated, predicted, observed and actual time as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish requested, planned, target, estimated, predicted, observed and actual time?","id":"requested-planned-target-estimated-predicted-observed-and-actual-time-q01","kind":"classification"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access requested, planned, target, estimated, predicted, observed and actual time, and under what role or authority?","id":"requested-planned-target-estimated-predicted-observed-and-actual-time-q02","kind":"validation"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify requested, planned, target, estimated, predicted, observed and actual time?","id":"requested-planned-target-estimated-predicted-observed-and-actual-time-q03","kind":"identity"}]}]},{"id":"plan-choice-and-constraints","name":"Plan choice and constraints","description":"Groups Journey / Trip context for plan choice and constraints without importing neighboring master lifecycles.","findings":[{"id":"journey-request-routing-result-selected-plan-itinerary-and-alternative","name":"Journey request, routing result, selected plan, itinerary and alternative","description":"Records journey request, routing result, selected plan, itinerary and alternative as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish journey request, routing result, selected plan, itinerary and alternative?","id":"journey-request-routing-result-selected-plan-itinerary-and-alternative-q01","kind":"decision"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access journey request, routing result, selected plan, itinerary and alternative, and under what role or authority?","id":"journey-request-routing-result-selected-plan-itinerary-and-alternative-q02","kind":"security"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify journey request, routing result, selected plan, itinerary and alternative?","id":"journey-request-routing-result-selected-plan-itinerary-and-alternative-q03","kind":"classification"}]},{"id":"accessibility-preference-party-luggage-mode-and-transfer-constraint","name":"Accessibility, preference, party, luggage, mode and transfer constraint","description":"Records accessibility, preference, party, luggage, mode and transfer constraint as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish accessibility, preference, party, luggage, mode and transfer constraint?","id":"accessibility-preference-party-luggage-mode-and-transfer-constraint-q01","kind":"constraint"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access accessibility, preference, party, luggage, mode and transfer constraint, and under what role or authority?","id":"accessibility-preference-party-luggage-mode-and-transfer-constraint-q02","kind":"privacy"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify accessibility, preference, party, luggage, mode and transfer constraint?","id":"accessibility-preference-party-luggage-mode-and-transfer-constraint-q03","kind":"composition"}]}]}]},{"id":"execution-progress-and-observation","name":"Execution, progress and observation","description":"Groups the governed Journey / Trip concern for execution, progress and observation.","layers":[{"id":"lifecycle-state-and-progress","name":"Lifecycle state and progress","description":"Groups Journey / Trip context for lifecycle state and progress without importing neighboring master lifecycles.","findings":[{"id":"proposed-confirmed-ready-started-in-progress-arrived-and-completed-state","name":"Proposed, confirmed, ready, started, in-progress, arrived and completed state","description":"Records proposed, confirmed, ready, started, in-progress, arrived and completed state as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish proposed, confirmed, ready, started, in-progress, arrived and completed state?","id":"proposed-confirmed-ready-started-in-progress-arrived-and-completed-state-q01","kind":"lifecycle"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access proposed, confirmed, ready, started, in-progress, arrived and completed state, and under what role or authority?","id":"proposed-confirmed-ready-started-in-progress-arrived-and-completed-state-q02","kind":"retention"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify proposed, confirmed, ready, started, in-progress, arrived and completed state?","id":"proposed-confirmed-ready-started-in-progress-arrived-and-completed-state-q03","kind":"relationship"}]},{"id":"current-leg-call-stop-sequence-progress-and-completion-evidence","name":"Current leg, call, stop sequence, progress and completion evidence","description":"Records current leg, call, stop sequence, progress and completion evidence as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish current leg, call, stop sequence, progress and completion evidence?","id":"current-leg-call-stop-sequence-progress-and-completion-evidence-q01","kind":"state"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access current leg, call, stop sequence, progress and completion evidence, and under what role or authority?","id":"current-leg-call-stop-sequence-progress-and-completion-evidence-q02","kind":"access"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify current leg, call, stop sequence, progress and completion evidence?","id":"current-leg-call-stop-sequence-progress-and-completion-evidence-q03","kind":"state"}]}]},{"id":"movement-observation-and-trajectory","name":"Movement observation and trajectory","description":"Groups Journey / Trip context for movement observation and trajectory without importing neighboring master lifecycles.","findings":[{"id":"position-fix-bearing-speed-odometer-observation-time-and-device","name":"Position fix, bearing, speed, odometer, observation time and device","description":"Records position fix, bearing, speed, odometer, observation time and device as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish position fix, bearing, speed, odometer, observation time and device?","id":"position-fix-bearing-speed-odometer-observation-time-and-device-q01","kind":"measurement"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access position fix, bearing, speed, odometer, observation time and device, and under what role or authority?","id":"position-fix-bearing-speed-odometer-observation-time-and-device-q02","kind":"exception"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify position fix, bearing, speed, odometer, observation time and device?","id":"position-fix-bearing-speed-odometer-observation-time-and-device-q03","kind":"lifecycle"}]},{"id":"actual-trajectory-temporal-geometry-gap-interpolation-and-confidence","name":"Actual trajectory, temporal geometry, gap, interpolation and confidence","description":"Records actual trajectory, temporal geometry, gap, interpolation and confidence as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish actual trajectory, temporal geometry, gap, interpolation and confidence?","id":"actual-trajectory-temporal-geometry-gap-interpolation-and-confidence-q01","kind":"evidence"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access actual trajectory, temporal geometry, gap, interpolation and confidence, and under what role or authority?","id":"actual-trajectory-temporal-geometry-gap-interpolation-and-confidence-q02","kind":"interoperability"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify actual trajectory, temporal geometry, gap, interpolation and confidence?","id":"actual-trajectory-temporal-geometry-gap-interpolation-and-confidence-q03","kind":"temporal"}]}]}]},{"id":"deviation-outcome-and-measures","name":"Deviation, outcome and measures","description":"Groups the governed Journey / Trip concern for deviation, outcome and measures.","layers":[{"id":"disruption-change-and-outcome","name":"Disruption, change and outcome","description":"Groups Journey / Trip context for disruption, change and outcome without importing neighboring master lifecycles.","findings":[{"id":"delay-cancellation-diversion-interruption-missed-connection-and-recovery","name":"Delay, cancellation, diversion, interruption, missed connection and recovery","description":"Records delay, cancellation, diversion, interruption, missed connection and recovery as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish delay, cancellation, diversion, interruption, missed connection and recovery?","id":"delay-cancellation-diversion-interruption-missed-connection-and-recovery-q01","kind":"exception"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access delay, cancellation, diversion, interruption, missed connection and recovery, and under what role or authority?","id":"delay-cancellation-diversion-interruption-missed-connection-and-recovery-q02","kind":"decision"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify delay, cancellation, diversion, interruption, missed connection and recovery?","id":"delay-cancellation-diversion-interruption-missed-connection-and-recovery-q03","kind":"spatial"}]},{"id":"boarding-alighting-no-show-abandonment-partial-completion-and-arrival-outcome","name":"Boarding, alighting, no-show, abandonment, partial completion and arrival outcome","description":"Records boarding, alighting, no-show, abandonment, partial completion and arrival outcome as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish boarding, alighting, no-show, abandonment, partial completion and arrival outcome?","id":"boarding-alighting-no-show-abandonment-partial-completion-and-arrival-outcome-q01","kind":"event"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access boarding, alighting, no-show, abandonment, partial completion and arrival outcome, and under what role or authority?","id":"boarding-alighting-no-show-abandonment-partial-completion-and-arrival-outcome-q02","kind":"identity"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify boarding, alighting, no-show, abandonment, partial completion and arrival outcome?","id":"boarding-alighting-no-show-abandonment-partial-completion-and-arrival-outcome-q03","kind":"provenance"}]}]},{"id":"distance-performance-and-impact","name":"Distance, performance and impact","description":"Groups Journey / Trip context for distance, performance and impact without importing neighboring master lifecycles.","findings":[{"id":"travelled-network-and-straight-line-distance-duration-wait-and-speed","name":"Travelled, network and straight-line distance, duration, wait and speed","description":"Records travelled, network and straight-line distance, duration, wait and speed as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish travelled, network and straight-line distance, duration, wait and speed?","id":"travelled-network-and-straight-line-distance-duration-wait-and-speed-q01","kind":"measurement"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access travelled, network and straight-line distance, duration, wait and speed, and under what role or authority?","id":"travelled-network-and-straight-line-distance-duration-wait-and-speed-q02","kind":"classification"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify travelled, network and straight-line distance, duration, wait and speed?","id":"travelled-network-and-straight-line-distance-duration-wait-and-speed-q03","kind":"ownership"}]},{"id":"occupancy-cost-energy-emissions-accessibility-and-service-quality-view","name":"Occupancy, cost, energy, emissions, accessibility and service-quality view","description":"Records occupancy, cost, energy, emissions, accessibility and service-quality view as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish occupancy, cost, energy, emissions, accessibility and service-quality view?","id":"occupancy-cost-energy-emissions-accessibility-and-service-quality-view-q01","kind":"quality"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access occupancy, cost, energy, emissions, accessibility and service-quality view, and under what role or authority?","id":"occupancy-cost-energy-emissions-accessibility-and-service-quality-view-q02","kind":"composition"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify occupancy, cost, energy, emissions, accessibility and service-quality view?","id":"occupancy-cost-energy-emissions-accessibility-and-service-quality-view-q03","kind":"authority"}]}]}]},{"id":"governance-provenance-and-interoperability","name":"Governance, provenance and interoperability","description":"Groups the governed Journey / Trip concern for governance, provenance and interoperability.","layers":[{"id":"provenance-reconciliation-and-lineage","name":"Provenance, reconciliation and lineage","description":"Groups Journey / Trip context for provenance, reconciliation and lineage without importing neighboring master lifecycles.","findings":[{"id":"source-actor-method-event-time-record-time-ingestion-time-and-assurance","name":"Source, actor, method, event time, record time, ingestion time and assurance","description":"Records source, actor, method, event time, record time, ingestion time and assurance as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish source, actor, method, event time, record time, ingestion time and assurance?","id":"source-actor-method-event-time-record-time-ingestion-time-and-assurance-q01","kind":"provenance"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access source, actor, method, event time, record time, ingestion time and assurance, and under what role or authority?","id":"source-actor-method-event-time-record-time-ingestion-time-and-assurance-q02","kind":"relationship"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify source, actor, method, event time, record time, ingestion time and assurance?","id":"source-actor-method-event-time-record-time-ingestion-time-and-assurance-q03","kind":"constraint"}]},{"id":"schedule-observation-conflict-correction-split-merge-and-successor","name":"Schedule-observation conflict, correction, split, merge and successor","description":"Records schedule-observation conflict, correction, split, merge and successor as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish schedule-observation conflict, correction, split, merge and successor?","id":"schedule-observation-conflict-correction-split-merge-and-successor-q01","kind":"validation"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access schedule-observation conflict, correction, split, merge and successor, and under what role or authority?","id":"schedule-observation-conflict-correction-split-merge-and-successor-q02","kind":"state"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify schedule-observation conflict, correction, split, merge and successor?","id":"schedule-observation-conflict-correction-split-merge-and-successor-q03","kind":"process"}]}]},{"id":"access-retention-and-projections","name":"Access, retention and projections","description":"Groups Journey / Trip context for access, retention and projections without importing neighboring master lifecycles.","findings":[{"id":"traveller-location-sensitivity-consent-purpose-access-legal-hold-and-retention","name":"Traveller location sensitivity, consent, purpose, access, legal hold and retention","description":"Records traveller location sensitivity, consent, purpose, access, legal hold and retention as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish traveller location sensitivity, consent, purpose, access, legal hold and retention?","id":"traveller-location-sensitivity-consent-purpose-access-legal-hold-and-retention-q01","kind":"privacy"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access traveller location sensitivity, consent, purpose, access, legal hold and retention, and under what role or authority?","id":"traveller-location-sensitivity-consent-purpose-access-legal-hold-and-retention-q02","kind":"lifecycle"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify traveller location sensitivity, consent, purpose, access, legal hold and retention?","id":"traveller-location-sensitivity-consent-purpose-access-legal-hold-and-retention-q03","kind":"event"}]},{"id":"transmodel-gtfs-moving-features-statistical-schema-org-time-and-provenance-projection","name":"Transmodel, GTFS, Moving Features, statistical, Schema.org, time and provenance projection","description":"Records transmodel, gtfs, moving features, statistical, schema.org, time and provenance projection as source-qualified Journey / Trip context while route, itinerary, service, schedule, place, person, vehicle, booking, ticket, shipment, incident and sensor masters remain external.","questions":[{"text":"Which journey identity, class, subject, endpoint, leg, time basis and source establish transmodel, gtfs, moving features, statistical, schema.org, time and provenance projection?","id":"transmodel-gtfs-moving-features-statistical-schema-org-time-and-provenance-projection-q01","kind":"interoperability"},{"text":"Who planned, undertook, operated, observed, asserted, corrected or may access transmodel, gtfs, moving features, statistical, schema.org, time and provenance projection, and under what role or authority?","id":"transmodel-gtfs-moving-features-statistical-schema-org-time-and-provenance-projection-q02","kind":"temporal"},{"text":"Which ordered components, measurements, uncertainties, exceptions, evidence and lineage qualify transmodel, gtfs, moving features, statistical, schema.org, time and provenance projection?","id":"transmodel-gtfs-moving-features-statistical-schema-org-time-and-provenance-projection-q03","kind":"measurement"}]}]}]}]},"agentConduct":{"may":["Register a journey and compose its legs.","Append position and timing observations.","Derive progress and delay estimates.","Flag deviations from the plan."],"mustNot":["Infer actual travel or boarding from a ticket or plan alone.","Reroute a vehicle or traveller consequentially without authority.","Share live location without consent.","Decide passenger rights or compensation."],"requiresHuman":["Consequential rerouting and safety interventions.","Disclosure of live location to third parties."]},"ethics":{"considerations":["Movement traces reveal home, work, health visits and associations.","Live location can enable stalking or harm.","Journey data used for pricing or policing can discriminate."],"affectedParties":["Travellers","Drivers and crew","Operators","People near the route"]},"owners":{"steward":"Declare the Dimension owner, responsible stewards and authority for personal, organizational, fleet and public-service journey records.","roles":[{"name":"Dimension owner","responsibilities":["Own namespace, mastership, delegation, access, retention and federation rules."]},{"name":"Journey steward","responsibilities":["Own journey boundary, composition, plan assertions, status derivation and reconciliation."]},{"name":"Traveller or vehicle steward","responsibilities":["Maintain authoritative subject identity, consent, role and permitted journey linkage."]},{"name":"Transport operator","responsibilities":["Own service, schedule, vehicle-journey and operational observations it performs."]},{"name":"Observation or data steward","responsibilities":["Govern devices, sources, clocks, quality, mappings and correction lineage."]},{"name":"Safety or regulatory authority","responsibilities":["Own restrictions, interventions and jurisdictional decisions outside Journey mastership."]},{"name":"Reviewer or auditor","responsibilities":["Review evidence, conflicts, corrections and protected use without rewriting originals."]},{"name":"Disclosure authority","responsibilities":["Approve recipient, purpose, location exposure, redaction and publication timing."]}],"masterSystems":[]},"relations":[{"target":"WM-FLW-007 Passenger Mobility / Transit","type":"references","note":"Resolve transit network, service, schedule, fare and mobility context without inheriting the broader model's lifecycle."},{"target":"WM-FLW-010 Route / Itinerary","type":"references","note":"Resolve reusable paths and planning results while preserving journey identity and actual divergence."},{"target":"Person, Vehicle, Organization, Place, Service, Schedule, Booking, Ticket, Shipment, Incident, Sensor and Evidence models","type":"references","note":"Resolve external masters without duplicating their identity, authority or lifecycle."},{"target":"Transmodel v6.2 and GTFS Schedule and Realtime","type":"aligned","note":"Project passenger-trip and vehicle-journey views with explicit vocabulary and version mappings."},{"target":"OGC and ISO Moving Features and GeoSPARQL","type":"aligned","note":"Project actual movement, temporal geometry and spatial-query views with CRS, gap and conformance controls."},{"target":"UNECE transport statistics, UN tourism statistics and Schema.org Trip","type":"aligned","note":"Project statistical and web-discovery views without treating their trip boundaries as universal."},{"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-007 Passenger Mobility / Transit","type":"neighbor","note":"Passenger Mobility owns transit networks, services, schedules, fares and aggregate mobility context. Journey / Trip owns one movement episode and may reference transit service or passenger-trip views without assuming inheritance."},{"target":"WM-FLW-010 Route / Itinerary","type":"neighbor","note":"A route is a reusable or selected spatial path and an itinerary is a planning result or ordered visit plan. A journey is the identity-bearing intended or undertaken movement that references them and preserves actual divergence."},{"target":"Person, Vehicle, Organization and Transport Service","type":"neighbor","note":"The journey assigns journey-scoped roles and references. Subject identity, vehicle lifecycle, operator authority, network, schedule and service operation remain externally mastered."},{"target":"WM-FLW-011 Shipment / Consignment","type":"neighbor","note":"A shipment may reference one or more transport journeys. Cargo, consignment, custody and logistics lifecycle remain shipment-owned and do not become journey composition."},{"target":"Observation, Sensor, Incident and Evidence","type":"neighbor","note":"The journey binds source-qualified position, passing, disruption and completion assertions. Sensor streams, generic incidents and evidentiary records retain independent identity and authority."},{"target":"Travel, Tour and Tourism Trip","type":"neighbor","note":"A wider travel episode or return journey may contain multiple one-way trips and activities. Tourism status depends on purpose, destination, usual environment and duration under a statistical profile."},{"target":"WM-FLW-007","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative journey master-system identifier and immutable revision identifier.","Governed globally resolvable journey, leg or observation IRI.","Adopting-Dimension UUID or ULID when no authoritative external identifier exists."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"required","items":["A journey has an origin, destination, ordered legs, mode, subject and start and end times.","Often confused with a route (path), an itinerary (plan), a service run and a shipment."]},"capabilities":{"applicability":"required","items":["Register journey: Create one governed journey identity and boundary.","Bind participants: Bind traveller, driver, operator, vehicle and service roles without importing their lifecycles.","Compose ordered legs: Append stages, modes, endpoints, calls and connection dependencies.","Record selected plan: Record requested, proposed or selected movement plan and alternatives.","Record journey observation: Append calls, passing times, position fixes and other journey-scoped observations.","Derive progress and state: Derive current leg, progress and lifecycle state from qualified evidence.","Reconcile journey times: Compare requested, planned, predicted, observed and actual times.","Handle deviation: Register disruption, impact, recovery, diversion or successor plan without overwriting history.","Calculate journey measures: Calculate qualified distance, duration, wait, speed and impact views.","Project journey: Produce minimum-necessary standards-aligned or stakeholder views."]},"hazards":{"applicability":"required","items":["Location privacy breach.","Wrong arrival predictions leading to missed connections.","Unsafe rerouting.","Mixing person and vehicle journeys."]},"interfaces":{"applicability":"required","items":["OGC Moving Features.","GTFS and GTFS Realtime.","CEN Transmodel and NeTEx.","ISO 8601 date and time."]},"context":{"applicability":"required","items":["EU multimodal information rules and UK travel-survey definitions are regional profiles, not universal journey law.","Transmodel and GTFS primarily describe passenger transport and service data; private, pedestrian, freight-linked and non-service vehicle journeys need explicit profiles.","Tourism-statistics purpose and duration definitions apply only when the relevant statistical population and usual-environment tests are satisfied."]}},"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":"Passenger Information Tutorial","url":"https://transmodel-cen.eu/index.php/passenger-information-tutorial/","note":"CEN Transmodel"},{"title":"Transmodel at a glance","url":"https://transmodel-cen.eu/index.php/transmodel-at-a-glance/","note":"CEN Transmodel"},{"title":"GTFS Schedule Reference","url":"https://gtfs.org/documentation/schedule/reference/","note":"MobilityData"},{"title":"GTFS Realtime Reference","url":"https://gtfs.org/documentation/realtime/reference/","note":"MobilityData"},{"title":"GTFS Realtime Trip Updates","url":"https://gtfs.org/documentation/realtime/feed-entities/trip-updates/","note":"MobilityData"},{"title":"OGC Moving Features standards","url":"https://www.ogc.org/standards/movingfeatures/","note":"Open Geospatial Consortium"},{"title":"OGC API Moving Features Part 1 Core","url":"https://docs.ogc.org/is/22-003r3/22-003r3.html","note":"Open Geospatial Consortium"},{"title":"OGC Moving Features Access","url":"https://docs.ogc.org/is/16-120r3/16-120r3.html","note":"Open Geospatial Consortium"},{"title":"ISO 19141 Geographic information - Schema for moving features","url":"https://www.iso.org/standard/41445.html","note":"International Organization for Standardization"},{"title":"Glossary for Transport Statistics, sixth edition","url":"https://unece.org/info/Transport/pub/411667","note":"UNECE, Eurostat and International Transport Forum"},{"title":"National Travel Survey 2024: notes and definitions","url":"https://www.gov.uk/government/statistics/national-travel-survey-2024/nts-2024-notes-and-definitions","note":"United Kingdom Department for Transport"},{"title":"International Recommendations for Tourism Statistics 2008","url":"https://unstats.un.org/unsd/tradeserv/IRTS%202008%20edited%20whitecover.pdf","note":"United Nations Statistics Division"},{"title":"Commission Delegated Regulation (EU) 2024/490","url":"https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32024R0490","note":"European Union"},{"title":"Trip","url":"https://schema.org/Trip","note":"Schema.org Community Group"},{"title":"GeoSPARQL","url":"https://www.ogc.org/standards/geosparql/","note":"Open Geospatial Consortium"},{"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: Timestamps","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"}],"openQuestions":["Approve or reject the WM-FLW-007 relation after generic Journey / Trip and Passenger Mobility / Transit boundaries are jointly reviewed.","Research WM-FLW-010 and decide whether reusable Route and selected Itinerary need separate model identities.","Create independently validated person-trip, vehicle-journey, service-journey, pedestrian, road, rail, maritime, aviation, private, shared, public and on-demand profiles.","Benchmark trip segmentation, identity matching, endpoint continuity, time reconciliation, map matching, trajectory reconstruction, completion inference, ETA and disruption handling.","Pin exact external releases and licensing conditions and obtain independent transport, geospatial, statistics, safety, accessibility, privacy, data and records review before promotion beyond reviewable-draft assurance.","Mode, jurisdiction, safety, immigration, border, accessibility, passenger-rights, employment-travel, privacy and retention profiles require exact current rules and competent review.","Person, organization, vehicle, route, itinerary, network, place, service, schedule, booking, ticket, fare, shipment, incident, payment, sensor and evidence lifecycles remain in neighboring masters.","Certified field crosswalks, trajectory-matching algorithms, trip-segmentation rules, prediction benchmarks and legal proof requirements remain future work."],"resources":{"spec":"/models/wm-flw-009-journey-trip/spec.yaml","agents":"/models/wm-flw-009-journey-trip/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-flw-009"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-flw-009-journey-trip/spec.yaml","ver-cy/world-models/card-supplements/wm-flw-009-journey-trip.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T20:04:02Z","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 journey is an occurrence; distances and times are recorded about it, the vehicles and people carry the physical properties.","_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}}