also looking at this
feat: add retained cargo fleet cancellation and recovery
#105
32 files
+2496
-27
| @@ -62,6 +62,22 @@ provides the separate [point-load intake prerequisite](cargo-delivery.md#point-l | ||
| 62 | 62 | It integrates real modeled mass/CG changes after one coincident inelastic point capture. |
| 63 | 63 | The caller still owns the parcel, finite station handling and captured fleet custody protocol. |
| 64 | 64 | |
| 65 | `createCargoStationHandler(declaration)` in `cargo/station.ts` owns one existing point | |
| 66 | through ballistic capture, finite rail transport, cancellation braking and a single | |
| 67 | departure. See the [station model and integration limits](cargo-station.md). It does not | |
| 68 | grant vehicle authority or confirm custody. | |
| 69 | ||
| 70 | `simulateCargoFleet({ scenario? })` and `cargoFleetSummary(run)` in `cargo/fleet.ts` | |
| 71 | execute [two-carrier handover](cargo-fleet.md) through actual retained source and receiver | |
| 72 | runtimes, a consumed station parcel, current-authority intake and captured custody. The | |
| 73 | eleven bounded fault cases retain incomplete outcomes and actual mass separately from receipts. | |
| 74 | `createCargoFleetSession()` exposes exact-epoch `step`, detached `snapshot`/terminal `result`, | |
| 75 | scoped `decide` and idempotent `close`, with the exported `CargoFleetOperatorDecision` type. | |
| 76 | `simulateCargoFleetControl({ case? })` in `cargo/fleet-control.ts` supports four explicit | |
| 77 | transport cancellation/recovery cases. The [operator contract](cargo-fleet.md#retained-world-and-explicit-transport-decisions) | |
| 78 | retains current authority, a single physical point, original receive deadlines and | |
| 79 | attempted-intake uncertainty. It does not restore a failed vehicle session. | |
| 80 | ||
| 65 | 81 | ## Target sources |
| 66 | 82 | |
| 67 | 83 | `createGpsTargetSource({ targetId, origin, maxSpeedMps?, now? })` converts trusted phone or GNSS fixes |