135 135 Stage prompts own lifecycle behavior, and `/system exec` owns code, test, debug, review, and git guidance only inside that command.
137 -Agents allocate IDs and paths from the System document contract, while extension write/edit gates block invalid documents and return actionable frontmatter or path errors.
137 +Artifact-authoring commands temporarily enable `system_slot` for their agent run.
139 +After choosing semantic titles, the agent calls `system_slot` for each new bundle and uses the returned IDs and paths exactly.
141 +Context determines which bundles, if any, the command creates.
143 +The extension derives each slug from its bundle title.
145 +Extension write/edit gates block invalid documents and return actionable frontmatter or path errors.
139 147 After creating or materially editing an artifact, the agent prints a copyable view line:
164 172 Issues amend or create specs only when the issue exposes a spec gap; normal bugs and security fixes do not force spec amendment.
166 -Finished phases and plans are immutable.
174 +Approved phases and plans are immutable.
168 -Create a new phase or plan instead of editing a finished one.
176 +Create a new phase or plan instead of editing an approved one.
170 178 The extension enforces immutability from frontmatter status.
181 -The extension owns lifecycle directories, type names, token generation, status enums, and metadata validation.
189 +The extension owns lifecycle directories, type names, token generation, the phase and plan status enum, and metadata validation.
183 191 Frontmatter references store IDs only; body links may use relative paths, slugs, or normal Markdown links that the renderer resolves.
185 193 Required known frontmatter fields are:
188 -| ---------- | --------------------------------------------------------------------- |
189 -| `research` | `id`, `type: research`, `title` |
190 -| `spec` | `id`, `type: spec`, `title`, optional `research: string[]` |
191 -| `phase` | `id`, `type: phase`, `title`, `spec`, `status: draft |
192 -| `plan` | `id`, `type: plan`, `title`, `spec`, optional `phase`, `status: draft |
193 -| `issue` | `id`, `type: issue`, `title`, `specs: string[]`, `status: open |
196 +| ---------- | ------------------------------------------------------------------------------- |
197 +| `research` | `id`, `type: research`, `title` |
198 +| `spec` | `id`, `type: spec`, `title`, optional `research: string[]` |
199 +| `phase` | `id`, `type: phase`, `title`, `spec`, `status: draft\|approved` |
200 +| `plan` | `id`, `type: plan`, `title`, `spec`, optional `phase`, `status: draft\|approved` |
201 +| `issue` | `id`, `type: issue`, `title`, `specs: string[]` |
195 203 Research references no System stage.
203 211 Issues may reference as many specs as make sense and may start with an empty array while the contract is unknown.
205 -Phase and plan `done` means human-approved, immutable, and eligible for exec.
213 +Phase and plan `approved` means human-approved, immutable, and eligible for exec.
207 -Specs and research have no status and remain editable under normal ownership gates.
215 +Specs, research, and issues have no status.
217 +Specs remain editable under ownership gates; research and issues remain editable.
209 219 Tests still use `SYSTEM-SPEC: <SPEC-ID>` comments when a test directly proves a spec contract.
221 231 Spec verification records claims checked, evidence, result, and proposed spec amendments; it does not become canonical project state.
223 -Phases record coarse milestones, ordering, dependencies, risks, and done criteria.
233 +Phases record coarse milestones, ordering, dependencies, risks, and completion criteria.
225 235 Plans record concrete implementation steps and checks at module, interface, package, or class level.
231 241 Terse pseudocode is allowed only when needed to explain an important change.
233 -Issues record symptom, impact, reproduction or evidence, related specs, and status.
243 +Issues record symptom, impact, reproduction or evidence, and related specs.
235 245 Exec logs record System refs, changed areas, verification evidence, and the copyable view line.