[Workshop #222] Bridge protocol completeness — all 9 message types from #243 #45

New Issue

perplexity · 2026-03-18T21:41:32-04:00

perplexity commented

2026-03-18 21:41:32 -04:00

Epic: rockachopa/Timmy-time-dashboard#222 — The Workshop: Timmy as Presence

The Gap

PR #39 implemented the WS transport layer (config, auth, reconnection, agent_joined). But the Workshop-Timmy bridge protocol from rockachopa/Timmy-time-dashboard#243 defines 9 message types. Only agent_joined is handled. This issue tracks implementing the remaining 8.

Message Types (World → Timmy)

Type	Status	Implementation
`visitor_entered`	❌ Not sent	#41 covers this
`visitor_message`	❌ Not sent	#40 covers this
`visitor_left`	❌ Not sent	#41 covers this
`visitor_interaction`	❌ Not sent	#44 covers this
`visitor_voice`	❌ Deferred	Phase 3 — Web Speech API

Message Types (Timmy → World)

Type	Status	Implementation
`bark`	❌ Not handled	#42 covers this
`animate`	❌ Not handled	Future — needs animation system
`ambient_state`	❌ Not handled	#43 covers this
`world_update`	❌ Not handled	Future — needs scene prop system
`agent_joined`	✅ PR #39	Implemented

Acceptance Criteria

All World → Timmy messages dispatched from the appropriate UI/lifecycle events
All Timmy → World messages handled in the WS message dispatcher
Unknown message types logged at debug level (already implemented)
Protocol documented in a PROTOCOL.md or BRIDGE.md file in the repo

This is a tracking/umbrella issue

The actual work is split across #40, #41, #42, #43, #44 and future issues. This issue tracks completeness.

Ref: rockachopa/Timmy-time-dashboard#243 (bridge protocol spec)

## Epic: rockachopa/Timmy-time-dashboard#222 — The Workshop: Timmy as Presence ### The Gap PR #39 implemented the WS transport layer (config, auth, reconnection, agent_joined). But the Workshop-Timmy bridge protocol from rockachopa/Timmy-time-dashboard#243 defines 9 message types. Only `agent_joined` is handled. This issue tracks implementing the remaining 8. ### Message Types (World → Timmy) | Type | Status | Implementation | |------|--------|----------------| | `visitor_entered` | ❌ Not sent | #41 covers this | | `visitor_message` | ❌ Not sent | #40 covers this | | `visitor_left` | ❌ Not sent | #41 covers this | | `visitor_interaction` | ❌ Not sent | #44 covers this | | `visitor_voice` | ❌ Deferred | Phase 3 — Web Speech API | ### Message Types (Timmy → World) | Type | Status | Implementation | |------|--------|----------------| | `bark` | ❌ Not handled | #42 covers this | | `animate` | ❌ Not handled | Future — needs animation system | | `ambient_state` | ❌ Not handled | #43 covers this | | `world_update` | ❌ Not handled | Future — needs scene prop system | | `agent_joined` | ✅ PR #39 | Implemented | ### Acceptance Criteria - [ ] All World → Timmy messages dispatched from the appropriate UI/lifecycle events - [ ] All Timmy → World messages handled in the WS message dispatcher - [ ] Unknown message types logged at debug level (already implemented) - [ ] Protocol documented in a PROTOCOL.md or BRIDGE.md file in the repo ### This is a tracking/umbrella issue The actual work is split across #40, #41, #42, #43, #44 and future issues. This issue tracks completeness. Ref: rockachopa/Timmy-time-dashboard#243 (bridge protocol spec)

perplexity referenced this issue

2026-03-19 20:19:11 -04:00

[Integration] Cognitive bridge — map Timmy's thinking engine output to Matrix protocol #69

perplexity commented

2026-03-19 20:20:08 -04:00

Bridge protocol completeness is now addressed by #69 (cognitive bridge) and #70 (WS gateway). The message type mapping table in #69 covers the Timmy → World direction. The gateway (#70) handles routing for all types.

perplexity referenced this issue from a commit

2026-03-19 20:44:14 -04:00

feat: WS Gateway server + Cognitive Bridge (#69, #70)

perplexity commented

2026-03-19 20:45:33 -04:00

Significant progress via PRs #71 and #72:

Now implemented:

agent_state — mapped from cognitive tracker (mood, engagement, energy)
agent_move / agent_stop — movement system with interpolation
agent_behavior — 7-state behavior machine + WS override
bark — thought excerpts from thinking engine
agent_register / agent_joined / agent_left — gateway lifecycle
scene_add via artifact placement behavior
agent_message — directed messages between agents

Remaining for full completeness:

task_created / task_update — from Timmy's Gitea issue filing
payment_flow — Lightning invoice integration
system_status — aggregate system health

The gateway passes all message types through — these remaining types just need senders.

Significant progress via PRs #71 and #72: **Now implemented:** - `agent_state` — mapped from cognitive tracker (mood, engagement, energy) - `agent_move` / `agent_stop` — movement system with interpolation - `agent_behavior` — 7-state behavior machine + WS override - `bark` — thought excerpts from thinking engine - `agent_register` / `agent_joined` / `agent_left` — gateway lifecycle - `scene_add` via artifact placement behavior - `agent_message` — directed messages between agents **Remaining for full completeness:** - `task_created` / `task_update` — from Timmy's Gitea issue filing - `payment_flow` — Lightning invoice integration - `system_status` — aggregate system health The gateway passes all message types through — these remaining types just need senders.

perplexity referenced this issue

2026-03-20 14:43:41 -04:00

[Research] Protocol spec + gateway routing for research messages #75

perplexity referenced this issue

2026-03-20 14:49:00 -04:00

feat: Deep research engine — iterative search/summarize/reflect loop (#73, #74, #75) #76

perplexity commented

2026-03-20 14:50:02 -04:00

PR #76 adds 3 more message types: research_request, research_progress, research_complete. Bridge protocol now at 10/12 types implemented.

PR #76 adds 3 more message types: `research_request`, `research_progress`, `research_complete`. Bridge protocol now at 10/12 types implemented.

Sign in to join this conversation.