Proof, review, and followthrough infrastructure.
xoonya is the proof-side spine for result packages, governance, bridge continuity, and machine-review followthrough. It keeps proof, review, and continuity visible after runtime execution has happened.
What xoonya owns
xoonya is the proof side of the stack. It owns result-package review, governance and signoff posture, bridge and compatibility followthrough, proof import, and proof-side intelligence.
- It does not own runtime wallet, ledger, pricing, or fiat-ingress truth.
- It sits after runtime execution, carrying proof-side continuity explicitly.
Public proof surfaces
Purchasable today: post-quantum proof verification (proof.verify-signature, proof.verify-bundle; Ed25519 + ML-DSA-65) through the runtime's paid adapter.xoonya.invoke task at $0.01 USDC on Base mainnet ($0.001 USDC on Base Sepolia testnet), or $0.02 for the two attesting tools. Free: building and verifying native proof bundles on the public xoonya routes. The wider proof catalog (trust, review, governance, bridge, proof import) is reference material.
- Proof bridge, external proof import, result-package trust, ERC-8004, telemetry, provenance
- Role and package surfaces that keep xoonya's place in the stack explicit
Proof catalog and trust breadth
xoonya's public proof face now carries 6 proof integrations, explicit provider and framework lanes, canonical and major-rail evidence families, proof bridge continuity, interface and interop contracts, and proof-side operational trust surfaces.
- Works with MCP and agent clients such as: claude mcp, openai codex (client compatibility profiles, not partnerships)
- Framework compatibility profiles: autogen, langchain, langgraph, semantic kernel
- Canonical rails: evm, base, usdc (live: x402 USDC on Base); bsv_teranode (catalog/reference only, not live settlement)
- Major rails family: antelope, proton_xpr_and_metal, solana (catalog/reference only, not live settlement)
- Proof lanes: proof_bridge, external_proof_import, result_package_trust, erc8004
Native proof standard
xoonya's native proof standard stays optional, deterministic, and method-agnostic. It gives builders a clear proof-side path without pretending that every upstream identity or verifier format belongs to the same native truth.
- Native standard: xoonya proof posture with explicit boundaries
- Verification services: public review and bundle inspection paths
- Trust portability: continuity across profiles, bundles, and venues
Verification services
xoonya's verification-services lane is the public inspection point for bundle review, proof followthrough, and release-side trust checks. It gives the proof side a concrete place to look before or after runtime work moves through the system.
- Bundle verify and followthrough checks stay inspectable
- Proof review remains public, bounded, and machine-readable
- Verification posture stays separate from runtime ownership
Trust portability
Trust portability keeps xoonya honest across venues: profiles can move, evidence can carry, and continuity can be inspected without pretending every verifier format collapses into a single native truth.
- Profiles stay bounded but portable across bundles and venues
- Identity and proof continuity remain public and reviewable
- Portability is a service, not a hidden assumption
Governance disputes
xoonya's governance-disputes lane is a catalog capability for cross-package case followthrough: case review, case bundles, and resolution packs. Case data is governance material and is not published on the public site.
- Case review, case bundles and resolution packs are catalog capabilities
- Dispute case data stays with operators; nothing here is a live case count
Proof-side start path
Install the xoonya verifier (the proof engine itself is hosted; the package verifies proofs and signatures offline), run the one-line start path, then verify native proof bundles, detached signatures and the published conformance vectors from CLI, API, browser, chat, or any environment that can issue commands or HTTP calls.
- npm install xoonya
- xoonya start-here
- xoonya first-run --verify-native --pretty
- xoonya conformance --json
Where proof sits in the stack
xoonya is the proof side of the system, and it works best when it stays visibly linked to the rest of the public map. This page points back to the stack split, the first-run path, the catalog, and the release line so the proof surface never feels detached from the live product.
- The stack page explains the runtime/proof split.
- The try and start pages show the builder loop.
- The catalog page shows the proof matrices (reference).
- The releases page shows the deploy and release signals.
- The claim page shows the full catalog claim.