dos-class-cyclelisted

# dos-class-cycle — the judge-gated plan-lifecycle tick > **Garden the portfolio, but never alone.** A plan's class (active / done / > parked / …) should track reality — a done plan should not sit "active," a > long-idle one should park. `/dos-class-cycle` runs ONE tick of that gardening: > it evaluates the declared triggers, asks a **JUDGE-rung adjudicator** (advisory, > fail-to-abstain) to approve each candidate transition, applies only the gated > ones, and logs the cycle. The class set, the legal transitions, and the > failsafes are **declared data** (`[lifecycle]`) — a 2-class repo and a richly- > classed one run the identical mechanism. The shape: **read the declared lifecycle → evaluate triggers → build candidates (deterministic order) → judge each → enact gated transitions → log.** The cycle is domain-free mechanism; the taxonomy is `[lifecycle]` policy; the judge content is a host `dos.judges` driver. ## Inputs - `--dry-run` (optional) — evaluate + judge but enact nothing (a preview cycle). ## Step 0 — Read the declared lifecycle + the layout ```bash dos doctor --workspace . --json ``` Read `lifecycle` — the declared `classes`, `transitions` (each `{from, to, trigger, auto}`), `veto_class`, `max_transitions_per_cycle`, and `per_plan_cooldown_hours` — and `paths` (the plan + run dirs). **Use these; never hardcode a class name, a trigger, or a cap.** A repo that declared only `active`/`done` cycles with those two; a repo with a richer taxonomy declares more. ##