# Stream Loop Local Health Receipt

**Status:** `stream_loop_local_health_receipt_manual_review_only_closed_until_human_yes`  
**Scope:** local proof-path inspection only; not a livestream, not an OBS/RTMP/Kick action, and not proof that a live platform session is healthy.

This receipt compresses the existing Sonic-Forage stream-loop proof paths into a short awake-operator check. It is useful when the proof hub already has generated bumpers and a committed master loop, but the operator needs a reminder to separate **local media health** from **remote RTMP/session/key health**.

## What this proves

- The repo contains a committed stream-ready master loop manifest.
- The proof hub links to the existing stream-ready loop and recent owned/generated bumper manifests.
- The aggregate site verifier can check the static proof surface without starting providers.
- Closed gates remain visible before any human-approved stream operation.

## What this does not prove

- It does **not** prove Twitch/Kick/RTMP is live.
- It does **not** test or print stream keys.
- It does **not** restart FFmpeg, OBS, Spaces, or any pusher.
- It does **not** confirm real Kick chat integration.
- It does **not** approve public posting, uploads, payments, GPU jobs, paid APIs, training, or cron mutation.

## 60-second local check

1. Run the static verifier:
   ```bash
   PYTHONDONTWRITEBYTECODE=1 python3 scripts/verify_site.py
   ```
   Expected highlight: `VERIFY OK afterparty explainer site`.

2. Parse the local receipt and stream manifests:
   ```bash
   python3 -m json.tool docs/data/stream-loop-local-health-receipt.json >/dev/null
   python3 -m json.tool docs/streaming/stream_ready/master_loop_manifest.json >/dev/null
   python3 -m json.tool docs/data/stream-ready-loop.json >/dev/null
   ```

3. Confirm proof paths exist before talking about media health:
   - `docs/streaming/stream_ready/intergalactic_radio_master_loop_720p30_48k.mp4`
   - `docs/streaming/stream_ready/master_loop_manifest.json`
   - `docs/streaming/operator_drops/oracle_poem_interrupt_010_receipt_orbit.json`
   - `docs/streaming/operator_drops/build_wall_status_card_011_gate_check.json`

4. Optional media-only inspection after human approval to inspect the local MP4:
   ```bash
   ffprobe -v error -show_format -show_streams docs/streaming/stream_ready/intergalactic_radio_master_loop_720p30_48k.mp4
   ```
   This command reads the local file. It must not be bundled with any stream start/restart.

## Safe wording

- "Local stream-loop media proof paths are inspectable in the repo."
- "The receipt does not prove a live RTMP/Kick session is healthy."
- "Any stream start, restart, OBS action, or platform publish still needs an awake human yes."
- "If RTMPS refuses reconnects, avoid duplicate pushers and rotate/reset keys outside the repo."

## Do not say

- "The stream is live because this receipt exists."
- "Kick chat is connected."
- "RTMP credentials were checked."
- "A pusher was restarted automatically."
- "Public posting or upload is approved."

## Closed gates

`public_posting=false` · `outreach=false` · `payments=false` · `stream_start_or_restart=false` · `obs_or_rtmp_action=false` · `private_media_upload=false` · `hf_publication=false` · `gpu_jobs=false` · `paid_api_jobs=false` · `model_downloads=false` · `training=false` · `voice_to_shell=false` · `chat_to_shell=false` · `cron_mutation=false` · `secret_exposure=false`

## Human approval question

Do you approve using this local health receipt to manually inspect stream-loop proof paths before any separate approved RTMP/OBS/Kick action?
