Recoverable Evidence
See the exact operation before it runs, inspect what actually landed through authoritative read-back, and keep the evidence and declared reversal limits attached to supported changes. The full outcome-and-Reverse flow is being built for early access.
Run history
Tune the Wooden Place jump
goal: raise the last jump so the landing pad reads at night
Plan: raise bounce on BouncePad.cpp. Approval when required before the owning route admits the write.
waiting on you to confirm the plan
Capture a playtest of the last jump under night lighting.
you confirmed the plan
Before-state reference and hash captured for BouncePad.cpp.
Technical detail
Verified by authoritative read-back
capture.target · Wooden Place in-game camera
Playtest set attached. Landing pad is in shadow.
BouncePad.cpp · bounce 620 → 780
FVector Launch = GetActorUpVector();- Launch *= 620.f;+ Launch *= 780.f;+ Launch += GetActorForwardVector() * 90.f;Pawn->LaunchCharacter(Launch, true, true);
Re-read BouncePad.cpp. Requested 780 · observed 780.
Technical detail
Verified by authoritative read-back
unreal.lighting · rim light on flag
Bounce change verified. Reverse supported for a new governed attempt.
Request Reverse
09:18:02 Cook started on this machine
09:18:41 Play: Maze
09:19:08 Wrote Binaries/Win64/Bloxiti.exe
09:19:44 Waiting on playtest review
Know the operation, scope, and way back before execution.
The project stays untouched until the planned operation is admitted. Approval is required when the owning route demands it—not as a universal gate on every execution mode.
Requested result
What this step is trying to achieve, in the terms of the project.
Exact operation and affected resources
The intended operation and the resources it will touch stay named before execution.
Current-state references and hashes
Before-state references and hashes are captured so later verification has something authoritative to compare.
Approval or execution authority, when required
Some modes require approval; sanctioned no-approval execution stays explicit when the owner route allows it.
Declared verifier and reversal support
How the result will be verified, and whether Reverse is supported, blocked, or unsupported for this route.
A governed new change—not a magic undo.
Recoverable Evidence declares whether Reverse is available for a supported operation. It does not promise universal snapshots, whole-project rewind, or a substitute for version control.
The boundary
Support is declared by the owner route
Reversal is available only where the owning operation declares support.
Current state is rechecked
Reverse rechecks current state and may be blocked or unsupported.
Not a VCS or UE-file rewrite
It is not a whole-project rewind or replacement for Git/Perforce; encoded Unreal assets must use UE Bridge.
Read-back, not a completion message, determines what landed.
A finished command is not treated as success until authoritative read-back compares requested and observed state.
Requested state versus observed state
The VerifiedOutcome compares what was asked for with what read-back actually saw.
Exact operations and resources changed
The operations and resources included in the executed step stay named with the record.
Before/after evidence references
References and hashes for the before and after states stay attached for inspection.
Machine read-back verdict
Read-back re-reads the authoritative surface. Presence alone is not verification.
Verified, failed, blocked, unsupported, or not-run
Missing, mismatched, blocked, or unsupported outcomes stay explicit—never quiet success.
Keep a governed path back when the owner route supports it.
The intended flow seals the verified outcome, its supporting proof, and a reversal record containing before/after references, the supported inverse or compensation, prerequisites, limitations, and an explicit unsupported state. Reverse starts a new governed attempt against the project’s current state.
ProofPack
Why the result is trusted: evidence, read-back verdict, checks, and the exact change.
ReversalPackage
What a future Reverse would require—references, inverse or compensation, prerequisites, and limits.
Reverse
A new plan and verified operation through the owning route—not an edit of history or instant undo.
Get on the list before Studio opens.
Studio isn’t public yet. Our team uses it today and opens access gradually.