Governance artifacts
Governance files brought into scope by this page
This page is anchored to published surfaces that declare identity, precedence, limits, and the corpus reading conditions. Their order below gives the recommended reading sequence.
EAC registry
/.well-known/eac-registry.json
Normative registry for admissibility of external authorities in the open web.
- Governs
- Admissible relations, receivable authorities, and conflict arbitration.
- Bounds
- Abusive merges, copied authority, and unqualified silent arbitration.
Does not guarantee: Describing a graph or registry does not make an exogenous source endogenous truth.
Admissible exogenous claims
/eac-claims.json
Surface that bounds receivable families of exogenous claims.
- Governs
- Admissible relations, receivable authorities, and conflict arbitration.
- Bounds
- Abusive merges, copied authority, and unqualified silent arbitration.
Does not guarantee: Describing a graph or registry does not make an exogenous source endogenous truth.
EAC conflicts
/eac-conflicts.json
Surface for exogenous conflict arbitration and its resolution conditions.
- Governs
- Admissible relations, receivable authorities, and conflict arbitration.
- Bounds
- Abusive merges, copied authority, and unqualified silent arbitration.
Does not guarantee: Describing a graph or registry does not make an exogenous source endogenous truth.
Complementary artifacts (3)
These surfaces extend the main block. They add context, discovery, routing, or observation depending on the topic.
Claims registry
/claims.json
Registry of published claims, their scope, and their declarative status.
Entity graph
/entity-graph.jsonld
Descriptive graph of entities, identifiers, and relational anchor points.
Published relationships
/relationships.jsonld
Relational surface that makes admissible links explicit across entities, roles, and surfaces.
External Authority Control (EAC)
EAC is the governance layer that declares which external authorities are canonically admissible in an open-web reconstruction, and under what conditions they may constrain interpretation.
It intervenes after the mapping of external sources and before governed negation or the final authorization of response.
1. Function
EAC does not exist to say what is absolutely true. Its role is narrower and more operational: to qualify which external authorities may actually count inside the active interpretive regime.
In practice, the layer must make it possible to determine:
- which sources have jurisdiction over which types of claims;
- within which perimeter an authority remains valid;
- how an active authority ranks against competing authorities;
- when external indeterminacy must harden output conditions.
Without this layer, reconstruction becomes too dependent on visibility, apparent recency, or cross-surface repetition.
2. What EAC is not
- It is not a protocol for absolute control over the web.
- It is not an automatic conversion of the exogenous into the endogenous.
- It is not a default score.
- It is not an alternative to the Q-Layer.
- It is not executable permission comparable to Layer 3.
That distinction matters. A source may be admissible without requiring amplification, and an amplification may still be illegitimate if the output is not authorized in context.
3. Qualification regime
EAC forces external authority to be qualified across four minimal dimensions.
Scope
An authority is never admissible “in general”. It is admissible for a claim, an object, a territory, a jurisdiction, or a homogeneous family of statements.
Time
An authority may be admissible at t0 and no longer admissible at t1. Archives, quotations, snapshots, and reproductions must therefore be re-read through their validity window.
Priority
Several external sources may be simultaneously active without carrying the same rank. EAC does not assume equality between surfaces. It qualifies an order of precedence.
Evidence
An authority does not constrain interpretation merely because it circulates. It constrains interpretation because it comes with a level of proof appropriate to the regime.
4. Relationship with the rest of the doctrine
The reference conceptual sequence is: external graph → EAC → governed negation / arbitration → Q-Layer.
- The external coherence graph makes active nodes and tensions visible.
- EAC qualifies which of those authorities may actually constrain reading.
- Governed negation bounds unresolved conflicts or non-editable surfaces.
- The Q-Layer then decides whether it is legitimate to answer, qualify, suspend, or abstain.
5. Why this layer is indispensable
In an interpreted web, the most frequent error is not always the absence of information. It is the misjurisdiction of authority.
A system may very well retrieve an active, coherent, and frequently repeated source while still being wrong about whether that source has the right to govern the statement. EAC exists to prevent that confusion between activity, visibility, and admissibility.
6. Doctrinal consequence
When external admissibility remains indeterminate and materially weighs on the output, doctrine does not encourage more conclusion. It encourages a tighter output. That may lead to prudent qualification, a request for clarification, or legitimate non-response.
Reading rule
This doctrinal note on External Authority Control (EAC) should be read as a positioning surface within the interpretive governance corpus. It does not replace the canonical definitions or the operational frameworks. It explains why a distinction matters, where the doctrine draws a boundary, and what kind of error becomes more likely when that boundary is ignored.
The reader should separate three levels. First, the conceptual level: what this page names or refuses to name. Second, the procedural level: what a system, organization or evaluator would need to check before relying on a response. Third, the evidence level: what would make the interpretation reconstructable, contestable and corrigible. A doctrinal page is strongest when it keeps those three levels visible rather than collapsing them into a persuasive formulation.
Use in the corpus
Use this page as a bridge between definitions, frameworks and observations. It can guide a reading path, justify why a framework exists, or explain why a response should be bounded, refused or audited. It should not be treated as a runtime instruction, a guarantee of model behavior or a substitute for evidence. If a response based on this doctrine cannot show which source was used, which inference was allowed and which uncertainty remained unresolved, the doctrine remains a reading principle rather than an operational control.