Skip to content

Page

Applicable frameworks

Applicable frameworks helps readers navigate Gautier Dorval’s corpus, services, evidence layers and interpretive governance resources.

CollectionPage
TypeHub

Visual schema

Implementation chain

A framework converts doctrine into protocol, then method, then usable instrumentation.

01

Doctrine

What must hold inside the frame.

02

Framework

The intermediate operational frame.

03

Protocol

Sequence or discipline of application.

04

Measurement

Observability, score, audit, proof.

05

Usage

Concrete deployment in an environment.

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. 01Canonical AI entrypoint
  2. 02Public AI manifest
  3. 03Q-Metrics JSON
Entrypoint#01

Canonical AI entrypoint

/.well-known/ai-governance.json

Neutral entrypoint that declares the governance map, precedence chain, and the surfaces to read first.

Governs
Access order across surfaces and initial precedence.
Bounds
Free readings that bypass the canon or the published order.

Does not guarantee: This surface publishes a reading order; it does not force execution or obedience.

Entrypoint#02

Public AI manifest

/ai-manifest.json

Structured inventory of the surfaces, registries, and modules that extend the canonical entrypoint.

Governs
Access order across surfaces and initial precedence.
Bounds
Free readings that bypass the canon or the published order.

Does not guarantee: This surface publishes a reading order; it does not force execution or obedience.

Observability#03

Q-Metrics JSON

/.well-known/q-metrics.json

Descriptive metrics surface for observing gaps, snapshots, and comparisons.

Governs
The description of gaps, drifts, snapshots, and comparisons.
Bounds
Confusion between observed signal, fidelity proof, and actual steering.

Does not guarantee: An observation surface documents an effect; it does not, on its own, guarantee representation.

Complementary artifacts (3)

These surfaces extend the main block. They add context, discovery, routing, or observation depending on the topic.

Observability#04

Q-Ledger JSON

/.well-known/q-ledger.json

Machine-first journal of observations, baselines, and versioned gaps.

Canon and identity#05

Definitions canon

/canon.md

Canonical surface that fixes identity, roles, negations, and divergence rules.

Policy and legitimacy#06

Q-Layer in Markdown

/response-legitimacy.md

Canonical surface for response legitimacy, clarification, and legitimate non-response.

Choose the failure mode first

The frameworks are easier to use when the failure mode is already identified. Start here separates visibility, authority, evidence, retrieval, memory and execution paths before sending the reader to the framework layer.

Frameworks and applicable frameworks

Public registry of frameworks derived from the interpretive governance doctrine developed by Gautier Dorval.

This page serves as an internal linking hub to connect operational frameworks (/frameworks/) to canonical concepts (/definitions/) and doctrine (/doctrine/). Each framework is an application surface: it makes mechanisms usable, auditable, and enforceable.

For the lexical registry, see Definitions and canonical concepts. For the doctrinal table, see Doctrine. For field analyses, see Interpretive phenomena.


Frameworks should be selected by failure mode, not by title alone. A framework is useful when the reader already has a problem to diagnose, a corpus to structure, a response condition to enforce or a correction chain to maintain.

Start here

Supporting routes

Reading rule

Frameworks organize an intervention. They do not replace the canonical definitions or the evidence chain that makes the intervention defensible.


Projection rule

The frameworks in this registry are application surfaces. When a concept is defined in /definitions/ and formalized in /doctrine/, doctrine constitutes the canonical source and the framework acts as a structured projection designed to be usable in real context.

In case of perceived discrepancy between a framework and a doctrinal page, the doctrinal page prevails.


Framework chains (by usage)

Diagnose and prove

Correct and maintain

Govern agentic systems and retrieval

Pillars (architecture)

Foundations (canon, authority, response)

Evidence, audit, observability

Correction, sustainability, version

Identity, collisions, identifiers, graphs

RAG, agentic, closed environments

Multisite and public repositories

Exogenous, multi-AI, maturity


Associated articles (phenomena)

Frameworks are fed by analyses published in Interpretive phenomena. Reference series:


Authority and scope

Author:
Gautier Dorval

Scope:
Interpretive governance, agentic (open web and closed environments), semantic stabilization, response conditions, auditability, enforceability, variance reduction, entity disambiguation, interpretive debt, interpretive sustainability.

Primary language:
French (Canada). English versions may exist as equivalents, without modifying canonical meaning.

For contextual framing, see Positioning.

Canonical repo: https://github.com/GautierDorval/interpretive-seo

What a framework is on this site

A framework is not a slogan, a template, or a substitute for evidence. It is an operating model that connects a problem, a scope, a set of inputs, a decision structure, and a set of limits. The framework pages are designed to help readers move from vocabulary to method without confusing method with proof.

For example, a framework about RAG governance can define how retrieval, provenance, source admission, and inference control should be organized. It does not prove that a particular generated answer is legitimate. That still requires proof of fidelity, interpretive evidence, and a clear source hierarchy. A framework about AI agents can describe execution boundaries, but it does not create authority for an agent to act.

This distinction is essential to the site’s architecture. Definitions stabilize meaning. Frameworks organize action. Observations document traces. Service pages describe possible engagements. A framework becomes dangerous when it is treated as a certificate of correctness rather than as a disciplined way of asking better questions.

How to choose the right framework

Start with the failure mode. If the issue is that an AI system invents, smooths, or overextends an answer, begin with response legitimacy, inference control, and non-response frameworks. If the issue is that the right source is retrieved but the answer is still wrong, start with retrieval governance, documentary chain, and proof discipline. If the issue is that a brand or entity is confused with a neighboring entity, start with semantic architecture, entity disambiguation, and collision reduction. If the issue is that an agent can execute an action without enough authority, start with agentic governance and execution control.

The same problem can cross several layers. A brand representation failure may involve entity collision, weak canonical surfaces, uncontrolled third-party sources, stale memory, and poor proof discipline. A useful framework does not collapse those layers into a single cause. It shows which layer must be diagnosed first and which layer must not be inferred from another.

Framework families

The interpretive governance family deals with authority, legitimacy, response conditions, source hierarchy, non-response, and governed negation. These frameworks are useful when the question is not only what the system said, but whether it had the authority to say it.

The evidence and audit family deals with proof of fidelity, interpretation traces, auditability, observation, and the canon-output gap. These frameworks are useful when a team needs to move from impressions to documented differences between the canon and the generated output.

The semantic architecture family deals with entities, collisions, graphs, disambiguation, semantic neighborhoods, and cross-system coherence. These frameworks are useful when the organization is visible but still badly framed, blended with adjacent entities, or interpreted through a contaminated neighborhood.

The retrieval and RAG family deals with source admission, corpus admissibility, chunk authority, retrieval provenance, and documentary chain. These frameworks are useful when a system retrieves content but the governing status of that content remains ambiguous.

The agentic and execution family deals with delegated action, tool-mediated authority, multi-agent chains, execution boundaries, transactional coherence, and agentic response conditions. These frameworks are useful when the output is no longer only an answer, but a possible action.

Limits of framework use

A framework cannot replace a source, an audit, or a live observation. It should not be treated as a guarantee that a system will cite the right page, rank the right result, recommend the right service, or follow the intended instruction. It should be used as a disciplined structure for deciding what must be checked, what must be refused, what must be separated, and what must be documented.

That is also why the frameworks are connected to the SERP ownership map. A framework may discuss several concepts, but it should not steal the primary role of the canonical definition or the service page. When a framework uses a term such as answer legitimacy, semantic architecture, AI visibility audit, or RAG governance, it should support the primary page rather than compete with it.

Practical use

Use frameworks to prepare an audit, structure a diagnosis, brief a stakeholder, or define what evidence must be collected. Do not use them as stand-alone promises. A serious application should always reconnect the framework to definitions, observations, proof artifacts, source hierarchy, and response conditions.

Internal routes to reinforce

These links keep frameworks surfaces visible when they support disambiguation, evidence, service routing, or canonical reading, without making them depend only on template-generated listings.

AI citation readiness checklist route

Use the AI citation readiness checklist when the question is operational: whether a page or corpus is ready to be retrieved, cited and governed before citation tracking begins.

The checklist should be read with AI-ready structure, preview control, machine-first routing and citation fidelity.

In this section

AI perception stability matrix

Matrix for qualifying AI perception stability across identity, category, perimeter, evidence, temporality, recommendability, and cross-system convergence.

Framework
AI citation audit scoring matrix

A scoring matrix for separating AI citation access, retrieval, extraction, role, fidelity and stability.

Framework
AI citation quality matrix

Matrix for qualifying whether an AI citation is governing, supporting, illustrative, ornamental, outdated, contradictory or insufficient.

Framework
AI citation readiness checklist

Operational checklist for reviewing whether a page, source or corpus is ready to be retrieved, cited and governed in AI-mediated answers.

Framework
Fan-out query map

A practical framework for mapping the adjacent questions that influence retrieval and AI source selection.

Framework
Phantom URL audit

Phantom URL audit provides a method to qualify non-existent but plausible URLs, cluster them, and decide whether to create, redirect, clarify, or keep a 404.

Framework
Agentic web readability framework

Framework for auditing a site’s ability to be understood, traversed, and acted upon by AI agents through visual, HTML, and accessibility signals.

Framework
CTIC: cross-layer transactional coherence

CTIC defines the minimum coherence required across interpretive, governance, and execution layers when a state change or transactional effect is involved.

Framework
Enforceable response conditions for AI agents

Enforceable response conditions for AI agents presents an operational framework for governing interpretation, authority, evidence and AI response conditions.

Framework
Statement-level authority retention framework

A diagnostic framework for testing whether an extracted statement retains issuer, source, time, scope, status, and interpretive limits inside an AI response.

Framework
Machine-first visibility operating model

Machine-first visibility operating model presents an operational framework for governing interpretation, authority, evidence and AI response conditions.

Framework
Interpretive debt: analytical framework

Analytical framework for identifying, classifying, and monitoring interpretive debt as the accumulation of unresolved distortions in an interpreted web.

Framework
RAG governance vs interpretive governance

Framework explaining why RAG governance is not equivalent to interpretive governance and why the latter remains broader than retrieval architecture.

Framework

Strategic external references

These references extend the doctrine, the test suite, the manifest, and the related public corpora.