dos-next-uplisted

# dos-next-up — the generic plan-and-ship snapshot > **This is the baseline screenplay DOS ships, not a prerequisite.** It drives the > kernel syscalls (`verify`, `gate`) against *any* repo whose layout lives in > `dos.toml`. It names no host directory, no host lane, and no host commit > convention — every host specific comes from `dos doctor --json` (paths/lanes, > via WCR) or `dos.toml [stamp]` (the ship grammar, via SCV). Copy it into your > own skills dir, point `dos` at your workspace, and it runs. The shape is domain-free: **discover the layout → walk the plans → audit each pick against the truth syscall → render a packet → gate the empty case.** The *policy* (which lanes, which plan grammar, where output lands) is data the screenplay reads, never literals it hardcodes. ## Inputs - `--scope <name>` (repeatable, optional) — narrow candidates to one lane (a name from the active `[lanes]` taxonomy) or one plan id. Omitted = all plans. - `--limit <N>` (optional, default 5) — how many top picks to render. ## Step 0 — Discover the workspace layout (one call) Run the doctor verb and read the result. **This is the WCR on-ramp: every path/lane below comes from here, never a literal.** ```bash dos doctor --workspace . --json ``` Parse the JSON object. The fields you use: - `paths.plans_glob` — the glob to walk for plan docs (whatever the workspace declared). **Use this value; never assume a fixed plans directory.** - `paths.next_packets` — where the rendered packet i