github/github-spec-kit
1
0
Fork 0
mirror of https://github.com/github/spec-kit.git synced 2026-07-04 04:45:43 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: revise Article VI to establish spec as source of truth

Browse Source 
Constitution and specifications are the versioned sources of truth.
Plans and tasks are derived execution artifacts. Implementation gaps
are addressed through new specifications, preserving the feed-forward
dependency direction rather than retrofitting code back into specs.
This commit is contained in:
Manfred Riem
2026-05-11 09:36:12 -05:00
parent 058256758f
commit fbb41195b4
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
spec-driven.md
View File

@@ -347,16 +347,16 @@ Without this article, LLMs default to functional-only implementations—code tha
#### Article VI: Governance and Versioning
All project artifacts—constitution, specifications, plans, and tasks—must be versioned, and changes must propagate consistently across dependent artifacts:
The constitution and specifications are the authoritative sources of truth. Plans and tasks are derived execution artifacts:
```text
Artifact changes MUST:
- Be versioned and traceable through version control
- Propagate to all dependent artifacts when modified
- Maintain cross-artifact consistency after every change
Governance MUST ensure:
- Constitution and specifications are versioned and traceable
- Derived artifacts (plans, tasks) remain consistent with their source specifications
- Implementation gaps are addressed through new specifications, not by retrofitting code back into existing specs
```
This article ensures that governance is not static and that drift between artifacts is caught rather than silently accumulated. When a specification changes, affected plans and tasks must be re-evaluated. When principles evolve, templates and command files must remain aligned. Version bumps are classified by impact—major for removed or redefined principles, minor for additions, patch for clarifications—creating an auditable trail of architectural decisions.
This article ensures that governance is not static and that the dependency direction is preserved—specifications drive implementation, never the reverse. When a gap or requirement emerges during implementation, it is addressed through a new specification rather than patching artifacts in place. Constitution amendments follow semantic versioning—major for removed or redefined principles, minor for additions, patch for clarifications—creating an auditable trail of architectural decisions.
#### Articles VII & VIII: Simplicity and Anti-Abstraction