Shop corridor status
Verduona commerce is request-gated until Sphere bridge proof is green.
This is the public readiness surface for shop.verduona.com. It describes the controlled WooCommerce to Sphere commerce bridge, but it does not claim live self-serve checkout, payment, workspace creation, or product access.
Do not send secrets, customer files, payroll, health data, incident records, contracts, or regulated records through email.
Gated beta proof
Public proof is allowed; runtime access is not granted here.
Public route
Ready as a request-gated status page
The shop route explains the intended Verduona commerce corridor without opening cart, payment, checkout, customer workspace, or product provisioning.Allowed users
Sphere controls product access
A buyer or invite can reach product access only after Sphere has an approved entitlement, tenant, seat, validity window, and provisioning state.Waiting users
Request access first
Visitors without an approved Sphere entitlement are routed to email/calendar request paths and do not receive app, runtime, workspace, or checkout access from this page.Deny-by-default
No payment-to-access shortcut
A public inquiry, planned WooCommerce order, failed payment, refund, or cancellation is not treated as authorization by AgentJack, CourseRoom, BOZP, CouncilNow, or Orbit.Sphere commerce bridge
Checkout can sell a package, but Sphere remains the source of authorization truth.
The planned commerce route separates billing UI from product entitlement. That keeps refunds, cancellations, provisioning failures, usage caps, tenant state, and revocation visible before any product runtime trusts access.
- WooCommerce remains the planned catalog, cart, receipt, invoice, coupon, refund, and customer billing UI.
- A signed commerce bridge sends order, subscription, membership, refund, cancellation, and dry-run verifier events to Sphere.
- Sphere maps SKU, plan, seats, credits, tenant, validity, provisioning, usage, and revocation.
- Products authorize against Sphere entitlement state only; they do not trust public shop state as access proof.
- Service purchases become Orbit work packets with evidence, owner, rollback notes, and fulfillment status.
Waiting-user path
No entitlement means no workspace session.
A waiting user may request access, book a scope call, or join a product waitlist. The denial path is intentional: without a Sphere approval/allowlist state, product surfaces must keep login, runtime, customer workspaces, and data upload unavailable.
Rollback and evidence