Why this pilot is reviewable.
This page does not try to prove everything. It explains what can be checked on one workflow surface, what cannot be claimed, and why the output can be reviewed without rebuilding the whole case from scratch.
What can be checked
What the system validates
The system validates whether a binding workflow transition remains admissible under the same contract identity, policy identity, and replay input conditions.
Validation evaluates admissibility state; verification reproduces the claim outcome.
The verification surface is replay-verifiable and execution-bound. It does not rely on observational reconstruction alone.
Replay non-equivalence invalidates the execution claim.
What is not checked
What result the pilot produces
The output is structured for internal review and next-step discussion without forcing teams to reconstruct the case from scratch. It does not become decision authority by itself.
Why the output is reviewable
Technical surfaces
These routes are for inspecting a documented result after the risk and boundary question are already understood. They are not the primary entry path for the pilot.