10-Minute VO Waveform Consent Receipt Ritual Before July Highlight Reel Mux (BUILD_RECEIPT + vo_consent_metadata)

Why this matters now (July 2026)

Teams are no longer blocked by “do we have the form?” They are blocked by a tighter, byte-level truth: the WAV that actually ships with your July highlight reel must carry the consent fields legal can audit—and it must keep carrying them after your real mux/export chain.

That sounds like an audio detail. In practice it is a release gate that shows up in exactly the same patterns every week:

1. Conversion passes, mux fails (or the reverse). Audacity shows the tags you expect; ffmpeg or an editor handoff strips or moves chunk data; legal reads a deliverable WAV and finds missing/changed fields.
2. Scope/expiry drift. The WAV embed might say consent_scope=highlight_reel, but your consent_log.csv or registry-approved enums say a different surface name—or the consent_expires date is earlier than the publish date.
3. AI VO tag failures look plausible. Model output can generate plausible-but-wrong values (wrong enum strings, missing booleans, inconsistent key casing). ffprobe and duration spot checks stay green even when legal rejects the file.
4. Receipt culture lags proof culture. People report “we copied consent fields” while the only thing BUILD_RECEIPT can trust is receipt paths that point at proof files.

This is why the site moved proof into receipts and receipts into BUILD_RECEIPT. This URL is the missing operational glue: a fast ritual that runs after you convert/generate the WAV, and before you run mux.

This ritual is not a replacement for deeper audits like the ffprobe verification matrix or the metadata survives mux challenge. It is the minimum loop that prevents “green technical receipts, red legal audit” weeks.

What this ritual flips

On a successful pass you should be able to do all of the following with confidence:

• Confirm the WAV consent fields exist (LIST/iXML) for the VO lines in your reel manifest.
• Confirm consent_scope, consent_expires, and opt_out match registry rules and your intent for public vs internal surface.
• Confirm you have the proof artifacts to support the booleans you will promote in BUILD_RECEIPT.json.
• File a ritual receipt JSON that records exactly what you checked (and what you intentionally did not check in 10 minutes).

This is where wav_consent_metadata_ok belongs: only after ritual pass + receipts point at verified proof files.

Non-repetition note: This URL owns the procedural “after conversion, before mux” loop. The VO evening tutorial owns export steps. The reason-codes workflow owns AI tag failure taxonomy. The governance note owns enum/expiry vocabulary. This one stitches them into a 10-minute, repeatable gate.

Who this ritual is for and what you get

Timebox and prerequisites

Time: 10 minutes per reel manifest update (default: 1 pass over the lines you are about to mux). \nEscalation time: 0–20 minutes depending on which lane fails (see the ladder below).

Prerequisites (minimum):

1. consent_log.csv (or the team’s consent row source) for the build/scope window.
2. Your reel’s WAV deliverables in the folder you will mux (the actual files legal reads, not just intermediate Audacity exports).
3. release-evidence/audio/VO_CONSENT_METADATA_RECEIPT.json for at least one VO line (cousin receipt from Lesson 250 pattern).
4. If you generated VO with a model: a filed reason-code receipt from AI Voice QA Reason-Codes (or explicitly mark ai_voice_qa_ok: not_applicable).

Optional but recommended (for faster triage):

• The consent scope/expiry governance registry pinned to the correct build_label.
• The ffprobe verification matrix if you have more than a handful of lines or you have any drift history.

Non-repetition anchor

This URL does one job: provide a repeatable, timeboxed gate after you convert/generate the WAV and before you run mux.

• The VO evening tutorial owns export/pin settings.
• The ffprobe matrix owns systematic clock drift across manifests.
• The mux challenge owns post-mux survival under your real command.
• The muxed-by-receipts opinion owns the “done means artifacts” culture.

This one stitches them into a 10-minute ritual.

The 10-minute ritual (after conversion, before mux)

Treat this like a release checklist you can run when the team is tired. The goal is not to prove everything perfectly in 10 minutes. The goal is to prevent the common failure class where:

technical proof looks green, but the consent bytes you actually ship are wrong.

The ritual gates (R1–R6)

Minute-by-minute (10 minutes)

0:00–1:00 — R1 Manifest lock

1. Copy your reel manifest’s VO lines into a single working list called reel_manifest_vo_locked.csv.
2. Ensure it uses the same asset_id values you will use to pick WAV deliverables.

Pass rule: If any WAV in the folder does not map to an asset_id in the manifest lock, do not include it in the ritual pass. You are auditing what you mux, not what happens to be in a folder.

1:00–3:00 — R2 Field presence spot-check (LIST/iXML)

Pick two lines from your manifest lock:

• one near the start of the reel (or earliest timestamp), and
• one near the end of the reel (or the line most likely to have been trimmed/padded).

For each selected WAV, read embedded fields (RIFF/LIST or iXML) and confirm all four keys:

• consent_record_id
• consent_scope
• consent_expires
• opt_out

Pass rule: All keys exist and can be parsed as strings/booleans consistently (no casing drift).

Fail rule: If keys are missing or empty, do not start a “second mux” loop. Route to:

• AI voice reason-codes lane (G2_EMBED_FAIL or G3_CONVERSION_STRIP) when the origin is AI/generated/export,
• or the VO export tutorial lane if you are missing embeds due to an export preset mismatch (VO evening tutorial).

3:00–5:00 — R3 Scope + expiry + opt_out

For each checked line:

1. Confirm consent_scope matches your registry-approved public surface (default: highlight_reel).
2. Confirm consent_expires is on or after the planned reel publish date (use your team’s buffer rule).
3. Confirm opt_out is false.

Pass rule: All three are aligned for both spot-check lines.

Fail rule: The fix is governance/intent, not ffmpeg:

• If scope or expiry disagree with your registry vocabulary, follow consent scope and expiry governance (#20).
• If opt_out=true for any manifest line you plan to mux into public, that line must be removed from the public manifest.

5:00–7:00 — R4 Receipt pointer sanity

Open (or locate) release-evidence/audio/VO_CONSENT_METADATA_RECEIPT.json.

Check:

• it contains the asset_id / consent_record_id rows you are about to mux,
• it matches the correct build_label window you will put into BUILD_RECEIPT.json,
• and it is not a stale receipt from an earlier playtest wave.

Pass rule: The receipt you will cite is the same evidence file you will reference in BUILD_RECEIPT.

Fail rule: Re-file the cousin receipt. This is the recurring incident class where people flip booleans early because “the sheet says it’s OK.”

7:00–8:00 — R5 Consent boolean intent (what you will flip)

Before any mux command:

• Write down (in your ritual receipt draft) the boolean values you will promote, based strictly on proof.

At minimum for July public facilitator VO reels:

• wav_consent_metadata_ok=true only if R2/R3/R4 passed.
• ai_voice_qa_ok is true only when you have an AI reason-codes receipt showing lines_fail=0 (or set to not_applicable if you are not using AI-sourced generation).

This is a culture gate: it prevents “we think it’s fine” and ensures BUILD_RECEIPT matches bytes shipped.

8:00–10:00 — R6 Ritual receipt filed

Create release-evidence/audio/vo_waveform_consent_ritual_receipts/vo_waveform_consent_ritual_receipt_v1.json (path may vary by team convention).

At minimum, record:

• ritual timestamp,
• manifest lock reference,
• build_label,
• pass/fail for R1–R6,
• proof file paths you checked.

Once the receipt exists, you may schedule the mux and later run deeper audits like mux survival challenge.

When you must escalate (even if R1–R6 “look” green)

Escalate immediately to batch audits when any of these is true:

• Your reel has more than 5 VO lines and you are seeing any drift history.
• You are converting multiple sample rates (e.g. 44.1k sources into a 48k July spine).
• You touched any mux/export parameters since last week.

Escalations:

• Duration drift: run ffprobe matrix (D-codes).
• AI tag failures: re-run reason-code triage and re-prompt/regenerate only on G1.
• Post-mux survival: run the mux survival challenge before final upload.

The receipt you file (JSON + evidence paths)

This ritual receipt is what makes the 10-minute gate auditable. It is also what enables the Thursday BUILD_RECEIPT row review loop to catch stale booleans before a partner upload.

File name and default location

Recommended path:

release-evidence/audio/vo_waveform_consent_ritual_receipts/
  vo_waveform_consent_ritual_receipt_v1.json

Recommended naming rule:

• one receipt per build_label per reel batch,
• keep it immutable after you schedule a mux night.

Receipt schema (drop-in template)

{
  "schema": "vo_waveform_consent_ritual_receipt_v1",
  "ritual_id": "vo_ritual_2026-07-01_buildlabel_rc1",
  "build_label": "playtest-july-2027-rc1",
  "reel_manifest_lock": "release-evidence/audio/reels/2026-07-reel/reel_manifest_vo_locked.csv",
  "checked_lines": {
    "count": 2,
    "asset_ids": ["facilitator_vo_01", "facilitator_vo_07"]
  },
  "gates": {
    "R1_manifest_lock": "pass",
    "R2_field_presence_spot_check": "pass",
    "R3_scope_expiry_opt_out": "pass",
    "R4_receipt_pointer_sanity": "pass",
    "R5_boolean_intent": "pass",
    "R6_ritual_receipt_filed": "pass"
  },
  "evidence_paths": {
    "vo_consent_receipt": "release-evidence/audio/VO_CONSENT_METADATA_RECEIPT.json",
    "consent_governance_receipt": "release-evidence/governance/consent_scope_governance_receipt_v1.json",
    "optional_ai_reason_codes_receipt": "release-evidence/audio/ai-voice/ai_voice_qa_reason_codes_receipt_v1.json",
    "spot_check_readout": "release-evidence/audio/vo_waveform_consent_ritual_receipts/spot_check_readout.txt"
  },
  "public_vo_mux_allowed": true,
  "public_reel_reason": "R2/R3 aligned; receipt pointers matched build_label; opt_out=false",
  "escalation_action": null,
  "timestamp_utc": "2026-05-27T19:10:00Z"
}

Beginner rule: When a gate fails, set public_vo_mux_allowed: false and keep escalation_action non-null. Do not delete failed receipt drafts—auditors want a paper trail.

How this plugs into BUILD_RECEIPT

At minimum, the ritual flips the booleans and receipt pointers that matter to promotion:

{
  "wav_consent_metadata_ok": true,
  "wav_consent_ritual_receipt": "release-evidence/audio/vo_waveform_consent_ritual_receipts/vo_waveform_consent_ritual_receipt_v1.json",
  "vo_consent_receipt": "release-evidence/audio/VO_CONSENT_METADATA_RECEIPT.json",
  "consent_governance": "release-evidence/governance/consent_scope_governance_receipt_v1.json",
  "ai_voice_qa_ok": true
}

Then Thursday BUILD_RECEIPT row review diff checks that the booleans still describe the same bytes you tested on Wednesday smoke.

What you intentionally do not prove in 10 minutes

This ritual is a gate, not a full forensic audit. In 10 minutes you should not claim:

• perfect coverage of every VO line’s LIST/iXML fields,
• sample-rate correctness for every asset (that belongs in the ffprobe matrix lane),
• post-mux survival for the exact deliverable extraction path (that belongs to the mux survival challenge).

Instead, you claim “enough spot-check evidence + receipt pointers to promote only when the risk is bounded.”

Receipt triad (ritual + tutorial + proof files)

The minimum triangle for July public facilitator VO reels:

If you are building an automated pipeline, generate the ritual receipt as part of your “pre-mux” step and only then run mux.

Escalation ladder (what to do when it fails)

The ritual fails for specific families of problems. Use the ladder so the team does not bounce between ffmpeg and AI vendors for the wrong reason.

Failure-to-lane map

“Do we rerun ffmpeg?”

Policy:

• If the ritual fails on fields (R2) or meaning (R3), ffmpeg retries are usually waste. ffmpeg can mux, but it cannot decide your registry-approved enums.
• If the ritual passes and later drift appears, route to:
  • ffprobe duration matrix for clock drift,
  • then mux survival challenge for chunk survival.

In other words:

The ritual prevents the wrong bug hunt. Cousin audits solve the fine-grain proof problems.

Reason codes for ritual receipt (small but important)

When you fail R2 or R3, record an escalation code inside the ritual receipt, for example:

{
  "escalation_action": {
    "primary": "R2_EMBED_MISSING_KEYS",
    "secondary": "G2_EMBED_FAIL"
  }
}

This helps producers coordinate with audio leads and legal without guessing which lane is owned.

The “public reel blocked” rule

Default policy:

• If public_vo_mux_allowed is false for the ritual receipt, keep the affected VO lines out of the public reel manifest.
• It is acceptable to keep them in an internal rehearsal manifest (internal_only) while you fix the lane.

Relationship to design and readability

R4 design timing (disclaimer readability on the video strip) assumes the VO WAV consent fields are correct. If scope/expiry is wrong, the design gate can still pass while legal fails.

So the escalation ladder is intentionally semantic first:

1. Consent truth (fields + scope + opt_out),
2. then readability truth (video strip and safe-zones),
3. then clock truth (ffprobe matrix),
4. then survival truth (mux challenge).

Beginner path vs working dev path

Same ritual. Different effort level.

Beginner path (one evening, one reel, two spot checks)

If you are a VO editor or audio lead doing this for the first time:

1. Pick the two WAV lines you are most likely to export incorrectly.
2. For each, verify the four consent keys exist in the WAV bytes:
   • consent_record_id
   • consent_scope
   • consent_expires
   • opt_out
3. Confirm:
   • consent_scope matches your public surface (default highlight_reel),
   • consent_expires is not earlier than your intended publish window,
   • opt_out=false.
4. Locate VO_CONSENT_METADATA_RECEIPT.json and confirm it is for the same build_label you will write into BUILD_RECEIPT.
5. File vo_waveform_consent_ritual_receipt_v1.json and set public_vo_mux_allowed accordingly.

You are done when your BUILD_RECEIPT booleans point at proof files, not at “we think it worked.”

Beginner time estimate: 10–20 minutes for the first reel; 10 minutes after your team reuses the receipt filenames.

Beginner “first failure” drills

These drills are how you train your team not to waste time:

• If a key is missing in WAV bytes, stop and follow AI Voice QA reason-codes for G2_EMBED_FAIL / G3_CONVERSION_STRIP instead of re-running mux.
• If scope/expiry mismatches your intent, stop and follow governance #20 instead of editing tags by hand.

Working dev path (multi-line reels, manifest automation, fewer human clicks)

For multi-line reels (or when you have drift history), run the ritual as a batch:

1. Generate or lock reel_manifest_vo_locked.csv (R1).
2. Run an automated inspector that extracts consent fields from each WAV:
   • ensure LIST/iXML keys exist and match the consent log row (consent_record_id join),
   • verify scope/expiry/opt_out values (R3).
3. Create the ritual receipt JSON with:
   • counted lines checked,
   • gate pass/fail,
   • evidence file paths.
4. Only then flip BUILD_RECEIPT:
   • wav_consent_metadata_ok=true,
   • and the ritual receipt path reference.

Rule for scaling up: When you exceed 5 VO lines or you touched mux/export parameters since last week, treat this ritual as “R2/R3 minimum” and escalate to:

• ffprobe duration matrix for clock drift,
• mux survival challenge for chunk survival.

Relationship to Lesson 250 and the VO receipt

This ritual is how you decide when to promote:

• wav_consent_metadata_ok in BUILD_RECEIPT,
• based on receipt proofs in the Lesson 250 pattern.

If you want the export steps that generate the underlying WAV consent fields, use the VO evening tutorial.

FAQ

Is this ritual redundant with the ffprobe matrix

No. The ffprobe verification matrix in #19 owns clock drift and sample-rate truth across all files. This ritual owns the semantic truth that LIST/iXML consent fields are present, have correct scope/expiry, and can support wav_consent_metadata_ok.

Does this replace the mux survival challenge

No. The mux survival challenge proves chunks survive your real mux/export chain. This ritual is the pre-mux gate that ensures you are not running mux on the wrong bytes.

What if only duration is wrong

If R2/R3 pass but your later duration spot-check fails, route to the ffprobe matrix. Duration failures are reason-coded in D-lane codes—not G-lane tag QA.

What if a manifest line has opt_out=true

Remove that line from the public manifest. opt_out=true is an immediate revocation regardless of consent_expires. Do not “fix” it by widening tolerance or re-muxing.

How do we capture evidence in 10 minutes

File the ritual receipt JSON and record the proof file paths you checked:

• VO_CONSENT_METADATA_RECEIPT.json (cousin receipt),
• any spot-check readout file you generate (optional but useful),
• and the ritual receipt itself under release-evidence/audio/vo_waveform_consent_ritual_receipts/.

Then Thursday row diff should only confirm receipt paths and booleans, not hunt evidence.

Do interns or junior editors handle this

Yes, with the beginner path. They should not change tags by hand; they should only run the spot-check and file the ritual receipt using the template. If R2/R3 fails, escalate to the lane owner using the escalation ladder in this article.

How does this relate to the VO evening tutorial

The VO tutorial in #VO evening tutorial teaches the export/pin settings that create the LIST/iXML fields. This ritual decides whether to promote the booleans that BUILD_RECEIPT uses after export—and before mux.

Can AI-generated VO use this ritual

Yes. If you generate VO with an AI tool, run the AI tag QA reason-codes workflow first (G1–G6) and require its receipt to show lines_fail=0. Then run this ritual so the final WAV bytes still match registry enums and opt_out rules.

What is the “minimum” receipt set for public reels

Minimum triangle:

1. VO tutorial/export discipline (so the WAV has fields to check),
2. This ritual receipt JSON (so you can timebox and audit the pre-mux gate),
3. Cousin proof receipts (governance #20, ffprobe matrix #19, mux survival challenge).

If you can’t produce the triangle, keep the reel internal.

When should the team re-run the ritual

Re-run for any change that could affect fields:

• you regenerated VO or re-embedded fields,
• you changed mux/export parameters,
• you migrated consent vocabulary (form_version / registry bump),
• or you detected any earlier drift history.

Treat it like a recurring “after conversion, before mux” release habit.

If you only remember one line: check WAV consent fields and registry-scoped eligibility in 10 minutes, file vo_waveform_consent_ritual_receipt_v1.json, and only then flip wav_consent_metadata_ok in BUILD_RECEIPT.

Final reminder: July reels do not fail on “vibes.” They fail when wav_consent_metadata_ok flips on BUILD_RECEIPT without bytes that actually carry valid WAV consent fields through your real mux chain.