Signals overview

For years the loop ran in one direction: a human explains a problem, the AI writes code, the product ships. If something then broke in production, it was on you to notice it, reconstruct the context, and explain it back to the assistant from scratch.

Pathrule Signals adds the arrow that was always missing: product to AI. Your running product becomes something that can speak. When a real flow breaks or recovers, your agents hear about it directly, already carrying the paths, rules and memories that touch that part of the code. Signals is available today in Pathrule Studio.

Signals is optional per workspace. Setup starts with a focused read-only scan, then shows a small proposal for a person to approve. Studio vendors a dependency-free SDK and adds only those approved points. Nothing starts observing a project from a generic background crawl.

The idea in one line

Human → AI → Product is only half the loop. Signals lets the product answer back.

What Signals is

• It watches, in the background. Signals reads your product's real runtime events and coalesces repeats, so an idle product produces no noise.
• A deterministic reporter. When an error or a flow crosses a worthiness threshold, Signals groups it into a single canonical incident and attaches a Context Brief built from facts Pathrule already holds, the resolved node path, the strict rules on it, the memories that explain it, and the recent activity around it.
• A runtime proof loop. After a fix ships, Signals keeps watching the next release. It can tell you honestly whether the issue recurred, went quiet, or was actually verified in production.

A narrow runtime-context contract

• Incident context, not user analytics. Signals carries no funnels, sessions, per-user tracking or raw event warehouse.
• Deterministic evidence. The Context Brief is built from stored facts before any person decides to act, with no LLM root-cause guess presented as fact.
• The existing execution path. Signals stops at the handoff. After you approve a task, planning and code execution continue through the same Tasks and Chat flows.

Why it matters

The expensive part of fixing a production issue was never the fix, it was the discovery, the context rebuild, and the manual watch afterward. Signals removes all three. Your agent starts a task already knowing what happened, where it maps, why it matters, and which rules govern the code. And once the fix is out, you get told when production actually confirms it.

What to read next

• How the loop works for detection, the Context Brief, the handoff, and the verification states.
• Setting up Signals to turn it on in Pathrule Studio.
• Plans, quotas and retention for monthly limits and how long Signals are kept.