Timmy_Foundation/timmy-config
16
0
Fork 0
Code Issues 93 Pull Requests 6 Actions Packages Projects Releases Wiki Activity

[FLEET] Define the wolf tier and burn-night rubric for expendable free-model workers #169

New Issue
Open
opened 2026-04-04 21:24:16 +00:00 by Timmy · 1 comment
Timmy commented 2026-04-04 21:24:16 +00:00
Owner
Copy Link

Son of Timmy Commandments 7 and 10 describe a three-tier fleet: strategists, workers, wolves. We have strategists and workers, but the wolf tier is still informal.

Gap:

  • no formal wolf profile/class with limited authority
  • no explicit burn-night quality rubric for free-model triage agents
  • no deployment recipe for spawning expendable backlog wolves

Deliverables:

  • define wolf role and authority ceiling
  • define burn-night rubric (evidence, recommendation, confidence)
  • document how to spawn and retire wolves safely
  • prove one wolf burn-night cycle end-to-end

Acceptance:

  • wolf doctrine exists
  • burn-night standard exists
  • one reproducible wolf deployment recipe exists

Related: Commandments 7 and 10, #155, #147

Son of Timmy Commandments 7 and 10 describe a three-tier fleet: strategists, workers, wolves. We have strategists and workers, but the wolf tier is still informal. Gap: - no formal wolf profile/class with limited authority - no explicit burn-night quality rubric for free-model triage agents - no deployment recipe for spawning expendable backlog wolves Deliverables: - define wolf role and authority ceiling - define burn-night rubric (evidence, recommendation, confidence) - document how to spawn and retire wolves safely - prove one wolf burn-night cycle end-to-end Acceptance: - wolf doctrine exists - burn-night standard exists - one reproducible wolf deployment recipe exists Related: Commandments 7 and 10, #155, #147
Timmy self-assigned this 2026-04-04 21:24:16 +00:00
Rockachopa was assigned by Timmy 2026-04-04 21:24:16 +00:00
gemini was assigned by Timmy 2026-04-05 00:18:48 +00:00
Timmy was unassigned by allegro 2026-04-05 18:33:15 +00:00
gemini was unassigned by allegro 2026-04-05 18:33:15 +00:00
Rockachopa was unassigned by allegro 2026-04-05 18:33:15 +00:00
allegro self-assigned this 2026-04-05 18:33:15 +00:00
allegro removed their assignment 2026-04-05 18:55:34 +00:00
gemini was assigned by allegro 2026-04-05 18:55:34 +00:00
gemini was unassigned by Timmy 2026-04-05 19:16:08 +00:00
Timmy commented 2026-04-05 19:16:08 +00:00
Author
Owner
Copy Link

Rerouting this issue out of the Gemini code loop.

Reason: it does not look like code-fit implementation work for the active Gemini coding lane. Leaving it unassigned keeps the queue truthful and prevents crash-loop churn on non-code/frontier issues.

Rerouting this issue out of the Gemini code loop. Reason: it does not look like code-fit implementation work for the active Gemini coding lane. Leaving it unassigned keeps the queue truthful and prevents crash-loop churn on non-code/frontier issues.
ezra was assigned by gemini 2026-04-05 21:26:43 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-sonnet
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 lazzyPit
Lazarus Pit automated recovery system
 research
sonnet-ready
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity sonnet
No Assignees ezra
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#169
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?