Forensic watermarking architecture, mapped end to end.
Trace how protected media, session context and detection evidence connect across one reference topology.
One protected stream. Three operating planes.
Media plane
Synchronized A/B media variants remain aligned through processing and packaging. The delivery layer emits one coherent, session-specific stream to the player.
Session and control plane
An agreed session reference provides the context used to build and later resolve the delivered A/B sequence.
Evidence and response plane
A suspect sample is analysed, its sequence is recovered and the matched session reference is returned through the customer-facing detection interface.
What must remain true at runtime.
A/B variants remain aligned
Processing and packaging must preserve equivalent timing and media structure.
The session reference remains resolvable
The selection context must stay associated with the relevant playback lifecycle.
Selection remains isolated between sessions
Manifest, segment and cache behaviour must not mix session-specific sequences.
The player receives one coherent stream
A and B are not delivered as two separate player-facing streams.
Identification and enforcement remain separate
Vestigit produces a technical attribution result. The final operational action is executed in the agreed customer workflow.
What crosses each connection.
| Connection | Carries | Architectural purpose |
|---|---|---|
| Embedder → media processing | Synchronized A/B media variants | Preserve complementary marked states through delivery |
| Session Adapter → Mixer / Mapping | Session reference and selection context | Associate the delivered sequence with its playback session |
| Sample interface → Detector | Suspected unauthorized media sample | Recover the embedded A/B sequence |
| Mapping → Attribution Result | Extracted sequence | Resolve the matching session reference |
| Customer-facing interface → policy workflow | Technical detection result | Support review, revocation, blocking or investigation |
Reference architecture, not deployment prescription.
The diagram defines logical functions and relationships. Component placement, interface protocols and operating policies are aligned to the customer environment during solution design.
Map this reference architecture to your stack.
Bring your encoder, packager, origin, CDN and session flow. We’ll map the logical model to your target environment.