Independent observation
Varqo queries the authoritative provider state rather than treating the agent's own output as evidence.
Varqo determines what must be true for a workflow to continue, independently proves those states across systems, and controls dependent execution from the result.
Choose a scenario and run the workflow. The simulation follows control patterns exercised in live Varqo experiments; it does not call a live provider.
————Varqo prepares the proof before the consequential write whenever possible. After the write, it binds only the runtime identity returned by the provider, executes an independent verifier, and evaluates the observation against the required outcome.
A successful write response is evidence of the action — not automatic permission for the workflow to continue.
The control boundary is designed around explicit proof rather than model confidence or a provider's success label.
Varqo queries the authoritative provider state rather than treating the agent's own output as evidence.
Evidence counts only when it proves the specific condition the downstream workflow depends on.
Missing verifiers, malformed responses, unknown states, transport failures, and exhausted polling remain unresolved.
Durable records preserve proof topology and verdicts without persisting raw tasks, provider bodies, or credential-like values.