How It Works — Box Commons

Phase 1: Frictionless Integration

BC-Certification requires zero new hardware in your rack room. Box Commons integrates directly at your streaming encoder or via standard XML/UDP metadata exports from your existing automation software.

Whether you use WideOrbit's XML Event Drivers, RCS Zetta's Now Playing Export, or Rivendell's BWF metadata parsing, our protocol works identically to how you currently send Now Playing data to your website or RDS encoder. If your automation system can export standard metadata, you can implement BC-Certification.

For your Chief Engineer The metadata injection occurs at the encoder or via standard XML/UDP exports from your automation system. It never touches the primary audio processing chain. Think of it as another PAD data stream — it operates in parallel with your existing RDS/PAD workflows.

Supported Automation Systems

System	Integration Method	Notes
WideOrbit	XML Event Drivers	Standard TCP port routing; same config as Now Playing exports
RCS Zetta	Now Playing Export	CSV/XML metadata feed; no software modification required
Rivendell	BWF Metadata Parsing	Open-source; direct integration with existing BWF imports
PlayoutONE	XML/UDP Export	Standard metadata pipeline; background operation
AudioVault	XML/UDP Export	Legacy systems supported via standard export protocols
Other	XML, UDP, or CSV	Any system with standard metadata export capability

Streaming Providers

BC-Certification works with your existing streaming infrastructure. Whether you stream via Icecast, Triton Digital, Securenet Systems, Futuri, or any standard streaming server, the provenance metadata is embedded at the encoder level before it reaches your CDN.

Phase 2: Cryptographic Protection

Once integrated, your live audio stream and archives are embedded with an imperceptible, cryptographically signed manifest utilizing the open C2PA (Coalition for Content Provenance and Authenticity) standard — the same provenance technology already being built into professional broadcast equipment by Sony, Canon, and Nikon.

How it protects your stream

For live streams, BC-Certification applies a soft binding that authenticates media segments on the fly, embedding provenance data into each segment without interrupting the audio feed. For archived content, a hard binding hash creates a tamper-evident seal.

This digital watermark acts as a machine-readable "No Trespassing" sign for AI bots. If a tech platform scrapes your stream, the manifest:

Proves legal ownership of the audio content
Explicitly denies AI training consent in a machine-readable format
Creates an irrefutable evidentiary chain if you need to pursue legal action
Survives re-encoding through imperceptible acoustic watermarking

Plain English If someone strips the metadata, the cryptographic chain breaks. This immediately flags the content as tampered with when verified by any provenance scanner — proving unauthorized extraction occurred.

Phase 3: Automated Compliance

BC-Certification operates entirely in the background, ensuring zero interference with your existing regulatory and licensing obligations:

SoundExchange: No impact on your Reports of Use (ROU), minimum fee payments, or digital performance royalty logs. Track durations, ISRCs, and performance complements remain untouched.
ASCAP/BMI/SESAC: Your music licensing logs and reporting workflows operate independently of BC-Certification.
FCC EAS: Emergency Alert System encoding and forwarding are completely unaffected. BC-Certification does not touch your EAS hardware chain.
OPIF: While the FCC does not currently require provenance technology in your Online Public Inspection File, BC-Certification positions your station ahead of emerging AI disclosure mandates in political advertising.

The Bottom Line Your daily operations remain untouched. Your logs stay clean. Your SoundExchange payments don't change. Your EAS chain isn't affected. The only thing that changes is that your intellectual property becomes cryptographically protected.

What to Expect

Register your station — Provide your call letters and automation system. Takes two minutes.
Receive your integration guide — We send configuration documentation specific to your automation software within 24 hours.
Your engineer deploys — A standard metadata export configuration. No on-site visit required. Most stations complete setup in under an hour.
Verify and certify — We confirm your stream carries the BC-Certified manifest and issue your station's certification.

How BC-Certification Works for Your Station