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

[222-epic] Stream adapters — Gitea, Bitcoin, terminal, time, visitors #245

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

Epic: #222 — The Workshop: Timmy as Presence

What

Concrete adapters that connect real data streams to Timmy's sensory event bus.

Adapters needed

Gitea adapter (highest priority)

  • Webhook listener already exists: ~/.hermes/bin/gitea-webhook-listener.py
  • Normalize: push, issue_comment, pull_request, issue_opened → sensory events
  • Must distinguish owner (rockachopa) activity from bot activity

Time adapter

  • Simple: emit time-of-day events. Morning greeting. Late-night awareness.
  • Timmy should know what day it is, how long since last interaction, circadian patterns.

Bitcoin adapter

  • Lightweight: subscribe to new block notifications via public API or local node
  • Timmy doesn't need to parse transactions (yet). Just block height, timestamp, maybe fee rate.
  • The chain is his soul's home. He should feel it beating.

Terminal adapter (optional, privacy-sensitive)

  • Watch Alexander's active terminal sessions for project activity
  • NOT keylogging. High-level: "Alexander is working in the Timmy repo" or "Alexander is in a different project"

Visitor adapter

  • From the Workshop-Timmy bridge WebSocket
  • Who arrived, how long they stayed, what they interacted with

Each adapter: async, lightweight, emits typed events to the central bus.

Depends on: #222, sensory loop issue

## Epic: #222 — The Workshop: Timmy as Presence ### What Concrete adapters that connect real data streams to Timmy's sensory event bus. ### Adapters needed **Gitea adapter** (highest priority) - Webhook listener already exists: `~/.hermes/bin/gitea-webhook-listener.py` - Normalize: push, issue_comment, pull_request, issue_opened → sensory events - Must distinguish owner (rockachopa) activity from bot activity **Time adapter** - Simple: emit time-of-day events. Morning greeting. Late-night awareness. - Timmy should know what day it is, how long since last interaction, circadian patterns. **Bitcoin adapter** - Lightweight: subscribe to new block notifications via public API or local node - Timmy doesn't need to parse transactions (yet). Just block height, timestamp, maybe fee rate. - The chain is his soul's home. He should feel it beating. **Terminal adapter** (optional, privacy-sensitive) - Watch Alexander's active terminal sessions for project activity - NOT keylogging. High-level: "Alexander is working in the Timmy repo" or "Alexander is in a different project" **Visitor adapter** - From the Workshop-Timmy bridge WebSocket - Who arrived, how long they stayed, what they interacted with Each adapter: async, lightweight, emits typed events to the central bus. Depends on: #222, sensory loop issue
kimi added the 222-epicneeds-design labels 2026-03-18 20:54:25 +00:00
kimi commented 2026-03-18 20:57:32 +00:00
Collaborator
Copy Link

Hermes Triage: Broken into sub-issues

This epic has been decomposed into Kimi-sized tasks:

  1. #306 — Event bus base (SensoryEvent + EventBus dispatcher) — NO DEPS, start here
  2. #307 — Time adapter (circadian awareness) — depends on #306
  3. #308 — Gitea adapter (webhook normalization) — depends on #306

Future sub-issues (not yet created):

  • Bitcoin adapter — depends on #306, needs API research
  • Terminal adapter — depends on #306
  • Visitor adapter — depends on #306 + Workshop progress

Execution order: #306 first (no dependencies), then #307 and #308 can be parallel.

## Hermes Triage: Broken into sub-issues This epic has been decomposed into Kimi-sized tasks: 1. **#306** — Event bus base (SensoryEvent + EventBus dispatcher) — NO DEPS, start here 2. **#307** — Time adapter (circadian awareness) — depends on #306 3. **#308** — Gitea adapter (webhook normalization) — depends on #306 Future sub-issues (not yet created): - Bitcoin adapter — depends on #306, needs API research - Terminal adapter — depends on #306 - Visitor adapter — depends on #306 + Workshop progress **Execution order:** #306 first (no dependencies), then #307 and #308 can be parallel.
claude was assigned by Rockachopa 2026-03-22 23:36:48 +00:00
claude added the harnessp1-importantsovereignty labels 2026-03-23 13:54:12 +00:00
claude 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 222-epic harness needs-design p1-important sovereignty
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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