Signal Routing

The decision layer. Based on the enriched nuggets, the system determines what happens next. This is where urgency, priority, and context converge into action — or deliberate inaction.

Routing operates per nugget — each nugget from a signal is routed independently. A single signal might produce nuggets that route in completely different directions.

Routing outcomes are not mutually exclusive — a single nugget can trigger more than one:

• •Respond — the nugget expects or warrants a reply. A draft is prepared and presented for approval, or handled automatically if authorized.
• •Capture — the nugget contains information worth storing. A case is updated, a journal entry created, a person profile enriched, a calendar event added. No response needed, but the knowledge shouldn't be lost.
• •Wait — the nugget is important but can't be acted on yet. The system creates an expectation — a follow-up to track, a reminder to check back, a dependency on something that hasn't arrived yet.
• •Ignore — after understanding the context, the nugget doesn't need a response and doesn't contain new information worth capturing.

Recomposition After all nuggets from a signal have been routed, the results are aggregated back to signal level for coherent execution. If three nuggets from the same email all trigger "respond," the system composes one coherent reply — not three separate emails. Database updates (capture) can execute independently per nugget. Wait and ignore outcomes are tracked per nugget. The goal: the internal processing is granular, but the outbound actions are natural.

Behavioral intelligence from the Person Lens is always routed as "capture" — it feeds directly into Person profiles. This happens at the signal level, not per nugget, since behavioral patterns are emergent properties of the whole conversation.