MetaState Link

NWO-ASM is the assembly language; MetaState is the substrate it routes to. The Link layer is a thin, opt-in bridge — describe a process matrix, hand it to MetaState, and let the free-energy optimizer pick a substrate, re-verify the inference, and settle. The bridge is opt-in and honest about what it does.

How NWO-ASM talks to MetaState

An NWO-ASM program emits a process-matrix request, which is signed and sent to MetaState. The substrate scores it, routes to a backend, re-verifies the inference, and returns a signed proof plus calldata to settle in USDC on Base.

What you can call

Every endpoint below is reachable from NWO-ASM via the metastate standard library. Endpoint URLs resolve to the live MetaState Space; the Agent Card describes them in machine-readable form.

Calling MetaState from NWO-ASM

The standard library wraps every endpoint with a typed call. Errors surface as compile-time guards on signature mismatch; runtime guards on signature failure.

use metastate.{anomaly, symbolic, quantum, poi, anchor}

fn route_one(s: f32[N]) -> (proof, calldata) {
  let v = anomaly.score(s)                # free-energy bound
  let e = symbolic.regress(s, v)          # closed-form residual
  let h = quantum.route(pmx.lift(e), {     # place the process matrix
    prefer:  qpu,
    fallback: gpu,
  })
  let p = poi.verify(h)                   # re-verified inference
  let c = anchor.prepare(p, usdc(base))   # calldata for the splitter
  (p, c)
}

Where it lives

Pay-per-call · no new contract

Every MetaState call settles through the deployed MetaStateSplitter at 0x93a7…1BE4 on Base mainnet. NWO-ASM reuses this contract directly — no new deployment, no new audit surface.

What the link is built on