Architecture
Two products. Nine steps.
Forge reads and predicts. Radar acts, governs, and learns. Nine named parts, in order, nothing skipped.
The forecast, risk, and read layer
NexOS Forge
Stands alone. Sellable on its own.
Forge is what a trader betting on energy or AI-infrastructure strain actually wants: the number, not the loop. Telemetry through Echo, the read and the calibrated call.
Telemetry
What Forge reads
Your data, your processes, your models, and the capacity actually on the floor. Forge reads what the operation already produces. There is nothing new to instrument.
Vector Processing
The read, projected forward
One instrument across a large quantity of data at once, and the predictive half of Forge: it reads the Telemetry and projects it forward, forecasting whether and when breach risk will cross the threshold, before anything is actually wrong yet.
Baros
The strain state
Demand pressed against the resistance the operation can actually offer. One reading for how close a system is to its limit, and which way it is moving.
Echo
The call
Fires when Baros is projected to cross its breach threshold. A calibrated breach-risk alert with the odds stated. It comes to you. You do not have to be watching a screen.
The call, the move, the gate, the ledger and the loop
NexOS Radar
Requires Forge underneath it. Not sold standalone.
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.
Envelope
The move
Sent when Echo fires, carrying the corrective instructions. The corrective half: receding-horizon control held inside a safety constraint. When no safe move exists it returns INFEASIBLE rather than a least-bad answer dressed as safe.
Covenant
The authority
Routes the Envelope to the human authority allowed to approve it. The system flags, the operator decides, and it never executes alone. That is structural, not a setting that loosens with earned trust.
Preport
The grade
Grades each Envelope: the call made to correct a coming breach, against the call to take no action at all. Scored win or loss against what actually happened.
Ledger
The record
Preports recorded in aggregate, and the public record. Wins and losses both printed. This is the part most vendors do not offer, and it is the part that makes the rest checkable.
Sweep
The loop
Reads the Ledger and learns, continuously. When enough breach-risk instances recur in one area, Sweep says so and suggests an automation to bring the count down. Advisory: a human capital decision, never the system acting.
How the loop closes
A forecast tells you the breach is coming. This is what stops it coming back.
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.