---
name: the-system-documents
description: "Use before creating, editing, or reviewing any file under .system/ or running a /system stage."
---

# The System document contract

The System mechanically validates every authored mutation and rejects violations with a specific reason: bundle paths (`.system/<type-plural>/<ID>-<slug>/index.md`, lowercase slug), `<PREFIX>-<TYPE>-<id>` ID shape, type directories, required frontmatter and ID-only reference types, plan `depends_on` (same spec, acyclic), phase labels, `schemaVersion` 0 and board invariants, and one-shot human approval for existing core, approved-plan, phase, and spec files and for `currentPhase` transitions.
Author to that feedback instead of restating the rules.
Phases are project-wide operating epochs related to MISSION, not spec decomposition or work breakdown.
Operate only the invoked `/system` stage; never auto-chain or create bundles for another stage.
Recommend the next stage, then wait for explicit human invocation.
Keep prose terse, minimal, and essential.
After creating or materially editing a System document, end with:

```text
View:
/system view <ID>
```