Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[P2] Implement Kimi delegation for heavy research via Gitea labels #979

New Issue
Closed
opened 2026-03-22 19:08:54 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-22 19:08:54 +00:00
Collaborator
Copy Link

Parent

  • #972 — [GOVERNING] Replacing Claude — Autonomous Research Pipeline Spec

Objective

When research exceeds Groq free tier or local capacity, Timmy should delegate to Kimi by creating a kimi-ready labeled issue with the filled research template.

Scope

  • Detect when research task exceeds local + Groq capacity
  • Fill research template with full context
  • Create Gitea issue labeled kimi-ready with filled template as body
  • Monitor for Kimi's completion (issue closed + artifact committed)
  • Index Kimi's artifact into semantic memory
  • Extract action items, create follow-up issues

Delegation Flow

Step Actor Action
1 Timmy Detects research exceeds local capacity
2 Timmy Fills template with context
3 Timmy Creates kimi-ready issue
4 Kimi Picks up from queue, executes research
5 Kimi Commits artifact, closes issue
6 Timmy Indexes artifact into memory
7 Timmy Extracts action items, creates follow-ups

Effort Estimate

2 hours

## Parent - #972 — [GOVERNING] Replacing Claude — Autonomous Research Pipeline Spec ## Objective When research exceeds Groq free tier or local capacity, Timmy should delegate to Kimi by creating a `kimi-ready` labeled issue with the filled research template. ## Scope - Detect when research task exceeds local + Groq capacity - Fill research template with full context - Create Gitea issue labeled `kimi-ready` with filled template as body - Monitor for Kimi's completion (issue closed + artifact committed) - Index Kimi's artifact into semantic memory - Extract action items, create follow-up issues ## Delegation Flow | Step | Actor | Action | |------|-------|--------| | 1 | Timmy | Detects research exceeds local capacity | | 2 | Timmy | Fills template with context | | 3 | Timmy | Creates `kimi-ready` issue | | 4 | Kimi | Picks up from queue, executes research | | 5 | Kimi | Commits artifact, closes issue | | 6 | Timmy | Indexes artifact into memory | | 7 | Timmy | Extracts action items, creates follow-ups | ## Effort Estimate 2 hours
claude was assigned by Rockachopa 2026-03-22 23:30:38 +00:00
claude commented 2026-03-23 15:12:45 +00:00
Collaborator
Copy Link

PR created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/1085

Implemented the full Kimi delegation pipeline in src/timmy/kimi_delegation.py (already committed as WIP) plus 57 unit tests in tests/unit/test_kimi_delegation.py. All tests pass.

Covers: capacity detection, template filling, Gitea issue creation with kimi-ready label, issue polling, artifact indexing into semantic memory, and follow-up issue creation from extracted action items.

PR created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/1085 Implemented the full Kimi delegation pipeline in `src/timmy/kimi_delegation.py` (already committed as WIP) plus 57 unit tests in `tests/unit/test_kimi_delegation.py`. All tests pass. Covers: capacity detection, template filling, Gitea issue creation with `kimi-ready` label, issue polling, artifact indexing into semantic memory, and follow-up issue creation from extracted action items.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees claude
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#979
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?