# Proof Hub Demo Scorecard

Status: `proof_hub_demo_scorecard_manual_review_only_closed_until_human_yes`
manual_review_required=true

Canonical namespace: `Sonic-Forage`
Canonical proof hub: <https://sonic-forage.github.io/afterparty-forge-explainer-site/>
Canonical source repo: <https://github.com/Sonic-Forage/jimsky-afterparty-entity-forge>
Canonical private HF dataset: `Sonic-Forage/jimsky-afterparty-logo-seed`

This is a manual review scorecard for an awake operator who wants to decide whether the proof hub is ready to show in a screen-share or private demo. It is not outreach, not a public post, not a stream script, not a checkout page, and not a claim that revenue, affiliation, upload, or training happened.

## Exact human approval question

Do you approve using this Sonic-Forage proof hub demo scorecard during a manual private review, with no posting, outreach, upload, stream, recording, payment, dataset release, GPU/training, secret exposure, or cron mutation?

## Preflight commands

Run from the repo root:

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

Expected highlights:

- `VERIFY OK afterparty explainer site`
- `STATIC SURFACE OK` appears through the aggregate verifier
- `git diff --check` prints no whitespace errors
- Canonical remote points at `Sonic-Forage/afterparty-forge-explainer-site`

## 60-second score path

1. Open the canonical Sonic-Forage Pages URL and say: "This is a proof-over-hype hub, not an auto-launch."
2. Show `Launch proof index` and confirm every allowed claim maps to a repo-local proof path.
3. Show `Wake report readiness` and confirm the final report command set is visible.
4. Show `Manual X thread drafts` and say they are copy/paste only, not posted or scheduled.
5. Show `Stream-ready loop` and say it is review-only media, not a live broadcast.
6. Show `Dataset catalog review` and say the HF namespace remains private and manual-release-only.
7. Stop and ask for exactly one approved next action.

## Scorecard

| Criterion | Pass condition | Proof path |
| --- | --- | --- |
| Canonical namespace | All public links and manifests point at Sonic-Forage | `docs/data/site-manifest.json` |
| Verifier readiness | Aggregate verifier passes before any demo claim | `scripts/verify_site.py` |
| Proof claim support | Launch claims map to local evidence paths | `docs/reports/LAUNCH_PROOF_INDEX.md` |
| Awake report discipline | Final report checklist requires commands and non-claims | `docs/reports/WAKE_REPORT_READINESS_CHECKLIST.md` |
| Social safety | X drafts are manual-post-only and approval-gated | `docs/social/X_THREAD_DRAFTS.md` |
| Stream safety | Stream rehearsal and loop packs are manual-run-only | `docs/streaming/STREAM_REHEARSAL_CHECKLIST.md` |
| Dataset safety | Private logo-seed catalog is release-gated | `docs/dataset/DATASET_CATALOG_REVIEW.md` |

## Closed gates

- public_posting=false
- outreach=false
- paid_promotion=false
- youtube_upload=false
- publishes_stream=false
- records_audio=false
- uploads_private_media=false
- auto_payment_enabled=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 an X thread, reply, quote, DM, or Space.
- Starting a livestream, OBS/RTMP push, recording, or rebroadcast.
- Uploading YouTube media, captions, private media, or datasets.
- Creating checkout/payment links, invoices, wallets, domains, or paid accounts.
- Claiming revenue, OpenAI affiliation, live customers, public launch, or training results.
- Starting GPU jobs, paid APIs, model downloads, training, or cron changes.
- Revealing secrets, `.env` values, tokens, stream keys, buyer info, or private logistics.

## Do-not-say lines

- Do not say "we made revenue" unless a verified payment receipt exists.
- Do not say "OpenAI-backed" or imply affiliation.
- Do not say "the stream is live" unless an awake operator explicitly started and verified it.
- Do not say "the dataset is public" unless the HF visibility and approval were verified.

## Cleanup after review

Close private tabs, clear terminal scrollback if secrets were nearby, stop any local preview process started by a human, and leave the repo with `git status --short --branch` clean before reporting.