# Verify this record

Exported 2026-09-27T18:37:45.961572Z from the **paper** ledger: 1331 events, head hash `388255d7522689e64798e67ab839058a16e062a729a381a4ae14ea50cc406751`.

## 1. Recompute every number (standard library only)

```
python scripts/recompute.py public/
```

It re-walks the hash chain of `ledger.jsonl` line by line, re-hashes every file in `blobs/` against its name, checks that `equity_hourly.csv` is exactly the ledger's hourly `mark` events, rebuilds every closed trade in `trades.csv` from the ledger's `fill` events, recomputes every field of `metrics.json` (Sharpe, its standard error, Sortino, max drawdown, win rate, turnover, fees and the 90% block-bootstrap intervals) and every arm in `arms.json`. Exit code 0 means every published number recomputes.

## 2. The pre-registration

- Genesis: seq 0, hash `ebbf607a8fe199bccc0f612ededf2a6902e4884a38d21fbfea498dff7da453a5`, created 2026-09-24T17:06:23.178588Z.
- Policy hash `55ff779b5d6f2c55082be1b4db6c9fde53865213cade58232f64f372ad73aeaf`: the SHA-256 of the canonical JSON of the policy it carries (recompute.py checks it).
- OpenTimestamps: submitted at 2026-09-24T17:06:25.431387Z, proof `blobs/421d631cb5bacb04172225e875905e6e0c7400bb8d5ec161ada7bfa1c3394a8e`. Check it with `ots verify` against the genesis event's canonical bytes.
- OpenTimestamps: upgraded at 2026-09-24T17:06:25.431387Z, proof `blobs/baa629fa33e45283c5caf393bd24cc169416ce0ac0c6e55f906af01900158f98`. Check it with `ots verify` against the genesis event's canonical bytes.
- The genesis hash was posted on X by the owner before the first order.

## 3. The orders exist on Bitget Demo

```
python scripts/verify_orders.py --public public/orders.json
```

One read-only `order --action detail --orderId <id> --paper-trading` per published order through Bitget's own Agent Hub CLI. It needs a Demo key for the account that traded, set up as the script's docstring describes; the owner may publish a read-only one.

## 4. Replay a decision without any key

```
t2sa replay --public public/ --decision <decision_id>
```

It re-runs the logged snapshot, the recorded completion, the kernel and the planner, and checks that the ruling and order intents hash to what the ledger holds.

## 5. Every card is its own evidence

Each `cards/<id>.json` lists the ledger `seq` of every event it was read from and every blob those events commit to; `sha256(blobs/<hash>)` equals the file name.