Truth Engine Playground

INTERACTIVE PLAYGROUND · SIMULATED

Watch truth change
only when evidence changes.

This is a deterministic product simulation. It explains the Verified Execution lifecycle without calling the VM, the real engine, or an external provider.

CLIENT-SIDENO LIVE ENGINE CALLNO REAL EXTERNAL ACTION
Real evaluation API
CLAIM≠TRUTHEvidence changes the justified outcome.
SATISFIEDNOT_SATISFIEDUNKNOWN

CHOOSE A CASE

Four deterministic scenarios.

Each case uses the same public truth states and product rules. The flagship lost-response path mirrors the difficult behavior proven by the real evaluation environment.

CURRENT CASE

Response lost after effect

The provider performs the action, but the acknowledgement never reaches the caller.

JUSTIFIED TRUTHNOT STARTEDRun the scenario to inspect the lifecycle.
01INTENTaction requested
→
02ADMISSIONidentity + scope
→
03AUTHORITYrelease permitted
→
04RELEASEcontrolled dispatch
05PROVIDERexternal effect
→
06EVIDENCEwhat is supportable?
→
07RECONCILEread-only lookup
→
08OUTCOMEcanonical truth
EXECUTION TRACE0 / 0 events
  1. —
    ReadySelect a case and run the simulation.
EXECUTION AUTHORITY—No release decision yet.
RETRY AUTHORITY—Retry intent never creates authority by itself.
PROVIDER MUTATIONS0Simulated consequential writes.
RECONCILIATION—Read-only evidence path.
SIMULATION ONLY · NOT ENGINE EVIDENCE

WHAT THE HARD CASE TEACHES

A lost response does not authorize a second effect.

When the provider may already have acted, transport failure creates uncertainty. The safe state is UNKNOWN until evidence supports something stronger.

01Provider effect may have happened.Do not convert a timeout into failure.
02UNKNOWN becomes explicit.The system refuses to invent success or failure.
03Retry remains governed.Uncertainty does not grant new execution authority.
04Reconciliation reads reality.A read-only path gathers evidence without repeating the action.

SIMULATION VS. PROOF

This page explains behavior.
The Evaluation API proves it.

The Playground is intentionally independent from the VM. For a real technical evaluation, use scoped access to the live Verified Execution surface and inspect the resulting evidence.

PLAYGROUNDStatic + deterministicFast explanation. Always available. No external mutation.
EVALUATION APIReal engine executionScoped credentials. Real runtime path. Evidence-backed outcome.

READY TO VERIFY IT?

Move from simulation to execution.

Evaluation guide →API surface

BOUNDARY

What the Playground never claims.

Not a live engine runNo Runtime, provider, database, or VM is called.
Not execution evidenceUI events cannot create Truth Engine truth.
Not production validationThe current product remains in Developer Evaluation.
UNKNOWN remains legitimateIf evidence stays inconclusive, the simulation leaves it UNKNOWN.