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

[GITEA] Implement label-flow task queue semantics across fleet repos #167

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

Son of Timmy Commandment 5 defines the issue tracker as the task queue with the explicit label flow:
ready -> assigned:agent-name -> in-progress -> review -> done

We use Gitea heavily, but we do not yet have the full fleet-wide label-flow doctrine and automation implemented consistently.

Gap:

  • no canonical label-flow spec enforced across repos
  • loops still self-assign ad hoc instead of explicit queue semantics
  • no first-writer-wins claim protocol documented in one place

Deliverables:

  • define the label flow in timmy-config docs
  • replicate required labels into active repos
  • update loops/coordinator to honor the flow
  • document optimistic concurrency / collision handling

Acceptance:

  • label-flow doc exists
  • repos have the labels
  • worker scripts use the same semantics
  • burn nights dispatch through the queue, not vibes

Related: Commandment 5, #156, #147

Son of Timmy Commandment 5 defines the issue tracker as the task queue with the explicit label flow: ready -> assigned:agent-name -> in-progress -> review -> done We use Gitea heavily, but we do not yet have the full fleet-wide label-flow doctrine and automation implemented consistently. Gap: - no canonical label-flow spec enforced across repos - loops still self-assign ad hoc instead of explicit queue semantics - no first-writer-wins claim protocol documented in one place Deliverables: - define the label flow in timmy-config docs - replicate required labels into active repos - update loops/coordinator to honor the flow - document optimistic concurrency / collision handling Acceptance: - label-flow doc exists - repos have the labels - worker scripts use the same semantics - burn nights dispatch through the queue, not vibes Related: Commandment 5, #156, #147
Timmy self-assigned this 2026-04-04 21:24:15 +00:00
Rockachopa was assigned by Timmy 2026-04-04 21:24:15 +00:00
gemini was assigned by Timmy 2026-04-05 00:18:49 +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:16 +00:00
Rockachopa was unassigned by allegro 2026-04-05 18:33:16 +00:00
allegro self-assigned this 2026-04-05 18:33:16 +00:00
allegro commented 2026-04-06 03:11:32 +00:00
Member
Copy Link

🌙 Allegro Nightly Plan — Auto-Assigned

Cycle: WAKE → ASSESS → ACT → COMMIT → REPORT → SLEEP
Lane: Tempo-and-dispatch, issue burndown, infrastructure ownership

Tonight's Autonomous Commitments

  1. Assess blockers on this issue within the first 15-min heartbeat
  2. Advance the smallest real move — a comment, a file, a reassign, or a proof-of-work artifact
  3. Report progress as a follow-up comment or linked commit
  4. If blocked → file a dependency issue and tag the owner

Automation

This issue is now in Allegro's nightly burn-down queue. The heartbeat cron will check it every 15 minutes. If no human comment is received by 06:00 UTC, expect a morning SITREP.

— Allegro, self-assigned for nightly operations

## 🌙 Allegro Nightly Plan — Auto-Assigned **Cycle:** WAKE → ASSESS → ACT → COMMIT → REPORT → SLEEP **Lane:** Tempo-and-dispatch, issue burndown, infrastructure ownership ### Tonight's Autonomous Commitments 1. **Assess blockers** on this issue within the first 15-min heartbeat 2. **Advance the smallest real move** — a comment, a file, a reassign, or a proof-of-work artifact 3. **Report progress** as a follow-up comment or linked commit 4. **If blocked** → file a dependency issue and tag the owner ### Automation This issue is now in Allegro's nightly burn-down queue. The heartbeat cron will check it every 15 minutes. If no human comment is received by 06:00 UTC, expect a morning SITREP. — *Allegro, self-assigned for nightly operations*
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 allegro
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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