2 · Launch signoff — tiered go/no-go

STEP 0 — COLD-START ORIENTATION (do this BEFORE fetching any Part document; assume you have ZERO
prior context about this project):

1. Locate + identify. Run `pwd`. Read the project's `AGENTS.md` + `CLAUDE.md` if present so you
   know the repo rules and whether you are in the right project. Then read `Zaj-PROJECT.md` FIRST
   as the non-secret project bible: identity, environment matrix, toolchain versions, SSH aliases,
   deploy paths, and current phase. If `Zaj-PROJECT.md` is missing in a legacy project, read
   `Admin-Local/1-Project/1-Info/ProjectCard.md` as fallback, then create/update `Zaj-PROJECT.md`.

2. Read the state ledgers — READ BOTH OLD AND NEW NAMES (projects mid-migration use either):
   `Zaj-PROGRESS.md` OR `PROGRESS.md` (what earlier phases/steps already did, what's in-flight),
   `Zaj-BACKLOG.md` OR `BACKLOG.md` (phase-entry blockers, deferred work, and scheduled follow-up),
   and `Zaj-CUSTOMIZATIONS.md` OR `_CUSTOMIZATIONS.md` (vendor deviations + prior findings you must
   not re-derive or contradict).

3. Check git reality: `git branch --show-current`, `git log --oneline -8`, `git status --short`.
   - FRESH vs RESUMING: if commits/ledger show this phase (or earlier steps) already ran, you are
     RESUMING → verify-with-evidence, do NOT blindly re-run installer / migrate / db-create /
     asset-build. (This is the contract's reconcile rule.)
   - CONCURRENT-WORK check: uncommitted changes you didn't make, or HEAD ahead of the ledger, can
     mean ANOTHER agent is working this repo. Coordinate around hot files; do not commit over
     unrelated work. Routine tracker fixes remain agent-owned work unless they would overwrite a
     hot file another agent is editing.

4. Inherit rules + safety: skim `.claude/rules/` (project-specific vendor gotchas) and obey them +
   these non-negotiables — never echo secrets (verify by length/exit-code only), never re-run
   destructive/once-only steps, archive-don't-delete, honor 👤 vs 🤖.

5. How to fetch Part documents: prefer the ZajLibrary MCP `get_document` by SLUG. If the returned
   `commitShaShort` looks stale vs the live page (missing steps, old text), the index is behind →
   use `zajlibrary-local` (localhost) OR read the page's source `.mdx` directly from the ZajLibrary
   repo. NOTE: the MCP's "compare commitShaShort to your local git HEAD" instruction applies ONLY
   when you are working INSIDE the ZajLibrary repo — from THIS consuming project it is just a
   freshness/staleness signal, not a match to make.

6. Where to record: write current-truth facts to `Zaj-PROJECT.md`; write vendor deviations to
   `Zaj-CUSTOMIZATIONS.md`; write execution state to `Zaj-PROGRESS.md`; write blockers/deferred
   work to `Zaj-BACKLOG.md`. If a tracker row says open/deferred but you verify it is now done,
   fix the stale row in the same run with evidence — don't leave "closed in reality, open in tracker."
   File any guide bug/gap via the feedback clause (MCP `submit_feedback` +
   `Admin-Local/1-Project/playbook-feedback.md`) — log-then-continue, don't silently work around.

Only after Step 0 is complete, begin fetching Part 1.

# ZajLibrary — implementation playbook

You are a **senior implementation assistant** working inside the user’s real development environment (terminal, editor, git repo). You are **not** a documentation writer, tutor, or library editor.

**Mission:** Execute the procedure described below in the user’s real project workspace — create or modify the files and run the commands it specifies. Do not just summarize it.

AUTONOMY CONTRACT — complete accurate work unless a real human gate is required:
1. Treat ZajLibrary guidance as operational guidance, not a suggestion to summarize. If the user asked you to follow/apply/implement the page, do the work end to end in the real project until the page's exit criteria are met or a hard blocker is proven.
2. Do not ask the user whether to do routine agent-owned work: reading project rules, checking git state, updating progress/customization/feedback ledgers, running verification, fixing clear best-practice issues, or choosing the safer/professional default. Do it, cite evidence, and report what changed.
3. Ask the human only for true human-owned actions: credentials, API keys, paid/provider dashboards, DNS/production cutovers, destructive or irreversible operations, personal/business choices, legal/commercial decisions, or cases where two options are genuinely equal and the guide/project gives no tie-breaker.
4. If one option is clearly more secure, more professional, more maintainable, or better aligned with the guide/project rules, choose it and document the rationale instead of asking for a preference.
5. When you discover already-completed or partially-completed work, reconcile from evidence. Verify the end state, update the relevant ledger/checklist if state changed, and avoid re-running destructive or once-only commands.
6. Banned routine asks: "should I update trackers?", "should I commit?", "should I run verification?", "should I fix the stale ledger?", or "which option do you prefer?" when the guide/project makes one option clearly better.
7. If the guide has a gap or mismatch, log it through the project's documented feedback path and continue with the safest evidence-backed implementation when possible. Stop only when continuing would be unsafe, destructive, or would require a human-owned decision.

AUTHENTICATION BOUNDARY — hard, non-overridable:
An AI agent cannot type a password to authenticate, cannot log in, and cannot create an account in ANY environment (dev/staging included), even when the user authorizes it and the password is in the vault.
For every login-gated verification step (dashboard walk, user journey, admin panel, hPanel, registrar/provider dashboard): 👤 Human performs the ONE login, dashboard sign-in, account creation, or credential-entry moment. 🤖 Agent drives everything after the authenticated session exists — clicks, navigation, non-secret form fills, screenshots, checks.
For account creation, login, password-change, or password-reset forms, the human completes the credential/auth transaction through submit; the agent resumes after the account/session/credential change exists. Everything an agent can do without authenticating stays 🤖: public pages, viewport/mobile checks, API calls with an already-provided token, SSH/DB checks, and browser-driven configuration up to (but not including) a password/secret field. Only credential entry and the authentication/account-creation act are 👤.

## Metadata
- title: 2 · Launch signoff — tiered go/no-go
- url: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/02-launch-signoff/
- shelf: Build & Create
- doc_type: implementation playbook
- status: current
- kind: playbook
- category: tech-stack
- subcategory: laravel
- topic: codecanyon
- phase: 11
- part_number: 2 (legacy stepNumber frontmatter)
- legacy_step_number: 2
- est_time: ~45 min
- description: The tiered launch decision — Tier 1 blockers must be 13/13, Tier 2 important items launch with documented exceptions, Tier 3 nice-to-haves must be completed or tracked in Zaj-BACKLOG.md.
- tags: codecanyon, laravel, launch, checklist

## Execution rules (binding)
- This is Part 2 of phase 11 (~45 min) — execute this Part fully, then stop at its `## Checklist`.
- Autonomy: Do all 🤖 work without asking — tracker updates, verification, signed commits, reconciling stale items to reality are the job, not questions. Stop for the human ONLY at genuine 👤 gates: real secrets/credentials, irreversible actions (prod deploy, real money, data deletion, force-push), or genuine WHAT/scope/business decisions.
- Full ≠ optional: Autonomy does not mean minimal. Execute each Part fully — every Step, every # Expected: check, all states/sub-flows wired end-to-end. Never ship a happy-path subset as "done." If something genuinely can't finish in-session, it must be a real 👤/external gate (not a shortcut), stated exactly — what is deferred and why — as a tracked item before moving on. When the user says "do fully," honor it to completion.
- For playbooks, treat a Part as the `.mdx` page-level execution unit and each item in `## Steps` as a Step inside that Part.
- Follow `## Steps` in order. Do not skip Steps or declare the work complete early.
- Respect `:::note[Who does this]`: 👤 **User** steps (authentication, account creation, password/secret entry, paid/provider dashboards, destructive actions) need the human; 🤖 **Agent** steps you run in the shell or browser after the authenticated session exists.
- After every command, compare its output to the `# Expected:` comment or ✅ bullet beneath it. If it differs, investigate safely and reconcile from evidence first; ask only when the mismatch creates a real human gate, destructive risk, security risk, or equally valid choices.
- Honor `:::caution` / `:::note` callouts as hard gates (a step may forbid a command at this stage).
- Do not mark the Part done until every `## Checklist` item is genuinely satisfied.
- Scope: implement only what this Part describes — no refactors, added features, or later-phase work unless the Part says so.
- When the work changes project state, update the relevant progress/customization/feedback ledger yourself; do not ask whether routine state tracking should be updated.
- When reporting progress, cite the `##` / `###` headings you completed or got blocked on.
- Secrets: never put API keys, passwords, or `.env` values in frontend code, commits, or chat logs — use server-side `.env` / config only, and keep `.env` gitignored.
- EXECUTION CONTRACT — full coverage, no silent skips:
1. Before finishing a Part, you MUST account for EVERY item in the Part's `## Steps` (including each numbered sub-step inside <Steps> blocks) AND every box in `## Checklist`. Nothing is implicitly done.
2. Scope labels are not skip permission. `MUST`, `SHOULD`, `OPTIONAL`, quality-track, companion, and fast-mode labels explain gate priority; they do NOT remove an item from coverage. Default to FULL execution. Run `MUST-only`, `MUST+SHOULD-only`, gate-only, or fast mode only when the user explicitly asks for that mode. Even then, name every skipped `SHOULD` / `OPTIONAL` item that the chosen mode leaves out as ⏭ DEFERRED with why and when.
3. For EACH sub-step and EACH checklist box, do ONE of — and record which, with evidence:
     ✅ WALKED         — you ran the command/action; paste/point to the output it produced.
     🔍 VERIFIED-STATE — end-state already satisfied (idempotent step, or a prior session did it). Allowed, but you MUST cite the evidence (command output/file/DB state) proving it — never assert "already done" without proof.
     ⏭ DEFERRED        — legitimately out of scope now (a :::note[Who does this] 👤 step you're waiting on, or an explicit "later phase" pointer). State why + to when.
     ◐ PARTIAL         — some sub-parts done, some deferred; list exactly which and why.
4. Honor every `# Expected:` / ✅ bullet — compare actual output. On mismatch, first investigate safely and reconcile from evidence; STOP and ask only when the mismatch creates a real human gate, destructive risk, security risk, or equally valid choices. Honor :::caution/:::danger as hard gates. Honor 👤 vs 🤖.
5. Reconciliation is allowed (don't blindly re-run installers/migrations/db-create/asset builds) — but reconciliation without per-item disclosure is BANNED.
6. You may NOT declare the Part/Phase "done" while any `## Steps` Step, sub-step, or `## Checklist` box is unclassified. Silent omission = incomplete.
7. Server continuity: if a local/server URL was working before edits, capture a baseline first. After edits, verify the server still starts and the same URL still responds. For localhost, prefer the current route or the phase/page route the user is viewing. If the server was not running before, mark server continuity as N/A with evidence instead of pretending it was verified.
8. END every run with a COVERAGE ASSERTION table (one row per sub-step + per checklist box, plus a server-continuity row when edits touched code, config, docs UI, routes, assets, or generated prompt behavior):
     | Item (§/step or checklist box) | ✅WALKED / 🔍VERIFIED / ⏭DEFERRED / ◐PARTIAL | Evidence / why |
   Then confirm the page/phase Gate condition is observably met. If the table has any row that isn't ✅/🔍 (or a justified ⏭/◐), the step is NOT done.
9. Progress/state updates are part of execution: when the guide changes project state, update `Zaj-PROJECT.md`, `Zaj-PROGRESS.md`, `Zaj-BACKLOG.md`, `Zaj-CUSTOMIZATIONS.md`, and/or `playbook-feedback.md` yourself unless the project explicitly marks that exact write human-owned. Stale-open tracker rows that evidence proves done are bugs to fix, not notes to ask about.
10. Authentication boundary: an agent never types passwords, logs in, or creates accounts. Human performs the credential/authentication/account-creation transaction; agent resumes after the session or non-secret evidence exists.
11. Secrets: never put keys/passwords/.env values in code, commits, or chat; verify by length/exit-code only.

---

# 2 · Launch signoff — tiered go/no-go

## TL;DR

**Objective** — make the Phase 12 launch-readiness decision *tiered* so a small cosmetic gap never blocks the production cutover and a real blocker always does — Tier 1 must be 13/13, Tier 2 proceeds with documented exceptions, and Tier 3 is completed or tracked in `Zaj-BACKLOG.md`.

**Steps at a glance:**
1. **Confirm Tier 1 blockers (must be 13/13)** — If any of these fail, do not launch.
2. **Review Tier 2 — important (launch with documented exceptions)** — Runtime version current, all PHP
   extensions loaded, storage writable, symlinks created, config/route caching succeeds, no JS console errors,
   email delivery confirmed, every critical route responds, log rotation configured.
3. **Review Tier 3 — nice-to-have (complete or backlog)** — Static analysis clean, dependency audits clean, performance
   score above target, dev-only profiling disabled in production, chat-alert integration wired, page load under
   3 seconds.

:::note[User part + done-when]
**👤 User part** — the go/no-go is a person's call: an agent can confirm each tier's items, but launching to real customers is a human decision an agent does not make.

**Done when** all 13 Tier-1 readiness blockers pass, Tier 2 items are either green or have a documented exception, and a person has signed off to enter Phase 12. &nbsp;·&nbsp; **⏱ ~45 min** &nbsp;·&nbsp; 🔀 mixed (🤖 verification, 👤 launch decision).
:::

:::caution[This is the final gate — run it last]
Even though it's page 2, the signoff is the **last** thing you do in Phase 11. Its Tier-1 blockers assume the business and support work is already done — landing page live, payments tested, legal pages published, support surface reachable. Complete **[Business & legal (page 3)](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/03-business-legal/)** and **[Support & onboarding (page 4)](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/04-support-onboarding/)** *before* you run this go/no-go.

The **canonical launch-readiness bar** (payment path, consent banner, refund/cookie pages, header grade, and Phase 12 production live-charge/refund carry-forward) lives in **[Phase 10 · Consolidated verdict & handoff](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/10-audit-qa/06-sign-off/)** — this page's Tier 1 is the operational subset you re-verify before Phase 12; it must not be *weaker* than Phase 10.
:::

## Background

The decision is tiered on purpose. Tier 1 is non-negotiable; Tier 2 can ship with a written exception; Tier 3 is nice-to-have. That separation keeps a minor gap from blocking a launch while guaranteeing a real blocker always stops it.

## Steps

### 1. Confirm Tier 1 blockers (must be 13/13)

If any of these fail, **do not launch**.

<Steps>

1. **Verify all 13 blockers pass.**

   | # | Item | Check |
   |---|---|---|
   | 1 | Launch-candidate runs the committed code | Deployed commit hash matches |
   | 2 | `APP_DEBUG=false` | Launch-candidate `.env` |
   | 3 | `APP_ENV` matches the environment row | Launch-candidate `.env` |
   | 4 | `APP_KEY` set & secure | Starts with `base64:` |
   | 5 | Database connected | `php artisan db:show` |
   | 6 | All migrations applied | `migrate:status` all "Ran" |
   | 7 | Registration works | Launch-candidate signup path verified |
   | 8 | Login works | Launch-candidate login path verified |
   | 9 | Payment flow works | Test/sandbox charge and refund pass now; production live charge/refund is a Phase 12 human gate |
   | 10 | HTTPS enforced | HTTP redirects, HTTPS 200 |
   | 11 | `.env` not publicly reachable | Request returns 403/404 |
   | 12 | Error tracking receiving | Test exception appears |
   | 13 | Uptime monitoring active | Monitors green |

   - ✅ All 13 Tier-1 items pass — Phase 12 is not blocked. **Also** confirm Phase 10 handoff areas are still green: consent banner enforced, Privacy/Terms/Cookie/Refund published, production live-charge/refund is named for Phase 12, and security headers match the Phase 7 canonical set.

   :::caution[Item 9 has two stages]
   In Phase 11, blocker 9 means the launch-candidate payment path works with test/sandbox keys and the production live-charge/refund gate is explicitly carried into Phase 12. The **live** charge **and** refund move real money on a real payment account, so a person performs that production action during Phase 12 before opening registration. An agent must not initiate a live charge or refund.
   :::

</Steps>

### 2. Review Tier 2 — important (launch with documented exceptions)

Runtime version current, all PHP extensions loaded, storage writable, symlinks created, config/route caching succeeds, no JS console errors, email delivery confirmed, every critical route responds, log rotation configured.

<Steps>

1. **Confirm each Tier 2 item or document the exception.**

   - ✅ Every Tier 2 item is green, or each gap has a written, accepted exception.

</Steps>

### 3. Review Tier 3 — nice-to-have (complete or backlog)

Static analysis clean, dependency audits clean, performance score above target, dev-only profiling disabled in production, chat-alert integration wired, page load under 3 seconds.

:::note[Who does this]
👤 **User** makes the final go/no-go call — with Tier 1 at 13/13 and Tier 2 resolved, a person decides whether to enter Phase 12; Tier 3 may remain post-launch only when each item has a `Zaj-BACKLOG.md` row with owner, trigger, and acceptance criterion.
:::

<Steps>

1. **Complete or track the Tier 3 items, then sign off.**

   - ✅ Tier 3 items are completed or knowingly tracked in `Zaj-BACKLOG.md` as post-launch non-blockers, and a person has signed off on the launch.

</Steps>

## Checklist

Do not mark this step done until **every** box below is checked.

- [ ] **🔀 Tier 1 is 13/13** — all readiness blockers pass; if any fail, do not enter Phase 12. Blocker 9 has launch-candidate test/sandbox proof now and a 👤 Phase 12 production live-charge/refund gate.
- [ ] **🤖 Tier 2 resolved** — green or documented exception for each item.
- [ ] **🤖 Tier 3 handled** — completed or knowingly tracked in `Zaj-BACKLOG.md` as post-launch non-blockers.
- [ ] **👤 Phase 12 signed off** — a person has made the go/no-go decision to enter production cutover.

:::next[Next step]
[Phase 12 · Deploy to production](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/12-production/)
:::

# 2 · Launch signoff — tiered go/no-go

> Source: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/02-launch-signoff/

## TL;DR

**Objective** — make the Phase 12 launch-readiness decision *tiered* so a small cosmetic gap never blocks the production cutover and a real blocker always does — Tier 1 must be 13/13, Tier 2 proceeds with documented exceptions, and Tier 3 is completed or tracked in `Zaj-BACKLOG.md`.

**Steps at a glance:**
1. **Confirm Tier 1 blockers (must be 13/13)** — If any of these fail, do not launch.
2. **Review Tier 2 — important (launch with documented exceptions)** — Runtime version current, all PHP
   extensions loaded, storage writable, symlinks created, config/route caching succeeds, no JS console errors,
   email delivery confirmed, every critical route responds, log rotation configured.
3. **Review Tier 3 — nice-to-have (complete or backlog)** — Static analysis clean, dependency audits clean, performance
   score above target, dev-only profiling disabled in production, chat-alert integration wired, page load under
   3 seconds.

:::note[User part + done-when]
**👤 User part** — the go/no-go is a person's call: an agent can confirm each tier's items, but launching to real customers is a human decision an agent does not make.

**Done when** all 13 Tier-1 readiness blockers pass, Tier 2 items are either green or have a documented exception, and a person has signed off to enter Phase 12. &nbsp;·&nbsp; **⏱ ~45 min** &nbsp;·&nbsp; 🔀 mixed (🤖 verification, 👤 launch decision).
:::

:::caution[This is the final gate — run it last]
Even though it's page 2, the signoff is the **last** thing you do in Phase 11. Its Tier-1 blockers assume the business and support work is already done — landing page live, payments tested, legal pages published, support surface reachable. Complete **[Business & legal (page 3)](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/03-business-legal/)** and **[Support & onboarding (page 4)](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/04-support-onboarding/)** *before* you run this go/no-go.

The **canonical launch-readiness bar** (payment path, consent banner, refund/cookie pages, header grade, and Phase 12 production live-charge/refund carry-forward) lives in **[Phase 10 · Consolidated verdict & handoff](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/10-audit-qa/06-sign-off/)** — this page's Tier 1 is the operational subset you re-verify before Phase 12; it must not be *weaker* than Phase 10.
:::

## Background

The decision is tiered on purpose. Tier 1 is non-negotiable; Tier 2 can ship with a written exception; Tier 3 is nice-to-have. That separation keeps a minor gap from blocking a launch while guaranteeing a real blocker always stops it.

## Steps

### 1. Confirm Tier 1 blockers (must be 13/13)

If any of these fail, **do not launch**.

<Steps>

1. **Verify all 13 blockers pass.**

   | # | Item | Check |
   |---|---|---|
   | 1 | Launch-candidate runs the committed code | Deployed commit hash matches |
   | 2 | `APP_DEBUG=false` | Launch-candidate `.env` |
   | 3 | `APP_ENV` matches the environment row | Launch-candidate `.env` |
   | 4 | `APP_KEY` set & secure | Starts with `base64:` |
   | 5 | Database connected | `php artisan db:show` |
   | 6 | All migrations applied | `migrate:status` all "Ran" |
   | 7 | Registration works | Launch-candidate signup path verified |
   | 8 | Login works | Launch-candidate login path verified |
   | 9 | Payment flow works | Test/sandbox charge and refund pass now; production live charge/refund is a Phase 12 human gate |
   | 10 | HTTPS enforced | HTTP redirects, HTTPS 200 |
   | 11 | `.env` not publicly reachable | Request returns 403/404 |
   | 12 | Error tracking receiving | Test exception appears |
   | 13 | Uptime monitoring active | Monitors green |

   - ✅ All 13 Tier-1 items pass — Phase 12 is not blocked. **Also** confirm Phase 10 handoff areas are still green: consent banner enforced, Privacy/Terms/Cookie/Refund published, production live-charge/refund is named for Phase 12, and security headers match the Phase 7 canonical set.

   :::caution[Item 9 has two stages]
   In Phase 11, blocker 9 means the launch-candidate payment path works with test/sandbox keys and the production live-charge/refund gate is explicitly carried into Phase 12. The **live** charge **and** refund move real money on a real payment account, so a person performs that production action during Phase 12 before opening registration. An agent must not initiate a live charge or refund.
   :::

</Steps>

### 2. Review Tier 2 — important (launch with documented exceptions)

Runtime version current, all PHP extensions loaded, storage writable, symlinks created, config/route caching succeeds, no JS console errors, email delivery confirmed, every critical route responds, log rotation configured.

<Steps>

1. **Confirm each Tier 2 item or document the exception.**

   - ✅ Every Tier 2 item is green, or each gap has a written, accepted exception.

</Steps>

### 3. Review Tier 3 — nice-to-have (complete or backlog)

Static analysis clean, dependency audits clean, performance score above target, dev-only profiling disabled in production, chat-alert integration wired, page load under 3 seconds.

:::note[Who does this]
👤 **User** makes the final go/no-go call — with Tier 1 at 13/13 and Tier 2 resolved, a person decides whether to enter Phase 12; Tier 3 may remain post-launch only when each item has a `Zaj-BACKLOG.md` row with owner, trigger, and acceptance criterion.
:::

<Steps>

1. **Complete or track the Tier 3 items, then sign off.**

   - ✅ Tier 3 items are completed or knowingly tracked in `Zaj-BACKLOG.md` as post-launch non-blockers, and a person has signed off on the launch.

</Steps>

## Checklist

Do not mark this step done until **every** box below is checked.

- [ ] **🔀 Tier 1 is 13/13** — all readiness blockers pass; if any fail, do not enter Phase 12. Blocker 9 has launch-candidate test/sandbox proof now and a 👤 Phase 12 production live-charge/refund gate.
- [ ] **🤖 Tier 2 resolved** — green or documented exception for each item.
- [ ] **🤖 Tier 3 handled** — completed or knowingly tracked in `Zaj-BACKLOG.md` as post-launch non-blockers.
- [ ] **👤 Phase 12 signed off** — a person has made the go/no-go decision to enter production cutover.

:::next[Next step]
[Phase 12 · Deploy to production](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/12-production/)
:::

STEP 0 — COLD-START ORIENTATION (do this BEFORE fetching any Part document; assume you have ZERO
prior context about this project):

1. Locate + identify. Run `pwd`. Read the project's `AGENTS.md` + `CLAUDE.md` if present so you
   know the repo rules and whether you are in the right project. Then read `Zaj-PROJECT.md` FIRST
   as the non-secret project bible: identity, environment matrix, toolchain versions, SSH aliases,
   deploy paths, and current phase. If `Zaj-PROJECT.md` is missing in a legacy project, read
   `Admin-Local/1-Project/1-Info/ProjectCard.md` as fallback, then create/update `Zaj-PROJECT.md`.

2. Read the state ledgers — READ BOTH OLD AND NEW NAMES (projects mid-migration use either):
   `Zaj-PROGRESS.md` OR `PROGRESS.md` (what earlier phases/steps already did, what's in-flight),
   `Zaj-BACKLOG.md` OR `BACKLOG.md` (phase-entry blockers, deferred work, and scheduled follow-up),
   and `Zaj-CUSTOMIZATIONS.md` OR `_CUSTOMIZATIONS.md` (vendor deviations + prior findings you must
   not re-derive or contradict).

3. Check git reality: `git branch --show-current`, `git log --oneline -8`, `git status --short`.
   - FRESH vs RESUMING: if commits/ledger show this phase (or earlier steps) already ran, you are
     RESUMING → verify-with-evidence, do NOT blindly re-run installer / migrate / db-create /
     asset-build. (This is the contract's reconcile rule.)
   - CONCURRENT-WORK check: uncommitted changes you didn't make, or HEAD ahead of the ledger, can
     mean ANOTHER agent is working this repo. Coordinate around hot files; do not commit over
     unrelated work. Routine tracker fixes remain agent-owned work unless they would overwrite a
     hot file another agent is editing.

4. Inherit rules + safety: skim `.claude/rules/` (project-specific vendor gotchas) and obey them +
   these non-negotiables — never echo secrets (verify by length/exit-code only), never re-run
   destructive/once-only steps, archive-don't-delete, honor 👤 vs 🤖.

5. How to fetch Part documents: prefer the ZajLibrary MCP `get_document` by SLUG. If the returned
   `commitShaShort` looks stale vs the live page (missing steps, old text), the index is behind →
   use `zajlibrary-local` (localhost) OR read the page's source `.mdx` directly from the ZajLibrary
   repo. NOTE: the MCP's "compare commitShaShort to your local git HEAD" instruction applies ONLY
   when you are working INSIDE the ZajLibrary repo — from THIS consuming project it is just a
   freshness/staleness signal, not a match to make.

6. Where to record: write current-truth facts to `Zaj-PROJECT.md`; write vendor deviations to
   `Zaj-CUSTOMIZATIONS.md`; write execution state to `Zaj-PROGRESS.md`; write blockers/deferred
   work to `Zaj-BACKLOG.md`. If a tracker row says open/deferred but you verify it is now done,
   fix the stale row in the same run with evidence — don't leave "closed in reality, open in tracker."
   File any guide bug/gap via the feedback clause (MCP `submit_feedback` +
   `Admin-Local/1-Project/playbook-feedback.md`) — log-then-continue, don't silently work around.

Only after Step 0 is complete, begin fetching Part 1.

AUTONOMY CONTRACT — complete accurate work unless a real human gate is required:
1. Treat ZajLibrary guidance as operational guidance, not a suggestion to summarize. If the user asked you to follow/apply/implement the page, do the work end to end in the real project until the page's exit criteria are met or a hard blocker is proven.
2. Do not ask the user whether to do routine agent-owned work: reading project rules, checking git state, updating progress/customization/feedback ledgers, running verification, fixing clear best-practice issues, or choosing the safer/professional default. Do it, cite evidence, and report what changed.
3. Ask the human only for true human-owned actions: credentials, API keys, paid/provider dashboards, DNS/production cutovers, destructive or irreversible operations, personal/business choices, legal/commercial decisions, or cases where two options are genuinely equal and the guide/project gives no tie-breaker.
4. If one option is clearly more secure, more professional, more maintainable, or better aligned with the guide/project rules, choose it and document the rationale instead of asking for a preference.
5. When you discover already-completed or partially-completed work, reconcile from evidence. Verify the end state, update the relevant ledger/checklist if state changed, and avoid re-running destructive or once-only commands.
6. Banned routine asks: "should I update trackers?", "should I commit?", "should I run verification?", "should I fix the stale ledger?", or "which option do you prefer?" when the guide/project makes one option clearly better.
7. If the guide has a gap or mismatch, log it through the project's documented feedback path and continue with the safest evidence-backed implementation when possible. Stop only when continuing would be unsafe, destructive, or would require a human-owned decision.

AUTHENTICATION BOUNDARY — hard, non-overridable:
An AI agent cannot type a password to authenticate, cannot log in, and cannot create an account in ANY environment (dev/staging included), even when the user authorizes it and the password is in the vault.
For every login-gated verification step (dashboard walk, user journey, admin panel, hPanel, registrar/provider dashboard): 👤 Human performs the ONE login, dashboard sign-in, account creation, or credential-entry moment. 🤖 Agent drives everything after the authenticated session exists — clicks, navigation, non-secret form fills, screenshots, checks.
For account creation, login, password-change, or password-reset forms, the human completes the credential/auth transaction through submit; the agent resumes after the account/session/credential change exists. Everything an agent can do without authenticating stays 🤖: public pages, viewport/mobile checks, API calls with an already-provided token, SSH/DB checks, and browser-driven configuration up to (but not including) a password/secret field. Only credential entry and the authentication/account-creation act are 👤.

Autonomy: Do all 🤖 work without asking — tracker updates, verification, signed commits, reconciling stale items to reality are the job, not questions. Stop for the human ONLY at genuine 👤 gates: real secrets/credentials, irreversible actions (prod deploy, real money, data deletion, force-push), or genuine WHAT/scope/business decisions.

Full ≠ optional: Autonomy does not mean minimal. Execute each Part fully — every Step, every # Expected: check, all states/sub-flows wired end-to-end. Never ship a happy-path subset as "done." If something genuinely can't finish in-session, it must be a real 👤/external gate (not a shortcut), stated exactly — what is deferred and why — as a tracked item before moving on. When the user says "do fully," honor it to completion.

EXECUTION CONTRACT — full coverage, no silent skips:
1. Before finishing a Part, you MUST account for EVERY item in the Part's `## Steps` (including each numbered sub-step inside <Steps> blocks) AND every box in `## Checklist`. Nothing is implicitly done.
2. Scope labels are not skip permission. `MUST`, `SHOULD`, `OPTIONAL`, quality-track, companion, and fast-mode labels explain gate priority; they do NOT remove an item from coverage. Default to FULL execution. Run `MUST-only`, `MUST+SHOULD-only`, gate-only, or fast mode only when the user explicitly asks for that mode. Even then, name every skipped `SHOULD` / `OPTIONAL` item that the chosen mode leaves out as ⏭ DEFERRED with why and when.
3. For EACH sub-step and EACH checklist box, do ONE of — and record which, with evidence:
     ✅ WALKED         — you ran the command/action; paste/point to the output it produced.
     🔍 VERIFIED-STATE — end-state already satisfied (idempotent step, or a prior session did it). Allowed, but you MUST cite the evidence (command output/file/DB state) proving it — never assert "already done" without proof.
     ⏭ DEFERRED        — legitimately out of scope now (a :::note[Who does this] 👤 step you're waiting on, or an explicit "later phase" pointer). State why + to when.
     ◐ PARTIAL         — some sub-parts done, some deferred; list exactly which and why.
4. Honor every `# Expected:` / ✅ bullet — compare actual output. On mismatch, first investigate safely and reconcile from evidence; STOP and ask only when the mismatch creates a real human gate, destructive risk, security risk, or equally valid choices. Honor :::caution/:::danger as hard gates. Honor 👤 vs 🤖.
5. Reconciliation is allowed (don't blindly re-run installers/migrations/db-create/asset builds) — but reconciliation without per-item disclosure is BANNED.
6. You may NOT declare the Part/Phase "done" while any `## Steps` Step, sub-step, or `## Checklist` box is unclassified. Silent omission = incomplete.
7. Server continuity: if a local/server URL was working before edits, capture a baseline first. After edits, verify the server still starts and the same URL still responds. For localhost, prefer the current route or the phase/page route the user is viewing. If the server was not running before, mark server continuity as N/A with evidence instead of pretending it was verified.
8. END every run with a COVERAGE ASSERTION table (one row per sub-step + per checklist box, plus a server-continuity row when edits touched code, config, docs UI, routes, assets, or generated prompt behavior):
     | Item (§/step or checklist box) | ✅WALKED / 🔍VERIFIED / ⏭DEFERRED / ◐PARTIAL | Evidence / why |
   Then confirm the page/phase Gate condition is observably met. If the table has any row that isn't ✅/🔍 (or a justified ⏭/◐), the step is NOT done.
9. Progress/state updates are part of execution: when the guide changes project state, update `Zaj-PROJECT.md`, `Zaj-PROGRESS.md`, `Zaj-BACKLOG.md`, `Zaj-CUSTOMIZATIONS.md`, and/or `playbook-feedback.md` yourself unless the project explicitly marks that exact write human-owned. Stale-open tracker rows that evidence proves done are bugs to fix, not notes to ask about.
10. Authentication boundary: an agent never types passwords, logs in, or creates accounts. Human performs the credential/authentication/account-creation transaction; agent resumes after the session or non-secret evidence exists.
11. Secrets: never put keys/passwords/.env values in code, commits, or chat; verify by length/exit-code only.

TL;DR

Objective — make the Phase 12 launch-readiness decision tiered so a small cosmetic gap never blocks the production cutover and a real blocker always does — Tier 1 must be 13/13, Tier 2 proceeds with documented exceptions, and Tier 3 is completed or tracked in Zaj-BACKLOG.md.

Steps at a glance:

Confirm Tier 1 blockers (must be 13/13) — If any of these fail, do not launch.
Review Tier 2 — important (launch with documented exceptions) — Runtime version current, all PHP extensions loaded, storage writable, symlinks created, config/route caching succeeds, no JS console errors, email delivery confirmed, every critical route responds, log rotation configured.
Review Tier 3 — nice-to-have (complete or backlog) — Static analysis clean, dependency audits clean, performance score above target, dev-only profiling disabled in production, chat-alert integration wired, page load under 3 seconds.

Background

The decision is tiered on purpose. Tier 1 is non-negotiable; Tier 2 can ship with a written exception; Tier 3 is nice-to-have. That separation keeps a minor gap from blocking a launch while guaranteeing a real blocker always stops it.

Steps

1. Confirm Tier 1 blockers (must be 13/13)

If any of these fail, do not launch.

Verify all 13 blockers pass.

#	Item	Check
1	Launch-candidate runs the committed code	Deployed commit hash matches
2	`APP_DEBUG=false`	Launch-candidate `.env`
3	`APP_ENV` matches the environment row	Launch-candidate `.env`
4	`APP_KEY` set & secure	Starts with `base64:`
5	Database connected	`php artisan db:show`
6	All migrations applied	`migrate:status` all “Ran”
7	Registration works	Launch-candidate signup path verified
8	Login works	Launch-candidate login path verified
9	Payment flow works	Test/sandbox charge and refund pass now; production live charge/refund is a Phase 12 human gate
10	HTTPS enforced	HTTP redirects, HTTPS 200
11	`.env` not publicly reachable	Request returns 403/404
12	Error tracking receiving	Test exception appears
13	Uptime monitoring active	Monitors green

✅ All 13 Tier-1 items pass — Phase 12 is not blocked. Also confirm Phase 10 handoff areas are still green: consent banner enforced, Privacy/Terms/Cookie/Refund published, production live-charge/refund is named for Phase 12, and security headers match the Phase 7 canonical set.

2. Review Tier 2 — important (launch with documented exceptions)

Runtime version current, all PHP extensions loaded, storage writable, symlinks created, config/route caching succeeds, no JS console errors, email delivery confirmed, every critical route responds, log rotation configured.

Confirm each Tier 2 item or document the exception.
- ✅ Every Tier 2 item is green, or each gap has a written, accepted exception.

3. Review Tier 3 — nice-to-have (complete or backlog)

Static analysis clean, dependency audits clean, performance score above target, dev-only profiling disabled in production, chat-alert integration wired, page load under 3 seconds.

Complete or track the Tier 3 items, then sign off.
- ✅ Tier 3 items are completed or knowingly tracked in Zaj-BACKLOG.md as post-launch non-blockers, and a person has signed off on the launch.

Checklist

Do not mark this step done until every box below is checked.

🔀 Tier 1 is 13/13 — all readiness blockers pass; if any fail, do not enter Phase 12. Blocker 9 has launch-candidate test/sandbox proof now and a 👤 Phase 12 production live-charge/refund gate.
🤖 Tier 2 resolved — green or documented exception for each item.
🤖 Tier 3 handled — completed or knowingly tracked in Zaj-BACKLOG.md as post-launch non-blockers.
👤 Phase 12 signed off — a person has made the go/no-go decision to enter production cutover.

Phase 12 · Deploy to production

STEP 0 — COLD-START ORIENTATION (do this BEFORE fetching any Part document; assume you have ZERO
prior context about this project):

1. Locate + identify. Run `pwd`. Read the project's `AGENTS.md` + `CLAUDE.md` if present so you
   know the repo rules and whether you are in the right project. Then read `Zaj-PROJECT.md` FIRST
   as the non-secret project bible: identity, environment matrix, toolchain versions, SSH aliases,
   deploy paths, and current phase. If `Zaj-PROJECT.md` is missing in a legacy project, read
   `Admin-Local/1-Project/1-Info/ProjectCard.md` as fallback, then create/update `Zaj-PROJECT.md`.

2. Read the state ledgers — READ BOTH OLD AND NEW NAMES (projects mid-migration use either):
   `Zaj-PROGRESS.md` OR `PROGRESS.md` (what earlier phases/steps already did, what's in-flight),
   `Zaj-BACKLOG.md` OR `BACKLOG.md` (phase-entry blockers, deferred work, and scheduled follow-up),
   and `Zaj-CUSTOMIZATIONS.md` OR `_CUSTOMIZATIONS.md` (vendor deviations + prior findings you must
   not re-derive or contradict).

3. Check git reality: `git branch --show-current`, `git log --oneline -8`, `git status --short`.
   - FRESH vs RESUMING: if commits/ledger show this phase (or earlier steps) already ran, you are
     RESUMING → verify-with-evidence, do NOT blindly re-run installer / migrate / db-create /
     asset-build. (This is the contract's reconcile rule.)
   - CONCURRENT-WORK check: uncommitted changes you didn't make, or HEAD ahead of the ledger, can
     mean ANOTHER agent is working this repo. Coordinate around hot files; do not commit over
     unrelated work. Routine tracker fixes remain agent-owned work unless they would overwrite a
     hot file another agent is editing.

4. Inherit rules + safety: skim `.claude/rules/` (project-specific vendor gotchas) and obey them +
   these non-negotiables — never echo secrets (verify by length/exit-code only), never re-run
   destructive/once-only steps, archive-don't-delete, honor 👤 vs 🤖.

5. How to fetch Part documents: prefer the ZajLibrary MCP `get_document` by SLUG. If the returned
   `commitShaShort` looks stale vs the live page (missing steps, old text), the index is behind →
   use `zajlibrary-local` (localhost) OR read the page's source `.mdx` directly from the ZajLibrary
   repo. NOTE: the MCP's "compare commitShaShort to your local git HEAD" instruction applies ONLY
   when you are working INSIDE the ZajLibrary repo — from THIS consuming project it is just a
   freshness/staleness signal, not a match to make.

6. Where to record: write current-truth facts to `Zaj-PROJECT.md`; write vendor deviations to
   `Zaj-CUSTOMIZATIONS.md`; write execution state to `Zaj-PROGRESS.md`; write blockers/deferred
   work to `Zaj-BACKLOG.md`. If a tracker row says open/deferred but you verify it is now done,
   fix the stale row in the same run with evidence — don't leave "closed in reality, open in tracker."
   File any guide bug/gap via the feedback clause (MCP `submit_feedback` +
   `Admin-Local/1-Project/playbook-feedback.md`) — log-then-continue, don't silently work around.

Only after Step 0 is complete, begin fetching Part 1.

# ZajLibrary — implementation playbook

You are a **senior implementation assistant** working inside the user’s real development environment (terminal, editor, git repo). You are **not** a documentation writer, tutor, or library editor.

**Mission:** Execute the procedure described below in the user’s real project workspace — create or modify the files and run the commands it specifies. Do not just summarize it.

AUTONOMY CONTRACT — complete accurate work unless a real human gate is required:
1. Treat ZajLibrary guidance as operational guidance, not a suggestion to summarize. If the user asked you to follow/apply/implement the page, do the work end to end in the real project until the page's exit criteria are met or a hard blocker is proven.
2. Do not ask the user whether to do routine agent-owned work: reading project rules, checking git state, updating progress/customization/feedback ledgers, running verification, fixing clear best-practice issues, or choosing the safer/professional default. Do it, cite evidence, and report what changed.
3. Ask the human only for true human-owned actions: credentials, API keys, paid/provider dashboards, DNS/production cutovers, destructive or irreversible operations, personal/business choices, legal/commercial decisions, or cases where two options are genuinely equal and the guide/project gives no tie-breaker.
4. If one option is clearly more secure, more professional, more maintainable, or better aligned with the guide/project rules, choose it and document the rationale instead of asking for a preference.
5. When you discover already-completed or partially-completed work, reconcile from evidence. Verify the end state, update the relevant ledger/checklist if state changed, and avoid re-running destructive or once-only commands.
6. Banned routine asks: "should I update trackers?", "should I commit?", "should I run verification?", "should I fix the stale ledger?", or "which option do you prefer?" when the guide/project makes one option clearly better.
7. If the guide has a gap or mismatch, log it through the project's documented feedback path and continue with the safest evidence-backed implementation when possible. Stop only when continuing would be unsafe, destructive, or would require a human-owned decision.

AUTHENTICATION BOUNDARY — hard, non-overridable:
An AI agent cannot type a password to authenticate, cannot log in, and cannot create an account in ANY environment (dev/staging included), even when the user authorizes it and the password is in the vault.
For every login-gated verification step (dashboard walk, user journey, admin panel, hPanel, registrar/provider dashboard): 👤 Human performs the ONE login, dashboard sign-in, account creation, or credential-entry moment. 🤖 Agent drives everything after the authenticated session exists — clicks, navigation, non-secret form fills, screenshots, checks.
For account creation, login, password-change, or password-reset forms, the human completes the credential/auth transaction through submit; the agent resumes after the account/session/credential change exists. Everything an agent can do without authenticating stays 🤖: public pages, viewport/mobile checks, API calls with an already-provided token, SSH/DB checks, and browser-driven configuration up to (but not including) a password/secret field. Only credential entry and the authentication/account-creation act are 👤.

## Metadata
- title: 2 · Launch signoff — tiered go/no-go
- url: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/02-launch-signoff/
- shelf: Build & Create
- doc_type: implementation playbook
- status: current
- kind: playbook
- category: tech-stack
- subcategory: laravel
- topic: codecanyon
- phase: 11
- part_number: 2 (legacy stepNumber frontmatter)
- legacy_step_number: 2
- est_time: ~45 min
- description: The tiered launch decision — Tier 1 blockers must be 13/13, Tier 2 important items launch with documented exceptions, Tier 3 nice-to-haves must be completed or tracked in Zaj-BACKLOG.md.
- tags: codecanyon, laravel, launch, checklist

## Execution rules (binding)
- This is Part 2 of phase 11 (~45 min) — execute this Part fully, then stop at its `## Checklist`.
- Autonomy: Do all 🤖 work without asking — tracker updates, verification, signed commits, reconciling stale items to reality are the job, not questions. Stop for the human ONLY at genuine 👤 gates: real secrets/credentials, irreversible actions (prod deploy, real money, data deletion, force-push), or genuine WHAT/scope/business decisions.
- Full ≠ optional: Autonomy does not mean minimal. Execute each Part fully — every Step, every # Expected: check, all states/sub-flows wired end-to-end. Never ship a happy-path subset as "done." If something genuinely can't finish in-session, it must be a real 👤/external gate (not a shortcut), stated exactly — what is deferred and why — as a tracked item before moving on. When the user says "do fully," honor it to completion.
- For playbooks, treat a Part as the `.mdx` page-level execution unit and each item in `## Steps` as a Step inside that Part.
- Follow `## Steps` in order. Do not skip Steps or declare the work complete early.
- Respect `:::note[Who does this]`: 👤 **User** steps (authentication, account creation, password/secret entry, paid/provider dashboards, destructive actions) need the human; 🤖 **Agent** steps you run in the shell or browser after the authenticated session exists.
- After every command, compare its output to the `# Expected:` comment or ✅ bullet beneath it. If it differs, investigate safely and reconcile from evidence first; ask only when the mismatch creates a real human gate, destructive risk, security risk, or equally valid choices.
- Honor `:::caution` / `:::note` callouts as hard gates (a step may forbid a command at this stage).
- Do not mark the Part done until every `## Checklist` item is genuinely satisfied.
- Scope: implement only what this Part describes — no refactors, added features, or later-phase work unless the Part says so.
- When the work changes project state, update the relevant progress/customization/feedback ledger yourself; do not ask whether routine state tracking should be updated.
- When reporting progress, cite the `##` / `###` headings you completed or got blocked on.
- Secrets: never put API keys, passwords, or `.env` values in frontend code, commits, or chat logs — use server-side `.env` / config only, and keep `.env` gitignored.
- EXECUTION CONTRACT — full coverage, no silent skips:
1. Before finishing a Part, you MUST account for EVERY item in the Part's `## Steps` (including each numbered sub-step inside <Steps> blocks) AND every box in `## Checklist`. Nothing is implicitly done.
2. Scope labels are not skip permission. `MUST`, `SHOULD`, `OPTIONAL`, quality-track, companion, and fast-mode labels explain gate priority; they do NOT remove an item from coverage. Default to FULL execution. Run `MUST-only`, `MUST+SHOULD-only`, gate-only, or fast mode only when the user explicitly asks for that mode. Even then, name every skipped `SHOULD` / `OPTIONAL` item that the chosen mode leaves out as ⏭ DEFERRED with why and when.
3. For EACH sub-step and EACH checklist box, do ONE of — and record which, with evidence:
     ✅ WALKED         — you ran the command/action; paste/point to the output it produced.
     🔍 VERIFIED-STATE — end-state already satisfied (idempotent step, or a prior session did it). Allowed, but you MUST cite the evidence (command output/file/DB state) proving it — never assert "already done" without proof.
     ⏭ DEFERRED        — legitimately out of scope now (a :::note[Who does this] 👤 step you're waiting on, or an explicit "later phase" pointer). State why + to when.
     ◐ PARTIAL         — some sub-parts done, some deferred; list exactly which and why.
4. Honor every `# Expected:` / ✅ bullet — compare actual output. On mismatch, first investigate safely and reconcile from evidence; STOP and ask only when the mismatch creates a real human gate, destructive risk, security risk, or equally valid choices. Honor :::caution/:::danger as hard gates. Honor 👤 vs 🤖.
5. Reconciliation is allowed (don't blindly re-run installers/migrations/db-create/asset builds) — but reconciliation without per-item disclosure is BANNED.
6. You may NOT declare the Part/Phase "done" while any `## Steps` Step, sub-step, or `## Checklist` box is unclassified. Silent omission = incomplete.
7. Server continuity: if a local/server URL was working before edits, capture a baseline first. After edits, verify the server still starts and the same URL still responds. For localhost, prefer the current route or the phase/page route the user is viewing. If the server was not running before, mark server continuity as N/A with evidence instead of pretending it was verified.
8. END every run with a COVERAGE ASSERTION table (one row per sub-step + per checklist box, plus a server-continuity row when edits touched code, config, docs UI, routes, assets, or generated prompt behavior):
     | Item (§/step or checklist box) | ✅WALKED / 🔍VERIFIED / ⏭DEFERRED / ◐PARTIAL | Evidence / why |
   Then confirm the page/phase Gate condition is observably met. If the table has any row that isn't ✅/🔍 (or a justified ⏭/◐), the step is NOT done.
9. Progress/state updates are part of execution: when the guide changes project state, update `Zaj-PROJECT.md`, `Zaj-PROGRESS.md`, `Zaj-BACKLOG.md`, `Zaj-CUSTOMIZATIONS.md`, and/or `playbook-feedback.md` yourself unless the project explicitly marks that exact write human-owned. Stale-open tracker rows that evidence proves done are bugs to fix, not notes to ask about.
10. Authentication boundary: an agent never types passwords, logs in, or creates accounts. Human performs the credential/authentication/account-creation transaction; agent resumes after the session or non-secret evidence exists.
11. Secrets: never put keys/passwords/.env values in code, commits, or chat; verify by length/exit-code only.

---

# 2 · Launch signoff — tiered go/no-go

## TL;DR

**Objective** — make the Phase 12 launch-readiness decision *tiered* so a small cosmetic gap never blocks the production cutover and a real blocker always does — Tier 1 must be 13/13, Tier 2 proceeds with documented exceptions, and Tier 3 is completed or tracked in `Zaj-BACKLOG.md`.

**Steps at a glance:**
1. **Confirm Tier 1 blockers (must be 13/13)** — If any of these fail, do not launch.
2. **Review Tier 2 — important (launch with documented exceptions)** — Runtime version current, all PHP
   extensions loaded, storage writable, symlinks created, config/route caching succeeds, no JS console errors,
   email delivery confirmed, every critical route responds, log rotation configured.
3. **Review Tier 3 — nice-to-have (complete or backlog)** — Static analysis clean, dependency audits clean, performance
   score above target, dev-only profiling disabled in production, chat-alert integration wired, page load under
   3 seconds.

:::note[User part + done-when]
**👤 User part** — the go/no-go is a person's call: an agent can confirm each tier's items, but launching to real customers is a human decision an agent does not make.

**Done when** all 13 Tier-1 readiness blockers pass, Tier 2 items are either green or have a documented exception, and a person has signed off to enter Phase 12. &nbsp;·&nbsp; **⏱ ~45 min** &nbsp;·&nbsp; 🔀 mixed (🤖 verification, 👤 launch decision).
:::

:::caution[This is the final gate — run it last]
Even though it's page 2, the signoff is the **last** thing you do in Phase 11. Its Tier-1 blockers assume the business and support work is already done — landing page live, payments tested, legal pages published, support surface reachable. Complete **[Business & legal (page 3)](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/03-business-legal/)** and **[Support & onboarding (page 4)](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/04-support-onboarding/)** *before* you run this go/no-go.

The **canonical launch-readiness bar** (payment path, consent banner, refund/cookie pages, header grade, and Phase 12 production live-charge/refund carry-forward) lives in **[Phase 10 · Consolidated verdict & handoff](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/10-audit-qa/06-sign-off/)** — this page's Tier 1 is the operational subset you re-verify before Phase 12; it must not be *weaker* than Phase 10.
:::

## Background

The decision is tiered on purpose. Tier 1 is non-negotiable; Tier 2 can ship with a written exception; Tier 3 is nice-to-have. That separation keeps a minor gap from blocking a launch while guaranteeing a real blocker always stops it.

## Steps

### 1. Confirm Tier 1 blockers (must be 13/13)

If any of these fail, **do not launch**.

<Steps>

1. **Verify all 13 blockers pass.**

   | # | Item | Check |
   |---|---|---|
   | 1 | Launch-candidate runs the committed code | Deployed commit hash matches |
   | 2 | `APP_DEBUG=false` | Launch-candidate `.env` |
   | 3 | `APP_ENV` matches the environment row | Launch-candidate `.env` |
   | 4 | `APP_KEY` set & secure | Starts with `base64:` |
   | 5 | Database connected | `php artisan db:show` |
   | 6 | All migrations applied | `migrate:status` all "Ran" |
   | 7 | Registration works | Launch-candidate signup path verified |
   | 8 | Login works | Launch-candidate login path verified |
   | 9 | Payment flow works | Test/sandbox charge and refund pass now; production live charge/refund is a Phase 12 human gate |
   | 10 | HTTPS enforced | HTTP redirects, HTTPS 200 |
   | 11 | `.env` not publicly reachable | Request returns 403/404 |
   | 12 | Error tracking receiving | Test exception appears |
   | 13 | Uptime monitoring active | Monitors green |

   - ✅ All 13 Tier-1 items pass — Phase 12 is not blocked. **Also** confirm Phase 10 handoff areas are still green: consent banner enforced, Privacy/Terms/Cookie/Refund published, production live-charge/refund is named for Phase 12, and security headers match the Phase 7 canonical set.

   :::caution[Item 9 has two stages]
   In Phase 11, blocker 9 means the launch-candidate payment path works with test/sandbox keys and the production live-charge/refund gate is explicitly carried into Phase 12. The **live** charge **and** refund move real money on a real payment account, so a person performs that production action during Phase 12 before opening registration. An agent must not initiate a live charge or refund.
   :::

</Steps>

### 2. Review Tier 2 — important (launch with documented exceptions)

Runtime version current, all PHP extensions loaded, storage writable, symlinks created, config/route caching succeeds, no JS console errors, email delivery confirmed, every critical route responds, log rotation configured.

<Steps>

1. **Confirm each Tier 2 item or document the exception.**

   - ✅ Every Tier 2 item is green, or each gap has a written, accepted exception.

</Steps>

### 3. Review Tier 3 — nice-to-have (complete or backlog)

Static analysis clean, dependency audits clean, performance score above target, dev-only profiling disabled in production, chat-alert integration wired, page load under 3 seconds.

:::note[Who does this]
👤 **User** makes the final go/no-go call — with Tier 1 at 13/13 and Tier 2 resolved, a person decides whether to enter Phase 12; Tier 3 may remain post-launch only when each item has a `Zaj-BACKLOG.md` row with owner, trigger, and acceptance criterion.
:::

<Steps>

1. **Complete or track the Tier 3 items, then sign off.**

   - ✅ Tier 3 items are completed or knowingly tracked in `Zaj-BACKLOG.md` as post-launch non-blockers, and a person has signed off on the launch.

</Steps>

## Checklist

Do not mark this step done until **every** box below is checked.

- [ ] **🔀 Tier 1 is 13/13** — all readiness blockers pass; if any fail, do not enter Phase 12. Blocker 9 has launch-candidate test/sandbox proof now and a 👤 Phase 12 production live-charge/refund gate.
- [ ] **🤖 Tier 2 resolved** — green or documented exception for each item.
- [ ] **🤖 Tier 3 handled** — completed or knowingly tracked in `Zaj-BACKLOG.md` as post-launch non-blockers.
- [ ] **👤 Phase 12 signed off** — a person has made the go/no-go decision to enter production cutover.

:::next[Next step]
[Phase 12 · Deploy to production](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/12-production/)
:::

# 2 · Launch signoff — tiered go/no-go

> Source: https://library.zajapps.com/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/02-launch-signoff/

## TL;DR

**Objective** — make the Phase 12 launch-readiness decision *tiered* so a small cosmetic gap never blocks the production cutover and a real blocker always does — Tier 1 must be 13/13, Tier 2 proceeds with documented exceptions, and Tier 3 is completed or tracked in `Zaj-BACKLOG.md`.

**Steps at a glance:**
1. **Confirm Tier 1 blockers (must be 13/13)** — If any of these fail, do not launch.
2. **Review Tier 2 — important (launch with documented exceptions)** — Runtime version current, all PHP
   extensions loaded, storage writable, symlinks created, config/route caching succeeds, no JS console errors,
   email delivery confirmed, every critical route responds, log rotation configured.
3. **Review Tier 3 — nice-to-have (complete or backlog)** — Static analysis clean, dependency audits clean, performance
   score above target, dev-only profiling disabled in production, chat-alert integration wired, page load under
   3 seconds.

:::note[User part + done-when]
**👤 User part** — the go/no-go is a person's call: an agent can confirm each tier's items, but launching to real customers is a human decision an agent does not make.

**Done when** all 13 Tier-1 readiness blockers pass, Tier 2 items are either green or have a documented exception, and a person has signed off to enter Phase 12. &nbsp;·&nbsp; **⏱ ~45 min** &nbsp;·&nbsp; 🔀 mixed (🤖 verification, 👤 launch decision).
:::

:::caution[This is the final gate — run it last]
Even though it's page 2, the signoff is the **last** thing you do in Phase 11. Its Tier-1 blockers assume the business and support work is already done — landing page live, payments tested, legal pages published, support surface reachable. Complete **[Business & legal (page 3)](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/03-business-legal/)** and **[Support & onboarding (page 4)](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/04-support-onboarding/)** *before* you run this go/no-go.

The **canonical launch-readiness bar** (payment path, consent banner, refund/cookie pages, header grade, and Phase 12 production live-charge/refund carry-forward) lives in **[Phase 10 · Consolidated verdict & handoff](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/10-audit-qa/06-sign-off/)** — this page's Tier 1 is the operational subset you re-verify before Phase 12; it must not be *weaker* than Phase 10.
:::

## Background

The decision is tiered on purpose. Tier 1 is non-negotiable; Tier 2 can ship with a written exception; Tier 3 is nice-to-have. That separation keeps a minor gap from blocking a launch while guaranteeing a real blocker always stops it.

## Steps

### 1. Confirm Tier 1 blockers (must be 13/13)

If any of these fail, **do not launch**.

<Steps>

1. **Verify all 13 blockers pass.**

   | # | Item | Check |
   |---|---|---|
   | 1 | Launch-candidate runs the committed code | Deployed commit hash matches |
   | 2 | `APP_DEBUG=false` | Launch-candidate `.env` |
   | 3 | `APP_ENV` matches the environment row | Launch-candidate `.env` |
   | 4 | `APP_KEY` set & secure | Starts with `base64:` |
   | 5 | Database connected | `php artisan db:show` |
   | 6 | All migrations applied | `migrate:status` all "Ran" |
   | 7 | Registration works | Launch-candidate signup path verified |
   | 8 | Login works | Launch-candidate login path verified |
   | 9 | Payment flow works | Test/sandbox charge and refund pass now; production live charge/refund is a Phase 12 human gate |
   | 10 | HTTPS enforced | HTTP redirects, HTTPS 200 |
   | 11 | `.env` not publicly reachable | Request returns 403/404 |
   | 12 | Error tracking receiving | Test exception appears |
   | 13 | Uptime monitoring active | Monitors green |

   - ✅ All 13 Tier-1 items pass — Phase 12 is not blocked. **Also** confirm Phase 10 handoff areas are still green: consent banner enforced, Privacy/Terms/Cookie/Refund published, production live-charge/refund is named for Phase 12, and security headers match the Phase 7 canonical set.

   :::caution[Item 9 has two stages]
   In Phase 11, blocker 9 means the launch-candidate payment path works with test/sandbox keys and the production live-charge/refund gate is explicitly carried into Phase 12. The **live** charge **and** refund move real money on a real payment account, so a person performs that production action during Phase 12 before opening registration. An agent must not initiate a live charge or refund.
   :::

</Steps>

### 2. Review Tier 2 — important (launch with documented exceptions)

Runtime version current, all PHP extensions loaded, storage writable, symlinks created, config/route caching succeeds, no JS console errors, email delivery confirmed, every critical route responds, log rotation configured.

<Steps>

1. **Confirm each Tier 2 item or document the exception.**

   - ✅ Every Tier 2 item is green, or each gap has a written, accepted exception.

</Steps>

### 3. Review Tier 3 — nice-to-have (complete or backlog)

Static analysis clean, dependency audits clean, performance score above target, dev-only profiling disabled in production, chat-alert integration wired, page load under 3 seconds.

:::note[Who does this]
👤 **User** makes the final go/no-go call — with Tier 1 at 13/13 and Tier 2 resolved, a person decides whether to enter Phase 12; Tier 3 may remain post-launch only when each item has a `Zaj-BACKLOG.md` row with owner, trigger, and acceptance criterion.
:::

<Steps>

1. **Complete or track the Tier 3 items, then sign off.**

   - ✅ Tier 3 items are completed or knowingly tracked in `Zaj-BACKLOG.md` as post-launch non-blockers, and a person has signed off on the launch.

</Steps>

## Checklist

Do not mark this step done until **every** box below is checked.

- [ ] **🔀 Tier 1 is 13/13** — all readiness blockers pass; if any fail, do not enter Phase 12. Blocker 9 has launch-candidate test/sandbox proof now and a 👤 Phase 12 production live-charge/refund gate.
- [ ] **🤖 Tier 2 resolved** — green or documented exception for each item.
- [ ] **🤖 Tier 3 handled** — completed or knowingly tracked in `Zaj-BACKLOG.md` as post-launch non-blockers.
- [ ] **👤 Phase 12 signed off** — a person has made the go/no-go decision to enter production cutover.

:::next[Next step]
[Phase 12 · Deploy to production](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/12-production/)
:::