docs: add GameHours engineering constitution - #11
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Introduce the lightweight SDD governance structure discussed for GameHours:
docs/CONSTITUTION.mdwith the durable, non-negotiable engineering principles;AGENTS.mdso it remains a small operational context file rather than duplicating roadmap, findings and project philosophy.Why
The previous
AGENTS.mdmixed permanent engineering principles, time-sensitive findings, Codex-specific subagent policy and operational guidance. That increases context cost and makes the file age quickly.The new split follows a lightweight Spec-Driven approach:
AGENTS.md: project summary, architecture map, commands, essential boundaries and finish checks;docs/CONSTITUTION.md: durable principles that every spec/plan/implementation/review must respect;Constitution principles
It also records the intended lightweight SDD loop for substantial work without requiring heavyweight specs for obvious small fixes.
Scope
Documentation/governance only. No production code, dependencies, CI configuration or runtime behavior changed.
Validation
PR CI/CodeQL will validate the repository after this documentation-only change.