Vigi Autonomous Escrow
The economic primitive the rest of the ecosystem draws on: value released when an agreed condition is demonstrated cryptographically, with nobody in the middle deciding whether it was met. The foundation is already in consensus and audited. The general condition — one that is neither a signature nor a block height — is the piece still missing.
The ten layers
A policy can require one post-quantum signature, an M-of-N quorum, or a height timelock wrapping either — and a timelock can wrap a quorum, so real arrangements express directly. Two conditional releases already run on this: a rollup exit against an inclusion proof, and a treasury spend against its registered policy.
Everything above releases on who signed or on when. Machine-to-machine contracts need a third kind: release on a proof that a service was delivered — storage still holding data, a computation performed, an API available. That is an extension to an audited primitive rather than a new subsystem, which is why it is stated as partly built and not as designed.
Storage payments, Proof of Recovery, compute, availability, dataset delivery and software delivery all need the same thing: value that cannot move until evidence exists. Building that once, in the layer everything shares, is what stops each service from inventing its own half-trusted settlement.
Autonomous escrow works where a condition can be demonstrated, not where it must be judged. Whether a file is still recoverable can be proven; whether a design is beautiful cannot. Disputes that need human judgement are outside this primitive on purpose — pretending otherwise would put an arbitrator inside a system built to remove one.
Sovereign post-quantum network for verified value.
Post-quantum cryptographic security software: a sovereign network that strengthens custody, settlement and identity. Testnet active; mainnet opens when independent validation supports it. Ten layers, each with its own page and its real state on it: four running, six still a design.
