Signals

Coming soon

The Signals view and its shared run controls aren’t available yet. This page describes the planned behavior. Existing capture and import tools keep their own controls.

A Signal is a configured way information feeds the record. It can receive connector updates, ask an agent to sweep sources, collect hook events, retain conversations or accept imports.

A source is the evidence a Signal receives. A run is one attempt to process that evidence. An entry is a result. Retaining a source doesn’t mean its statements posted as entries.

Authorization

Each Signal names its sources, workspace, boundary and compartments. Its connection and authorization limit what it can read and write. A connector’s access doesn’t give a reviewing agent permission to change access or act as you.

A sweep or routine uses a bounded authorization called a mandate. You can inspect and revoke it. See Sweeps and routines.

Review windows

When one item needs a person, other work in that Signal continues. The whole Signal pauses if its shared connection, placement or authorization fails.

A review window determines how long an item waits. Workspace administrators set the default. Boundary and compartment owners can set a window for their area. The nearest applicable setting applies.

When the window expires, the item gets an expiry receipt. Expiry doesn’t count as approval. Mandates and source retention don’t renew automatically.

Read a run’s outcome

The planned view distinguishes a healthy connection, sources filed, entries posted and items waiting for review. A run reports what it covered, skipped or couldn’t complete. One posted entry doesn’t prove the whole run finished.