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

Release line

The public stack is one website and two npm packages. The release line is intentionally simple.

• xytara 2.11.0: npm install xytara
• xoonya 2.11.0: npm install xoonya
• 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, execution truth, adapter depth, and proof-center posture.

• 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: execution truth summary is reachable and bounded to claimed runtime paths
• xytara adapter depth: provider-live adapter depth remains explicitly bounded
• 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 framework provider promotion: LangGraph and LangChain stay reference-contract adapters unless live endpoint, auth, health, latency, and failure evidence exists
• xoonya proof center: proof center reports deterministic, portable, replayable proof posture
• 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
• 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 · 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
• 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 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 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 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, runtime readiness, proof readiness, 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, execution truth, adapter-depth, framework-provider promotion, and treasury public-boundary surfaces
• xytara exposes a governed full-catalog matrix with explicit protocol-family, lifecycle-stage, market-class, claim-status, and evidence-status metadata
• xytara exposes dedicated market-lane summaries for compute, data, storage, messaging, device/robotics, and treasury/payments with explicit bounded claim posture
• xytara exposes operator observability as a read-only surface without mutation, fund-movement, settlement-submission, or secret-material affordances
• xoonya exposes a proof-center 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 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
• The canonical end-to-end verifier exercises credit grant, execution, result export, proof pickup, and proof verification