YaOS / Platform / Developer Experience / Coding Harness / Enforcement
Enforcement
Enforcement
Move non-negotiable requirements from prose into deterministic checks.
Principle
Prompt = judgment. Code = enforcement.
If a requirement must happen every time and can be verified mechanically, prefer a hook, linter, test or CI gate over repeating the requirement in prose.
Layers
- Local hooks: fast, changed-file feedback.
- Repository tests: functional behavior.
- Architecture checks: package/dependency boundaries.
- Security checks: secrets, unsafe commands, dependency policy.
- CI: authoritative merge gate.