Release gates

The release gate pack is now browsable.

This page makes the pre-release and post-deploy gate chain easy to inspect without falling into private logs or operator tickets. It’s the public operator map for the checks that keep the line honest.

View JSON gates 3.0.0 gate summary
What the chain covers

Gate phases

The gates split into pre-release local checks, post-deploy public surfaces, and post-deploy operator commands.

  • pre_release_local: prove local package, service, full-catalog, verification-service, command, evidence, and smoke gates before synchronized release work
  • post_deploy_public_surfaces: prove the deployed public JSON surfaces, full-catalog claims, and verification-service summaries still agree after deploy
  • post_deploy_operator_commands: prove public independence, proof coherence, full-catalog coherence, package/release distribution, and public release verification state from one operator shell
Repeatable checks

Verifier scripts

These are the command names the release gate pack expects to remain available.

  • verify:service
  • verify:provider-runtime-breadth
  • verify:provider-runtime-journeys
  • verify:first-run-conversions
  • verify:delivery-summary
  • verify:runtime-durability
  • verify:revenue-launch-paths
  • verify:market-lanes
  • verify:market-lane-depth
  • verify:market-lane-traces
  • verify:market-lane-promotion
  • verify:trust-portability
  • verify:full-catalog-coherence
  • verify:first-run-kit-boundary
  • verify:public-independence-boundary
  • verify:partner-activation-evidence
  • verify:security-drill-evidence
  • verify:release-smoke
  • verify:release-line-drift
  • verify:deployment-fingerprint
  • verify:release-evidence-digest
  • verify:release-verification-kit
  • verify:release-verification-receipt
  • verify:release-gate-evidence
  • verify:tracker-freshness
  • verify:pre-deploy-gates
  • verify:public-proof-coherence
  • verify:release-distribution
  • verify:public-release-verification
  • verify:post-deploy-gates
  • verify:release-gates
Why this matters

Gate summary

The release gate page keeps the deploy logic legible and ties the public proof, digest, receipt, release-verification kit, support lanes, ecosystem lanes, and final 3.0.0 launch gate pack together.

Release kit · Receipt · Evidence digest · Claim · Support · Ecosystem · 3.0.0 contract · 3.0.0 gates · Operator shell · Activation path · Governance disputes

What it is not

Boundaries

The gate page is an index, not a substitute for the private operator evidence that the gate script validates.

  • release_gate_pack_is_an_operator_index_not_a_new_claim_source
  • pre_release_commands_must_complete_before_synchronized_package_and_github_release_work
  • post_deploy_commands_must_complete_after_the_public_site_and_service_deployments_are_live
  • public_gate_commands_must_not_require_secret_values_in_command_text
  • full_catalog_claims_require_family_market_lifecycle_and_verification_coherence_before_promotion
  • runtime_durability_claims_require_public_blocker_recovery_and_snapshot_visibility_before_promotion
  • provider_runtime_claims_require_named_provider_profiles_and_public_runtime_gates_before_promotion
  • post_deploy_gate_output_must_include_public_release_verification
  • distribution_truth_must_match_npm_latest_and_authenticated_github_release_objects