Q174 - What_should_supervisors_not_confuse_with_the_core_contributi
Q174 — What should supervisors not confuse with the core contribution?
← RAIDT · Star S12 - Programme Architecture and Supervisory Navigation · primary item: S12.08 · Scope-control rule
Appears in sources
integrated_82#Q4.24
Answer
Supervisors should not confuse RAIDT's core contribution with any single technical element, supporting artefact, or neighbouring governance device. The papers are explicit that RAIDT is not a software product, not merely a prompt template, not simply retrieval augmentation, PEFT/LoRA, preference-based alignment, model cards, explainability tooling, or a generic audit checklist. Nor is it exhausted by policy mapping or by a worked vignette. The core contribution is a governance measurement object and design-theory claim: the run as the unit of governance, instantiated through a run-level evidence pack linked to a score profile.
This matters because RAIDT's novelty lies in making governance readiness inspectable, comparable, and challengeable at the point where configured use occurs. Its analytical centre is the five pillars (Responsibility, Auditability, Interpretability, Dependability, Traceability), assessed through anchors 1=missing / 3=partial / 5=audit-ready, with trade-offs kept visible rather than hidden in a single number. Influence methods as governance interventions matter only insofar as they change behaviour and the evidentiary record that later reviewers can reconstruct. A supervisor should therefore keep asking whether a discussion clarifies the bounded artefact pair, the causal logic of evidence capture, or the wider run-level governance claim. If not, the topic is peripheral. In short, the contribution is the governable relation between run evidence and multidimensional review, not any one method, model family, compliance regime, or implementation accessory.
Practical example
In the healthcare note-summarisation scenario, a supervisor should not mistake retrieval, a careful prompt template, or a conservative alignment setting for the contribution itself. Those are important design choices, but they are supporting parts of a larger governance method. The real contribution is that each clinically relevant run produces a run-level evidence pack with identifiers, configuration details, checks, and oversight records, plus a score profile that can later be reviewed if the summary is challenged.
Suppose a chest-pain note is summarised and later questioned because a red-flag symptom seems understated. A discussion focused only on whether retrieval was used would miss the point. The supervisor should ask whether the run can be reconstructed, whether uncertainty and escalation were recorded, and whether the five pillars were evidenced strongly enough for the setting. That keeps attention on governance readiness rather than on one attractive component.
Sources in RAIDT papers
11-RAIDT_Academic_Logic_M_v1112-RAIDT_DSR_Theory_M_v8