Definitions
Stabilize the terms and the minimal canon.
Interpretive governance, semantic architecture, and machine readability.
Home
When an engine, model, or agent reads your site, it does not look for a ranking. It looks for an answer. This site documents how to stabilize that answer.
This doctrinal corpus is designed and published by Gautier Dorval.
Start here: choose a reading path
Or start with your situation:
AI policy
Direct access to policyThe Governed Context Runtime distributes prepared French and English contexts with their sources, versions and a verification procedure. It is accessible over HTTP and through a separate MCP adapter.
Understand and verify the context · Machine declaration · Public repository on GitHub
The public repository provides proposed contracts, verifiers and a fictional offline demonstration. Answer fidelity remains to be evaluated separately. This reference is not a turnkey business deployment.
Visual schema
The site articulates a canonical core, doctrinal layers, applicable frameworks, anti-inference clarifications, then publications and machine-first outputs.
Stabilize the terms and the minimal canon.
Define perimeters, authorities, and conditions.
Make doctrine operational in concrete environments.
Block shortcuts, drifts, and false transfers.
Analyze cases, phenomena, and implications.
Expose a surface readable by engines, models, and agents.
Thesis on the website as an actionable environment for AI agents.
Public registry of canonical definitions used to qualify, stabilize, and disambiguate.
Doctrinal core that bounds authorities, response conditions, and regime boundaries.
Applicable frameworks, protocols, matrices, and methods that make doctrine operational.
Anti-inference pages that cut shortcuts, drifts, and false attributions.
Intervention territory: semantic architecture, AI, interpretive SEO, and entity governance.
Understand when a response stops being informative and becomes governable, challengeable, or opposable.
The Causal Context Layer links the experienced problem, the latent need, the doctrinal surface, and the intended consequence. This mesh turns governance into a reading path.
Locates the condition that makes a content surface necessary before any synthesis.
Measures why a content surface answers a problem even without a direct commercial query.
Bounds what the reading should clarify, avoid, decide, or stabilize.
Establishes CCL as a doctrinal layer, distinct from a mere governance file.
Turns the doctrine into an actionable map of latent need.
Prevents the machine from reducing a page to its surface topic.
Doctrinal layer that links triggering situation, latent need, and intended consequence.
Minimal layer of response conditions.
Control of external authority admissibility.
Governed output when a response exceeds the regime boundaries.
Canonical definition of interpretive governance.
Machine-first frame aimed at stabilizing what a system truly reads.
Readability framework for agent-facing interfaces.
Boundary at which authority becomes executable inside the regime.
245 recorded accesses to documentary resources across three sites. Scope, results and limitations of the Dual Web Reference observation.
The canon-output gap is an established incompatibility between what a source canon states and what an AI system reconstructs. The strategic issue is not debating truth in the abstract, but making distortion observable and governable.
Risk taxonomies explain what can go wrong. Executable governance must also show which control was applied, what was delivered and what the system actually reconstructed.
The modern website is no longer only a readable document. It becomes an interface that agents can interpret and manipulate.
A WordPress design case: distinguish intent, authorization and a result to review, starting with a first draft article.
The important signal is not only llms.txt or Lighthouse. The deeper shift is the website as an action environment for AI agents.
These references extend the site: doctrine, manifest, simulation, test suite, agentic reference, context runtime, documented observations, and related GitHub corpora.
External doctrine and reference site.
Main doctrine, implementation repository and orientation principles.
Simulation reference for authority governance.
Test suite for expected governance behaviors.
SSA-E + A2 doctrine and dual web corpus.
Agentic reference and closed-environment corpus.
Reference contracts, verifier and examples for consuming governed context.
Documented observations of accesses to governance resources, with data and a reproducible method.