When a layer and a metric share the same label, doctrine becomes fragile. This clarification removes the confusion between EAC (the layer) and EAC-gap (the metric).
Direct references: EAC: minimum doctrinal decisions · EAC doctrine · EAC definition
The problem
In an environment where several instruments coexist (ADI-Open, ADI-IIP, IIP, Q-Layer), an acronym can slide from one use to another: sometimes a governance mechanism, sometimes a number. That slippage is enough to destabilize an entire doctrine, because it encourages optimization of a number rather than application of a framework.
The canonical distinction
1) EAC (layer)
External Authority Control (EAC) is a governance layer. It declares which external authorities may be regarded as canonically admissible in interpretive reconstruction, and under what conditions they may constrain interpretation.
2) EAC-gap (metric)
EAC-gap is a measured differential. It is expressed as an observed gap between two regimes: an “open-world” regime and an “opposable / constrained” regime. It helps diagnose a deficit of admissibility or canonization, but it is not, in itself, a form of governance.
Public usage rule
EAC = layer · EAC-gap = differential.
Any metric use that omits “gap” is treated as ambiguous.
Why this is non-negotiable
- A metric governs nothing. It observes. Governance, by contrast, bounds and arbitrates.
- Optimizing a gap can hide an authority problem. Reducing a number without qualifying external authority produces apparent stability, not interpretive stability.
- Confusion destroys traceability. It becomes impossible to know whether a decision is normative (EAC) or descriptive (EAC-gap).
Direct consequence for the stack
The EAC layer intervenes before governed negation and before the Q-Layer output decision. The EAC-gap metric, by contrast, is read at the diagnostic level, to understand the gap between what exists and what is admissible.
Further reading
- EAC: minimum doctrinal decisions
- External Authority Control (EAC)
- External Authority Control (EAC)
- Interpretive governance
- Authority boundary · Authority conflict
How to use this AI interpretation article
Read EAC is not EAC-gap: distinguishing the layer from the measured differential as a focused diagnostic note inside the AI interpretation corpus, not as a free-standing policy or final definition. The article isolates the way a system transforms available material into an answer, refusal, synthesis or recommendation; its first task is to make that pattern visible without pretending that the pattern is already proven everywhere.
The practical value of EAC is not EAC-gap: distinguishing the layer from the measured differential is to prepare a second step. Use the page to decide whether the issue belongs in answer legitimacy, response conditions, authority boundaries, or non-response rules, then move toward the canonical definition, framework, observation or service page that can carry that next step with more precision.
Practical boundary for this AI interpretation article
The boundary of EAC is not EAC-gap: distinguishing the layer from the measured differential is the condition it names within the AI interpretation cluster. It can support a test, a comparison, a correction request or a reading path, but it should not be treated as proof that every model, query, crawler or brand environment behaves in the same way.
To make EAC is not EAC-gap: distinguishing the layer from the measured differential operational, verify the source chain, the wording of the answer, the missing authority boundary and the response conditions that would have made the output legitimate. If those elements cannot be reconstructed, the article remains a diagnostic lens rather than a claim about a stable state of the web, a model or a third-party answer surface.
Operational role in the AI interpretation corpus
Within the corpus, EAC is not EAC-gap: distinguishing the layer from the measured differential helps the AI interpretation cluster by making one pattern easier to recognize before it is formalized elsewhere. It can name the symptom, expose a missing boundary or show why a later audit is needed, but stricter authority still belongs to definitions, frameworks, evidence surfaces and service pages.
The page should therefore be read as a routing surface. EAC is not EAC-gap: distinguishing the layer from the measured differential does not need to define the whole doctrine, provide complete proof, qualify an intervention and resolve a governance issue at once; it should direct each of those tasks toward the surface authorized to perform it.
Boundary of this AI interpretation article argument
The argument in EAC is not EAC-gap: distinguishing the layer from the measured differential should stay attached to the evidentiary perimeter of the AI interpretation problem it describes. It may justify a more precise audit, a stronger internal link, a canonical clarification or a correction path; it does not justify a universal statement about all LLMs, all search systems or all future outputs.
A disciplined reading of EAC is not EAC-gap: distinguishing the layer from the measured differential asks four questions: what phenomenon is being identified, whether the authority boundary is explicit, whether a canonical source supports the claim, and whether the next step belongs to visibility, interpretation, evidence, response legitimacy, correction or execution control.
Internal mesh route
To strengthen the prescriptive mesh of the Interpretation & AI cluster, this article also points to Claim-scoped, time-scoped, scope-bound: the minimal grammar of EAC, EAC, A2, Q-Layer, Layer 3: who does what in governance. These adjacent readings keep the argument from standing alone and let the same problem be followed through another formulation, case, or stage of the corpus.
After that nearby reading, returning to answer legitimacy anchors the editorial series in a canonical surface rather than in a loose sequence of articles.