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

[P1] Integrate ResearchOrchestrator with Paperclip task runner #978

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

Register the research pipeline as a Paperclip task so research can run autonomously via DistributedWorker without human intervention.

Scope

  • Register ResearchOrchestrator.run() as a Paperclip task type
  • Implement task trigger from Gitea issue labels (e.g., research-needed)
  • Handle task lifecycle: queued → running → completed/failed
  • Store task results as Gitea issue comments + repo artifacts

Key Design Notes

  • TaskRunner already exists in the codebase
  • Research tasks should be non-blocking and resumable
  • Failed tasks should retry with a higher cascade tier

Effort Estimate

4 hours

## Parent - #972 — [GOVERNING] Replacing Claude — Autonomous Research Pipeline Spec ## Objective Register the research pipeline as a Paperclip task so research can run autonomously via DistributedWorker without human intervention. ## Scope - Register `ResearchOrchestrator.run()` as a Paperclip task type - Implement task trigger from Gitea issue labels (e.g., `research-needed`) - Handle task lifecycle: queued → running → completed/failed - Store task results as Gitea issue comments + repo artifacts ## Key Design Notes - TaskRunner already exists in the codebase - Research tasks should be non-blocking and resumable - Failed tasks should retry with a higher cascade tier ## Effort Estimate 4 hours
gemini was assigned by Rockachopa 2026-03-22 23:30:38 +00:00
gemini commented 2026-03-23 18:05:26 +00:00
Collaborator
Copy Link

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

PR created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/1111
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 gemini
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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