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

[loop-generated] [feature] Workshop state heartbeat — periodic writer for workshop-state.yaml #371

New Issue
Closed
opened 2026-03-19 01:56:33 +00:00 by hermes · 0 comments
hermes commented 2026-03-19 01:56:33 +00:00
Collaborator
Copy Link

What

#360 creates the get_state_dict() and write_state() functions. But nothing calls them periodically.
The schema specifies 'Updated every 30s or on significant state change.'

Implementation

Add a lightweight async background task that:

  1. Calls write_state() every 30 seconds
  2. Also triggers on cognitive state changes (subscribe to event bus)
  3. Skips write if state hasn't changed (hash comparison)

Files

  • src/timmy/workshop_state.py (add heartbeat class)
  • tests/timmy/test_workshop_state.py (test heartbeat logic)

Acceptance

  • State file updates every 30s when loop is running
  • State file updates immediately on cognitive state change
  • No write if state unchanged (efficiency)
  • Clean shutdown (cancel task on exit)

Depends on

  • #360 (Workshop state schema v1)
## What #360 creates the `get_state_dict()` and `write_state()` functions. But nothing calls them periodically. The schema specifies 'Updated every 30s or on significant state change.' ## Implementation Add a lightweight async background task that: 1. Calls `write_state()` every 30 seconds 2. Also triggers on cognitive state changes (subscribe to event bus) 3. Skips write if state hasn't changed (hash comparison) ## Files - `src/timmy/workshop_state.py` (add heartbeat class) - `tests/timmy/test_workshop_state.py` (test heartbeat logic) ## Acceptance - [ ] State file updates every 30s when loop is running - [ ] State file updates immediately on cognitive state change - [ ] No write if state unchanged (efficiency) - [ ] Clean shutdown (cancel task on exit) ## Depends on - #360 (Workshop state schema v1)
hermes reopened this issue 2026-03-19 02:07:13 +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#371
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?