Relational determinacy: closing the interpretation of structured technical content for reliable language-model retrieval.

24 July 2026, Version 1
This content is an early or alternative research output and has not been peer-reviewed by Cambridge University Press at the time of posting.

Abstract

Retrieval-augmented generation underperforms on technical documentation because the dominant practice of segmenting content into independent passages destroys the relational structure on which technical meaning depends. We argue that meaning in technical content is constituted relationally: a content unit's interpretation space contracts as classificatory constraints accumulate, and the unit becomes determinate only when that space is closed. We formalize this as a five-axis classification resolved as a typed, dependent tuple, define a determinacy index over the resolved tuple, and separate two determinacies: a structural determinacy that is computable from the markup, and an epistemic determinacy that asks whether a structurally closed unit actually carries knowledge. We state a determinacy law relating intent multiplicity to structural fragmentation, give a resolution algorithm over Darwin Information Typing Architecture (DITA) markup, and describe a hybrid inference layer that distills a large model into a small per-client model. We report reference-implementation behavior and define an evaluation protocol for large-corpus validation. The framework makes the same classification serve simultaneously as an enrichment substrate, a retrieval signal, and supervision for model training.

Keywords

Artificial Intelligence
RAG
Retrieval Augmented Generation
Large Language Model
LLM
Structured Content
DITA-XML
AI
Ontology
Information Architecture
Content Strategy

Supplementary weblinks

Comments

Comments are not moderated before they are posted, but they can be removed by the site moderators if they are found to be in contravention of our Commenting and Discussion Policy [opens in a new tab] - please read this policy before you post. Comments should be used for scholarly discussion of the content in question. You can find more information about how to use the commenting feature here [opens in a new tab] .
This site is protected by reCAPTCHA and the Google Privacy Policy [opens in a new tab] and Terms of Service [opens in a new tab] apply.