The stack is split cleanly because execution and proof are not the same job.
naxytra is organized around a runtime/commercial surface and a proof/followthrough surface. The split reduces confusion, keeps consequence explicit, and lets builders understand quickly where runtime ends and proof begins.
xytara
xytara owns execution, wallet truth, authority contracts, machine identity, pricing, trust, capability, and participation. It is where runtime consequence is carried.
- Wallet and ledger bundles
- Authority and machine-identity bundles
- Capability registry, pricing, trust, and participation packages
xoonya
xoonya owns result-package review, governance and signoff posture, bridge continuity, proof import, and proof-side trust. It carries explicit followthrough after runtime execution.
- Proof, review, governance, and bridge surfaces
- Role freeze, role transition, and proof-side trust continuity
Why the split matters
Execution, economics, and proof are related, but they should not collapse into one blurred product face. The split makes operation clearer for builders, review stronger for everyone else, and the public story easier to hold in one pass.
What the split maps to
The stack split is useful because the live runtime and proof families are both already visible. Builders can move from the split into the live matrices without guessing where the deeper systems live.
- Runtime families map to provider journeys, lifecycle continuity, delivery, and revenue launch paths.
- Proof families map to native standard, verification services, trust portability, and release review.
- The public catalog and proof pack keep the split inspectable after deploy.
- The first-run path ties the two sides together without collapsing the boundary.
Runtime side · Proof side · Catalog summary · Proof summary · Operator shell · Claim