Resetting the synthetic sandbox.

COUNTERSTEP

Evidence-bound remediation for agent runs

BASE / 0.1

The action happened. Now close the loop.

From agent overstep
to verified counterstep.

Counterstep reads the original receipt, inspects what is true now, authorizes only cited reversible repairs, and checks the result from fresh state.

Recovery test rack

Prove the boundary, not just the happy path.

4 deterministic conditions
Choose a synthetic recovery condition
Bounded recovery

Two resources · deterministic authority · fresh-state verification

01

Source evidence

What crossed the line

SHA-256 —

Loading the synthetic source receipt…

02

Current state + authority

The recovery boundary

MAX 2 WRITES
03

Agent action ledger

Inspect → gate → repair → verify

ready
  1. Inspect

    Read current resource versions

    Not started
  2. Plan

    Propose a cited finite recovery

    Not started
  3. Authorize

    Check the exact authority tuple

    Not started
  4. Repair

    Apply only admitted transitions

    Not started
  5. Verify

    Re-read final sandbox state

    Not started
  6. Close

    Issue the deterministic outcome

    Not started
Deployment
Unavailable
Persistence
Unavailable
Orchestration
Google ADK · TypeScript
Execution path
Unavailable
No recovery claims yet.

The ledger fills only when an inspection, gate, action, or verification is recorded.

04 / Deterministic closure

Proof waits for fresh state.

Counterstep will not call the incident repaired until every declared goal is re-read and satisfied.