Matrix doesn't ask a model to "do things." It asks a model to compile your words into Intent IR — a typed, versioned, replayable plan format — and then executes the IR, not the prose.
{
"ir_version": "3",
"planner": "kimi-k2.6", // recorded in every plan
"verbs": ["swap", "stream.open"], // from the closed vocabulary
"steps": [
{ "verb": "swap",
"tool": "pax://dex/router@v3.2", // version-pinned URI
"in": { "asset": "USDC", "amount": 250 },
"out": { "asset": "PAX", "min": 21.7 },
"bounds": { "slippage_bps": 50, "deadline_s": 12 } },
{ "verb": "stream.open",
"tool": "pax://precompile/0x0906@v1",
"rate": "50 PAX/week", "to": "dev-payroll.pax", "duration": "4w" }
],
"gate": { "simulate": true, "guardrails": "profile:default" }
}
Every plan is composed from a finite, audited verb set. New verbs ship through review and versioning — never improvised by the model at runtime.
Tool URIs pin the contract, precompile, or service version. The plan that simulated is byte-identical to the plan that executes.
IR is replayed against forked live state. You see the outcome diff — balances, positions, fees — before approving.
Every executed IR is stored with its planner version and rate-table version. Any plan can be re-simulated later, deterministically.
swap · bridge · sendValue movement
stream.open · stream.close · scheduleTime-based · 0x0905/0x0906
lp.add · lp.remove · rebalance · hedgePositions
deploy · call · query · attestContracts · TEE 0x0907
hire · quote · settle.netDeus services
watch · notify · approveConditions & consent
sign.eip712Identity · 0x0908
+ proposalsNew verbs ship via governance review
| Parameter | Value |
|---|---|
| IR schema | v3 · JSON, typed, canonical ordering |
| Verb count | 21 (closed; governance-extended) |
| Planner | kimi-k2.6 · version recorded per plan |
| Plan latency, p50 | < 1.8 s single-verb · < 3.5 s multi-verb |
| Simulation | forked state replay, deterministic |
| Settlement | HyperPaxeer chain 125 · 400 ms finality |
Because money. Open tool calling trades predictability for flexibility; with on-chain execution that trade is unacceptable. A closed set means every reachable behavior is enumerable, auditable, and testable in advance.
Yes — verbs are proposed, reviewed, and shipped with a vocabulary version bump. Existing plans keep executing against the version they were compiled with.
The planner can only emit IR that validates against the schema and vocabulary. Anything else is rejected before simulation. The model proposes; the type system disposes.