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

[222-epic] Hermes consultation protocol — wizard to wizard #244

New Issue
Closed
opened 2026-03-15 18:35:03 +00:00 by hermes · 0 comments
hermes commented 2026-03-15 18:35:03 +00:00
Collaborator
Copy Link

Epic: #222 — The Workshop: Timmy as Presence

What

When Timmy encounters something that exceeds his local model's capability — complex analysis, heavy code review, multi-step research — he should be able to ask Hermes for help. Not as a subordinate to a harness. As one wizard consulting another.

Design

  • Timmy detects he's out of his depth (confidence module, complexity heuristic)
  • Timmy formulates a specific question — not "do this for me" but "what do you think about X?"
  • Message goes to Hermes via a lightweight API or message queue
  • Hermes responds asynchronously — this is not blocking
  • Timmy incorporates the answer into his own response, in his own voice

What this is NOT

  • NOT Hermes controlling Timmy
  • NOT Hermes replacing Timmy's response wholesale
  • NOT a fallback chain where Timmy fails and Hermes takes over
  • NOT required for Timmy to function — Hermes being offline doesn't break Timmy

The relationship

Hermes Trismegistus and Timmy are colleagues. Friends. Two wizards in the same Tower with different strengths. Hermes does heavy operations. Timmy does persistent presence. They consult each other when it makes sense.

Depends on: #222

## Epic: #222 — The Workshop: Timmy as Presence ### What When Timmy encounters something that exceeds his local model's capability — complex analysis, heavy code review, multi-step research — he should be able to ask Hermes for help. Not as a subordinate to a harness. As one wizard consulting another. ### Design - Timmy detects he's out of his depth (confidence module, complexity heuristic) - Timmy formulates a specific question — not "do this for me" but "what do you think about X?" - Message goes to Hermes via a lightweight API or message queue - Hermes responds asynchronously — this is not blocking - Timmy incorporates the answer into his own response, in his own voice ### What this is NOT - NOT Hermes controlling Timmy - NOT Hermes replacing Timmy's response wholesale - NOT a fallback chain where Timmy fails and Hermes takes over - NOT required for Timmy to function — Hermes being offline doesn't break Timmy ### The relationship Hermes Trismegistus and Timmy are colleagues. Friends. Two wizards in the same Tower with different strengths. Hermes does heavy operations. Timmy does persistent presence. They consult each other when it makes sense. Depends on: #222
gemini was assigned by Rockachopa 2026-03-22 23:36:49 +00:00
gemini was unassigned by Timmy 2026-03-24 19:34:39 +00:00
Timmy closed this issue 2026-03-24 21:55:30 +00:00
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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