workspace-file-governancelisted

# Workspace File Governance ## Overview Govern every file-creation act (Mode A — Creation Gate) and perform deep, autonomous workspace reorganization (Mode B — Deep Refactor). All rules are agent- and model-agnostic: they rely only on generic filesystem operations (list, search, move), plain Markdown, and the workspace's own tooling. **Operating principle: reversible actions are autonomous; irreversible or function-risking actions are escalated.** Do not interrupt the user for routine decisions. Do interrupt for the small set of major ones (see the Autonomy Matrix in `references/placement-rules.md` §2). ## Core Principles 1. **Understand before touching.** Never move, rename, or delete anything before completing the Phase 0 understanding pass. A file whose purpose is unknown is a file that stays in place. 2. **Existing governance wins.** The workspace's own index/governance docs (AGENTS.md, README, workspace guides, maintenance contracts) override every generic rule in this skill — including their explicit "do not rename / do not touch" lists. 3. **Canonical beats derived.** Identify authoritative sources vs. generated artifacts (e.g. generator script → .docx, master manual → downstream deliverables). Reorganize around the canonical source; never "fix" a derived artifact in isolation. 4. **Update beats create; trash beats delete.** Same-purpose file exists → update it. Suspect content → `_trash-YYYYMMDD/`, never hard deletion. 5. **Deep, not co