# ckb-decide — edge cases Reference material for the `ckb-decide` skill. Read when a run hits an unusual situation the main steps don't cover. - **No `wiki/decisions/` directory yet** — create it along with `index.md` and `log.md` (using the scaffold this template ships), then record the decision as `0001-…`. - **The user describes a decision that was already recorded** — don't create a duplicate. Point at the existing record and ask whether they want to supersede it, correct it, or leave it. - **A decision with no clear decider** ("we just kind of settled on it") — record `decided_by: unknown` rather than guessing or attributing it to whoever is in the room. Unattributed is a fact; misattributed is a defect. - **A decision that was never actually made** ("we should probably...") — record it as `status: proposed` with no `decided_on`, or don't record it at all. Ask which; a proposal filed as `accepted` is the most damaging failure mode this skill has. - **A decision that reverses a reversal** — normal chaining. Each link points one step back; the chain is the history. - **Bulk import of historical decisions** (a meeting-notes backlog) — that's `ckb-ingest`'s job for the extraction, then this skill's format for the pages. Record them in chronological order so the numbers run in the same order as the decisions. --- *Licensed under the Apache License, Version 2.0 — see [LICENSE](../../../LICENSE) at the repository root, or .*