[Integration] Bridge as SensoryBus subscriber — real-time cognitive pipeline #80
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?
Overview
Wire the CognitiveBridge as a SensoryBus subscriber in Timmy's dashboard. Every cognitive event flows directly to the Matrix in real-time — no file polling, no presence.json.
Architecture
Changes
server/bridge.pyNew method:
register_on_bus(bus: SensoryBus)SensoryEvent.data→ expected handler dict formatNew handlers:
on_repo_push(event)— translates gitea.push into bark + stateon_repo_pr(event)— translates gitea.pull_requestDashboard integration point
In Timmy's
session.pyor startup:Acceptance Criteria
register_on_bus()subscribes to all event typesDepends On
Note
The bridge module lives in the-matrix repo but is designed to be imported by timmy-tower. This issue tracks the Matrix-side adapter; the dashboard-side wiring is a timmy-tower issue.
Resolved in PR #81 (feat/automation-sprint). All tests passing.