The call, the move, the gate, the ledger and the loop
The move, not just the number.
Radar is what happens after the call: the corrective move, the authority it routes to, the grade on whether it was right, and the loop that turns a recurring failure into something you fix once.
Requires Forge underneath it. Not sold standalone.
What you get
The move, the authority, the grade, the record, the loop.
Envelope
The move
Covenant
The authority
Preport
The grade
Ledger
The record
Sweep
The loop
Forge tells you the breach is coming. Radar is what stops it coming back.
How the loop closes
A failure that keeps happening is a job, not a fact.
Without this, we are a forecast company. This is the part that makes it automation.
Sweep flags it
Sweep reads every call and every outcome, continuously. When the same breach keeps recurring, it does not simply log it again. The pattern surfaces in the Ledger.
You are asked
The Ledger puts the question plainly: this breach has occurred eleven times this month. Would you like to add a solution?
A human approves
Nothing is built on a machine's say-so. The same rule that governs every directive governs this one: the system flags, the operator decides.
Studio builds the workflow
NexOS Studio builds the thing that resolves the recurrence. A person builds it, scoped to your operation, and you own what is yours at the end of it.
Radar grades it
The workflow is measured against the baseline it replaced. If it earned its place, the Ledger says so. If it did not, the Ledger says that too.
What we claim, and what we do not
Built and tested component by component. The MPC layer and Covenant have each run across multiple demos and simulations, and Covenant has run live in production. Not yet proven as one integrated system with the receipts Forge carries.
See it read
The instrument reads every channel of an operation against its own limit, including the channels where no safe move exists. Hospitality carries the fullest version of it.
Start at the read, or take the whole instrument.
Radar deploys under contract, on Forge. The first conversation is about which capacity system you are worried about and what you already measure.
Contract deployments