com.airplaneian.contrail.temp.trip

            "description": "Free-text name for the trip, for example 'Tokyo, spring 2026'. Optional, and as with any free text it is public and permanent once published.",

            "description": "Short identifier for the tool that produced this record, for example 'flighty' or 'manual'. Same meaning as on a flight record: together with 'sourceId' it lets a tool update the trips it wrote previously instead of duplicating them on a re-import."

            "description": "The flights that made up this trip, in the order they were flown, as AT-URIs pointing at com.airplaneian.contrail.temp.flight records. Plain AT-URIs rather than content-pinned strong references, because flight records are expected to be corrected in place as better data arrives, and a pinned reference would break on every such correction. References may dangle if a flight is later deleted; readers must tolerate that rather than treat it as an error."

            "description": "The identifier the tool named in 'source' uses for this trip, in that tool's own namespace. Note that a source's grouping key may be sensitive even when the resulting grouping is not -- a booking reference, for instance, is a credential that can be used to retrieve a reservation and must not be written here. Derive an opaque identifier instead where the natural key cannot be published."

            "description": "When this record was written, as distinct from when the trip happened. The only required field. Write it with an explicit UTC offset and no fractional seconds, for example '2026-07-25T18:22:05-07:00'."

      "description": "An assertion that a set of flights belonged to one journey. Grouping is kept as its own record rather than as a field on the flight, so that a flight record remains a standalone assertion that does not depend on any grouping existing, and so that deleting a trip orphans nothing. The reference points one way only, from trip to flight: nothing in the protocol keeps two directions consistent, so a flight does not carry a trip reference. A trip references only flight records the author wrote, and carries no claim about flights in anyone else's repository. As with flight records, only 'createdAt' is required and absent means unknown or not applicable. Values derivable from the referenced flights are excluded on purpose: start and end dates, leg count, total distance, and origin and destination are all computable by a reader that resolves the references, and storing them guarantees drift once a referenced flight is corrected. Note that a trip discloses more than its flights do individually, because it asserts that particular journeys were a single continuous absence."