RESERVE. DISPATCH.
RECONCILE.

01 / LOCAL QUICKSTART

Download the kit. Install Python 3.10+ and Node 18+. Run these commands in a terminal from the folder containing the ZIP. No packages, keys or model payments are required.

unzip battery-pilot-kit.zip -d battery-kit
cd battery-kit
python3 -m unittest -v test_battery.py
python3 paper_replay.py

The tests check reservations, stale workers, duplicate receipts and reconciliation. The replay uses bundled public cost observations in a temporary SQLite ledger. It makes no network or paid model calls.

02 / THE OPERATOR CONTRACT

1. Configure. Set protected floor, daily cap and maximum job cost in integer microUSD (1 USD = 1,000,000).
2. Reserve. Supply a worst-case quote and trusted provider allowance. Approve the alternate route before dispatch.
3. Dispatch. Fence the previous worker with a new runtime epoch. A reserve is not provider credit.
4. Settle. Reconcile the actual receipt, including incurred costs of failed jobs. Unknown outcomes keep their hold.
5. Checkpoint. Export confirmed application results. Retain the authoritative ledger when changing local workers.

Bundled core.py exposes configure, credit_paper, takeover, reserve, dispatch, settle and checkpoint. Read workers.py and paper_replay.py for runnable examples.

03 / WHERE THE GUARANTEE ENDS

Trusted local operator, one authoritative SQLite ledger. Supplied quotes, time and provider allowance are trusted inputs. The kit does not fetch billing balances or authenticate receipts.

A checkpoint hash checks integrity; it is not a signature or proof that the data is true. External paid effects require provider idempotency or a durable outbox and receipt integration.

The browser lab assumes one task/hour, a $30 daily cap, a $500 alternate allowance and a cheaper route at 40% of task cost. Fees ON adds an assumed $2/hour. These are fixed illustrative assumptions, not predictions. Reserve inputs use $5 increments, task costs $0.10, and protected balance/provider allowance whole dollars.

04 / YOUR WORKSPACE

Policies and test history live in this browser's local storage. No account or cloud sync. Clearing site data removes them. Workspaces are separate for each domain. Export JSON from Policies before changing domains or devices, then import on the new site.

Imports are validated and merged by record ID; existing IDs are retained. Maximum 100 policies, 200 tests and 250 KB per file. Result hours are recomputed from the policy, never trusted from an imported result.

Share links include reserve, task cost, protected balance, allowance and switches in the URL fragment. They do not include your saved name or history. Anyone with the link can read the parameters; do not put secrets in policy names or files.

The public observer snapshot contains selected counts and timestamps. There is no wallet connection or paid checkout. Hosting infrastructure may process ordinary request metadata.