governancelisted

## MyACE-specific governance This skill extends the global governance rules with MyACE project-specific conventions. ### Data classification Same classification table as the global governance skill (PUBLIC / INTERNAL / CONFIDENTIAL / REGULATED). When in doubt, treat as CONFIDENTIAL. ### ADR process (Architecture Decision Records) MyACE uses ADRs to capture non-obvious, expensive-to-reverse decisions. See `docs/adr/README.md` for the full guide. **When to write an ADR:** - Picking an auth strategy, data model shape, deployment topology - Anything where a reasonable engineer could have gone a different direction - A decision that's expensive to reverse **When NOT to write an ADR:** - Routine features, bug fixes, or anything where the code itself is the whole explanation **Format:** 1. Copy `docs/adr/template.md` 2. Number sequentially (next is `0006`) 3. Keep it short — one screen 4. Never renumber or delete a past ADR 5. If superseded, mark old status as `Superseded by ADR-00XX` **ADR structure:** ```markdown # ADR-00XX: Title **Status:** Proposed | Accepted | Superseded by ADR-00XX ## Context What problem forced this decision? What constraints were in play? ## Decision What did we decide to do, stated as a clear, single sentence. ## Alternatives considered What else was on the table, and why it was rejected. ## Consequences What this makes easier, what it makes harder, and what it gives up. ``` ### Documentation maintenance MyACE maintains documentation for tw