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