Q215 - Audit_and_accountability_lineage_definition_example_and_why_

Q215 — Audit and accountability lineage — definition, example, and why it matters in RAIDT

← RAIDT · Star S7 - Academic Theory and Design Logic · primary item: S7.11 · Audit lineage

C. Theory & Foundation | Ordered by mind-map priority: inner circles first, then operational detail.

Appears in sources
Answer

In RAIDT, audit and accountability lineage means that the framework is explicitly rooted in traditions that require preserved evidence, reviewable trails, answerability for decisions, and a credible route for contesting one use event. The lineage is visible in RAIDT's insistence that governance must be demonstrated through a run-level evidence pack rather than through abstract claims about a model or a policy. It is also visible in the score profile, which expresses governance readiness across the five pillars (Responsibility, Auditability, Interpretability, Dependability, Traceability) and uses anchors 1=missing / 3=partial / 5=audit-ready to specify what adequate evidence looks like.

This matters because generative AI behaviour is shaped at run time by prompts, retrieval, tools, adapter lineage, settings, and review actions. RAIDT therefore treats influence methods as governance interventions, since they alter not only outputs but also what must be preserved for later reconstruction. The audit lineage is what prevents governance from collapsing into compliance theatre: if a run cannot be reconstructed, compared, and challenged, accountability remains weak even when organisational principles sound strong. RAIDT's contribution is to make that accountability operational by treating the run as the unit of governance and by creating a bounded proof object that managers, compliance teams, auditors, and affected users can all inspect for different purposes.

Practical example

A concrete example is a finance workflow that generates an adverse-action explanation for a credit decision. If the customer disputes the explanation, the organisation needs more than a general statement that the model was responsibly deployed. It needs to show the exact prompt structure, the criteria or policy text supplied, the model and tool configuration, the generated explanation, and the human review step that authorised use.

RAIDT packages that information into a run-level evidence pack and renders it visible through a score profile. If the evidence shows recorded criteria, preserved provenance, and a documented review path, the organisation can answer the challenge in a disciplined way. If evidence is missing, the weak pillar scores make that weakness visible instead of hiding it. That is why audit and accountability lineage matters in RAIDT: it turns contestability into an evidence-bearing organisational practice.

Sources in RAIDT papers
Powered by Forestry.md