RELEASEEvidence agrees
The requested, measurable checks support the pinned release.
Release desk 01 WooCommerce evidence
Check the release before it ships.
Start with a passive public preflight. Verified store owners can then make a version-pinned release decision from signed, aggregate-only evidence.
READ-ONLY PREFLIGHTNO ORDER CREATEDNO PAYMENT DATAABSTAINS WHEN UNREADABLE
Preflight recordFree · no login
Checks public WooCommerce, robots, structured data and declared agent-protocol surfaces. It does not log in or change the store.
Preflight result
02 Explicit outcomes
A decision record, not a confidence theatre.
Every checked family carries an observable state and reason. A blocked target is not treated as a broken store, and silence is never promoted to proof.
HOLDA check failed
A reproducible finding needs attention before this release.
PARTIALSome checks remain
Useful evidence exists, but the requested scope is incomplete.
ABSTAINNo claim made
The target was blocked, unreadable or outside measurable scope.
03 Release workflow
Public check first. Owner evidence second.
The free surface helps diagnose what can be observed from outside. The Release Gate is deliberately separate: it requires ownership and signed plugin evidence tied to a specific run.
Inspect public surfaces
Run the preflight against a public HTTPS origin. No plugin, login or store mutation is required.
Run it nowConnect an owned store
Install the WordPress beta, verify store ownership and choose whether signed aggregate evidence may be sent.
Download the betaPin and decide
Start a version-pinned run, review per-family evidence and claim the terminal record once. Replays are never billable.
Open owner setup04 Evidence boundary
What crosses the boundary—and what never does.
The connected Release Gate accepts a narrow, documented aggregate contract. It does not need customer identity, order contents or payment credentials.
Allowed evidence
- WooCommerce and WordPress version identifiers
- Aggregate product and endpoint counts
- Boolean capability and configuration checks
- Timestamp, run identity and cryptographic signature
Evidence is bound to an owned store and a finite release run.
Rejected data
- Customer names, emails or addresses
- Order line items or payment credentials
- WordPress administrator passwords
- Private product descriptions or uploaded documents
The free preflight reads only public web surfaces.
05 Put it in the workflow
Use the same preflight where releases happen.
The web desk is the quickest first check. The beta plugin and repository action bring the same public preflight contract closer to WooCommerce administration and CI.
Local readiness snapshot with explicit evidence consent.
Inspect local configuration before connecting. No scheduled evidence is enabled at activation.
Fail a release workflow on an explicit HOLD.
Run the public preflight from CI and write a reason-coded summary. BLOCKED and UNMEASURED remain abstentions.
View action setup06 Questions
Before you run it
Does a public preflight certify my store?
No. It reports the selected public surfaces at the observation time. It does not certify future availability, discoverability or checkout success.
Why can a result be BLOCKED or UNMEASURED?
A store may reject automated access, expose an unsupported response, time out or leave a protocol undeclared. AgentReady records that uncertainty instead of converting it into a failure.
Does Release Gate create a test order?
No. The root Release Gate contract does not create orders, reserve inventory, handle payment credentials or send customer email.
Is the Release Gate available for purchase?
Not yet. The public preflight is free; Release Gate settlement remains disabled while owner-authorized evidence and usage invariants are measured.