Ramp
A field sweep, in order.
Three things on this list are built and running on every deploy. Everything under Next and Later is a description of something that does not exist.
The list
Two instruments anybody can run
The Gauge measures any Uniswap V3-style pool on Base and the Moment bench measures any ERC-4626 vault, both from the reader’s browser with no key, no wallet and no server. They import the same modules as the published scan.
The contract, executable in the page
Yoke.sol compiles, 14 properties run on a real EVM through an eth_call state override, and the four sabotaged builds ship so a reader can watch the suite bite.
The measurement, and its own reproduction
The 48-hour scan is published with the previous run beside it, because the statistic that reproduces and the one that does not are the finding.
A Yoke you can deploy and use
Not a canonical one — YOURS. Four transactions from your own wallet put a test token and a Yoke on Base Sepolia, and deposit, Field and redeem are real calls after that. What is still missing is a single shared deployment, which needs a funded key this repository does not hold: put an address in brand.deployments and every marker on the site follows.
Holding time on the vault page itself
Every rate a Yoke reports carries the sample size behind it — the same estimator that runs on the Gauge and the Moment bench.
Audit, then mainnet
In that order. The property suite in this repository is a floor and not a substitute; nothing here has been through third-party review.
Audit, then mainnet. In that order.
The suite executes 15 properties on an EVM and confirms that 4 sabotaged copies each fail it. That is a floor. It was written by the same hand as the contract and tests what that hand thought of, which is exactly the failure mode third-party review exists for.