Sagitta Radar launched

Sagitta Radar launched on 28 July 2026. It watches three pillars of external dependency — oracle price freshness and deviation, bridge route settlement and pauses, and liquidity-pool depth and imbalance — and delivers signals as alerts and as structured daily briefings.

The three pillars are not an arbitrary selection. They are the dependencies a protocol does not own and cannot fix. A team can audit its own contracts, rehearse its own incident response, and rewrite its own governance; it cannot make an oracle publish a fresh price, cannot make a bridge settle, and cannot conjure depth into a pool that has thinned. Those are the failure paths that arrive from outside, on someone else's schedule, and they are the ones a protocol is least likely to be watching at the moment they matter.

Radar runs on the Sagitta Continuity Engine backend, which is what connects an infrastructure signal to continuity doctrine rather than leaving it as an isolated alert. The distinction is the product's reason for existing. An alert that a bridge has paused is information. The same alert, read against a doctrine that already names what a paused settlement route means for this protocol and what it should do next, is a decision — and the gap between those two is usually where the damage happens.

Delivery is to Discord, Telegram, and webhooks, which is a deliberate choice to meet operators where incidents are actually handled rather than requiring anyone to be watching a dashboard at the time.

Subscription plans and current pricing are published on the product page and are deliberately not restated here: they move, and a figure republished on an evergreen record is a figure that will eventually be wrong.