One provider write.
Capture the action result and persist the pending verification work. Keep the dependent effect held.
Implemented · local evaluation
Watch the workflow.
Understand the decision.
The local Varqo console brings the verification kernel into view. Start a fixed workflow, compare expected and observed state, inspect the gate, and export the evidence behind the decision.
Local technical POC. Synthetic provider and local effect. No cloud credentials required for the lab.
Five fixed console scenariosSuccess is one path.
Success is one path.
The failures matter too.
Explore the expected decisions below. This is an interactive explanation of the local console, not an executing kernel or a live system connection.
Success without the outcome
HELDProvider actioncompleted
Required resource stateactive
Observed resource stateoff
Provider writes1
Dependent local effects0
The provider action completed, but the required resource state remains unproven. The dependent effect stays held.
Pending-proof recovery · local labA restart should not
A restart should not
mean a repeated write.
After trusted response capture, the local lab preserves pending work and its held dependency. A new process can resume the proof with the same state directory.
Resume explicitly.
A new process leases the captured work and revalidates the saved plan. It does not repeat the original write.
Require real proof.
Independently verify action and resource state. Authenticate the local evaluator receipt before commit and release.
One local effect.
Release only with valid proof. Replayed requests remain idempotent in the tested local path.
This proves a scoped local recovery path after capture. Atomic write-and-capture, production key isolation, tenant isolation, external effects, and generic rollback remain open work.
From run to explanation
Evidence you can inspect.
The actual local console reads saved service state. Its verdicts come from the kernel, not from an animation in the browser.
Persisted run history
Reopen local runs, inspect expected and observed state, and understand why dependencies were held, blocked, or released.
Projected evidence export
Export a minimized view of observations and decisions. Raw provider bodies, key material, and certificate bytes are excluded; the export is not a public attestation.
Repeatable installation
An internal Python wheel packages the kernel, CLI, console assets, and local lab for evaluation. This is not a publicly published package or hosted service.
Adversarial regression lab
A separate nine-scenario lab covers premature continuation, false claims, forged identity, wrong dependencies, replay, failed reads, divergence, and timeouts.
Implemented todayA focused local
A focused local
evaluation surface.
- Five fixed synthetic console workflows
- Independent action and resource proof
- Saved runs, gate explanations, safe export
- Explicit resume of captured pending work
Next to validateFrom local proof
From local proof
to a scoped integration.
- Guided live-provider connection
- A real LLM adapter in this recovery path
- A disposable, idempotent external effect
- Atomic capture and production state protection
No account management, arbitrary workflow editor, SSO, hosted deployment, or generic rollback is included in the current console.
Evaluate with usBring one workflow.
Request a guided evaluation Bring one workflow.
Define what must be true.
Help test whether a platform engineer can explain success, divergence, and restart from the evidence alone.