Accountability begins before the artifact travels.
Traditional digital flow often separates the artifact from the context around who participated, how it was created, and what history followed. Northlight keeps those elements connected so continuity can travel forward with the artifact.
VCSI, VeriShield Confidence-State Infrastructure, uses confidence states to summarize the available evidence supporting media’s recorded origin and history. It makes missing context visible so reviewers can decide whether to proceed, request more evidence or escalate.
Compare the difference between a conventional artifact flow and a Northlight accountability flow.
The final file rarely tells the whole story.
A person looking at digital media can usually see what arrived. They may not be able to see who stood behind it, what happened at origin, or what happened afterward.
Captured media and synthetic media begin differently.
CaptureShield
CaptureShield begins at first-party creation: a verified operator, relevant capture conditions, the capture event and the artifact are bound at origin.
AuthorShield
In development: AuthorShield is designed to let a verified human accept accountable ownership and declare the extent of synthesis.
Shared infrastructure. Four application modules.
VTR, the VeriShield Trust Registry, provides participant identity and authorization history. PML, the Portable Mutation Ledger, preserves recorded events and changes. These shared systems support VeriShield Hardware, CaptureShield, AuthorShield and OnAirShield. CaptureShield is Northlight’s current licensing focus.
VeriShield Hardware
Designed to support trust-critical execution in an enabled device.
CaptureShield
Designed to bind a verified operator, capture event and artifact at origin.
AuthorShield
In development: AuthorShield is designed to let a verified human accept accountable ownership and declare the extent of synthesis.
OnAirShield
In development: designed to carry confidence signaling into live and broadcast workflows.
Confidence states expose gaps in the available recorded evidence. A reviewer can inspect supporting origin and history records, then proceed, request more evidence or escalate.
Architecture describes the intended responsibilities. Implementation and release status depend on integration, enabled-device evidence and validation; membership does not imply commercial availability. CaptureShield is Northlight’s current licensing focus. The broader portfolio remains subject to development, validation and commercial priorities.
The architecture is designed to ingest C2PA provenance when available. CAWG identity assertions can supply human or organizational identity within C2PA provenance. Northlight’s integration remains subject to implementation and validation; completed production validation is not claimed.
A later reviewer can inspect more than the final file.
Context can persist instead of resetting every time media changes hands. The everyday surface can stay legible while deeper evidence remains available for expert review.
A capture event or accountable declaration creates the initial context.
The media enters downstream products, workflows and handoffs.
Relevant changes can remain part of the reviewable record.
The person sees a human-readable surface and can go deeper when needed.
The architecture serves the person making the decision.
Northlight does not remove human judgment. It is designed to make important context easier to carry forward and easier to inspect.
What the architecture provides.
Evidence context
Available origin and history evidence informs a bounded confidence state.
Accountable origin
CaptureShield is designed for first-party capture within a supported workflow.
Participant history
VTR provides participant identity and authorization history.
Reviewer judgment
Missing context remains visible so the reviewer can choose the next action.
Want to understand where this architecture fits inside an existing workflow?
Talk to Northlight about CaptureShield, technical diligence, or the broader accountability architecture.