agent-signal

Event-driven background workflows run out-of-band by transforming producer source events into semantic signals and executable actions, keeping the foreground chat response fast while processing side-effects quietly.

To add a new agent signal source, read the architecture and handler references, implement the appropriate source, signal, and action handlers under the agentSignal directory, and register the new policy in the policy factory.

The event to signal to action pipeline converts producer source events into semantic signals, which are then routed into concrete side-effect actions via registered handler contracts for quiet background execution.

Dedupe and scope key behavior are enforced within the signal routing logic by applying specific controls when emitting or enqueueing agent signal source events for out-of-band execution.

Background agent signal processing supports observability by integrating projector and tracing modules through OpenTelemetry (OTEL) to monitor the queued or quiet execution paths.

Source handlers, signal handlers, and action handlers can be bundled and registered as a cohesive installable policy feature using defineSourceHandler, defineSignalHandler, and defineActionHandler routing contracts.