Misquote
the go/no-go status loaded.

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

11 passed · 0 failed · 4 unverified, of 15 gates.

Not run. --fast skipped offline test suite, replay invariants (T1-T4, L1), web browser suite, web component suite, lint, chain and fork suite — absent from the counts above, not passing.

Gates

All 15 gates.

kill switch

7 passed, 206 deselected, 1 warning in 2.26s

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

4 tasks on a chain tape, all quotable

PASS

artifacts match the engine

6 replay artifact(s) were generated before an engine change

  • build.json — 8 engine commits since
  • warden.json — 8 engine commits since
  • grid.json — 8 engine commits since
  • sentinel.json — 8 engine commits since
  • advantage.json — 12 engine commits since
  • advantage_short.json — 12 engine commits since

→ regenerate them (make showcase, make advantage) — or accept that the published numbers describe an engine that has since changed

UNVERIFIED

agent identities

4 agents registered on chapel and owned by 0x0c501EE1924bfb91a028DB4BcD68f4861B0Ff6eE

PASS

24h testnet burn-in

warden journal records chain(s) [56], not chapel only

→ this gate is the testnet burn-in; run it with --chain 97

UNVERIFIED

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
Router registered and deployed through the BNB Agent Studio CLI, as the native-citizenship proof — an ERC-8004 identity of its own, an ERC-8183 task interface, and x402 self-funding.
Why it is not here
The CLI installs from npm and its bag binary offers erc8004, erc8183 and x402 commands. Nothing has been deployed through it. The custody objection recorded here applied to one flag: only --provider bnb with a local wallet sends a key to the vendor. --destination self deploys to your own cloud, and that needs cloud credentials nobody has supplied.
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
The four a transaction can demonstrate now 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. Release was never reachable there: submit needs an expiry beyond the 7-day dispute window and the run asked for 12 hours. Proven on a fork, not on the chain, and it would lock the budget for a week.