Skip to content

Doctrine

Authority Governance (Layer 3): doctrine and regime boundary

Layer 3 doctrine: adjacent regime that bounds executable authority when interpretive outputs become action-bearing inputs.

CollectionDoctrine
TypeDoctrine
Layertransversal
Version1.0
Levelnormatif
Stabilization2026-03-03
Published2026-03-03
Updated2026-03-11

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.

  1. 01EAC registry
  2. 02Admissible exogenous claims
  3. 03EAC conflicts
Graph and authorities#01

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.

Graph and authorities#02

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.

Graph and authorities#03

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.

Graph and authorities#04

Claims registry

/claims.json

Registry of published claims, their scope, and their declarative status.

Graph and authorities#05

Entity graph

/entity-graph.jsonld

Descriptive graph of entities, identifiers, and relational anchor points.

Graph and authorities#06

Published relationships

/relationships.jsonld

Relational surface that makes admissible links explicit across entities, roles, and surfaces.

Objective: publicly stabilize the boundary between interpretation governance and execution governance, without disclosing operational protocol.

This page does not describe an execution architecture or a detailed permission system. It establishes what is now considered canonical when interpretive outputs become action-bearing inputs.


1. What Layer 3 governs

Authority Governance (Layer 3) governs executable authority. It does not bound the meaning of a web page, nor the mere admissibility of a source, nor the narrative legitimacy of a response. It bounds permission to act in closed or semi-closed environments: agents, workflows, orchestrations, decision systems, transactional environments.

Layer 3 intervenes when the organization no longer delegates merely a reconstruction capability, but a share of authority liable to produce a real effect.


2. The 3 entry conditions

  1. Exposure: the output of a system is connected to an environment capable of acting.
  2. Impact: that action or decision has a real effect on a state, a right, an amount, a compliance requirement, or a reputation.
  3. Delegation: a share of authority is effectively transferred to the system.

If any single one of these conditions is absent, one remains under interpretive governance. If all three are met, Layer 3 becomes relevant.


3. The 8 minimum boundary decisions

  1. Layer 3 begins only where authority becomes executable.
  2. Layer 3 does not govern truth.
  3. EAC admissibility never implies executable rights.
  4. Q-Layer legitimacy never implies executable permission.
  5. Any state-changing, rights-affecting, or financially binding action requires Layer 3.
  6. Layer 3 is role-bound, context-bound, and capability-bound.
  7. Human escalation is part of Layer 3, not evidence of failure.
  8. No public-web signal alone can grant executable authority.

4. What this doctrine is not

  • It is not an SEO layer.
  • It is not a default extension of the open web.
  • It is not a published security protocol.
  • It is not a promise of model obedience.
  • It is not an implicit authorization derived from an admissible source.

5. Articulation with the open stack

The interpreted web sequence remains: SSA-E → EAC → A2 → Q-Layer.

Layer 3 is not the “next link” in that chain. It is an adjacent regime that becomes necessary when a response ceases to be a response and becomes a delegated action or decision.

Canonical formula: Layer 3 is not the next layer of open-web interpretive governance. It is the adjacent regime that becomes necessary when interpretive outputs acquire delegated execution power.


6. Public / private

  • Public: definition, regime boundary, entry conditions, minimum decisions, non-implications.
  • Private: permission logic, role matrices, gates, escalations, rollback, execution traces, internal authorization rules.

This page is deliberately doctrinal. It declares the regime boundary without publishing the mechanism.


See also