Main finding
The financial case rests on four operational surfaces, not on replacing the ledger or the control framework: liquidity intelligence across venues and chains, execution and capital efficiency inside a fragmented market, a continuous second reader on smart-contract risk, and token utility tied to usage that already pays. All four are served by one market state that reads prices, depth, flow, funding and on-chain activity together, which is where a world model earns its place. Savings remain internal estimates until the current cost baseline is measured.
What supports it
- Tool-using agents already execute multi-step operational workflows that once required a person moving between systems, and confidence signals let weak output route to a human instead of acting automatically (Yao et al. 2022; Kadavath et al. 2022).
- Instruction tuning makes models follow specified operating procedures more reliably, which is what a control environment requires (Ouyang et al. 2022).
- The dominant smart-contract vulnerability classes are catalogued and updated publicly, which gives a concrete checklist to test against (OWASP Smart Contract Top 10).
- Live transaction monitoring catches behaviour no pre-deployment review can see, because it depends on what the contract actually receives.
- A purchase-and-burn rule is arithmetic executed by a contract: it changes supply, not demand, and implies nothing about price.
- Order-level generative simulators reproduce realistic market dynamics across venues, so a liquidity or execution strategy can be stressed against scenarios before capital moves (Li et al., MarS, ICLR 2025).
- In crypto markets the full book and the chain are observable, and order flow carries information about subsequent returns, which is the strongest observability any forecasting model gets (Journal of Financial Markets, 2026; Kolm et al. 2023).
What this does not claim
- False negatives are the real security risk: a quiet report is not a clean contract.
- Adversarial code can be written to look benign; AI review raises the cost of an attack but does not remove it.
- No time-and-motion baseline has been built, so the efficiency claim is unquantified.
- Oversight, exception handling and audit cost money; they belong in the same comparison as the savings.
- No price appreciation, yield or return is implied by any token design described here.
Planning assumptions used
- The first two pilots are liquidity planning and reconciliation review, both measurable within one quarter.
- All write actions pass through existing approval limits, unchanged.
- Every automated finding is reproduced by a deterministic tool or a test before it is reported.
- Any token layer is built after the intelligence service has paying usage, not before it.
Open before signature
- What are today's cycle time, error rate and cost per process?
- How is the system benchmarked against known incidents and public audit findings?
- Which controls must remain manual by policy or regulation?
- Does the licence permit using the security and liquidity outputs commercially?
Sources
- OWASP Smart Contract Top 10
- Yao et al., ReAct (2022)
- Ouyang et al., Instruction following with human feedback (2022)
- Li et al., MarS: a financial market simulation engine (ICLR 2025)
- Order Flow and Cryptocurrency Returns (Journal of Financial Markets, 2026)
- Kolm et al., Deep order flow imbalance (2023)
- Internal economics research
Figures marked illustrative are planning assumptions. This note separates published evidence from project assumptions and does not present a supplier quotation, a valuation or a forecast of returns.