approval-consolelisted

# approval-console - **Roadmap feature:** F027. **On-disk spec:** `specs/021-approval-console/`. When the spec-dir number (021) and the roadmap F-number (F027) disagree, the roadmap F-number wins: this is F027. The kit STOPS at judgment calls (Principle V) and the readiness spine RESERVES the slot for the answer (`readiness-status.yaml` `approvals[]`; the `unresolved-questions.md` Open-questions `Resolution` column). What it lacks is the LOOP between "a question was raised" and "the named human's answer is recorded in the committed artifacts". This skill is that loop, and only that loop. It does two things: (1) packages a raised judgment call into a reviewable DECISION PACKAGE (a request), and (2) once a named human answers, RECORDS that decision back into the committed artifacts. An approval that lives only in chat is not an approval -- it cannot be reviewed, advance a gate, or be audited. ## Authority declaration (F024 module contract -- filled) - **Authority category:** Product Module - **Capability level:** `artifact-writing` *(exactly one)* - **Product layer:** 1-6 *(all stages -- the functional axis; orthogonal to category)* - **Roadmap feature:** F027 **On-disk spec:** `specs/021-approval-console/` - **Owner:** the named human who decides each judgment call (the console transcribes; it is never the owner) - **Status:** Authored (skill + two templates + one docs page; no runtime code) ### What it does (one line) > Consumes a raised judgment call + a named