# Proof Hub First-Click Mini-Card

Status: `proof_hub_first_click_card_manual_review_only_closed_until_human_yes`

This is the shortest operator card for an awake Sonic-Forage reviewer who opens the proof hub and needs to know exactly what to click first. It is a website-summary polish increment only: no public post, YouTube upload, livestream, Space, outreach, payment link, invoice, dataset release, GPU job, model training, spend, secret exposure, OpenAI affiliation claim, revenue claim, or cron mutation is approved or performed.

## Canonical namespace and URLs

- Canonical org: `Sonic-Forage`
- Proof hub: <https://sonic-forage.github.io/afterparty-forge-explainer-site/>
- Source engine: <https://github.com/Sonic-Forage/jimsky-afterparty-entity-forge>
- Explainer source: <https://github.com/Sonic-Forage/afterparty-forge-explainer-site>
- Private dataset namespace: <https://huggingface.co/datasets/Sonic-Forage/jimsky-afterparty-logo-seed>

## Exact human approval question

Do you approve using this Sonic-Forage first-click mini-card as the opening screen path for a manual proof-hub review, with all public posting, upload, stream, payment, outreach, dataset release, GPU/training, and cron actions still closed?

## 30-second first-click path

1. Open the canonical proof hub: `https://sonic-forage.github.io/afterparty-forge-explainer-site/`.
2. Say: “This is a proof-over-hype hub; every safe claim has a repo-local path or verifier behind it.”
3. Click or scroll to `PROOF HUB START-HERE PATH` and show the manual-review gate.
4. Click `Start-here operator path`, then return to the page.
5. Click `Static surface verification` and point at the verifier command: `PYTHONDONTWRITEBYTECODE=1 python3 scripts/verify_site.py`.
6. Click `Launch proof index` and say: “This is the claim map; non-claims stay non-claims.”
7. Stop and ask for exactly one approved next action.

## Terminal proof commands

Run from the repo root:

```bash
PYTHONDONTWRITEBYTECODE=1 python3 scripts/verify_site.py
git diff --check
git status --short --branch
```

Expected highlights:

- `STATIC SURFACE OK` appears.
- `VERIFY OK afterparty explainer site` appears.
- `git diff --check` exits cleanly.
- After commit/push, `git status --short --branch` is clean and synced.

## Safe wording

- “This is a Sonic-Forage proof hub and operator path.”
- “The site contains manual review assets, verifier receipts, proof docs, videos, manifests, and closed-gate runbooks.”
- “No public posting, upload, stream start, outreach, payment link, invoice, revenue claim, OpenAI affiliation claim, dataset release, GPU job, training run, secret exposure, or cron mutation is part of this first click.”

## Do-not-say lines

- Do not say revenue has been earned unless a verified payment exists.
- Do not say Sonic-Forage is affiliated with OpenAI.
- Do not say the stream, YouTube upload, X post, dataset release, training run, or buyer outreach happened.
- Do not imply hidden live endpoints or customer results.

## Failure recovery

- If the Pages site looks stale, open `/index.html?cb=<commit-sha>` and the JSON manifest directly.
- If the verifier fails, stop the demo and read the failing path before making claims.
- If a tab exposes private local paths or tokens, close the tab and restart the share with only the static proof hub visible.

## Post-demo cleanup

- Close all proof tabs that are no longer needed.
- Do not leave shell history showing secret-bearing commands.
- Record any human-approved next action in a tracked doc before acting.

## Proof paths

- `docs/index.html`
- `docs/launch/PROOF_HUB_START_HERE.md`
- `docs/data/proof-hub-start-here.json`
- `docs/reports/LAUNCH_PROOF_INDEX.md`
- `docs/data/launch-proof-index.json`
- `docs/reports/STATIC_SURFACE_VERIFICATION.md`
- `scripts/verify_site.py`

## Closed gates

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

## Blocked without approval

- Posting or scheduling X/social copy.
- Uploading YouTube videos, captions, Shorts, or thumbnails.
- Starting a Space, livestream, stream supervisor, or recording.
- Sending outreach, DMs, emails, forms, invoices, or payment links.
- Publishing or changing visibility of datasets or private media.
- Starting GPU, paid API, model download, or training work.
- Claiming revenue, affiliation, customer results, or live external integrations.
- Creating, updating, deleting, or chaining cron jobs.