24 lines
1.1 KiB
Markdown
24 lines
1.1 KiB
Markdown
|
# Implementation: Framework Self-Enforcement
|
||
|
|
|
||
|
|
## Summary
|
||
|
|
|
||
|
|
Added rules and instructions so the framework applies its own task-driven development principles to itself.
|
||
|
|
|
||
|
|
## Changes Made
|
||
|
|
|
||
|
|
### `.rules.md`
|
||
|
|
Replaced the template placeholder with concrete, enforceable rules:
|
||
|
|
|
||
|
|
- **Task-Driven Development**: All changes must go through tasks (SPEC → phases → VERDICT), no direct file edits, no manual `mkdir tasks/`
|
||
|
|
- **VRAM-Aware Task Sizing**: Check `config.md` VRAM limits before scoping tasks, verify fit within max peak context
|
||
|
|
- **Changelog**: Append entry to CHANGELOG.md when a task reaches Resolution
|
||
|
|
- **Self-Improvement**: One rule per observed failure mode with concrete example, consolidate monthly
|
||
|
|
- **Session Discipline**: After writing SPEC.md, stop and wait for user approval before implementing
|
||
|
|
|
||
|
|
### `system-prompt.md`
|
||
|
|
Added step 4: "Read ~/.automaton/.rules.md (global framework rules)" to the startup sequence.
|
||
|
|
|
||
|
|
## Files Modified
|
||
|
|
- `.rules.md` — converted from template to concrete rules (25 lines)
|
||
|
|
- `system-prompt.md` — added global rules reading instruction
|