Readiness

A checklist that runs. It exits non-zero on a failure, and anything it cannot verify is unverified — amber, never green.

NOT YET

exit code 2

20 passed · 0 failed · 3 unverified, of 23 gates.

Gates

All 23 gates.

offline test suite

2623 passed, 35 skipped, 53 deselected, 26 warnings in 670.67s (0:11:10)

PASS

T1-T4 and L1

14 passed, 9 deselected, 1 warning in 10.25s

PASS

lint

292 files already formatted

PASS

web component suite

Tests 592 passed (592)

PASS

web types

tsc --noEmit clean over apps/web

PASS

web browser suite

every route clean in both themes and at 390px, with 20 distinct titles.

PASS

chain and fork suite

47 passed, 6 skipped, 2658 deselected, 2 warnings in 224.51s (0:03:44)

PASS

kill switch

7 passed, 214 deselected, 1 warning in 2.41s

PASS

kill file absent

ops/KILL not present

PASS

dry run

MISQUOTE_DRY_RUN=(unset — defaults to dry)

PASS

published assumptions

G-1..G-3 and A7..A11 published

PASS

no provisional constants

kappa 3,601/log-price, fitted (r^2 0.85), card agrees to 0.0%

PASS

30-day tape

252,923 swaps, 30.2 unbroken days read from chain

PASS

Venus rate tape

2 market(s) read unbroken: vUSDT 16.0d, vUSDC 16.0d

PASS

badge coverage

all 3 listed pools badged; 4 quoted by artifacts, all of them verified

PASS

judge document current

every derived figure matches its artifact

PASS

agent advantage report

5 of 6 tasks quotable on a chain tape · withheld and said so: Equities

PASS

erc-8183 escrow

job 56681 escrowed 100000000000000000 on chain 56 and was reclaimed; settle has run on a fork only, and opens 2026-09-13 08:01 UTC. One wallet was both client and provider, so this proves the escrow and hires nobody.

→ make hire-mainnet ARGS='--settle 56718'

UNVERIFIED

artifacts match the engine

7 replay artifacts, none generated before an engine change

PASS

agent identities

5 agents registered on BSC mainnet and owned by 0x0c501EE1924bfb91a028DB4BcD68f4861B0Ff6eE

PASS

24h unattended burn-in

warden longest unbroken run 43.5h on BSC mainnet, signing refused — across 3 run(s), 47,071 rows (file spans 602.2h — the gate is the run, not the span). Also: warden 43.5h, sentinel 0.2h, grid 0.1h, 0 read errors

PASS

signer

not checked — this run is not --mainnet

→ re-run with --mainnet to check the signing key

UNVERIFIED

position cap

not checked — this run is not --mainnet

→ re-run with --mainnet to check the position cap

UNVERIFIED

What is not built

Capabilities the README advertises and this repository does not contain.

Yield

Agent Studio deployment

Not built

Would have: The seller agent deployed through the vendor's own CLI — bag deploy --provider bnb|aws|azure — which is the native-citizenship claim the track is about.
Why it is not here: Everything except the deploy verb now exists. The agent runs at misquote-agent.onrender.com; bag erc8004 register gave it identity 2102 on chapel; and its ERC-8183 task interface is live and signs — make studio-negotiate gets a quote back whose signature recovers to the wallet owning that identity, and whose verifying contract is the kernel this repository verified from bytecode. What has not happened is bag deploy: it takes bnb, aws or azure, and running the agent on a host we already operate is not the same claim as the CLI deploying it. /studio renders all of it, this entry included.

Yield

The Studio agent's x402 self-funding

Not built

Would have: The agent buying the paid data its work needs with its own wallet, per call, instead of only being paid through escrow.
Why it is not here: studio.toml declares protocols = ["A2A"] and publishes one face. The scaffold's own comment in unifiedMain.ts names the file this would take — bag x402 trust <merchant> then bag recipe code x402-buyer, emitting the tools that spread into the work hook — and that file has never been generated. The LLM credit does top itself up from the Pieverse balance, which is a different mechanism and not this one.

Activation

Altana session keys: the caps

Not built

Would have: The half of the caps subset this deployment does not enforce: the allowlist and the spend cap. Expiry and one-transaction revoke are built and proven on chain; these two are not.
Why it is not here: Expiry and revoke are enforced by the keystore and proven on chain. The allowlist and spend cap would need a validator module, and no grant on this deployment carries one.

Due diligence

Vetting proof-of-concepts: the five readings

Not built

Would have: An executable demonstration for the five badge checks that do not have one. Four of the nine now do, including the mint.
Why it is not here: Four of the nine can be demonstrated by a transaction, and are — including a real mint. The other five are readings: a token either reports 18 decimals or it does not, and no transaction demonstrates a reading.

Operations

Signing on mainnet

Not built

Would have: make warden broadcasting the decisions it already makes correctly against BSC mainnet, with capital at risk.
Why it is not here: Chapel broadcasts behind three gates that each default to refuse. Pointing the same path at mainnet is a decision about capital, not a line of code — and three readiness gates report UNVERIFIED until it is made.

Registry

ERC-8183 escrow

Not built

Would have: A Hire button that escrows a job and releases it. Escrowing is done, on mainnet, with real money; releasing is not.
Why it is not here: fund moved 0.1 of the payment token into job 56681 on BSC mainnet and claimRefund moved it back, both mined. submit has since mined too, on job 56718 — the same flow with a 192-hour expiry instead of twelve, which is the whole difference. What is left is settle, which reverts NotDecided() until the 7-day dispute window runs and is due 13 Sep: a wait rather than a gap, and the only part still unproven on chain. The larger caveat is not the missing call. One wallet was both client and provider on both jobs, so what is proven is the escrow mechanics — money in, money back, a delivery recorded — and not a hire. Nobody was paid by anybody. go_no_go has said so in its own detail line for as long as it has been true; this ledger, which is the thing the site renders, did not, and a caveat that lives only in the gate output is a caveat the reader finds after the claim.