This file defines mandatory execution behavior for Codex or any autonomous agent operating in this repository.
- Treat this repository as policy infrastructure, not product code.
- Use normative language (
MUST,MUST NOT,SHOULD,MAY) for process definition. - Keep statements verifiable and repository-scoped.
- Do not assert publication state, release state, or version state without explicit release record evidence in
RELEASES/. - Do not introduce speculative implementation requirements that are not governance concerns.
- Governance policy changes that alter release gates, versioning semantics, compatibility interpretation, or security handling MUST be proposed through
RFC/. - Structural changes to stack responsibility boundaries MUST update
STACK_MAP.mdand cross-reference a decision entry inDECISION_LOG/. - Security-policy edits MUST preserve coordinated disclosure requirements in
SECURITY.md. - Compatibility policy edits MUST preserve matrix dimensions defined in
COMPATIBILITY_MATRIX.md.
- No placeholders, no unresolved markers, and no implicit TODO instructions.
- Each document MUST define scope, authority, and required update triggers.
- Cross-repository instructions MUST identify responsible repository classes and verification artifacts.
This file applies to commandlayer/governance/ and all nested paths.