# Proof Hub Operator Quickstart

Status: `proof_hub_operator_quickstart_manual_run_only_closed_until_human_yes`

This is a manual, screen-share-safe quickstart for an awake Sonic-Forage operator. It makes the proof hub easier to show without starting streams, posting to X, uploading YouTube assets, sending outreach, creating payment links, running GPU jobs, mutating cron, or exposing secrets.

## Clean setup commands

```bash
cd /opt/data/workspace/projects/afterparty-forge-explainer-site
git status --short --branch
PYTHONDONTWRITEBYTECODE=1 python3 scripts/verify_site.py
git diff --check
python3 -m http.server 8765 --directory docs
```

Open local preview only after the verifier passes:

- `http://127.0.0.1:8765/`
- Canonical Pages URL for public read-only verification: `https://sonic-forage.github.io/afterparty-forge-explainer-site/`
- Canonical source repo: `https://github.com/Sonic-Forage/afterparty-forge-explainer-site`
- Canonical entity forge repo: `https://github.com/Sonic-Forage/jimsky-afterparty-entity-forge`

## 45-second click path

1. Hero: say "Afterparty Forge 2045 is a proof-over-hype rebound engine under Sonic-Forage."
2. Launch art/control room: show the QR flyers and explain that posting and Spaces remain manual-only.
3. YouTube/framework pack: show thumbnail, captions, chapters, and manual upload gates.
4. Operator audio drops and stream-ready loop: show review-only media links; do not start a broadcast.
5. Proof index / final receipt / wake readiness: show that claims map to repo-local evidence and verifier commands.
6. Finish on the static verifier card; run the command if the audience wants proof.

## API / terminal proof commands

```bash
PYTHONDONTWRITEBYTECODE=1 python3 scripts/verify_site.py
PYTHONDONTWRITEBYTECODE=1 python3 scripts/verify_static_surface.py
python3 - <<'PY'
import json
from pathlib import Path
m=json.loads(Path('docs/data/proof-hub-operator-quickstart.json').read_text())
print(m['status'])
print('requires_human_approval=', m['requires_human_approval'])
print('proof_paths=', len(m['proof_paths']))
PY
git diff --check
```

Expected highlights:

- `VERIFY OK afterparty explainer site`
- `STATIC SURFACE OK ...`
- `proof_hub_operator_quickstart_manual_run_only_closed_until_human_yes`
- `requires_human_approval= True`

## Safety / closed-gate script

Say this before showing any launch, stream, or buyer-facing material:

> This is a local/manual proof hub. It does not post, DM, upload, stream, record, spend, create payment links, claim revenue, claim affiliation, start GPU jobs, download models, train models, expose secrets, or mutate cron. Any public/commercial/media action requires an explicit awake human yes after reviewing the exact copy and assets.

## Failure recovery

- If `verify_site.py` fails, stop the demo and show only the failing command plus the file path to fix.
- If a media file fails to load locally, use the manifest/doc proof path instead of trying to regenerate media during the call.
- If a browser tab shows a token, tunnel URL, private customer file, or unrelated workspace, close it before screen sharing.
- If Pages looks stale, verify `/index.html?cb=<short-sha>` and the exact `docs/data/*.json` path before claiming deployment failure.

## Post-demo cleanup

```bash
# stop the local preview server with Ctrl-C in its terminal
git status --short --branch
```

If any smoke command generated files, either restore them or intentionally include them in a verified commit. Do not leave frame caches, transient media workdirs, or secrets in served roots.

## Closed-gate literals for verifier

- public_posting=false
- publishes_stream=false
- records_audio=false
- youtube_upload=false
- payment_links=false
- claim_openai_affiliation=false
- starts_gpu=false
- starts_training=false
- secret_exposure=false
- mutates_cron=false

## Human approval question

Do you approve using this Sonic-Forage proof hub quickstart for a live/manual screen-share demo, with no posting, upload, stream, recording, payment, outreach, GPU/training, secret exposure, or cron mutation unless separately approved?

## Blocked without approval

- X/Twitter posting, replies, DMs, scheduling, paid promotion, or Spaces.
- YouTube uploads, caption uploads, thumbnails posted publicly, or social cross-posts.
- Livestream creation, RTMP publishing, recording, or private-media upload.
- Checkout/payment links, invoices, wallet actions, spend, or revenue claims.
- GPU jobs, paid APIs, model downloads, model training, or dataset publication.
- Outreach to buyers, partners, sponsors, attendees, or communities.
- Secret-bearing commands, `.env` display, token printing, or cron mutation.