How It Works
Inline runtime governance, at every state transition, on any model.
CHURPRIMO™ evaluates continuity inside the running system rather than after failure.
Where it sits
Between an agent deciding what to do and that thing happening. Not off to the side watching, and not afterwards reading the logs.
Figure 1. CHURPRIMO™ sits inline, in the path of the action.
What it checks
We don’t ask whether the agent is smart or right. We ask whether it’s still itself.
At each state transition, CHURPRIMO™ reads several independent signals about the agent and evaluates whether they remain consistent with what the agent was deployed to be. Divergence across those signals is drift. CHURPRIMO reports it in-process, while a correction is still cheap.
Computers compute. They do not think. CHURPRIMO evaluates the system while it is computing, not its output after the fact.
Nothing is committed to on a prediction. A deviation has to be causally active, actually present in the running system, before anything is done about it.
CHURPRIMO evaluates and reports. The controlled system, and the people responsible for it, act on what it reports. Keeping measurement and intervention in separate hands is a design constraint, not a limitation.
What it catches that evals and monitoring do not
The evaluated object is continuity, not correctness. Evals ask whether the output was right. This asks whether the system that produced it is still the system you deployed.
- 1The unit of evaluation is the state transition: each move from one agent state to the next, in-process, not sampled.
- 2At each transition, an evaluator beside the agent reads its turn events and evaluates continuity against the agent's declared plan, limits and authority.
- 3Evidence sets the ceiling on the response. A deviation that has only been observed can justify nothing irreversible. Nothing happens on a hunch.
- 4CHURPRIMO returns the assessment. It never modifies model weights or orchestration logic, and it never acts on its own.
Model-agnostic. Framework-agnostic. Runs beside the agent process, in the same loop.