C0.01 - RAIDT
C0.01 — RAIDT
flowchart LR
A[Background problem:
policy claims, model-level assurance,
limited case reconstruction] --> B[RAIDT framework]
F[Finance, healthcare, public services,
education, enterprise work] --> B
B --> C[Run as unit of governance]
C --> D[Run-level evidence]
D --> E[Evidence pack]
E --> G[RAIDT score profile]
B --> H[Reviewability and contestability]
G --> I[Governance readiness]
H --> I
I --> J[Audit, learning, policy alignment]← Star C0 - RAIDT Core, Definition, Values, Claims and Innovation
Star context: Defines the project identity of RAIDT and anchors the whole mind map around the claim that responsible GenAI governance must be grounded in run-level evidence rather than broad assurance alone.
Definition / background
RAIDT is a run-level evidence framework for the responsible governance of generative AI systems used in organisational work. It defines the governed object not as the model in the abstract and not as policy at the organisational level, but as a specific configured run: one use of a GenAI system for a particular task, at a particular time, in a particular context. In that sense, RAIDT is both the name of the overall framework and the core architectural idea around which the rest of the project is organised.
Conceptually, RAIDT addresses a persistent gap in AI governance. Many governance approaches describe principles, controls, or model properties, but they do not always preserve enough evidence to reconstruct what happened in one material use event. RAIDT responds by making the run inspectable. It asks what was asked, which model or workflow was used, what contextual inputs mattered, what output was produced, what checks or interventions occurred, and what evidence was retained for later review.
This matters because responsible governance of GenAI rarely fails at the level of abstract principle alone; it fails when an organisation cannot explain or defend a specific use. RAIDT therefore sits above and connects C0.02 · Run, C0.03 · Run-level evidence, C0.04 · Evidence pack, and C0.05 · Score profile. The framework turns these parts into a coherent governance method.
RAIDT differs from a generic AI governance framework in four important ways. First, it is centred on run-level evidence rather than policy aspiration alone. Second, it produces practical outputs that can be reviewed and compared. Third, it uses the five RAIDT pillars, Responsibility, Auditability, Interpretability, Dependability, and Traceability, to make governance judgement more explicit. Fourth, it is designed for governance readiness: review, contest, audit, and improvement in organisational settings.
Why this concept matters
RAIDT matters because organisations need a way to govern actual GenAI use, not only models, vendors, or policy statements. Without a framework like RAIDT, governance discussions can remain too high-level to answer the practical question that supervisors, regulators, internal reviewers, and affected stakeholders eventually ask: what happened in this case, and what evidence supports the account?
The concept solves an operationalisation problem. It connects broad responsible-AI commitments with a repeatable evidential method for documenting and assessing use. It also reduces a common confusion between governance of systems in general and governance of specific uses in context. RAIDT shows that a system may be acceptable in principle while a particular run is poorly documented, weakly controlled, or difficult to defend.
If this concept is missing, an organisation may have impressive governance language but weak case-level accountability. That creates risks for audit, challenge handling, policy compliance, service quality, and organisational learning after failures or disputes. RAIDT provides a route from principle to inspectable practice.
Key idea: RAIDT matters because it transforms a single GenAI use from an ephemeral interaction into a structured, reviewable governance object.
What this item explains
- RAIDT defines the overall project object and the logic that ties the whole C0 branch together.
- RAIDT explains why the run, rather than the model alone, is the primary unit of governance in organisational GenAI use.
- RAIDT explains how run-level evidence is collected and assembled into an evidence pack.
- RAIDT explains why a five-pillar score profile is needed to interpret governance quality rather than relying on a single metric.
- RAIDT explains how reviewability, contestability, audit readiness, and organisational learning emerge from evidential structure.
- RAIDT explains how claims about responsible GenAI can be supported with inspectable records rather than assertion alone.
Practical example / likely audience question
Audience question
Is RAIDT simply another responsible AI framework, or does it add something operational that existing policies and documentation do not provide?
Answer
The concern behind the question is that the governance field already contains many principles, checklists, and assurance documents. A supervisor, reviewer, or practitioner may reasonably worry that RAIDT just renames existing good practice. The direct answer is that RAIDT adds an operational layer that many generic governance approaches leave under-specified: it treats each material GenAI use as a reviewable run and requires evidence sufficient to reconstruct that use.
For example, suppose a finance team uses a GenAI assistant to produce an explanation of a quarterly variance for executive review. A generic governance approach may confirm that an approved model was used, that a policy exists, and that staff received training. RAIDT goes further by capturing the prompt or task framing, relevant source context, system configuration, output, timestamp, reviewer action, and the resulting five-pillar profile. That means the explanation can later be reviewed as an accountable event rather than as a vague memory of system use.
RAIDT handles this issue better than a generic AI governance approach because it does not stop at institutional assurance. It creates a structured bridge between use, evidence, judgement, and governance action. That bridge is what allows challenge, reconstruction, and improvement when questions arise.
Practical example in RAIDT terms
Consider a public-sector benefits office using a GenAI tool to draft a case summary for a claimant review meeting. The use case appears efficient, but the governance issue sits at run level: if the summary omits a crucial fact, overstates a risk, or misrepresents supporting evidence, the organisation must be able to reconstruct what happened in that particular interaction.
In RAIDT terms, the run would record the task purpose, user role, prompt, supporting documents supplied to the system, model or workflow version, output generated, any human edits, and the final decision about whether the draft was accepted or revised. The evidence pack would need enough material to show how the summary was produced and how it was reviewed. The most affected pillars would be Responsibility, because human oversight and use conditions matter; Auditability, because the case must be reviewable later; Interpretability, because the reasoning behind the summary should be explainable; Dependability, because consistent drafting quality matters; and Traceability, because the output must be linked to sources and actions.
RAIDT improves governance readiness here by making the case summary a reconstructable event. Instead of relying on policy assurances alone, the office can show how a specific run was performed, what evidence exists, what scores were assigned, and what follow-up action was taken.
Detailed link to RAIDT
This item links to RAIDT in four ways.
First, it defines RAIDT itself as the project's central claim that GenAI governance should be organised around inspectable runs rather than abstract commitments alone.
Second, it establishes why C0.02 · Run and C0.03 · Run-level evidence are foundational rather than secondary concepts.
Third, it shows how C0.04 · Evidence pack and C0.05 · Score profile become the practical outputs through which governance is documented and judged.
Fourth, it links the framework to C0.08 · Core value: reviewability, C0.09 · Core value: contestability, audit readiness, and organisational learning.
RAIDT core definition → Run → Run-level evidence → Evidence pack → RAIDT score profile → Governance readiness
This chain matters because RAIDT is not only a conceptual umbrella. It is the mechanism that turns one GenAI use into evidential material that can support explanation, review, challenge, and improvement.
Link to the five RAIDT pillars
Responsibility
RAIDT strengthens Responsibility by requiring that a run be situated in a role, purpose, context, and review process rather than treated as anonymous system output.
Example evidence / implication:
- Evidence can show who initiated the run, for what task, and under what organisational authority.
- Review records can show whether a human decision-maker accepted, revised, or rejected the output.
Auditability
RAIDT is strongly tied to Auditability because the framework exists to make a specific GenAI use reconstructable and assessable after the fact.
Example evidence / implication:
- A reviewer can inspect the configuration, inputs, outputs, timestamps, and interventions associated with the run.
- The evidence pack can support internal audit, external scrutiny, or post-incident review without relying on recollection alone.
Interpretability
RAIDT supports Interpretability by requiring governance-relevant explanation at the level of use, including how an output was produced, what context informed it, and how it was assessed.
Example evidence / implication:
- Review notes can clarify why an output was considered acceptable, uncertain, or problematic.
- Source linkage or contextual references can help explain the basis of the generated response.
Dependability
RAIDT contributes to Dependability by making consistency, reliability, and control visible across repeated runs rather than assuming stable performance from model claims alone.
Example evidence / implication:
- Comparable score profiles across similar runs can reveal unstable behaviour or control weaknesses.
- Recorded reviewer interventions can show where the system repeatedly requires correction before use.
Traceability
RAIDT is strongly tied to Traceability because it depends on connecting outputs to prompts, sources, configurations, decisions, and subsequent governance actions.
Example evidence / implication:
- The organisation can trace a contested output back to the specific run that produced it.
- The retained record can show how a final artefact, decision, or communication depended on GenAI assistance.
Why this item is more than a generic concept
In general AI governance, a framework may mean a set of principles, risk categories, lifecycle controls, or policy commitments. In RAIDT, the meaning is more operational and narrower in a productive way. RAIDT is a framework that produces inspectable evidence at the level where organisational accountability is usually tested: the concrete use event.
That makes the RAIDT meaning more than a generic concept. It is not just a language for discussing responsibility; it is a method for structuring evidence, scoring governance quality, and supporting later review. The concept becomes operational because it is tied directly to run-level evidence.
Common misunderstanding
Misunderstanding
RAIDT is just a scoring tool for rating GenAI systems.
Correction
The score profile is only one output of RAIDT. RAIDT is the broader governance framework that defines the unit of analysis, specifies what evidence should be captured, and supports review and challenge. For example, if an organisation only kept a five-pillar score without the underlying run details, it would not be following the full RAIDT logic. The score is meaningful because it is grounded in evidence about a specific run.
Boundary and limitation
RAIDT does not prove that a GenAI output is true, fair, lawful, or optimal simply because a run has been documented. It also does not replace sector regulation, domain expertise, human judgement, or broader organisational controls. A well-documented run may still contain a poor answer, a biased framing, or a flawed decision pathway.
The framework depends on disciplined evidence capture, sensible scoping of material runs, and a review process that can interpret the evidence. If logging is incomplete, if staff bypass the workflow, or if reviewers do not act on the findings, RAIDT will be weakened. RAIDT handles this limitation by making gaps visible and by supporting iterative improvement rather than pretending that documentation alone resolves governance risk.
Implementation levels
Manual implementation
A researcher or small team can implement RAIDT manually by defining what counts as a run, capturing prompts and outputs in a structured template, recording review decisions, and assigning a five-pillar profile for significant cases. This is suitable for pilot studies, doctoral fieldwork, or early governance prototyping.
Semi-automated implementation
A semi-automated RAIDT implementation can use templates, form-based metadata capture, workflow checklists, repository structures, and review dashboards to reduce omission and improve consistency. In this mode, evidence collection is partly standardised while human reviewers still interpret the case.
Fully automated implementation
At scale, RAIDT can be implemented through a wrapper, orchestration layer, logging system, or governance pipeline that automatically records run metadata, binds outputs to evidence objects, generates draft score profiles, and routes contested or high-risk cases for review. In this mode, the framework becomes part of the operational infrastructure for enterprise GenAI governance.
Practical use in the RAIDT project
Within the RAIDT project, this item provides the conceptual anchor for explaining the contribution across papers and outputs. In Paper 08 Foundations, it defines the framework and justifies the move from principle-led governance to run-level evidence. In Paper 09 Empirical Validation, it supports the claim that actual organisational uses can be documented and assessed in a repeatable way. In Paper 10 Policy Pathways, it helps articulate how evidence-centred governance can inform implementable oversight models rather than remaining at the level of policy rhetoric.
The item is also useful for sector playbooks, evidence-pack design, scoring-rubric explanation, influence methods, and governance interventions because it gives one stable answer to the question, 'What exactly is RAIDT?' For supervision, viva defence, conference presentation, and journal positioning, it provides the top-level articulation that connects all subordinate concepts without collapsing them into a vague umbrella term.
Key audience questions to prepare for
Q1. Why is RAIDT centred on the run rather than the model?
Because many governance failures become visible only in a specific use context. The run captures the concrete interaction where inputs, configuration, output, review, and consequences meet.
Q2. Is RAIDT intended to replace existing AI governance frameworks?
No. RAIDT is better understood as an operational complement. It gives organisations a way to evidence and assess actual GenAI use within or alongside broader governance arrangements.
Q3. What does RAIDT produce that a normal policy framework does not?
It produces practical run-level outputs: an evidence pack and a five-pillar score profile tied to a specific use event. Those outputs support reconstruction, comparison, and review.
Q4. Can RAIDT work outside high-risk sectors?
Yes. The framework is especially valuable in high-stakes contexts, but the underlying logic also applies to enterprise productivity, education, customer service, and other organisational uses where accountability still matters.
Q5. What is the main innovation claim behind RAIDT?
The main claim is that responsible GenAI governance becomes more reviewable and contestable when the governed object is the run and when governance judgements are tied to retained evidence rather than assertion alone.
Suggested citation concepts to support this item
- operational AI governance for generative AI
- run-level documentation and audit trails for AI systems
- evidence-based AI assurance
- contestability and reviewability in automated decision support
- traceability and provenance in large language model workflows
- socio-technical accountability for organisational AI use
- human oversight in generative AI-assisted work
- model cards versus use-case-level governance documentation
- audit readiness for enterprise AI deployments
- organisational learning from AI incidents and exceptions
Short explanation for presentation
RAIDT is the central framework in the project for governing generative AI use through evidence at the level of a single run. Instead of asking only whether a model or organisation appears responsible in general, RAIDT asks whether one specific configured use can be reconstructed, reviewed, and defended. It therefore treats the run as the unit of governance and produces two practical outputs: a run-level evidence pack and a five-pillar score profile covering Responsibility, Auditability, Interpretability, Dependability, and Traceability. This matters because organisational accountability is usually tested in concrete cases, not in abstract principles. RAIDT provides a structured way to move from broad governance claims towards inspectable evidence, clearer review, stronger contestability, and better readiness for audit and continuous improvement.
One-line takeaway
RAIDT is a run-level evidence framework because it turns a specific GenAI use into a reviewable governance object.
Related items in RAIDT core, definition, values, claims and innovation
Mentioned in reference-paper summaries (2)
Paper summaries live in Port/93-References/pdf_summaries/. Each file listed below contains the key term at least once.
_pilot_task.md_pilot_task_v2.md
Anchored questions
- Q001: What is RAIDT and how is the mind map organised around it?
- Q099: What is RAIDT in one sentence?
- Q100: Why must RAIDT be treated as the project object before its internal components?
- Q178: RAIDT — 100-slide workshop edition
- Q184: RAIDT in one paragraph
- Q190: A. Core & Scope — branch overview
- Q191: RAIDT — definition, example, and why it matters in RAIDT