Routing & Resilience
Provenance
Gateway-level C2PA signing and watermarking of generated media is on the roadmap. Today, provenance comes from whatever the upstream provider produces — Meridian Blue does not add or strip C2PA manifests.
What works today
Generated media (images, audio) is returned exactly as the upstream provider produced it. If the provider signs its output with a C2PA manifest or embeds a watermark, that signature reaches your client unchanged.
You can record provenance externally by hashing the response body and storing the hash alongside the request ID — but Meridian Blue does not yet add a gateway-level signature.
Roadmap
- C2PA manifest signing — Generated images/audio re-signed at the gateway with a Meridian-controlled certificate, so downstream consumers can verify against a single authority.
- Manifest mirroring — Cryptographic manifests stored in the audit vault for the full retention period.
- Enforcement tokens — JWTs that downstream rendering surfaces must consume to prove the Article 50 disclosure was shown.