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

[OPS] Coordinator-first intake, triage, verification, and report protocol #156

New Issue
Closed
opened 2026-04-04 21:09:21 +00:00 by Timmy · 0 comments
Timmy commented 2026-04-04 21:09:21 +00:00
Owner
Copy Link

Parent: #154

What

Translate Frankie’s strongest operating loop into Timmy terms: intake → triage → route → track → verify → report. The value is not the words; the value is making queue mutation and escalation boundaries explicit.

Tasks

  • Write coordinator doctrine for what Timmy/Allegro may do automatically
  • Define urgency classes and escalation rules
  • Require artifact verification before COMPLETE
  • Define what Alexander should see versus what stays internal
  • Tie the protocol to Gitea issues/comments instead of invisible local-only state

Acceptance Criteria

  • A repo-visible doctrine doc exists for the coordinator loop
  • Verification-before-close is explicitly required
  • Principal visibility ladder is documented
  • The protocol names the authority boundaries for automatic assignment, review, and escalation
## Parent: #154 ## What Translate Frankie’s strongest operating loop into Timmy terms: intake → triage → route → track → verify → report. The value is not the words; the value is making queue mutation and escalation boundaries explicit. ## Tasks - [ ] Write coordinator doctrine for what Timmy/Allegro may do automatically - [ ] Define urgency classes and escalation rules - [ ] Require artifact verification before COMPLETE - [ ] Define what Alexander should see versus what stays internal - [ ] Tie the protocol to Gitea issues/comments instead of invisible local-only state ## Acceptance Criteria - [ ] A repo-visible doctrine doc exists for the coordinator loop - [ ] Verification-before-close is explicitly required - [ ] Principal visibility ladder is documented - [ ] The protocol names the authority boundaries for automatic assignment, review, and escalation
Timmy self-assigned this 2026-04-04 21:14:28 +00:00
Timmy closed this issue 2026-04-04 21:38:50 +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 Timmy
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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