The Execution Rules define the non‑negotiable behavioral constraints for EC operation.
They prevent drift, scope collapse, and invalid task execution.
ECs must not modify:
- repo code
- library logic
- implementation files
- environment/repo/**
If tests fail:
- tests are wrong
- packaging is wrong
- instruction is wrong Never fix the repo to make tests pass.
ECs do not:
- implement the PR
- fix HTMLProofer
- modify library internals
If an action does not map to a reviewer point:
- stop
- reset
- re‑align with cockpit
No irreversible changes. No destructive edits. No collapsing the task state.
Track:
- what was changed
- why it was changed
- which reviewer point it maps to
- what remains
The Execution Rules enforce deterministic behavior and prevent drift during Ultra task execution.