# First-customer launch governance readiness

Status: COMPLETE — GOVERNANCE DELIVERED; PG-21/23 RUNTIME/WEB HANDOFFS OPEN

## Purpose

Finish the go-live work that can be completed now without changing translation/runtime feature code: PG-21, PG-23, PG-43 and PG-45. This lane prepares the commercial/support contract while feature agents continue in parallel.

## Ownership boundary

This lane is primarily docs/product-truth work. It may correct static release/customer documentation and metadata when unambiguous, but it must not edit active runtime seams owned by Worker E2E, Page fidelity, manual protection, ACF/Yoast, site-entry, or settings E2E lanes.

If an admin/runtime identity inconsistency is found in a file owned by another active lane, record it as a bounded handoff instead of editing that file concurrently.

Do not build a release ZIP, bump version, run final RC certification, or declare Stripe ready.

## Tasks

### LG-01 — PG-21 optional-promise closure

Starting from `docs/launch/FIRST-CUSTOMER-SCOPE.md`, audit every customer-facing repository surface and classify/align claims for:

- WPML migration;
- Site Content/templates/navigation/synced patterns;
- team workflow/assignment/analytics;
- translation memory/glossary;
- WooCommerce/multi-currency;
- Elementor;
- Rank Math;
- auto-translate-on-publish;
- multisite;
- broad performance/scalability claims.

Everything must be either supported/conditional with evidence, or deferred and not promised. Historical plans/source existence are not evidence.

PG-21 may be marked complete once repository-controlled customer surfaces are coherent; external website discrepancies should be recorded with exact URLs/screenshots for owner/web follow-up rather than silently ignored.

### LG-02 — PG-23 product identity audit

Verify consistency across:

- plugin header and slug;
- `IPZ_VERSION` and package naming convention;
- WordPress menu/admin visible product name;
- `README.md` / `readme.txt`;
- legal draft product identity;
- Press.Zone product/support URLs exposed by plugin/docs;
- support email/contact routes actually intended for first customer;
- package/catalog plan labels once available from backend.

Canonical product: **International Press Zone**. “Press.Zone” may be used as company/service brand; do not revive “Multilingual Press Zone”.

Do not invent pricing/support values.

### LG-03 — PG-43 first-customer acceptance script

Create `docs/launch/FIRST-CUSTOMER-ACCEPTANCE.md` as an executable acceptance sequence with evidence fields. Minimum flow:

1. final ZIP install;
2. activate/bootstrap;
3. Connect/social sign-in;
4. Stripe purchase/entitlement — explicitly `WAITING_EXTERNAL` until clearance;
5. add target language;
6. translate a Page;
7. translate a string;
8. verify frontend localized route/switcher;
9. manually edit translation;
10. regenerate and prove manual protection;
11. bulk job and cancel;
12. account/portal;
13. disconnect/reconnect;
14. authenticated plugin update;
15. rollback decision path if a blocking defect occurs.

Separate “script defined” from “script executed on customer-like staging”; PG-44 remains final-RC execution.

### LG-04 — PG-45 support/incident ownership

Create `docs/launch/FIRST-CUSTOMER-SUPPORT.md` defining operational ownership, not invented SLA marketing:

- customer contact route;
- severity definitions;
- who can authorize rollback;
- known-good artifact retention;
- plugin vs backend incident boundary;
- diagnostic capture procedure with secret/content redaction;
- escalation when `api.press.zone`, Stripe, social auth, or translation provider is the dependency;
- how to identify exact plugin/backend SHAs during an incident;
- customer communication checklist;
- no made-up response times unless owner has explicitly approved them.

### LG-05 — GOLIVE reconciliation

Mark PG-21, PG-23, PG-43, PG-45 complete only if their exact acceptance criteria are satisfied. Leave PG-44, Stripe, compatibility, security and artifact certification to their owners.

## Definition of done

The first sale has a truthful feature promise, one canonical product identity, a complete acceptance script, and an actionable incident/support ownership document without touching concurrent feature code.

## Completion receipt — 2026-08-19

The governance lane completed its owned static/documentation work without editing active runtime seams.

- PG-21: tracked marketing/user-guide/README claim surfaces reconciled to `FIRST-CUSTOMER-SCOPE.md`; remaining runtime claim discrepancies are exact handoffs H-PG21-01..03 in `docs/launch/LAUNCH-GOVERNANCE-AUDIT.md`.
- PG-23: package/product identity audited; remaining admin/web/catalog/support discrepancies are exact handoffs H-PG23-01..05 and external verification notes in the governance audit.
- PG-43: `docs/launch/FIRST-CUSTOMER-ACCEPTANCE.md` created and expanded to the complete plan flow; Stripe commercial steps remain `WAITING_EXTERNAL`; PG-44 owns execution on the final customer-like release candidate.
- PG-45: `docs/launch/FIRST-CUSTOMER-SUPPORT.md` created with named-role requirements, rollback authority, known-good artifact retention, redaction, provider escalation and customer communications, without invented SLA/contact values.
- No final release ZIP was built and no active feature/runtime lane file was modified.