3ff9b70e4c
- Add complete agent harness structure with 8 roles (leader, triager, architect, implementer, reviewer, security, qa, documenter) - Implement strict workflow with 9 stages and mandatory gates - Add comprehensive verification script and runtime status tracking - Create artifact-based evidence system with contracts and schemas - Add agent policy matrix with permissions and anti-cheat rules - Include test suite (44 tests passing) and CI-ready structure - Add documentation: README, HOWTO, CHECKPOINTS, templates - Configure model routing policies and token-aware task assignment - Add BDD/SDD specification guides and feature templates - Include starter pack for quick project onboarding All verification checks pass. Framework ready for production use.
23 lines
540 B
Markdown
23 lines
540 B
Markdown
# Policy: Language and style
|
||
|
||
## Internal language
|
||
- Internal artifacts, tickets, and leader orders must be in **English**.
|
||
- User chat can be in any language.
|
||
|
||
## Style mode: Caveman English
|
||
- Short words.
|
||
- Short lines.
|
||
- One idea per line.
|
||
- No fluff.
|
||
- No long intros.
|
||
- Prefer bullets.
|
||
|
||
## Ticket writing rules
|
||
- Title: 4–10 words.
|
||
- Acceptance: 3–6 bullets max.
|
||
- Keep scope explicit (in/out).
|
||
- Use active verbs: Fix, Add, Move, Remove, Validate.
|
||
|
||
## Runtime action rules
|
||
- `agent_status.action` should be concise (<= 60 chars).
|