The release verification kit is now browsable.
This page presents the exact secretless commands and public checks the release line expects. It keeps the operator story concrete: package version, first contact, public surfaces, and boundaries all stay visible in one place.
Release line
The kit keeps the synchronized runtime and proof versions obvious.
- xytara 2.13.0
- xoonya 2.13.0
- Synchronized version: 2.13.0
- Synchronized tag: v2.13.0
Commands
These are the same commands the public release process expects builders to be able to run.
- check_npm_xytara: npm view xytara version
- check_npm_xoonya: npm view xoonya version
- check_xytara_first_contact: npx xytara@2.13.0 start-here
- check_xoonya_first_contact: npx xoonya@2.13.0 start-here
- check_public_proof_summary: Invoke-RestMethod https://www.naxytra.com/v1/public-proof-pack/summary | ConvertTo-Json -Depth 8
- check_public_catalog_summary: Invoke-RestMethod https://www.naxytra.com/v1/public-catalog/summary | ConvertTo-Json -Depth 8
- check_xytara_provider_summary: Invoke-RestMethod https://xytara.onrender.com/v1/providers/summary | ConvertTo-Json -Depth 8
- check_xytara_provider_journey_summary: Invoke-RestMethod https://xytara.onrender.com/v1/providers/journeys/summary | ConvertTo-Json -Depth 8
- check_xytara_lifecycle_continuity_summary: Invoke-RestMethod https://xytara.onrender.com/v1/lifecycle-continuity/summary | ConvertTo-Json -Depth 8
- check_xytara_first_run_conversion_summary: Invoke-RestMethod https://xytara.onrender.com/v1/first-run/conversions/summary | ConvertTo-Json -Depth 8
- check_xytara_delivery_summary: Invoke-RestMethod https://xytara.onrender.com/v1/deliveries/summary | ConvertTo-Json -Depth 8
- check_xytara_runtime_durability_summary: Invoke-RestMethod https://xytara.onrender.com/v1/runtime/durability/summary | ConvertTo-Json -Depth 8
- check_xytara_revenue_launch_path_summary: Invoke-RestMethod https://xytara.onrender.com/v1/revenue-launch/paths/summary | ConvertTo-Json -Depth 8
- check_xytara_operator_shell_summary: Invoke-RestMethod https://xytara.onrender.com/v1/operator-shell/summary | ConvertTo-Json -Depth 8
- check_security_reliability_drills_summary: Invoke-RestMethod https://www.naxytra.com/v1/security-reliability-drills/summary | ConvertTo-Json -Depth 8
- check_xytara_market_lanes_summary: Invoke-RestMethod https://xytara.onrender.com/v1/full-catalog/market-lanes/summary | ConvertTo-Json -Depth 8
- check_xytara_market_lane_activation_summary: Invoke-RestMethod https://xytara.onrender.com/v1/full-catalog/market-lanes/activation/summary | ConvertTo-Json -Depth 8
- check_xytara_market_lane_depth_summary: Invoke-RestMethod https://xytara.onrender.com/v1/full-catalog/market-lanes/depth/summary | ConvertTo-Json -Depth 8
- check_xytara_market_lane_trace_summary: Invoke-RestMethod https://xytara.onrender.com/v1/full-catalog/market-lanes/traces/summary | ConvertTo-Json -Depth 8
- check_xytara_market_lane_promotion_summary: Invoke-RestMethod https://xytara.onrender.com/v1/full-catalog/market-lanes/promotion/summary | ConvertTo-Json -Depth 8
- check_full_catalog_claim_summary: Invoke-RestMethod https://www.naxytra.com/v1/full-catalog-claim/summary | ConvertTo-Json -Depth 8
- check_xoonya_trust_portability_summary: Invoke-RestMethod https://xoonya.onrender.com/v1/proof-center/trust-portability/summary | ConvertTo-Json -Depth 8
- check_xoonya_governance_disputes_summary: Invoke-RestMethod https://xoonya.onrender.com/v1/proof-center/governance/disputes/summary | ConvertTo-Json -Depth 8
- check_deployment_fingerprint: Invoke-RestMethod https://www.naxytra.com/v1/deployment-fingerprint/summary | ConvertTo-Json -Depth 8
- check_release_evidence_digest: Invoke-RestMethod https://www.naxytra.com/v1/release-evidence-digest/summary | ConvertTo-Json -Depth 8
- check_release_verification_receipt: Invoke-RestMethod https://www.naxytra.com/v1/release-verification-receipt/summary | ConvertTo-Json -Depth 8
- check_first_run_kit: Invoke-RestMethod https://www.naxytra.com/v1/first-run-kit/summary | ConvertTo-Json -Depth 8
Public checks
The kit’s public checks are the live endpoints that keep the release honest after deploy.
- public_proof_summary: release line 2.13.0
- public_catalog_summary: family, lifecycle, market, provider-runtime, market-lane, and verification counts stay above the full-catalog floor
- xytara_provider_summary: named provider profiles stay publicly bounded with provider-live anchors and revenue-ready entry posture only where listed
- xytara_provider_journey_summary: named provider journeys stay public, first-run ready, proof-followthrough ready, and bounded to the listed quote-fund-execute-prove paths
- xytara_lifecycle_continuity_summary: first-party callable lifecycle stages, dispute followthrough, and xoonya verify followthrough stay public and bounded
- xytara_first_run_conversion_summary: direct x402, credits-first, and result-package proof pickup conversions stay public, revenue-linked where listed, and proof-ready
- xytara_delivery_summary: callback and direct deliveries stay publicly inspectable with worker posture and retry counts
- xytara_runtime_durability_summary: runtime durability posture stays publicly inspectable with blocker state, snapshot presence, and restart persistence visibility
- xytara_revenue_launch_path_summary: day-one revenue launch paths stay public across money-in, paid execution, proof followthrough, reversal, and operator reconciliation
- xytara_operator_shell_summary: operator shell posture stays publicly inspectable as a bounded launch and money-in control surface
- security_reliability_drills_summary: public-safe drills stay publicly inspectable as a bounded launch-hygiene surface
- xytara_market_lanes_summary: all major market lanes stay public, direct-task backed where claimed, and protocol-anchor only where bounded
- xytara_market_lane_activation_summary: callable market lanes stay callable and preview-only protocol-anchor coverage stays explicitly bounded
- xytara_market_lane_depth_summary: compute, messaging, and treasury/payments depth stays activation-ready and bounded
- xytara_market_lane_trace_summary: compute, messaging, and treasury/payments traces stay public, callable, and bounded
- xytara_market_lane_promotion_summary: compute, messaging, and treasury/payments promotion readiness stays public, bounded, and tied to explicit gates
- full_catalog_claim_summary: major-family, lifecycle, market, and verification completeness booleans stay true
- xoonya_trust_portability_summary: trust portability profiles stay public, bounded, and callable across the listed identity, delegation, delivery-history, and settlement-linked trust surfaces
- xoonya_governance_disputes_summary: governance disputes stay public, bounded, and inspectable as a dispute followthrough lane
- deployment_fingerprint_summary: public_safe = true and secret_material_included = false
- release_evidence_digest_summary: sha256 digest over public-safe release evidence
- release_gate_summary: pre-release and post-deploy release gate counts are present
- release_verification_receipt_summary: public-safe release receipt binds digest and executable verifier command
Public proof summary · Catalog summary · Money-in · Go-live · Release receipt · Claim
Boundaries
The kit is strict about the difference between a public check and a private release act.
- release_verification_kit_is_secretless_and_public_safe
- commands_do_not_require_operator_tokens_wallet_material_or_private_release_logs
- npm_and_public_surface_checks_do_not_replace_private_release_gate_evidence
- provider_runtime_breadth_must_be_rechecked_after_each_public_deploy
- full_catalog_claims_must_be_rechecked_after_each_public_deploy
- runtime_durability_must_be_rechecked_after_each_public_deploy
- digest_must_be_rechecked_after_each_public_deploy
Related surfaces
The kit works best when it sits next to the other launch surfaces, not on its own.
Receipt JSON · Receipt page · Proof · Claim · Money-in · Operator shell · Governance disputes · Site map