Skip to content

Signals

A signal evaluates an observation against a condition. The signal gives the team a reason to act or to look closer. A data feed supplies the observation, and a playbook carries out any work the team decides to start.

Record the source and observation ID before evaluating the team’s rule. A condition should make clear which data must be present and which cases should be held. A matched observation can propose work. The workspace decides whether the trigger is enabled, the destination team is eligible, and the occurrence has already been handled.

This is decision logic for an implementation. The draft leaves the portable signal schema open.

Observe a dated hiring announcement with a source URL.
If company identity or announcement date is ambiguous, hold for specialist review.
If the announcement is new and matches the team’s criteria, propose a research goal.
If its occurrence was already handled, link to the existing outcome.

Keep the observation, the matched rule, any human decision, and the resulting goal or run together by reference. A later revision can change the rule and be checked against a replayed fixture. The existing outcome remains evidence of what happened under the prior revision.

See feeds, scheduled work, and specialist feedback and evals.