Freeze a baseline
Architectural responsibilities and test expectations are versioned before consequential evaluation.
RESEARCH
The central question is whether consequential automated systems can preserve executable distinctions between formal derivation, authority, warrant, reliance and action permission.
PRIMARY QUESTION
The research treats the architecture as a falsifiable hypothesis. A useful negative result is preferable to a persuasive but unsupported claim.
FormalDerivation != AuthorityToApplyRule
WARRANTED(P) != MAY_RELY_ON(P,U)
MAY_RELY_ON(P,U) != ACTION_TECHNICALLY_PERMITTED
Projection != Authority
LLM memory != authoritative system semantics
METHOD
Architectural responsibilities and test expectations are versioned before consequential evaluation.
Authority, provenance and modelling conveniences are represented separately rather than silently conflated.
Negative, ambiguous and structurally novel cases are retained rather than removed from the evidence set.
The intended end state is a decision that can be rebuilt from governed artefacts without conversational memory.
STATUS DISCIPLINE
FUNCTIONAL RESPONSIBILITIES
The public research description deliberately focuses on what must be done rather than prescribing one implementation technology.
BOUNDARIES
Universal domain independence
Elimination of AI hallucination or agent drift
Official DfT D-TRO conformance or certification
Legal advice or legal correctness
TM Forum affiliation or endorsement
Production safety for unrestricted consequential action
That generated output is automatically warranted
That a projection is independently authoritative
WORKING DEMONSTRATOR
Studio v1.1 exposes model structure, validation outcomes, generated artefacts, provenance and unresolved semantics in the browser.
Open Studio v1.1