dos-goal-fleetlisted

# dos-goal-fleet — wave-launched self-stopping goal workers, witnessed not narrated > **A fleet that trusts each worker's "I'm done" is a fleet of silent fails.** > The move this skill makes is the one the whole substrate exists for: a worker's > "the goal is met" is a *claim with a byte-author*, and the byte-author is the > judged worker. So each child's stop is gated on `dos-goal-gate` — it cannot > declare done until a witness it did not write (git ancestry, an effect > read-back) corroborates the goal's effects. The fleet launches the leaves; the > kernel decides which ones actually landed. The skill narrates; it never rules. Take an operator-supplied context describing several **independent objectives**, turn each into ONE headless worker armed with a single goal, and fire them in **waves** sized to whatever seat pool the host exposes — so the launch is load-balanced and no single account walls. This is the fan-out analogue of two sibling skills: - **`dos-goal-gate`** is one self-stopping leaf — a single agent whose "done" is grounded. `dos-goal-fleet` arms *many* such leaves at once. Each child runs the goal-gate discipline; this skill is the launcher and the rollup around them. - **`dos-witness-claim`** is the *fold* — believing only the confirmed effects when many workers' results converge. Step 5 here is that fold, applied to the fleet's per-instance outcomes. The shape is domain-free: **decompose into independent goals → price the wave into its serial/co