DPO Radio

Reading Audit Lineage

Overview Image

Why Reading Audit Lineage Matters

When a regulatory inspector asks "what did the AI say about this DPIA?", the customer needs more than a chat transcript. The inspector wants the full lineage — which record the assistant was looking at, which regulatory packs it had access to, which tool calls it made, which citations came back, what got drafted, what got approved.

The audit lineage view assembles all of that automatically. The audit lead opens the view from any AI-touched record and walks the chain from the originating call through every committed downstream change.

How It Works

Open From Any AI-Touched Record

The lineage view is reachable from any record-bearing surface where Forseti has touched the record — DPIAs, RoPA activities, contracts, vendors, incidents, rights requests, governance documents, controls.

Filter Chips

Source (chat, workflow, MCP, scheduled), persona, time window, requesting key prefix. Filters combine for deep drill-down.

Per-Event Detail

Each event in the lineage shows the tool name, the arguments (where appropriate), the citation outcome, and the resulting state change.

Cross-Module Trace

The view follows the chain across modules — for example, a DPIA chat that called regulatory search, generated a task, attached evidence, and triggered a workflow run carries the cross-module trace inline.

Tamper-Evident Anchor

The same chain-of-custody anchor that protects every other audit event in the platform protects every Forseti event. The proof tap is nightly and tamper-evident.

The Difference

Graphic Image

Without an Audit Lineage View

Graphic Image

With Forseti Audit Lineage

IconAI-touched records do not carry visible provenance.
IconPer-record lineage view stitches every AI event end to end.
Icon"What did the AI say about this?" requires reconstruction across systems.
IconFilter chips isolate source, persona, time window, key prefix.
IconTamper-evident verification of the audit chain is not available.
IconTamper-evident anchor verifies the chain.

Built for Auditable AI

Build For Image

The lineage view is read-only and immutable. No event is silently removed; rejected suggestions, declined approvals, and expired pending writes all surface.

Build For Image

The chain-of-custody anchor is the same anchor that protects every other audit event in the platform. The proof tap is nightly.

Build For Image

Filter chips do not hide events; they isolate the requested subset. Every event remains walkable when the filters clear.

Overview Image

Inspect the Review Record

Follow which playbook informed the chat and which sources fed the workflow. For a run with a documented review, inspect what the reviewer sampled and decided. Use Verifying Quotes and Drafts to follow the source check and reviewer challenge.

Background Image

See Reading Audit Lineage in Action

Ready to see a DPIA's full AI lineage walked end to end with filter chips? Request a personalised demo.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Next Steps

Icon Image

Start a Compliance Pilot

Run a 30-day pilot and walk the audit lineage with your internal audit lead.

Icon Image

Discuss Your Compliance Needs

Talk to our team about how the lineage view fits your existing inspection-readiness posture.

Frequently Asked Questions About Reading Audit Lineage

Any record-bearing surface where Forseti has touched the record. The lineage button surfaces on records with AI activity.

Source, persona, time window, requesting key prefix. Filters combine for deep drill-down.

Yes. The lineage view is comprehensive. Rejections, declined approvals, and expired pending writes are all visible alongside accepted events.

Yes. Lineage export runs through the platform's unified export pipeline. The export carries the same events and filter state as the view.

Yes. All tiers — Light, Standard, Enterprise — have access to the audit lineage view. The activity you can see depends on the features used and the records you can access.