Skip to content

B2B workflow simulator

The exact YouTube Content ID sequence for generated audio

Six ordered steps from sealed prescription to claim resolution, with the payload you send at each stage. Pick a saved session to see the simulator run against its real identifiers.

AI-GENERATED AUDIOComposed by a generative model from your physiological data. Not a medical device — fitness guidance only.

FTC 16 CFR §255 · EU AI Act Art. 50

Running on a sample session. Generate and save one to simulate with your own identifiers.

0/6 steps completeA-VO2-14611C3157A5
  1. 01

    Seal the physiological session

    VO₂max.One pipeline · instant

    Before any audio exists, the prescription is written to the append-only audit table. This row is what every later Content ID claim points back to as proof of authorship.

    • Insert the prescription row and capture its hash-chained row_hash
    • Freeze the input set (VO₂max, age, resting HR, target zone)
  2. 02

    Render and watermark the audio

    VO₂max.One pipeline · ~40 s / track

    The renderer embeds the inaudible watermark payload and writes ID3 TXXX frames, including the machine-readable AI-generated disclosure, before the file ever leaves the pipeline.

    • Embed spread-spectrum watermark at −28 dBFS
    • Write ai_generated=true, disclosure_text and physiological_prescription_id into ID3
    • Store audio_sha256 back on the audit row
    id3 write
    TXXX:ai_generated            = true
    TXXX:disclosure_text        = AI-generated audio — VO₂max.One
    TXXX:prescription_id        = rx_14611c3157a5
    TXXX:session_id             = ses_4f7c3547
    WM:payload                  = RX_14611C3157A5:SES_4F7C3547
  3. 03

    Deliver the Content ID reference

    You (CMS partner) · 1–2 h to ingest

    Upload the rendered master as a reference asset in your YouTube CMS, with sound-recording ownership asserted for your territories. Do this BEFORE the public upload so your own video is matched to your own asset.

    • Create the asset and attach the audio reference file
    • Assert 100% sound-recording ownership in all territories you control
    • Set the reference to 'match audio only'
    asset delivery (CMS API)
    POST /youtube/partner/v1/assets
    {
      "type": "sound_recording",
      "customId": "A-VO2-14611C3157A5",
      "metadata": {
        "title": "VO2max.One session ses_4f7c3547",
        "artist": "VO2max.One",
        "customId": "A-VO2-14611C3157A5",
        "notes": "AI-generated; prescription rx_14611c3157a5"
      }
    }
  4. 04

    Attach the usage policy

    You (CMS partner) · instant

    A match policy decides what happens when the reference matches a video. For generated wellness audio the safe default is monetize on your own channels and track (not block) elsewhere, so partner apps are never taken down by your own asset.

    • Match policy: monetize on owned channels, track on third-party
    • Whitelist partner channels to suppress claims against licensees
    • Never set 'block' — it breaks partner playback
    match policy
    policy:
      - condition: { requiredTerritories: [worldwide] }
        action: monetize          # your channels
      - condition: { matchDuration: ">=7s" }
        action: track             # third-party uploads
      whitelist: [ "UC_vo2max_lab" ]
  5. 05

    Publish with an on-platform AI disclosure

    You (uploader) · instant

    YouTube requires the altered-or-synthetic content disclosure in the upload flow, and the FTC expects a clear, unavoidable disclosure for consumers. Set both: the platform toggle and a visible line in the description and player screen.

    • Toggle 'Altered or synthetic content' in the upload checks
    • Add the disclosure sentence to the first line of the description
    • Keep the on-screen AI-generated badge visible in your own player
    description header
    AI-generated audio. Composed by VO2max.One from a physiological
    prescription. Not a medical device — fitness guidance only.
  6. 06

    Monitor claims and resolve disputes

    You + VO₂max.One support · ongoing

    If a third-party library claims your generated track, the audit row is the evidence packet: prescription id, sealed timestamp, watermark payload and reference delivery receipt. Attach it to the dispute.

    • Review the daily claims report for your asset
    • Dispute false claims citing the audit record and watermark decode
    • Release accidental claims your asset raised against licensees
    dispute evidence
    prescription_id : rx_14611c3157a5
    sealed_at       : 2026-08-12T11:22:00.000Z
    asset_custom_id : A-VO2-14611C3157A5
    watermark       : decoded → RX_14611C3157A5
    chain           : verify_audit_chain() → true

Need this wired into your CMS? Submit a partner intake →