S1.01 - Original_PhD_route
S1.01 ? Original PhD route
flowchart LR
A[Responsible AI
managerial uncertainty
information disorder] --> B[RAIDT
run-level evidence framework]
H[Practical settings
healthcare, finance, public services
prompts, sources, review notes] --> C[[Original PhD route
from broad governance problem
to operational RAIDT design]]
I[IS governance
audit and accountability lineage
GenAI operational pressure] --> B
B --> C
C --> D[Run-level evidence pack]
C --> E[RAIDT score profile]
D --> F[Reviewer reconstruction
contestability]
E --> G[Governance readiness
organisational learning]? Star S1 - Origins, Background and History
Star context: Explains the intellectual route by which RAIDT emerged from Responsible AI, managerial uncertainty, information disorder, IS governance, audit traditions, and GenAI operational pressure, rather than from a single narrow concern such as auditability alone.
Academic picture
Definition / background
The original PhD route refers to the initial conceptual path from which RAIDT emerged. The project did not begin as a narrowly technical study of audit logs, nor as a purely abstract discussion of AI ethics. It began with a broader Responsible AI concern: how management and organisational actors can use AI-supported decision processes under conditions of uncertainty, incomplete information, misinformation, dynamic change, and accountability pressure. From the start, the problem was practical as well as conceptual. Organisations needed ways to justify decisions and review AI-assisted work when the informational environment was unstable and when outputs could not be treated as fully deterministic or self-explanatory.
This route matters because it explains why RAIDT eventually took its present form. Responsible AI supplied the normative concern. Managerial uncertainty supplied the decision context. Information disorder highlighted the difficulty of relying on contested or incomplete inputs. IS governance contributed the organisational and control perspective. Audit and accountability traditions contributed the expectation that actions should later be reconstructable and reviewable. GenAI operational pressure then made the issue urgent, because organisations were already using systems whose outputs were probabilistic, configurable, and often woven into everyday work.
Within RAIDT, the original PhD route therefore functions as a design rationale. It explains why the framework is centred on run-level evidence rather than broad policy claims alone, why the evidence pack is necessary, and why the five-pillar score profile combines Responsibility, Auditability, Interpretability, Dependability, and Traceability. These are not arbitrary elements added after the fact. They are the operational expression of the original research problem.
The concept also differs from a generic project history. In RAIDT, the original route is analytically important because it clarifies the framework's scope. RAIDT is about responsible governance of real GenAI use in organisational work. It belongs neither to pure model evaluation nor to generic ethics rhetoric alone. Its intellectual route explains why the framework sits between governance theory, operational assurance, and evidence-based review of concrete runs.
Why this concept matters
This concept matters because it prevents RAIDT from being misunderstood as a framework that emerged only from auditability or only from compliance thinking. If the original route is forgotten, the framework can appear narrower than it really is. In reality, RAIDT addresses a more difficult problem: how to govern situated uses of GenAI when people must act under uncertainty and still remain answerable for outcomes.
The concept also avoids confusion between a research origin story and a governance logic. The origin route is not merely autobiographical background. It explains why RAIDT moves from principles to operational evidence, why it focuses on the run, and why the framework treats governance as something that must work in practice rather than only in policy documents. Without this item, audiences may miss the intellectual coherence linking Responsible AI, organisational governance, and run-level review.
For organisations using GenAI, this matters because governance frameworks are often challenged on two fronts at once: they are criticised for being too abstract to operationalise and too technical to explain to decision-makers. The original PhD route shows why RAIDT is neither. It begins from an organisational problem of accountable decision support and arrives at a practical governance method grounded in evidence packs and score profiles.
Key idea: The original PhD route matters because it explains why RAIDT treats GenAI governance as accountable decision support under uncertainty, operationalised through run-level evidence rather than left at the level of principle alone.
What this item explains
- The intellectual and practical origins of RAIDT as a response to Responsible AI concerns in organisational decision-making.
- Why managerial uncertainty and information disorder were central to the project before the framework was formalised.
- How IS governance and audit traditions helped shift the project from broad ethical concern to structured organisational accountability.
- Why GenAI operational pressure made the move from conceptual governance to run-level evidence urgent.
- Why RAIDT uses the run as the unit of governance rather than relying only on model-level or policy-level assurance.
- How the evidence pack and five-pillar score profile emerged from the original governance problem rather than from an arbitrary design preference.
- Why RAIDT should be understood as an operational governance framework for organisational work, not only as an audit device or an ethics vocabulary.
Practical example / likely audience question
Audience question
Did RAIDT start as auditability only?
Answer
No. Auditability became one important pillar, but it was not the sole or original framing of the PhD route. The earlier concern was broader: how to support responsible organisational decisions when AI is used under uncertainty, when information may be incomplete or misleading, and when actors remain accountable for the consequences of using those outputs.
The misconception behind the question is that RAIDT began as a technical assurance mechanism and then expanded outward. The actual route was almost the reverse. The project began with a broad governance and decision-support problem, then narrowed toward the practical question of what kind of evidence would allow a specific use of GenAI to be reviewed, contested, and justified. Auditability was therefore a consequence of the original route, not its only source.
A practical example is a manager using GenAI to help draft a strategic risk briefing from mixed-quality internal and external information. The problem is not merely whether the interaction was logged. The deeper issue is whether the organisation can show what information was used, what the tool produced, how uncertainty was handled, who reviewed the result, and whether the outcome was governance-ready. RAIDT handles this better than a generic AI governance approach because it ties that practical problem to the run, to evidence capture, and to a structured scoring profile rather than stopping at high-level policy statements.
Practical example in RAIDT terms
Consider a public-service team using GenAI to draft an internal briefing on housing-support demand for the next quarter. The use case seems straightforward, but the underlying information is uncertain: some data are current, some are delayed, and some narrative inputs come from informal frontline reports that may be incomplete or inconsistent.
The run-level issue is not only whether the GenAI system produced fluent text. The issue is whether the briefing can be trusted as a governance input. Evidence is needed on the task definition, the prompt or template used, the source datasets and notes supplied, the model configuration, the generated draft, human edits, reviewer comments, and the final version used in decision-making. Responsibility is affected because roles and sign-off must be clear. Auditability is affected because the run must be reconstructable. Interpretability is affected because reviewers need to understand how the output related to the inputs and instructions. Dependability is affected because unstable inputs may produce misleading summaries. Traceability is affected because the briefing must be linked to time, source material, and downstream use.
This item improves governance readiness because it explains why such evidence is needed in the first place. The original PhD route frames the run not as an isolated technical event but as a situated organisational decision-support episode under uncertainty. That framing is what makes RAIDT especially useful for operational governance.
Detailed link to RAIDT
Original PhD route links to RAIDT in four ways.
First, it explains the RAIDT core idea that GenAI governance should begin from real organisational use under uncertainty, not only from abstract principle statements or model-level claims.
Second, it leads directly to the run as the unit of governance, because the original research problem was how to examine one concrete episode of AI-supported work in context.
Third, it explains why RAIDT needs both a run-level evidence pack and a five-pillar score profile: evidence is needed for reconstruction, while scoring is needed for structured judgement across key governance dimensions.
Fourth, it connects RAIDT to reviewability, contestability, audit readiness, and organisational learning by showing that each of these depends on understanding how a particular run was shaped, used, and assessed.
Original PhD route ? Run-level evidence ? Evidence pack ? RAIDT score profile ? Governance readiness
The item therefore acts as a bridge between the conceptual origins of the project and the practical mechanics of the framework. It shows that RAIDT's architecture is a response to a governance problem that began before the framework had a name.
Link to the five RAIDT pillars
Responsibility
The original route strongly influences Responsibility because the project began from the question of how organisational actors remain answerable when GenAI contributes to decisions or work products under uncertainty.
Example evidence / implication:
- Named roles for initiating, reviewing, approving, or relying on a run.
- Clear statement of the organisational purpose and decision context behind the use of GenAI.
Auditability
This item also has a strong link to Auditability because the route drew on audit and accountability traditions that require later reconstruction and scrutiny of important actions.
Example evidence / implication:
- Records that allow a reviewer to reconstruct what happened in one run.
- Documentation showing whether the use of GenAI met procedural expectations and review requirements.
Interpretability
The route supports Interpretability because uncertainty and probabilistic outputs create a need to explain how an output emerged in context, even when internal model mechanisms remain only partly interpretable.
Example evidence / implication:
- Captured prompt logic, source material, and reviewer notes explaining why an output was accepted or corrected.
- Explanation of how uncertainty, ambiguity, or information disorder affected the run.
Dependability
Dependability matters here because the original route was concerned with whether GenAI-assisted processes can be relied upon in dynamic organisational environments.
Example evidence / implication:
- Comparison between expected use conditions and what actually occurred in the run.
- Notes on observed failure modes, instability, or quality issues across similar runs.
Traceability
Traceability is central because the route moved toward governance designs in which the path from input conditions to output use must be visible enough for review and learning.
Example evidence / implication:
- Timestamped links between source material, model configuration, output, and downstream decision use.
- Clear connection between the run and the records needed for later challenge or investigation.
The original PhD route affects all five pillars, but it is especially formative for Responsibility, Auditability, and Traceability because these make the move from broad Responsible AI discourse to concrete organisational governance operational.
Why this item is more than a generic concept
In general AI governance, a project's origin may be treated as background narrative with limited analytical value. In RAIDT, the original PhD route has methodological significance. It explains why the framework is designed as it is and why its unit of analysis is the run rather than the model, vendor, or policy statement alone.
The RAIDT meaning is therefore more operational than a generic concept of research background. It shows how a broad concern with responsible AI under uncertainty becomes a structured framework built around run-level evidence, evidence packs, score profiles, and governance readiness. In RAIDT, origin is not incidental history. It is part of the explanatory architecture of the framework.
Common misunderstanding
Misunderstanding
The original PhD route is just a personal or historical note about how the researcher happened to arrive at RAIDT.
Correction
It is more than a personal backstory. The route identifies the actual problem logic that shaped the framework: responsible decision support under uncertainty, translated into operational governance for GenAI use. For example, if this item were treated as merely autobiographical, a reviewer might assume RAIDT could have been designed around any arbitrary set of governance criteria. In fact, the five pillars, the focus on the run, and the need for evidence packs all make more sense once the original problem framing is understood. The item therefore helps explain why RAIDT has this structure and not another.
Boundary and limitation
The original PhD route does not by itself prove that RAIDT is empirically effective, normatively complete, or universally applicable across all sectors. It explains where the framework came from and why its architecture is coherent, but it is not a substitute for empirical validation, policy analysis, or sector-specific testing.
The concept also has a boundary in that origin logic can illuminate a framework without determining every later design choice. As RAIDT develops, additional refinements may arise from empirical findings, implementation constraints, sector use cases, or policy demands. RAIDT handles this limitation by treating the original route as a foundational rationale rather than as the only source of authority. The route explains the framework's direction; validation and application must still be demonstrated through evidence and use.
Implementation levels
Manual implementation
A researcher or small team can apply this item manually by using it as a structured design-rationale note in supervision meetings, drafts, viva preparation, and paper introductions. The key manual task is to explain consistently how the project moved from Responsible AI and uncertainty concerns to run-level governance.
Semi-automated implementation
Semi-automated implementation can use templates, concept maps, linked notes, and structured metadata in Obsidian or a research workflow to connect this item to related concepts such as managerial uncertainty, information disorder, evidence packs, and the five RAIDT pillars. This helps preserve conceptual consistency across papers, slides, and knowledge-base entries.
Fully automated implementation
At scale, a research platform, governance dashboard, or knowledge-management layer could encode the design rationale behind RAIDT by linking origin concepts to framework components, scoring logic, and evidence requirements. In organisational implementations, this would help users understand not only what fields must be captured for a run, but why those fields matter from a governance perspective.
Practical use in the RAIDT project
This item is especially useful for Paper 08 Foundations because it explains the conceptual route by which RAIDT emerged and clarifies why the framework is grounded in accountable use under uncertainty. It helps a reader see that RAIDT is neither merely an ethics statement nor merely an audit instrument, but a framework designed to govern real organisational uses of GenAI.
For Paper 09 Empirical Validation, the item matters because it clarifies what the framework is trying to solve before validation is attempted. Empirical work can then test whether the run-level evidence approach actually improves reviewability, scoring consistency, and governance readiness in practice. For Paper 10 Policy Pathways, the item helps translate RAIDT into policy language by showing how broad governance concerns can be operationalised into structured evidence requirements.
The note is also useful for sector playbooks, evidence-pack design, scoring-rubric explanation, governance interventions, supervisor discussion, viva defence, and journal positioning. When asked why RAIDT takes this particular form, this item gives the most concise and coherent answer.
Key audience questions to prepare for
Q1. Why does the original route matter once the framework has already been defined?
It matters because framework design is easier to defend when its problem logic is explicit. This item shows why RAIDT focuses on real use under uncertainty and why run-level evidence is central rather than optional.
Q2. Is this item mainly theoretical or mainly practical?
It is both. It is theoretical because it explains the conceptual origin of RAIDT, and practical because that origin directly shapes evidence capture, scoring logic, and governance application.
Q3. Could RAIDT have emerged from auditability alone?
Not convincingly. Auditability is important, but RAIDT also responds to uncertainty, information quality problems, managerial accountability, and the realities of GenAI in organisational work. The broader route explains why the framework is more than a logging or compliance tool.
Q4. How does this item help in a viva or supervision setting?
It gives a disciplined explanation of the project's intellectual coherence. Instead of listing influences loosely, it shows how those influences combine into a single governance architecture centred on the run.
Q5. What is the practical consequence of forgetting this route?
The framework may be misread as narrower, more technical, or more generic than it actually is. That weakens explanation, paper framing, and the defence of RAIDT as a distinct contribution to GenAI governance.
Suggested citation concepts to support this item
- Responsible AI in organisational decision-making under uncertainty
- Managerial uncertainty and AI-supported judgement
- Information disorder and decision quality in digital organisations
- Information systems governance for AI-enabled work
- Auditability and accountability in sociotechnical systems
- Generative AI governance in organisational contexts
- Evidence-based AI assurance and reviewability
- Operationalising AI governance beyond principles
- Human oversight and contestability in AI-assisted workflows
- From AI ethics principles to implementable governance mechanisms
Short explanation for presentation
The original PhD route explains where RAIDT came from and why it has its present structure. The project did not begin as a narrow auditability exercise. It began with a broader Responsible AI problem: how organisations can use AI for decision support under uncertainty while remaining accountable for outcomes. That route brought together managerial uncertainty, information disorder, IS governance, audit traditions, and the operational pressure created by GenAI. RAIDT emerged when that broad problem was translated into a practical governance question at the level of one run: what evidence is needed to reconstruct, review, and score a concrete use of GenAI in context? This is why RAIDT is built around run-level evidence, evidence packs, and five-pillar scoring. The route matters because it shows that RAIDT is an operational governance framework grounded in accountable organisational use, not merely an abstract ethics model or a logging tool.
One-line takeaway
Original PhD route is the conceptual pathway from Responsible AI under uncertainty to RAIDT because it explains why the framework operationalises governance through run-level evidence.