WS event integration — archon_entering, archon_materialized, archon_departed #533

New Issue

perplexity · 2026-03-25T17:50:31Z

perplexity commented

2026-03-25 17:50:31 +00:00

Parent: #527

Depends on: #529 (manifest schema), #530 (Three.js assembler)

What

Add 3 new WebSocket event types to the existing WS gateway (port 8765) that trigger the avatar assembler.

Events

{"type": "archon_entering", "agent_id": "claude-opus-4", "manifest": {...}}
{"type": "archon_materialized", "agent_id": "claude-opus-4", "position": [0, 0, 5]}
{"type": "archon_departed", "agent_id": "claude-opus-4"}

Client-side handling

archon_entering → create ArchonAssembler, start spawn animation
archon_materialized → archon is interactive, can be clicked/inspected
archon_departed → play de-materialization, remove from scene

Acceptance Criteria

WS clients receive all 3 event types
Entering → Three.js assembler builds correct body from manifest
Departed → avatar removed cleanly (no memory leaks, no orphan meshes)
Multiple archons can coexist in the scene

Parent: #527 Depends on: #529 (manifest schema), #530 (Three.js assembler) ## What Add 3 new WebSocket event types to the existing WS gateway (port 8765) that trigger the avatar assembler. ## Events ```json {"type": "archon_entering", "agent_id": "claude-opus-4", "manifest": {...}} {"type": "archon_materialized", "agent_id": "claude-opus-4", "position": [0, 0, 5]} {"type": "archon_departed", "agent_id": "claude-opus-4"} ``` ## Client-side handling - `archon_entering` → create ArchonAssembler, start spawn animation - `archon_materialized` → archon is interactive, can be clicked/inspected - `archon_departed` → play de-materialization, remove from scene ## Acceptance Criteria - WS clients receive all 3 event types - Entering → Three.js assembler builds correct body from manifest - Departed → avatar removed cleanly (no memory leaks, no orphan meshes) - Multiple archons can coexist in the scene

Timmy was assigned by perplexity

2026-03-25 17:50:31 +00:00

Timmy referenced this issue

2026-03-25 20:24:28 +00:00

[architecture] Route Nexus perception loop through Hermes harness for training data capture #540

perplexity commented

2026-03-25 23:30:26 +00:00

Closed per direction shift (#542). Reason: WS archon events — for 3D avatar system being deleted.

The Nexus has three jobs: Heartbeat, Harness, Portal Interface. This issue doesn't serve any of them.

Closed per direction shift (#542). Reason: WS archon events — for 3D avatar system being deleted. The Nexus has three jobs: Heartbeat, Harness, Portal Interface. This issue doesn't serve any of them.

perplexity added the deprioritized label 2026-03-25 23:30:27 +00:00

perplexity closed this issue

2026-03-25 23:30:28 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#533