govern-registerlisted

# /govern register Skill body for the canonical adopter-side governance-mutation entry point. Both hook-invocation (via additionalContext from `pre-write-guard.sh` branch #1 detection Classes A/B/C/D) and direct user invocation share a single code path. Plans-tree creation is ORTHOGONAL — use `/new-plan` or `/backlog-research`; never `/govern register`. ## Invocation contracts (per A31 + L-72) ```sh # Class A — new top-level vault folder /govern register --kind folder --target <vault-relative-path> [--inherit-from <parent-path>] # Class B/C — new vault-root file or new file-type within existing folder /govern register --kind file-type --name <type-slug> --contract <path-to-file-type-contract.json> # Tag-dimension extension (operator-driven; no hook auto-fire) /govern register --kind tag-extension --dimension <prefix> --values <comma-list> # Class D — new vault-writer registration (hook auto-fire OR SP07 wizard OR direct) /govern register --kind writer --writer-name <name> --writer-kind <connector|agentic-flow|auto-research|scheduled-skill|custom> [--writer-subtype <s>] [--writer-skill <skill-slug>] [--from-template <path>] ``` `process.sh` exposes three sub-verbs matching the 6-step protocol's deliberation/commit/skip arcs: - `process.sh propose --kind <K> --target <T> [...]` — emit proposal JSON to stdout (Claude renders it for the user; user redlines per-field). - `process.sh commit --kind <K> --proposal <validated.json>` — invoke `lib/overlay-master-mutate.sh`