System overview
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 and keeps consequence, trust, and review explicit.
Runtime engine
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
Proof spine
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
Ownership rules
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 and review stronger for everyone else.