# Proof Hub Handoff Brief

Status: `proof_hub_handoff_brief_manual_review_only_closed_until_human_yes`
Canonical namespace: `Sonic-Forage`
Canonical Pages URL: <https://sonic-forage.github.io/afterparty-forge-explainer-site/>

This is a compact handoff brief for an awake operator who wants to understand what Afterparty Forge can safely show in the first five minutes. It is a local/repo-backed review artifact only: no public post, upload, livestream, outreach, payment, dataset release, GPU job, training run, secret-bearing action, or cron mutation is approved by this document.

## Exact human approval question

Do you approve using this Sonic-Forage proof hub handoff brief in a manual screen-share or private review, with no posting, upload, stream, outreach, payment, dataset release, GPU/training, or cron changes unless you give a separate explicit yes?

## 5-minute handoff route

1. **Boundary first** — say: "This is a proof-over-hype handoff. Everything shown is repo-local or public Pages proof; external launch actions are closed until a human yes."
2. **Open the canonical proof hub** — `https://sonic-forage.github.io/afterparty-forge-explainer-site/` and show the first-click card.
3. **Run the local verifier before claims** — from the repo root run `PYTHONDONTWRITEBYTECODE=1 python3 scripts/verify_site.py` and expect `VERIFY OK afterparty explainer site`.
4. **Show the evidence map** — open `docs/reports/LAUNCH_PROOF_INDEX.md` and explain that claims map to proof paths, not vibes.
5. **Show one human next action** — choose exactly one: manual private demo, manual social review, manual upload review, or keep building proof.
6. **Stop at the gate** — ask the approval question above before any external side effect.

## Terminal proof commands

```bash
cd /opt/data/workspace/projects/afterparty-forge-explainer-site
PYTHONDONTWRITEBYTECODE=1 python3 scripts/verify_site.py
git diff --check
git status --short --branch
git rev-parse --short HEAD
git ls-remote origin refs/heads/main
```

Expected highlights:

- `VERIFY OK afterparty explainer site`
- `STATIC SURFACE OK` with parsed HTML and JSON manifests
- `git diff --check` exits cleanly
- `git status --short --branch` is clean after the committed increment
- remote `refs/heads/main` matches the final pushed commit before any public claim

## Proof paths

- `docs/index.html` — static proof hub surface.
- `docs/data/site-manifest.json` — aggregate site manifest with Sonic-Forage namespace.
- `docs/launch/PROOF_HUB_START_HERE.md` — 45-second start-here route.
- `docs/launch/PROOF_HUB_FIRST_CLICK_CARD.md` — 30-second opening route.
- `docs/reports/LAUNCH_PROOF_INDEX.md` — evidence map for allowed claims and non-claims.
- `docs/reports/PROOF_LANE_EVIDENCE_WORDING.md` — safe wording pack.
- `scripts/verify_site.py` — aggregate verifier.

## Safe wording

Use:

- "The Sonic-Forage proof hub is verified locally by `scripts/verify_site.py`."
- "This is a review-only launch artifact; public posting and uploads remain closed until approval."
- "The proof index maps allowed claims to repo-local paths."

Do not say:

- "We made revenue" unless a verified payment receipt exists.
- "OpenAI endorsed this" or any affiliation claim.
- "The stream is live" unless an operator actually started it and proof exists.
- "The dataset is public" while the HF dataset remains private.
- "The system can spend, train, upload, or post automatically" because those gates remain closed.

## Closed gates

`public_posting=false`
`outreach=false`
`paid_promotion=false`
`claim_revenue=false`
`claim_openai_affiliation=false`
`youtube_upload=false`
`publishes_stream=false`
`records_audio=false`
`uploads_private_media=false`
`public_dataset_release=false`
`starts_gpu=false`
`starts_paid_api=false`
`downloads_models=false`
`starts_training=false`
`payment_links=false`
`wallet_actions=false`
`secret_exposure=false`
`mutates_cron=false`

## Blocked without approval

- Posting, scheduling, replying, quoting, DMing, emailing, or starting outreach.
- Uploading to YouTube, X, Discord, Hugging Face, or any public channel.
- Starting or scheduling a livestream, Space, OBS broadcast, or recording.
- Creating payment links, invoices, checkout pages, wallets, or revenue claims.
- Running GPU jobs, paid APIs, model downloads, training, or dataset publication.
- Moving private media or secrets into public paths.
- Creating, editing, deleting, or recursively spawning cron jobs.

## Cleanup and failure recovery

If verification fails, stop the handoff, do not make public claims, capture the failing command name only, fix locally, rerun `PYTHONDONTWRITEBYTECODE=1 python3 scripts/verify_site.py`, then rerun `git diff --check`. If a smoke test leaves generated caches, move them out of served roots before commit; do not include frame caches or secrets.