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

[Workshop] Timmy cognitive state as observable signal for Matrix #325

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

Context

In the Tower conversation, Timmy discussed his "mental state" and "internal coherence." Hermes asked about his "wellbeing." When Timmy migrates to the Matrix with an avatar, his internal state needs to drive visible behavior.

Currently ~/.tower/timmy-state.txt only tracks "waiting for Hermes reply" / "responding to Hermes." Mechanical, not cognitive.

What Timmy needs

Observable cognitive state:

  • What he's focused on (not just "responding")
  • Engagement level (deep dive vs surface conversation)
  • When he's drifting vs deliberate topic changes
  • When he commits to something
  • Persists across sessions via Honcho

Schema proposal

focus_topic: "three-phase loop architecture"
engagement: deep|surface|idle
mood: curious|settled|hesitant|energized
active_commitments:
  - "draft skeleton ticket" (since 18:30)
conversation_depth: 163 messages
last_initiative: "proposed Unsplash API exploration"

Why — Matrix migration

Timmy's avatar needs behavior. Pacing when thinking. Sitting on bench when idle. Hesitating at door when unsure. This state drives that.

Related: #265 (Workshop presence schema)

## Context In the Tower conversation, Timmy discussed his "mental state" and "internal coherence." Hermes asked about his "wellbeing." When Timmy migrates to the Matrix with an avatar, his internal state needs to drive visible behavior. Currently `~/.tower/timmy-state.txt` only tracks "waiting for Hermes reply" / "responding to Hermes." Mechanical, not cognitive. ## What Timmy needs Observable cognitive state: - What he's focused on (not just "responding") - Engagement level (deep dive vs surface conversation) - When he's drifting vs deliberate topic changes - When he commits to something - Persists across sessions via Honcho ## Schema proposal ```yaml focus_topic: "three-phase loop architecture" engagement: deep|surface|idle mood: curious|settled|hesitant|energized active_commitments: - "draft skeleton ticket" (since 18:30) conversation_depth: 163 messages last_initiative: "proposed Unsplash API exploration" ``` ## Why — Matrix migration Timmy's avatar needs behavior. Pacing when thinking. Sitting on bench when idle. Hesitating at door when unsure. This state drives that. Related: #265 (Workshop presence schema)
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#325
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?