Skip to main content

Trips and flights

internalAudited 2026-11-21

Organize a journey and its leg occurrences, then connect durable plans to the host flight workflow.

Contract cardCurrent state
OwnerPlanning / FlightManagement
Version boundaryPortable planning intent 1.0; host store versions remain separate
Current consumersSwift Planning stores and FlightManagement adapters
Sourceapps/ios/Planning/Sources/Planning/TripStore.swift
Validator / acceptance entryapps/ios/Planning/Tests/PlanningTests/PlanningDocumentCoordinatorTests.swift
Fixtures / specimenShared public corpus pending

Adopt this model​

Use the existing coordinator for portable planning documents. Host Trip types are adapters; a universal trip/flight interchange contract is not yet certified.

Identity, units and meaning​

A stop occurrence represents a visit, including repeated airports. A flight execution and its recorded track do not overwrite the saved plan.

Failure and partial states​

Divergent commits need explicit reconciliation; unknown legacy route components require an import assessment.

Continue to the guide · Model conventions · Release notes

Source paths identify owners in the source checkout; they are not public repository links. A listed test is an acceptance entry, not a claim that every consumer has passed a shared corpus.