also looking at this
feat: model one point-load intake with conserved momentum
#99
45 files
+3133
-169
| @@ -38,6 +38,30 @@ forgetting a lease, not a guaranteed real-time deadline. Do not automatically re | ||
| 38 | 38 | without independently checking operator authority. `close()` is idempotent. The SITL example has |
| 39 | 39 | a hard 30-second duration and a deliberately artificial target. |
| 40 | 40 | |
| 41 | ## Modeled cargo missions | |
| 42 | ||
| 43 | The cargo modules expose the owned runtime directly, without an external-autopilot dependency: | |
| 44 | ||
| 45 | - `planCargoDelivery(configuration)` in `resources/functions/drone/cargo/plan.ts` captures a | |
| 46 | complete declaration and validates the normal/alternate mission graph and declared reserve. | |
| 47 | - `simulateCargoDelivery({ configuration, scenario? })` in `cargo/delivery.ts` under the same | |
| 48 | drone folder runs its actual loaded rigid body through the raw sensors, estimator, mission, | |
| 49 | controls, authority and watchdog. Omitting configuration selects only the closed named fixture. | |
| 50 | - `cargoDeliverySummary(run)` produces a bounded compact projection, preserving actual mission, | |
| 51 | custody and host-loss outcomes. A matched failure demonstration is not delivery completion. | |
| 52 | - `createCargoDeliveryCoordinator(declaration, modeledMechanism)` in `cargo/coordinator.ts` | |
| 53 | implements `VehiclePayloadPort`, captured readiness and idempotent cancellation. Its adapter | |
| 54 | contract is synchronous and explicitly modeled, with no built-in hardware I/O. | |
| 55 | ||
| 56 | The [cargo guide](cargo-delivery.md) defines the flat synthetic origin, finite load/route bounds, | |
| 57 | one-release and receipt semantics, phase-bound faults, native CLI exit codes and remaining | |
| 58 | fleet/physical/BVLOS work. Budgets are declared power ceilings, not electrical measurements. | |
| 59 | ||
| 60 | `createReceivingRigidBody({ expectedPointLoad, ...bodyOptions })` in `controls/physics.ts` | |
| 61 | provides the separate [point-load intake prerequisite](cargo-delivery.md#point-load-intake-prerequisite). | |
| 62 | It integrates real modeled mass/CG changes after one coincident inelastic point capture. | |
| 63 | The caller still owns the parcel, finite station handling and captured fleet custody protocol. | |
| 64 | ||
| 41 | 65 | ## Target sources |
| 42 | 66 | |
| 43 | 67 | `createGpsTargetSource({ targetId, origin, maxSpeedMps?, now? })` converts trusted phone or GNSS fixes |