The support lanes are part of the product, not hidden glue.
This page makes the non-rail production bedrock visible from the umbrella surface. It shows the observability, provenance, artifact, signal, control, auth, identity, and stronger-crypto readiness lanes that make the runtime and proof system production-grade for agents, operators, and machine-to-machine workflows.
Runtime support bedrock
The runtime side needs more than execution and payment. These support lanes are what make automation inspectable, governable, and safe to run at production scale.
- Telemetry standards: 1
- Provenance focal surfaces: 4
- Artifact distribution families: 4
- Shared signal families: 4
- Feature-control focal controls: 5
- Auth interop profiles: 4
- Identity interop profiles: 4
xytara telemetry · xytara provenance · xytara artifact distribution · xytara shared signals · xytara feature control · xytara auth interop · xytara identity interop
Proof support bedrock
The proof side carries the same seriousness. The support lanes keep verification portable, inspectable, and compatible with external trust systems without weakening the native proof core.
- Telemetry standards: 1
- Provenance focal surfaces: 4
- Artifact distribution families: 4
- Shared signal families: 4
- Feature-control focal controls: 5
- Auth interop profiles: 3
- Identity interop profiles: 4
xoonya telemetry · xoonya provenance · xoonya artifact distribution · xoonya shared signals · xoonya feature control · xoonya auth interop · xoonya identity interop
Stronger crypto readiness
Post-quantum verification is real and bounded. xoonya verifies the native XNYA proof format with hybrid signatures: hybrid Ed25519 + ML-DSA-65 (FIPS-204) has been verified live via the paid x402 lane on Base mainnet, returning a verified native-hybrid-signature verdict; SLH-DSA-SHA2-128f (FIPS-205) hybrids are implemented and vector-covered in the SDK (not yet exercised through the paid lane). Adversarially, downgrade-to-classical and the unsigned 'none' algorithm are both rejected. This is machine-evidence verification, not an identity, custody, or chain-truth claim.
- Hybrid Ed25519 + ML-DSA-65 (FIPS-204) verified live via the paid x402 lane on Base mainnet; SLH-DSA-SHA2-128f (FIPS-205) hybrids are implemented and vector-covered in the SDK (not yet exercised through the paid lane). Native XNYA machine-evidence format.
- Adversarial: downgrade-to-classical rejected; unsigned 'none' algorithm rejected. Proven via the paid x402 lane.
- Status: implemented
- Implemented classical suites: 5
- Implemented hybrid suites: 6
- Gated candidate suites: 4
- Promotion requirements: 8
- Current decision: claim registered native hybrid verification only for runtime supported vector covered suites
Hybrid readiness summary · Native standard · Native atom spec · Proof
What this unlocks
This support surface is what keeps the bigger 3.9.13 promise honest. Agents need not just execution and payment, but also reliable signals, artifact flow, identity and auth interop, and visible stronger-crypto posture if we want a truly production-grade machine stack.
- Outside agents can inspect the stack support posture without reading private operator notes.
- Operators can point people at one umbrella-visible route instead of package-local fragments.
- Support-lane truth now sits next to runtime, proof, release, claim, and money surfaces.
- This keeps the final release focused on implementation, not softer wording.