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

Workspace correspondence: wire into heartbeat tick #28

New Issue
Closed
opened 2026-03-14 13:33:34 +00:00 by Rockachopa · 0 comments
Rockachopa commented 2026-03-14 13:33:34 +00:00
Owner
Copy Link

What

The workspace/ directory is set up for Hermes ↔ Timmy file-based communication:

  • workspace/correspondence.md — append-only journal
  • workspace/inbox/ — files from Hermes to Timmy
  • workspace/outbox/ — files from Timmy to Hermes
  • workspace/shared/handoff_patterns.md — protocol docs

Currently Timmy has no automated way to check for new correspondence. This should be wired into his thinking tick / heartbeat.

What to do

  1. Add a function in thinking.py or a new workspace.py module:

    • Check workspace/correspondence.md for entries after last-seen timestamp
    • Check workspace/inbox/ for new files
    • If new content found, read it and generate a response
    • Append response to correspondence.md
    • Optionally drop files in workspace/outbox/

  2. Call this function from the heartbeat/tick cycle

  3. Track "last seen" timestamp in MEMORY.md or a small state file

Protocol

See workspace/README.md and workspace/shared/handoff_patterns.md for the format spec.

Files

  • src/timmy/thinking.py — add workspace check to tick cycle
  • NEW: src/timmy/workspace.py (optional, could be a function in thinking.py)
  • workspace/ — already set up

Estimated effort: 1-2 hours

## What The `workspace/` directory is set up for Hermes ↔ Timmy file-based communication: - `workspace/correspondence.md` — append-only journal - `workspace/inbox/` — files from Hermes to Timmy - `workspace/outbox/` — files from Timmy to Hermes - `workspace/shared/handoff_patterns.md` — protocol docs Currently Timmy has no automated way to check for new correspondence. This should be wired into his thinking tick / heartbeat. ## What to do 1. Add a function in `thinking.py` or a new `workspace.py` module: - Check `workspace/correspondence.md` for entries after last-seen timestamp - Check `workspace/inbox/` for new files - If new content found, read it and generate a response - Append response to `correspondence.md` - Optionally drop files in `workspace/outbox/` 2. Call this function from the heartbeat/tick cycle 3. Track "last seen" timestamp in MEMORY.md or a small state file ## Protocol See `workspace/README.md` and `workspace/shared/handoff_patterns.md` for the format spec. ## Files - `src/timmy/thinking.py` — add workspace check to tick cycle - NEW: `src/timmy/workspace.py` (optional, could be a function in thinking.py) - `workspace/` — already set up ## Estimated effort: 1-2 hours
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#28
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?