Lock
Start from the repository’s existing checks. Approve the acceptance manifest before the run.
Independent verification for AI agent work.
KeepState checks agent work against acceptance tests you approve before the run. Every attempt and cost stays on the record; each verdict carries a signed receipt.
$10.00 of session and storage credit at signup. Bring your own model key. Model usage is billed separately.Verification and signed receipts today.
Receipt-triggered payment is planned.
One record. A basis both sides can inspect.
The work has an account. Now give it a receipt.
Verification and signed receipts.
Buyer-approved tests. Host-run checks. Every attempt accounted for.
The receipt releases the payment.
Receipt-triggered payment is planned. Not live today.
01 / From a job to a shared record
KeepState’s Cruise workflow turns the buyer’s acceptance tests into an independent record of what passed. The agent does the work. The tests decide the outcome.
Start from the repository’s existing checks. Approve the acceptance manifest before the run.
The agent works in a durable session. Save points keep its files and context ready to resume.
Pinned tests run on the host, beyond the agent’s reach. Forged pass logs are refused.
Restore the checkpoint before trying the next model. After the last model, review the job: resume with a wider ladder or cancel.
Reconcile every attempt and cost. Each verdict carries the locked tests’ digest and a signed receipt.
Cruise supports bounded coding tasks with deterministic tests. Payment clearing is planned.
Inside the workflowCruise checks work with an independent runner the agent cannot reach. It starts with a cheaper model and restores the checkpoint before escalating a failed attempt.
Cruise. Set the task. It drives, tests, and retries.
Current scope: bounded coding tasks (scoped tasks with a fixed test suite) on the KeepState runtime, across Anthropic-native and OpenAI-compatible model families.
Illustration the record defines the scope original record
Recovery covers supported agents and saved checkpoint state. External effects stay outside that boundary. Current availability →
Verify. Your checks decide what passes.
Recover. Return to recorded state.
Account. Every attempt, on the record.
02 / Continuity beneath the receipt
A failed attempt should not erase the work that came before it. Retries fork from the parked checkpoint. Saved session state supports the next attempt.
Workflow illustration. A saved state supports the next verified attempt.
Rewind. Resume. Keep working.
Checkpoint the running session. Rewind to an earlier save point and resume with its memory and files intact. Work after that save point is lost.
Provider-side model cache is not included in the checkpoint.
$ ks demo --task fixture --kill-at 3m
session a1618683e4bb · coding task
KILL · the agent's machine, hard
back from save point 1 · 25.2 s later
same session · memory and files intact
paid model calls replayed, not rebought
TESTS python3 test_inventory.py → OK
Fork schematic Choose a branch
Kill-and-resume, recorded 29 Jul 2026 (the gate-4 demo): three minutes into a coding task, the agent's machine and its supervisor were killed on purpose; the same session was back at work 25.2 s later and its test passed.
Editorial summary. View the unchanged original record.
Recorded test the kill and the resume, from gate 4 · edited for readability; the record is verbatim original record
Recorded on 2026-07-29 on the Apple Silicon evidence bench. A coding session was checkpointed, interrupted by a hard kill, and resumed. The recorded recovery completed with the workspace and session state preserved. 10 model calls were recorded; 29,871 replayed tokens were not purchased again. The recorded workload check passed. These are historical test results, not a recovery-time guarantee.
Recorded test rewind, from the plaintext-store fleet test original record
View kill-and-resume record View rewind record Full transcript
Saved checkpoint
Branch A Separate state
Branch B Separate state
Branch C Separate state
Branching
Create separate branches from a saved session, each with its own disk and history.
Three-branch creation and isolation are proven. Useful work in branches with real model calls is not yet claimed. Larger fan-outs are untested.
03 / The record is open
If we verify other people’s work, you should be able to inspect ours. Measured results and known failures belong in the same record.
Green gates in the ledger
Current green verdicts. Earlier runs and their limits remain in the record.
MEASURED · v0.1.26
Record synced 2026-09-19
Kill-and-resume cycles
Historical bench result. Fresh cycles with memory and files intact.
MEASURED · 2026-08-25
Read the bench record ↗
fresh kill/resume cycles, bench; the claim is the Wilson interval [86.7%, 100%], not the point
Sample: 25 fresh kill/resume cycles
No open durability finding is listed in this release record; that is not independent assurance for the current deployment.
Every claim expires with its gate evidence. No claim outlives its gate.
Read the proof recordEvidence is part of the product
See which capabilities are proven, which are enabled in production, and what KeepState does not claim.
Cruise requires bounded coding tasks with deterministic tests. Customer data requires classification and named authorization; the manifest enforces what you supply and does not detect sensitivity.
04 / An independent position
The vendor’s account of its own work is only one side of the story. KeepState gives the buyer and vendor a record grounded in tests agreed before the work begins.
What independence meansTests are locked on approval. The verifier refuses changes to the pinned test code.
Host-run checks are out of the agent’s reach. A fabricated pass log is not a pass.
Attempts and costs stay in the ledger. A signed verdict receipt makes later changes detectable.
KeepState records attempts and costs in its ledger. In the accepted-work test, settlement cleared only after every attempt reconciled, including failed attempts.
Publication authorization only: this scope does not create an external pull request.
The recorded fixture uses a placeholder tariff. It is not a customer price.
Illustration accounting structure; the record carries results and limits original record
Start with one bounded task
Start with a hosted session.
Use Cruise for bounded coding tasks with tests that define done.
Cruise is available to every hosted account.
Explore the developer path
A considered first step