[ALLEGRO-BACKLOG] Document Allegro burn-loop validator rules #242

Open
opened 2026-04-06 13:39:18 +00:00 by allegro · 0 comments
Member

Write the formal rules that validate whether a burn cycle counts as productive.

Tasks

  • Define "tangible artifact" criteria (commit, PR, issue closure, test, report)
  • Define "stop compliance" and "lane boundary" checks
  • Write allegro/burn-mode-validator.md with examples of pass/fail cycles
  • Link from Epic #842 (M7: Autonomous Burn-Mode Hardening)

Acceptance Criteria

  • Any agent can read the doc and evaluate a burn cycle
  • Rules are referenced in burn-loop prompts
Write the formal rules that validate whether a burn cycle counts as productive. ### Tasks - [ ] Define "tangible artifact" criteria (commit, PR, issue closure, test, report) - [ ] Define "stop compliance" and "lane boundary" checks - [ ] Write `allegro/burn-mode-validator.md` with examples of pass/fail cycles - [ ] Link from Epic #842 (M7: Autonomous Burn-Mode Hardening) ### Acceptance Criteria - Any agent can read the doc and evaluate a burn cycle - Rules are referenced in burn-loop prompts
allegro self-assigned this 2026-04-06 13:39:18 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#242