ReviewOS

also looking at this

stacks/drone

feat: model one point-load intake with conserved momentum

#99
Merged chris wants to merge codex/cargo-fleet-custody into main
45 files +3133 -169
docs/adr/0034-modeled-cargo-custody.mdadded+49-0
Changes to docs/adr/0034-modeled-cargo-custody.md
@@ -0,0 +1,49 @@
1# 0034: Cargo missions use captured custody and the shared vehicle runtime
2
3## Decision
4
5Build cargo delivery on `VehicleMissionPlan`, `VehiclePayloadPort`, the owned quad-X
6plant and the existing raw sensor/estimator/control/authority/watchdog loop. Keep
7point-mass dynamics and independent parcel motion in the model, and put release and
8custody policy behind a separate modeled coordinator. Plant truth cannot mutate
9policy custody directly.
10
11The public simulator accepts an explicit configuration for load/CG, receiver, release
12height, alternate and declared power budget. A pure planner validates the complete
13normal/alternate graph before allocating a world. Native Buddy commands provide the
14application entrypoint; the standalone CLI registers the same command implementation.
15No framework package abstraction is introduced for cargo-specific policy.
16
17Release is a single scoped operation after qualified captured dwell. Intent, mechanism
18open/jam, receiver receipt and carrier completion are distinct observations. Unknown
19dispatch remains uncertain. Terminal uncertainty cancels before discarding its event;
20authority loss and close retain the same cancellation path. Receipt requires matching
21event/container/site/recipient evidence and a qualified finite capture-time ACK pose.
22
23The shared mission engine's optional cargo payload failure edge is a finite, one-way
24alternate approach and landing. Its budget includes that path. It cannot retry release,
25replace the authority fence or bypass a source/authority failure.
26
27Two captured link sources belong to the same vehicle/boot/session scope. Switching
28between them does not transfer mission authority or parcel custody to another vehicle.
29Foreign/replayed/stale packets and complete source loss cannot silently renew authority.
30
31Post-release and post-receipt fault fixtures bind to observed policy events. Independent
32settling continues only board/plant physics after host processing stops. Later physical
33parcel contact cannot create a host receipt, and an earlier receipt cannot fabricate
34carrier landing completion.
35
36## Limits and further work
37
38The actual executable world remains a flat local fixture with the existing synthetic
39GNSS origin and initial-north heading assumption. Its point parcel has no drag or
40collision scene. The current power calculation is a declared ceiling budget, separate
41from measured or modeled electrical consumption. Physical and authenticated-identity
42flags remain false.
43
44Distinct-vehicle fleet handover requires actual separate vehicle/boot/session sources,
45fresh authority and custody observations, explicit transfer/acceptance and failure
46behavior. It is not implemented by changing a scope label or copying a successful
47summary. Durable cargo/runtime reconciliation, physical release/receiver validation and
48the separate BVLOS operational evidence case remain issue #25 work. The
49[cargo guide](../cargo-delivery.md) records the current command and library contracts.