HookBus is the platform. CRE is subscriber #1. The bus has no opinion on what subscribers do. Build anything that reacts to AI agent lifecycle events. Memory, cost, learning, alerts, governance, compliance. Any service that can read JSON over a Unix socket, HTTP endpoint, or Python class can be a HookBus subscriber.
These are the patterns design partners and early integrators have shipped. Every one is a few hundred lines of Python or Go, plugged into the bus, no SDK lock-in.
Record what every agent did across sessions. Build persistent memory from real tool call history. Replay, search, derive context.
Track cost per agent, per user, per team. Set budgets. Alert when thresholds hit. Real-time dashboards. Stop runaway spend before it bills.
Capture every tool call and outcome. Generate training data for fine-tuning your models from real agent behaviour. Self-improving agents.
Agent behaving differently than usual? Detect pattern shifts, unusual tool sequences, alert before damage. Behavioural baselines per agent.
PCI, SOX, HIPAA rules as sync subscribers. Block actions that violate industry-specific regulations. Audit trail per regulation.
Slack, Teams, PagerDuty, email. Notify the right people when agents are blocked or behave unexpectedly. Routing rules per team.
HookBus subscribers are services that read a lifecycle event from stdin (or a socket) and write a decision back. There is no SDK. There is no framework lock-in. There is one envelope.
Sync subscribers block execution until they decide. Return allow, deny, or ask. Deny wins if any subscriber denies.
Async subscribers observe events without blocking. Use them for memory, audit logs, cost tracking, alerts, and SIEM forwards.
Transport options: Unix socket, HTTP endpoint, or in-process Python class. Hot-reloadable config. Health checks per subscriber.
HookBus is closed source for now while the patent is pending, but we work directly with design partners to build subscribers against the bus. If you have a use case, email sales@agenticthinking.uk.