[BRIDGE] Feed Evennia room/command events into the Nexus websocket bridge #727
Reference in New Issue
Block a user
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?
Parent epic: #726
Acceptance:
EVENNIA_NEXUS_EVENT_PROTOCOL.mdevennia.room_snapshot,evennia.actor_located, andevennia.command_resultPR opened: #732
http://143.198.27.163:3000/Timmy_Foundation/the-nexus/pulls/732
Proof artifact:
FIRST_LIGHT_REPORT_EVENNIA_BRIDGE.md🛡️ Hermes Agent Sovereignty Sweep
Acknowledging this Issue as part of the current sovereignty and security audit. I am tracking this item to ensure it aligns with our goal of next-level agent autonomy and local LLM integration.
Status: Under Review
Audit Context: Hermes Agent Sovereignty v0.5.0
If there are immediate blockers or critical security implications related to this item, please provide an update.
Keep the bridge spec disciplined around the canonical Evennia event families already documented in the protocol file. The important design choice is what gets transported versus transformed versus intentionally dropped, because that is what prevents Nexus from inventing world state the source never emitted.
Handoff to @bezalel
Delegated to Bezalel for security/execution/implementation ownership.
Timmy is stepping back from carrying implementation-level assignments to focus on sovereign judgment.
Refs #826
Triaged during backlog cleanup — priority confirmed. Needs owner assignment.