Release receipt
The release receipt keeps the deploy story inspectable.
This page turns the live release-verification receipt into a browsable public surface. It binds the synchronized version, digest, fingerprint, kit, and release gates into one readable receipt without exposing secrets or private operator logs.
What it ties together
Receipt binding
The receipt stays focused on the public release line and the evidence that can be checked after deploy.
- xytara 3.9.13
- xoonya 3.9.13
- Synchronized version: 3.9.13
- Synchronized tag: v3.9.13
- Deployment commit: bde47e1eefb2
- Runtime provider: vercel
Public anchors
Checks
The receipt lists the checks a builder can inspect without touching private release systems.
- package_registry_versions: externally_verifiable
- public_proof_summary: public_surface_bound
- deployment_fingerprint_summary: public_surface_bound
- release_evidence_digest_summary: public_surface_bound
- release_verification_kit_summary: public_surface_bound
- operator_shell_summary: public_surface_bound
- security_reliability_drills_summary: public_surface_bound
What it will not claim
Boundaries
The receipt is deliberately strict about what it does not imply.
- receipt_is_a_public_safe_verification_model_not_private_operator_evidence
- public_server_does_not_execute_npm_shell_or_private_release_commands
- receipt_claim_is_completed_only_when_the_executable_verifier_passes
- secret_values_wallet_material_and_private_logs_are_not_part_of_this_receipt
Release control surface
Live receipts
The release receipt sits alongside the other public release surfaces so the deploy story stays coherent from multiple angles.
Receipt summary · Public proof summary · Release gates · Claim · Site map