The short proof that this is live, installable, and bounded.

Release line

The public stack is one website, one bootstrap package, and two product packages. The release line is intentionally simple.

• naxytra 3.1.0: npm install naxytra
• xytara 3.1.0: npm install xytara
• xoonya 3.1.0: npm install xoonya
• naxytra start-here
• xytara start-here
• xoonya start-here

Live readiness

The evidence pack points to the live readiness surfaces that matter for launch: runtime readiness, settlement readiness, frozen runtime truth, frozen adapter/protocol truth, frozen proof-side truth, and the final 3.0.0 contract and gate surfaces.

• xytara launch readiness: launch-ready state with zero blocking issues
• xytara native settlement readiness: ready=true for the configured launch settlement path
• xytara execution truth: the frozen execution-truth summary is reachable and bounded to the claimed runtime quote_execute_deliver_settle_prove path
• xytara adapter and protocol truth: the frozen adapter-and-protocol truth summary is reachable and keeps first-party defaults and bounded bridge breadth explicit
• xytara provider runtime breadth: named provider profiles stay public, revenue-ready only where listed, and provider-live anchors remain explicitly bounded
• xytara provider runtime journeys: named provider quote, fund, execute, and prove paths stay publicly inspectable and bounded to listed provider journeys
• xytara first-run conversions: launch-grade quote, funded execution, proof pickup, and inspection paths stay publicly inspectable as bounded first-run conversion contracts
• xytara delivery summary: delivery counts and callback delivery posture stay publicly inspectable
• xytara runtime durability: runtime durability posture stays publicly inspectable as explicit recovery and blocker state
• xytara revenue launch paths: day-one revenue paths include money-in, paid execution, proof followthrough, refund/reversal, and operator reconciliation
• xytara operator shell: operator shell posture stays publicly inspectable as a bounded launch and money-in control surface
• security reliability drills: public-safe drills stay publicly inspectable as a bounded launch-hygiene surface
• xytara full catalog: major family, lifecycle, and market matrices are surfaced as a governed runtime catalog
• xytara market lanes: compute, data, storage, messaging, device/robotics, and treasury/payments stay inspectable as bounded market-class lanes
• xytara market lane activations: callable market lanes stay callable while device/robotics remains preview-only unless deeper evidence exists
• xytara market lane depth: compute, messaging, and treasury/payments expose explicit depth summaries with bounded callable and provider-anchor posture
• xytara market lane traces: compute, messaging, and treasury/payments expose explicit callable transaction traces that stay bounded to listed surfaces
• xytara market lane promotion: compute, messaging, and treasury/payments promotion readiness stays publicly bounded to listed gates, traces, and evidence posture
• xytara framework provider promotion: LangGraph and LangChain stay reference-contract adapters unless live endpoint, auth, health, latency, and failure evidence exists
• xoonya proof truth: the frozen proof-truth summary is reachable and keeps canonical proof objects deterministic, portable, and inspectable
• xoonya XNYA conformance mark: XNYA-compatible mark remains tied to exact vectors, error codes, and claim boundaries
• xoonya XNYA reference implementations: JavaScript canonical reference is implemented; Python candidate scaffold has atom/payload/frame, non-signed proof-bundle parity, and reproducible optional Ed25519 crypto verification; Rust source scaffold is packaged but not vector-verified
• xoonya verification services: bundle, delivery, settlement, dispute replay, identity-link, and anchor/finality verification stay first-class services
• xoonya trust portability: identity, delegation/capability, delivery history, and settlement-linked trust portability stay publicly bounded to the listed proof-facing followthrough surfaces
• xoonya governance disputes: governance disputes stay public, bounded, and inspectable as a followthrough lane
• naxytra partner activation pack: partner activation remains bounded to runtime-first, packaged, adapter-author, and proof-followthrough tracks with blocked overclaims
• naxytra full catalog claim: major-family, lifecycle, market-class, and verification-service completeness claims stay public and bounded
• naxytra deployment fingerprint: release line and runtime deployment identity are public-safe and carry no secret material
• naxytra release evidence digest: public-safe release evidence has a deterministic SHA-256 digest
• naxytra release verification kit: outside builders get secretless npm, first-run, public proof, deployment, and digest checks
• naxytra release verification receipt: release verification requirements are represented as a public-safe receipt model

JSON proof pack · Summary JSON · 3.0.0 contract · 3.0.0 gates · Activation path · Release kit · First-run kit · Safety drills · Governance disputes · Evidence digest · Money-in · Go-live · Release gates · Activation summary · Evidence template

Boundaries

The proof pack is useful because it states what is real and what should not be overclaimed.

• do not claim every possible rail is live
• claim governance disputes only as bounded followthrough, not as standalone runtime truth
• do not expose private custody refs, wallet refs, credentials, or gateway internals
• do not publish secretless public first-run commands with wallet secrets, bearer tokens, private keys, or angle-bracket placeholders
• do not directly reference external storefront brands or legacy native-format names from public naxytra/xytara/xoonya surfaces
• claim treasury live rails only when public claim boundaries match configured profile states and public surfaces do not expose landing or custody refs
• claim operator observability only as read-only visibility, not as fund movement, settlement submission, mutation, or secret-bearing control plane behavior
• describe external money-in lanes as gateway and adapter-bound
• claim provider runtime breadth only for the named provider profiles and their listed public gates, not as unbounded external-provider platform coverage
• claim provider depth only for task refs and tool bindings listed by adapter-depth surfaces
• claim full-catalog completeness only when the public catalog, full catalog claim pack, and verification-service summaries agree on the same family, lifecycle, and market matrices
• claim major market-class coverage only when dedicated market-lane surfaces remain public and bounded
• claim callable market-lane depth only when activation summaries still distinguish callable and preview-only postures
• claim deeper callable market-lane depth only when the dedicated depth summaries remain public, activation-ready, and bounded to listed compute, messaging, and treasury surfaces
• claim market-lane transaction traces only when the dedicated trace summaries remain public and bounded to the listed compute, messaging, and treasury consequence paths
• claim market-lane promotion readiness only when the dedicated promotion summary agrees with the public depth and trace summaries for the same bounded compute, messaging, and treasury surfaces
• claim trust portability only for the listed identity, delegation, delivery-history, and settlement-linked trust surfaces without implying global identity, custody, or chain truth
• claim framework providers as live only after framework-provider promotion evidence exists
• claim partner activation only as bounded next-phase outreach, not as partner adoption already achieved
• claim partner adoption outcomes only from private redacted partner activation evidence manifests
• claim deployed runtime identity only from the public-safe deployment fingerprint and keep private deploy logs outside public JSON
• claim release evidence digest only as a public-surface digest, not proof that private operator commands were run
• claim release verification kit only as public self-check guidance, not private release gate evidence
• claim release verification receipt only as a public model until the executable verifier passes in an operator or builder shell
• claim production tracker counts only when tracker freshness verification passes against generated summaries
• claim private drills as completed only from private operator evidence manifests, not public templates
• claim pricing optimization maturity only after experiment plans clear live-sample and operator-review gates
• claim delivery summary visibility only as an operator-observable posture for callback and direct deliveries, not as proof of every callback target response
• claim runtime durability only as an explicit recovery posture and blocker state, not as proof that every restart environment is fully persistent
• claim operator shell only as a browsable launch and money-in control surface, not as mutation authority or settlement control
• claim security reliability drills only as public-safe launch hygiene surfaces, not as private operator evidence
• claim day-one revenue launch readiness only when money-in, paid execution, proof followthrough, reversal, and operator reconciliation paths remain publicly inspectable and bounded
• claim external proof issuer, signature, revocation, or DID-resolution truth only when external verifier evidence refs exist
• claim native proof as optional, while keeping xoonya method-agnostic
• claim XNYA-compatible only when exact vectors, errors, byte rules, and mark boundaries are satisfied
• claim Python or Rust XNYA references only after full independent vector parity, always-on signature-suite verification, round-trip gates, conformance-mark review, forbidden-claim review, and reference-promotion evidence validation pass

Public evidence

The short public story is live website, installable packages, frozen runtime/proof truth surfaces, and a canonical end-to-end verifier.

• naxytra.com is the single public website
• xytara is installable as the runtime package
• xoonya is installable as the proof package
• The public first-run path shows quote, funding, execution, proof, and inspection as one bounded builder flow
• The public first-run command kit is guarded by deterministic rejection codes for PowerShell-hostile placeholders, secret material in secretless commands, and quote-only regressions
• Public naxytra surfaces are checked for independence from external storefront brands and legacy native-format naming
• xytara exposes launch readiness, settlement readiness, frozen execution truth, frozen adapter-and-protocol truth, framework-provider promotion, and treasury public-boundary surfaces
• xytara exposes named provider runtime breadth profiles so OpenAI Codex and Claude MCP stay publicly bounded to the listed callable entry paths, provider-live anchors, and proof-followthrough posture
• xytara exposes named provider runtime journeys so OpenAI Codex and Claude MCP have explicit quote, fund, execute, prove, and inspect paths instead of implied launch narratives
• xytara exposes first-run conversion contracts so direct x402, credits-first, and result-package proof pickup paths stay publicly inspectable as launch-grade quote-to-proof loops
• xytara exposes a governed full-catalog matrix with explicit protocol-family, lifecycle-stage, market-class, claim-status, and evidence-status metadata
• naxytra exposes public evidence lanes for adapter certification, trust portability boundaries, and signed audit/provenance on the umbrella website
• xytara exposes a lifecycle continuity summary so first-party callable stages, dispute followthrough, and xoonya verify followthrough stay publicly legible as one bounded rail
• xytara exposes dedicated market-lane summaries for compute, data, storage, messaging, device/robotics, and treasury/payments with explicit bounded claim posture
• xytara exposes canonical market-lane activation paths so callable market classes and preview-only protocol-anchor lanes remain publicly distinguishable
• xytara exposes dedicated market-lane depth summaries for compute, messaging, and treasury/payments so the next callable depth layer stays inspectable without overstating provider breadth
• xytara exposes dedicated market-lane traces for compute, messaging, and treasury/payments so each deeper lane has a public end-to-end consequence path
• xytara exposes dedicated market-lane promotion summaries for compute, messaging, and treasury/payments so stronger bounded live claims stay tied to explicit gates and evidence posture
• xytara exposes operator observability as a read-only surface without mutation, fund-movement, settlement-submission, or secret-material affordances
• xytara exposes an operator shell summary so launch visibility and money-in stay publicly inspectable as a bounded control surface
• xytara exposes security reliability drills so launch hygiene stays publicly inspectable as a bounded public-safe surface
• xoonya exposes a frozen proof-truth summary with deterministic and replayable proof posture
• xoonya exposes first-class verification services for bundle, delivery, settlement, dispute replay, identity-link, and anchor/finality review
• xoonya exposes a governance disputes summary so dispute case and open-case posture stay publicly inspectable as a bounded followthrough lane
• xoonya exposes cross-venue trust portability profiles for agent identity, delegation/capabilities, delivery history, and settlement-linked trust followthrough
• xoonya exposes an external proof import gate that rejects issuer, signature, revocation, or DID-resolution truth claims unless external verifier refs exist
• xoonya exposes an XNYA conformance mark boundary for native standard compatibility claims
• xoonya exposes an XNYA reference implementation plan with JavaScript canonical reference, Python non-signed proof-bundle plus reproducible optional Ed25519 crypto verifier, Rust source-only scaffold boundary, and deterministic reference-promotion evidence gate
• naxytra exposes a full catalog claim pack that ties family coverage, lifecycle coverage, market coverage, and verification coverage together under one public-safe claim surface
• naxytra exposes a partner activation pack that converts adoption intelligence into bounded tracks, gates, blocked claims, and proof evidence links
• naxytra exposes a partner activation evidence template so private partner outcomes can be recorded without leaking secrets or partner-confidential material
• naxytra exposes a deployment fingerprint so public release line and runtime deployment identity can be inspected without private operator evidence
• naxytra exposes a deterministic public release evidence digest for the public-safe release proof surfaces
• naxytra exposes a secretless release verification kit for outside builders to independently check npm packages and public release surfaces
• naxytra exposes a public-safe release verification receipt that binds the release line, digest, and executable verifier without claiming private command execution
• naxytra verifies the production tracker stays aligned with generated public proof and expansion closeout counts
• xytara exposes delivery summary posture tying callback and direct deliveries into inspectable worker, retry, and signing visibility
• xytara exposes runtime durability posture tying snapshot recovery, blocker state, and restart persistence into inspectable operator visibility
• xytara exposes revenue launch paths tying hosted checkout, credits, paid execution, proof followthrough, refund/reversal, and operator reconciliation into inspectable day-one revenue motion
• The canonical end-to-end verifier exercises credit grant, execution, result export, proof pickup, and proof verification

Where proof sits in the stack

Proof is most useful when it stays visibly connected to the rest of the public stack. This page points back to the stack split, the first-run path, the catalog, the final 3.0.0 contract, and the release line so evaluators can move between proof and the live system without losing context.

• The stack page explains the runtime/proof split.
• The start and try pages show the first-run loop.
• The operator shell page shows the commercial control surface.
• The catalog page shows the live matrices behind the proof claims.
• The releases page shows the deploy and release signals.
• The final 3.0.0 contract and gates show the exact launch bar.
• The go-live page shows the current launch-readiness posture.
• The claim page shows the full catalog claim.
• The disputes page shows governance followthrough.

Stack · Start · Catalog · Money-in · Operator shell · Claim · 3.0.0 contract · 3.0.0 gates · Governance disputes · Go-live · Site map · Releases

Native proof standard

xoonya keeps native proof optional, deterministic, and method-agnostic. The public surface exposes the native standard, the anchor profile, verification services, and trust portability so evaluators can inspect the proof side without assuming any one external verifier replaces the others.

• Native proof stays optional rather than mandatory
• Anchor binding is visible without claiming external chain or issuer truth
• Verification services and trust portability remain first-class public surfaces

Native standard · Anchor profile · Verification services · Trust portability