Trips and flights
Organize a journey and its leg occurrences, then connect durable plans to the host flight workflow.
| Contract card | Current state |
|---|---|
| Owner | Planning / FlightManagement |
| Version boundary | Portable planning intent 1.0; host store versions remain separate |
| Current consumers | Swift Planning stores and FlightManagement adapters |
| Source | apps/ios/Planning/Sources/Planning/TripStore.swift |
| Validator / acceptance entry | apps/ios/Planning/Tests/PlanningTests/PlanningDocumentCoordinatorTests.swift |
| Fixtures / specimen | Shared 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.