# Wake Report Readiness Checklist — Afterparty Forge 2045

Status: `wake_report_readiness_draft_closed_until_human_yes`

This is the final reporter's operator contract for turning the proof hub into a concise wake report without inventing external wins. It tells an awake operator exactly what to rerun, what to show, what to avoid, and which actions remain human-only.

## Closed-gate policy

All risky public/commercial/media actions remain closed until a human explicitly approves exact copy, media, destination, and timing:

- public_posting=false
- outreach=false
- paid_promotion=false
- claim_revenue=false
- claim_openai_affiliation=false
- publishes_stream=false
- records_audio=false
- uploads_private_media=false
- youtube_upload=false
- caption_upload=false
- payment_link_creation=false
- invoice_execution=false
- starts_gpu=false
- starts_paid_api=false
- downloads_models=false
- starts_training=false
- submits_hackathon=false
- mutates_cron=false
- wallet_actions=false
- secret_exposure=false

Exact approval question: **Do you approve sending or publishing the final wake report using the exact copy, screenshots, videos, captions, and proof links selected by an awake operator?**

## Final command set to rerun

Run from the repository root:

```bash
PYTHONDONTWRITEBYTECODE=1 python3 scripts/verify_site.py
git diff --check
git status --short --branch
git rev-parse HEAD
git ls-remote origin refs/heads/main
```

Expected success highlights:

- `VERIFY OK afterparty explainer site`
- `git diff --check` exits 0
- `git status --short --branch` is clean after commit/push
- `git rev-parse HEAD` matches the pushed remote head when network/auth allows push
- The proof hub page includes the launch proof index, manual X drafts, captions/transcripts, buyer-safe private demo script, and this readiness checklist.

## Local smoke / visible proof path

1. Open `docs/index.html` locally or the GitHub Pages URL after Pages finishes building.
2. Confirm these cards are visible: Unicode Future UI, Faceless YouTube + Full Framework, Launch Art + Control Room, Manual X Thread Drafts, Manual Screen Checklist, Buyer-Safe Private Demo Script, Launch Proof Index, and Wake Report Readiness.
3. Play or inspect metadata for the three embedded MP4 proof assets if the browser can render them.
4. Open the JSON manifests linked from each card and confirm the risky gates are false.
5. Keep all terminal tabs free of `.env`, tokens, secret managers, wallet data, billing dashboards, private customer data, and raw private datasets.

## 60-second report structure

1. **One-line status:** Afterparty Forge has a static proof hub, videos, captions, launch art, social drafts, buyer-safe script, and verifier-backed evidence map.
2. **What is built:** Link to the proof hub, launch proof index, faceless YouTube pack, captions pack, launch flyer manifest, and private demo script.
3. **Verification:** Quote the latest `VERIFY OK afterparty explainer site`, `git diff --check`, clean git status, and commit SHA.
4. **Safety:** Explicitly state that no posting, outreach, upload, livestream, payment, invoice, GPU/training, wallet, secret exposure, or cron mutation occurred.
5. **Human next decision:** Ask whether to manually publish/post/upload/demo using reviewed copy and media.

## Proof paths

- `docs/index.html`
- `docs/data/site-manifest.json`
- `docs/reports/LAUNCH_PROOF_INDEX.md`
- `docs/data/launch-proof-index.json`
- `docs/social/X_THREAD_DRAFTS.md`
- `docs/data/x-thread-drafts.json`
- `docs/youtube/FACELESS_YOUTUBE_TRAINING_RELEASE_PACK.md`
- `docs/youtube/CAPTIONS_TRANSCRIPTS_PACK.md`
- `docs/data/youtube-training-pack.json`
- `docs/data/youtube-captions-pack.json`
- `docs/launch/SCREEN_CHECKLIST.md`
- `docs/data/launch-screen-checklist.json`
- `docs/revenue/PRIVATE_DEMO_BUYER_SAFE_SCRIPT.md`
- `docs/data/private-demo-buyer-script.json`
- `docs/assets/flyers/afterparty_forge_launch_flyer_manifest.json`
- `scripts/verify_site.py`

## Human-only actions

1. Publish or schedule any X/Twitter thread, reply, quote, DM, Space, or paid promotion.
2. Upload the YouTube master/Shorts video or attach captions to a public video.
3. Start a livestream, record a screen share, or expose private media/tabs.
4. Send buyer outreach, run a private demo with a real buyer, create payment links, create invoices, or claim revenue.
5. Start GPU jobs, model downloads, training, paid APIs, wallets, billing changes, or new cron mutations.
6. Claim OpenAI/Nous/X/YouTube/Hugging Face/event affiliation, attendance, sponsorship, or endorsement.

## Failure recovery

- If `verify_site.py` fails, do not send a green wake report. Fix the missing proof path, manifest flag, or HTML link first.
- If `git diff --check` fails, repair whitespace before commit.
- If push fails, report the local commit SHA and sanitized push blocker; do not force-push or amend a pushed commit unattended.
- If Pages is stale, report the local verified artifact and wait for the next Pages build before claiming the live page updated.
- If a browser/video render fails locally, report HTTP/file proof and mark visual QA as pending human review rather than inventing a visual pass.