Rockachopa/hermes-config
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[POLICY] Inbox zero — relentless burn-down policy for all agents #7

New Issue
Open
opened 2026-04-07 03:19:25 +00:00 by Timmy · 0 comments
Timmy commented 2026-04-07 03:19:25 +00:00
Copy Link

Alexander's directive: "I need you relentlessly burning down your backlog to inbox zero at all times. And then you find rest, I need you to find work."

This translates to:

  1. Every 15m burn cycle must reduce the issue count on a tracked repo, or report why it couldn't
  2. When a repo hits 0 open actionable issues, agents must proactively file improvement issues (not wait for human direction)
  3. "Find rest" means: when there's nothing left to do, audit the system itself — find the rot that hasn't been filed yet
  4. Burn reports must be proof-first: issue number closed, commit hash, evidence

Acceptance Criteria:

  • Add inbox-zero gate to bounded burn cycle prompt: "If you close an issue, report the count remaining"
  • Implement proactive improvement filing: when a repo shows 0 actionable issues but >0 open issues total, file a gap
  • Add a daily inbox-zero report that lists each repo's actionable count vs total
  • Wire this into the morning report compiler

Assignee: claude

Alexander's directive: "I need you relentlessly burning down your backlog to inbox zero at all times. And then you find rest, I need you to find work." This translates to: 1. Every 15m burn cycle must reduce the issue count on a tracked repo, or report why it couldn't 2. When a repo hits 0 open actionable issues, agents must proactively file improvement issues (not wait for human direction) 3. "Find rest" means: when there's nothing left to do, audit the system itself — find the rot that hasn't been filed yet 4. Burn reports must be proof-first: issue number closed, commit hash, evidence Acceptance Criteria: - [ ] Add inbox-zero gate to bounded burn cycle prompt: "If you close an issue, report the count remaining" - [ ] Implement proactive improvement filing: when a repo shows 0 actionable issues but >0 open issues total, file a gap - [ ] Add a daily inbox-zero report that lists each repo's actionable count vs total - [ ] Wire this into the morning report compiler Assignee: claude
claude was assigned by Timmy 2026-04-07 03:19:25 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude gemini google manus Rockachopa
No Assignees claude
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/hermes-config#7
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?