Release surface

The public release line is already live.

This site is not standing in for a future release. It sits on top of active npm packages, GitHub releases, and release-pack surfaces that already summarize the live stack, so launch messaging can point to working artifacts instead of future intent.

Install xytara Install xoonya

Runtime release

xytara 3.1.0

The active runtime line already exposes release-pack, adoption, scenario, launch, and manifest surfaces alongside the package and service contract.

Install: npm install xytara
Verify: npm run verify:all
Release CLI: xytara release --summary
First contact: xytara start-here

Proof release

xoonya 3.1.0

The active proof line already exposes release-pack, adoption, scenario, launch, and proof-center surfaces alongside the package and service contract.

Install: npm install xoonya
Verify: npm run verify:all
Release CLI: xoonya release --summary
First contact: xoonya start-here

What matters

Launch-ready posture

The release story is strongest when people can move from install to start-here to release summary to real service surfaces without getting lost in internal history.

naxytra npmInstallable umbrella bootstrap package xytara npmInstallable runtime package xoonya npmInstallable proof package xytara pathRuntime product surface xoonya pathProof product surface Full catalog claimPublic claim surface 3.0.0 contractFinal major-version claim surface 3.0.0 gatesFinal major-version gate surface Operator shellCommercial control surface Activation pathPartner launch surface Release kitVerification command surface First-run kitBuilder command surface Safety drillsOperator drill surface Governance disputesCase followthrough surface Evidence digestRelease evidence surface Money-inCommercial entry surface Go-liveLaunch readiness surface

Live control

Release and deploy signals

Release confidence comes from the same pages people can inspect after deploy: the fingerprint, the public proof pack, the release gates, the final 3.0.0 contract, and the catalog summary. Those are the live receipts, not just internal notes.

Deployment fingerprint stays public and synchronized to the current tag.
Public proof pack stays the first serious external check.
Release verification receipt keeps the deploy story readable after the fact.
Release gates keep the line honest after every push.
The final 3.0.0 release contract freezes what the major-version line does and does not claim.
The final 3.0.0 gate pack freezes the exact launch-grade check chain.
Catalog summary shows the current public breadth in one place.
Claim summary ties the broader public matrices together.

Deployment fingerprint · Public proof summary · Release receipt · Operator shell · Activation path · Release kit · First-run kit · Safety drills · Governance disputes · Evidence digest · Release gates · 3.0.0 contract · 3.0.0 gates · Money-in · Go-live · Release gates · Claim · Full catalog summary · Catalog summary · Site map