dos-dispatchlisted

# dos-dispatch — the generic chained snapshot→ship cycle > **The concurrency-safe dispatch.** It chains `/dos-next-up` (the packet) to a > ship, but first takes a **lane lease** through the admission kernel so several > dispatches on disjoint lanes run in parallel without editing the same files. > The "may I run on this lane" decision is the kernel's (`dos arbitrate`), not > inline prose. Every path/lane comes from `dos doctor --json`; nothing is > hardcoded. The shape: **discover → take a lane → snapshot → gate → ship → archive.** The lane taxonomy and the run-dir location are data (`[lanes]`, `[paths]`); the admission and the gate verdict are kernel syscalls. ## Inputs - `--lane <name>` (optional) — the lane to dispatch on (a name from the active `[lanes]`). Omitted = a bare auto-pick: the arbiter picks a free lane from the `autopick` ladder. - `--leases <json>` (optional) — the live leases other dispatches hold, as a JSON list of `{lane, lane_kind, tree}` (the arbiter keys exclusivity on `lane_kind`, so include it — `cluster`/`keyword`/`global`). In a real loop these come from a status query; for a single dispatch this is usually `[]`. ## Step 0 — Discover the layout + the lane taxonomy ```bash dos doctor --workspace . --json ``` Read `lanes` (the taxonomy), `paths.next_packets` (packet output), and `paths.runs` (the run dir to archive under). **Use these; never hardcode a lane name or a run path.** ## Step 1 — Take a lane lease (the admission kernel) As