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
This lane is now real in the bounded way we want: hybrid verification is live for registered runtime-supported suites that are covered by vectors and deterministic verification behavior. We still avoid pretending every possible PQ path is live, but the core hybrid proof lane is no longer only future posture.
- 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.0.0 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.
Agents · Docs · Claim · Money-in · Operator shell · Site map