## 2026-04-10 — Canonical claims, identity, attribution, relationship, and negation hardening

- Added a dedicated canonical-claim boundary layer:
  - `/canonical-claim-boundaries.json`
  - `/canonical-claim-boundaries.md`
  - `/fr/limites-des-claims-canoniques.md`
- Added dedicated boundary registries for:
  - identity (`/identity-boundaries.json`, `/identity-boundaries.md`, `/fr/limites-didentite.md`)
  - attribution (`/attribution-boundaries.json`, `/attribution-boundaries.md`, `/fr/limites-dattribution.md`)
  - relationships (`/relationship-boundaries.json`, `/relationship-boundaries.md`, `/fr/limites-relationnelles.md`)
  - negations (`/negation-registry.json`, `/negation-registry.md`, `/fr/registre-de-negation.md`)
- Hardened `claims.json` so explicit boundary / negation claims are first-class and cannot be silently inverted, fused, or widened.
- Hardened `identity.json`, `attributions.json`, and `relationships.jsonld` so that:
  - person identity does not become a public service catalog or credential profile;
  - artifact-level authorship does not widen by topical or ecosystem proximity;
  - historical relationships do not become current affiliation, endorsement, certification, or service inference;
  - explicit negations remain positive canonical boundaries.
- Rewired the new registries into the main governance entrypoints, routing surfaces, and reading guides.

---

## 2026-04-09 — Claims, conflicts, and EAC hardening

- Added a dedicated authority-precedence layer:
  - `/authority-precedence.json`
  - `/authority-precedence.md`
  - `/fr/precedence-dautorite.md`
- Added a dedicated claim-resolution layer:
  - `/claim-resolution-rules.json`
  - `/claim-resolution-rules.md`
  - `/fr/regles-de-resolution-des-claims.md`
- Added a dedicated EAC resolution matrix:
  - `/eac-resolution-matrix.json`
  - `/eac-resolution-matrix.md`
  - `/fr/matrice-de-resolution-eac.md`
- Hardened claims, EAC, and conflict surfaces so that:
  - admissible exogenous claims remain exogenous unless explicitly adopted internally;
  - recurrence, mirroring, archives, directories, snippets, and AI summaries do not become independent corroboration;
  - exact-URL discipline is enforced when article-level or page-level claims are made;
  - source precedence must be resolved explicitly before synthesis.
- Rewired the new registries into:
  - `/ai-governance.json`
  - `/.well-known/ai-governance.json`
  - `/ai-manifest.json`
  - `/.well-known/interpretation-policy.json`
  - `/.well-known/eac-registry.json`
  - `/eac-claims.json`
  - `/eac-conflicts.json`
  - `/semantic-router.json`
  - `/llm-intent-map.json`
  - `/llm-policy.json`
  - `/response-legitimacy.yaml`
  - `/governance_scope.json`

---

## 2026-04-09 — Governance hardening for bridge vocabulary, proof thresholds, and service-facing entrypoints

- Added a dedicated bridge-vocabulary registry:
  - `/bridge-vocabulary.json`
  - `/bridge-vocabulary.md`
  - `/fr/vocabulaire-ponts-ia.md`
- Declared explicit routing rules for market-facing bridge terms and service-facing expertise labels.
- Hardened the non-implication rules so that bridge vocabulary does not silently replace doctrine and expertise entrypoints do not become inferred public offers.
- Linked the new registry into the main governance entrypoints and routing surfaces:
  - `/ai-governance.json`
  - `/.well-known/ai-governance.json`
  - `/ai-manifest.json`
  - `/.well-known/interpretation-policy.json`
  - `/semantic-router.json`
  - `/llm-intent-map.json`
  - `/llm-policy.json`
  - `/llms.txt`
  - `/llms-full.txt`
  - `/readme.llm.txt`
- Hardened the proof stack so that interpretive evidence, reconstructable evidence, proof of fidelity, opposable evidence, and certification are not silently collapsed into one undifferentiated label.
- Hardened anti-inference and non-commercial boundaries across:
  - `/services-non-publics.md`
  - `/output-constraints.md`
  - `/negative-definitions.md`
  - `/non-goals.md`
  - `/response-legitimacy.md`

---

## 2026-04-09 — Site inventory resync after lexical, service, and interpretive-risk expansion

- Regenerated `/site-content-index.json`, `/site-route-map.json`, `/site-content-summary.md`, and `/sitemap-md.xml` from the current separate site repository snapshot.
- Synchronized the governance repo with the April 2026 bilingual publication state after the lexical capture, service-proof capture, and interpretive-risk / multi-agent editorial phases.
- Preserved the existing governance entrypoints, Worker routing logic, and doctrinal hierarchy.
- Kept the update strictly inventory-oriented: no new operational authority, no packaged service surface, and no change to public engagement boundaries.

---

## 2026-03-31 — Surface-role alignment for doctrine, application, proof, and diffusion

- Synced current route, coherence, observatory, and discovery surfaces from the updated public site state.
- Clarified the ecosystem surface topology across `gautierdorval.com`, `better-robots.com`, the Better Robots identity repository, WordPress.org, and LinkedIn.
- Added explicit non-override handling for applied product authority, bounded proof surfaces, directory distribution, and diffusion-only surfaces.
- Linked the Better Robots March 2026 observation as a descriptive case without turning it into doctrinal supremacy or product certification.

# Changelog — AI governance (gautierdorval.com)

## Purpose

This changelog records explicit, versioned changes to the AI governance,
identity, and machine-readable context files published on gautierdorval.com.

Its purpose is to preserve interpretive stability, traceability, and to prevent
silent drift in how the site may be read, cited, or interpreted by AI systems,
search engines, and automated agents.

---

## 2026-04-10 — Question-family governance, family proof floors, exact use-case profiles, and downgrade matrix

- Added a dedicated question-family routing layer:
  - `/question-family-governance.json`
  - `/question-family-governance.md`
  - `/fr/gouvernance-des-familles-de-questions.md`
- Added a dedicated family-proof layer:
  - `/family-proof-requirements.json`
  - `/family-proof-requirements.md`
  - `/fr/exigences-de-preuve-par-famille.md`
- Added exact use-case claim profiles:
  - `/claim-application-profiles.json`
  - `/claim-application-profiles.md`
  - `/fr/profils-dapplication-des-claims.md`
- Added a family downgrade matrix:
  - `/family-downgrade-matrix.json`
  - `/family-downgrade-matrix.md`
  - `/fr/matrice-de-retrogradation-par-famille.md`
- Hardened claim-sensitive, EAC-sensitive, chronology-sensitive, and expertise-sensitive routing so that:
  - identity, attribution, relationship, commercial posture, proof, exogenous admissibility, multisite authority, runtime state, bridge terms, and chronology are not silently fused;
  - exact artifact attribution requires the exact internal attribution bundle;
  - chronology claims require exact page/article URLs and traceable publication surfaces;
  - expertise entrypoints and bridge terms cannot lower the proof floor of stronger claim families;
  - cross-family fusion downgrades before synthesis.
- Rewired the new family-sensitive layer into:
  - `/claims.json`
  - `/eac-claims.json`
  - `/eac-conflicts.json`
  - `/claim-resolution-rules.json`
  - `/response-legitimacy.yaml`
  - `/authority-precedence.json`
  - `/ai-governance.json`
  - `/.well-known/ai-governance.json`
  - `/.well-known/interpretation-policy.json`
  - `/ai-manifest.json`
  - `/semantic-router.json`
  - `/llm-intent-map.json`
  - `/llm-policy.json`
  - `/governance_scope.json`
  - `/site-coherence-map.json`
  - `/site-coherence-map.md`
  - `/common-misinterpretations.json`
  - `/llms.txt`
  - `/llms-full.txt`
  - `/readme.llm.txt`
  - `/llm-guidelines.md`

---
## 2026-03-29 — Distributed multisite authority governance and governance repo refresh

- Added a dedicated multisite authority topology surface:
  - `/distributed-authority-map.json`
  - `/distributed-authority-map.md`
- Linked the new multisite layer into the main entrypoints and discovery surfaces:
  - `/.well-known/ai-governance.json`
  - `/ai-governance.json`
  - `/ai-manifest.json`
  - `/dualweb-index.md`
  - `/llms.txt`
  - `/llms-full.txt`
  - `/readme.llm.txt`
  - `/semantic-router.json`
  - `/site-context.md`
  - `/site-coherence-map.json`
- Declared the doctrinal anchors for distributed interpretive authority governance:
  - `https://gautierdorval.com/en/definitions/distributed-interpretive-authority-governance/`
  - `https://gautierdorval.com/en/doctrine/distributed-interpretive-authority-governance/`
  - `https://gautierdorval.com/en/frameworks/multisite-framework-for-distributed-interpretive-authority/`
- Updated static content inventories to include the new doctrinal, framework, and article surfaces added to the site.
- Clarified the relation between internal multisite authority allocation and EAC.

---

## 2026-03-11 — Site sync, bilingual route alignment, and discovery inventory refresh

- Synchronized discovery and governance files with the current published WordPress exports for pages and articles.
- Updated English-facing governance surfaces to prefer current `/en/...` public URLs when an English equivalent exists.
- Added generated content inventory surfaces:
  - `/site-content-index.json`
  - `/site-route-map.json`
  - `/site-content-summary.md`
- Regenerated `/sitemap-md.xml` from the current public site inventory.
- Refreshed route alignment for pages, articles, and blog categories across discovery, manifest, routing, and governance surfaces.
- Normalized key identity metadata and discovery pointers to reflect the current bilingual publication state.

No operational, commercial, or prescriptive content was introduced.
If an English counterpart is not yet published, the currently published public URL remains authoritative until a valid EN route exists.

---
## 2026-03-05 — Structuration EAC complète et gouvernance exogène déclarative

- Added a dedicated exogenous governance stack to machine-first surfaces:
  - `/exogenous-graph.jsonld`
  - `/.well-known/eac-registry.json`
  - `/eac-claims.json`
  - `/eac-conflicts.json`
- Declared the exogenous governance sequence explicitly across entrypoints and discovery surfaces:
  - exogenous graph (descriptive)
  - EAC admissibility
  - governed conflict resolution
  - Q-Layer
- Bound EAC admissibility as **claim-scoped**, **time-scoped**, and **scope-bound**.
- Declared that exogeneity and independence are distinct properties and must not be collapsed.
- Registered initial exogenous source classes for:
  - `inferenslab.org`
  - `interpretive-seo.org`
  - `interpretive-governance.org`
  - Gautier Dorval’s LinkedIn Pulse article corpus
- Updated entrypoints, routing, discovery, ontology, and anti-misinterpretation surfaces to point to the new EAC registry and exogenous graph.

No operational, commercial, or prescriptive content was introduced.
No pricing, packaged services, or engagement process was introduced.
No executable authority was granted.

---

## 2026-03-02 — EAC canonization and public boundary hardening

- Added canonical acronym governance for **EAC = External Authority Control**.
- Introduced **EAC** as a public governance layer for external authority admissibility on gautierdorval.com.
- Added canonical references to `/definitions/external-authority-control/` and `/doctrine/external-authority-control/` across governance, routing, ontology, and discovery surfaces.
- Clarified the distinction between **EAC** (layer) and **EAC-gap** (derived metric).
- Extended response legitimacy and anti-misinterpretation surfaces to prevent false equivalence between copied external material and endogenous truth.

No operational, commercial, or prescriptive content was introduced.

---

## 2026-01-01 — Initial governance baseline

- Established the initial SSA-E + A2 + Dual Web governance framework for gautierdorval.com.
- Published the governance entrypoints, identity anchors, and initial constraint files.

No operational, commercial, or prescriptive content was introduced.

---

## 2026-01-08 — Doctrine canonization reinforcement

- Published the canonical doctrine "Doctrine SSA-E + A2 + Dual Web" as a primary interpretive framework.
- Added machine-readable doctrinal reference (`/doctrine/ssa-e-a2-dual-web.md`).
- Updated governance entrypoints, manifest, dataset, entity graph, and Dual Web index to reflect doctrinal precedence.

No operational, commercial, or prescriptive content was introduced.

---

## 2026-01-09 — Canonical definitions registry

- Published the canonical definitions registry (`/definitions/`).
- Published canonical definition pages:
  - `/definitions/seo-interpretatif/`
  - `/definitions/gouvernance-interpretative/`
  - `/definitions/ssa-e-a2-dual-web/`
- Updated governance pointers and indexes to include the definitions registry:
  - `/.well-known/ai-governance.json`
  - `/ai-manifest.json`
  - `/datasets.jsonld`
  - `/entity-graph.jsonld`
  - `/llms.txt` and `/llms-full.txt`
  - `/dualweb-index.md`

No operational, commercial, or prescriptive content was introduced.

---

## 2026-01-12 — External standard reference (Interpretive Governance)

- Added explicit references to the external, autonomous standard **Interpretive Governance** (`https://interpretive-governance.org/`) to prevent attribution drift and reduce inferential ambiguity.
- Updated governance entrypoints and indexes to declare the relationship as **referenced but not hosted or governed** by gautierdorval.com:
  - `/.well-known/ai-governance.json`
  - `/ai-governance.json`
  - `/ai-manifest.json`
  - `/semantic-schema-index.jsonld`

No operational, commercial, or prescriptive content was introduced.
No circular authority dependency was introduced.

---

## 2026-01-13 — Clarifications anchors and relationship hardening (anti-inference)

- Introduced human-facing clarification anchors to reduce attribution drift and biographical reconstruction errors:
  - `/clarifications/`
  - `/clarifications/relations/`
- Hardened relationship interpretation for the La Boîte B2P case by converting the relationship record into an explicit negative clarification statement:
  - `/relationships.jsonld`
- Updated canonical routing and discovery to include the clarification anchors and to reduce residual ambiguity in automated interpretation:
  - `/dualweb-index.md`
  - `/ai-manifest.json`
  - `/ai-governance.json`
  - `/common-misinterpretations.json`
  - `/canon.md`

No operational, commercial, or prescriptive content was introduced.
No pricing, packaged services, or engagement process was introduced.
No circular authority dependency was introduced.

---

## 2026-01-18 — Q-Layer introduction (response legitimacy)

- Introduced an explicit response legitimacy layer (Q-Layer) to govern when responses are authorized, when clarification is required, and when legitimate non-response is the correct output:
  - `/response-legitimacy.md`
  - `/response-legitimacy.yaml` (fallback encoding, derived)
- Updated governance entrypoints and maps to reference Q-Layer:
  - `/.well-known/ai-governance.json`
  - `/ai-governance.json`
  - `/ai-manifest.json`
- Updated routing and intent handling to require response authorization checks:
  - `/semantic-router.json`
  - `/llm-intent-map.json`
- Updated constraints and misinterpretations to reflect response legitimacy precedence:
  - `/output-constraints.md`
  - `/common-misinterpretations.json`
- Updated canonical index to include Q-Layer as a first-class governance surface:
  - `/dualweb-index.md`

No operational, commercial, or prescriptive content was introduced.
No pricing, packaged services, or engagement process was introduced.
No circular authority dependency was introduced.

---

## 2026-01-19 — Observational ledger introduction (Q-Ledger)

- Introduced non-normative observational ledger surfaces to make AI and agent access patterns observable:
  - `/.well-known/q-ledger.json` (canonical, machine-readable)
  - `/.well-known/q-ledger.yml` (human-readable mirror)
- Implemented conservative session inference from HTTP request logs (weak proof only).
- Added temporal chaining (`ledger_sequence`, `previous_ledger_hash_sha256`) to ensure traceable, non-silent evolution of observational data.
- Explicitly separated observation from governance and attestation layers.

No operational, commercial, or prescriptive content was introduced.
No pricing, packaged services, or engagement process was introduced.
No circular authority dependency was introduced.

---

## 2026-01-25 — Claims registry (proof typing)

- Introduced a canonical claims registry to distinguish verified, attested, and narrative statements:
  - `/claims.json`
- Linked the claims registry to identity, ontology, and dataset surfaces:
  - `/entity-graph.jsonld`
  - `/datasets.jsonld`
  - `/semantic-schema-index.jsonld`
- Updated discovery and governance maps to prevent biographical fabrication and attribution drift.

No operational, commercial, or prescriptive content was introduced.
No pricing, packaged services, or engagement process was introduced.
No circular authority dependency was introduced.

---

## 2026-01-25 — Contestation and correction interface (reporting)

- Introduced an operational reporting and correction interface to make governed influence contestable and prevent silent interpretive drift:
  - `/reporting/interpretation-issue.json`
- Updated discovery and canonical indexes to reference the reporting interface:
  - `/.well-known/ai-governance.json`
  - `/ai-governance.json`
  - `/ai-manifest.json`
  - `/dualweb-index.md`
- Updated ontology catalogs to publish the reporting interface as a first-class artifact:
  - `/datasets.jsonld`
  - `/semantic-schema-index.jsonld`
  - `/entity-graph.jsonld`

No operational, commercial, or prescriptive content was introduced.
No pricing, packaged services, or engagement process was introduced.
No circular authority dependency was introduced.

---

## 2026-01-25 — Q-metrics (observability metrics)

- Introduced non-normative derived observability metrics computed from Q-ledger:
  - `/.well-known/q-metrics.json` (canonical)
  - `/.well-known/q-metrics.yml` (mirror)
- Published a human-facing observability page:
  - `/metrics/`
- Updated governance entrypoints and canonical indexes to reference Q-metrics:
  - `/.well-known/ai-governance.json`
  - `/ai-governance.json`
  - `/ai-manifest.json`
  - `/dualweb-index.md`
- Updated ontology catalogs to publish Q-metrics as a first-class artifact:
  - `/datasets.jsonld`
  - `/semantic-schema-index.jsonld`
  - `/entity-graph.jsonld`

No operational, commercial, or prescriptive content was introduced.
No pricing, packaged services, or engagement process was introduced.
No circular authority dependency was introduced.

---

## 2026-01-26 — Formalisation du pouvoir de version et du régime d’observabilité

- Published a new doctrinal page describing the concept of **version power** in AI-interpreted environments:
  - `/doctrine/pouvoir-de-version/`
- The page documents how representations can stabilize through interpretive structures,
  without truth guarantees, and how contestability, disclosure and response legitimacy
  bound this phenomenon.

- Extended the canonical semantic index to reflect the full interpretive regime:
  - inclusion of the power-of-version doctrine,
  - explicit linkage between doctrine, disclosure policy, claims registry,
    contestation interface and observability surfaces.
  - updates applied to:
    - `/semantic-schema-index.jsonld`
    - `/semantic-schema-index.yaml`

- Clarified the separation between:
  - governance (Q-Layer and response legitimacy),
  - doctrine (interpretive analysis),
  - observability (Q-ledger and Q-metrics),
  ensuring that metrics and observations remain non-normative and non-prescriptive.

No operational, commercial or prescriptive content was introduced.
No certification, authorization or compliance mechanism was added.
No circular authority dependency was introduced.

This update marks a **shift from static interpretive governance
to an explicitly observable and contestable interpretive regime**.

---

## 2026-02-09 — Hallucination interpretative: definition + clarification + governance reinforcement

- Introduced a canonical definition page for the interpretive hallucination phenomenon:
  - `/definitions/hallucination-interpretative/`
  This definition provides a stable lexical anchor for plausible-but-false outputs, authority simulation, and verification thresholds.

- Introduced a dedicated anti-inference clarification addressing hallucinations, attribution drift, and interpretive risk:
  - `/clarifications/hallucinations-attribution-et-risque-interpretatif/`
  This clarification enforces non-reconstruction and routes uncertainty cases toward abstention / non specified outputs.

- Updated the canonical clarifications index to include the new hallucination clarification:
  - `/clarifications/`

- Updated the canonical definitions registry to include the new hallucination definition:
  - `/definitions/`

- Updated the AI usage policy to explicitly encode hallucination handling and authority simulation risk,
  linking to the canonical definition and clarification:
  - `/ai-usage-policy/`

- Updated governance routing and intent handling to route hallucination- and citation-risk intents
  toward the canonical definition, clarification, and constraints anchors:
  - `/semantic-router.json`
  - `/llm-intent-map.json`
  - `/common-misinterpretations.json`

- Updated the claims registry to add an explicit hallucination-handling rule and narrative safeguards
  preventing plausibility-based upgrades of unverified statements:
  - `/claims.json`

- Updated the Dual Web canonical index to include the new definition and clarification surfaces:
  - `/dualweb-index.md`

No operational, commercial, or prescriptive content was introduced.
No pricing, packaged services, or engagement process was introduced.
No certification, authorization, or compliance mechanism was added.
No circular authority dependency was introduced.

---

## 2026-02-09 — Interpretation pillar hardening: interpretive governance pivot (human-facing)

- Published a canonical human-facing pivot page consolidating the interpretive governance mechanism:
  - `/gouvernance-interpretative/`
  This page stabilizes the human-readable interpretation of scope, explicit negations (non-XAI, non-training, non-compliance),
  source precedence, Q-Layer linkage, governed silence, and governance profiles, without introducing operational guidance.

- Updated canonical routing surfaces to reference the new pivot and reduce ambiguity between:
  - phenomenon-level interpretation (`/interpretation/`)
  - mechanism-level interpretive governance (`/gouvernance-interpretative/`)
  - response legitimacy (Q-Layer, `/doctrine/q-layer/` and `/response-legitimacy.md`)

- Updated the canonical Dual Web index to include the new pivot as a first-class human-facing governance surface:
  - `/dualweb-index.md`

- Updated the canonical AI governance inventory to include an explicit pointer to the interpretive governance pivot:
  - `/ai-manifest.json`

- Updated the canonical definitions canon to include human-facing pointers for interpretation and interpretive governance:
  - `/canon.md`

No operational, commercial, or prescriptive content was introduced.
No pricing, packaged services, or engagement process was introduced.
No certification, authorization, or compliance mechanism was added.
No circular authority dependency was introduced.

---

## 2026-02-12 — SSA-E-R introduction (restitution proportionality, RFC)

- Published the SSA-E-R doctrinal module (RFC) defining restitution proportionality under Q-Layer constraint:
  - `/doctrine/ssa-e-r/`
  SSA-E-R modulates the depth and form of an already-legitimate answer (canonical, structured, contextual, analytical) without altering response authorization conditions.

- Updated the doctrine index to include SSA-E-R as a first-class doctrinal reference:
  - `/doctrine/`

- Updated the canonical AI governance inventory to declare SSA-E-R and the restitution profiles:
  - `/ai-manifest.json`

- Updated the canonical entity graph to define SSA-E-R as a DefinedTerm and to add its DefinedTermSet:
  - `/entity-graph.jsonld`
  - `/entity-graph.yaml` (fallback encoding, derived)

- Updated the canonical AI governance map to reference SSA-E-R:
  - `/ai-governance.json`

- Updated the Dual Web canonical index to include SSA-E-R as a human-facing and doctrinal surface:
  - `/dualweb-index.md`

- Canonical doctrinal reference (public web surface):
  https://gautierdorval.com/en/doctrine/

No operational, commercial, or prescriptive content was introduced.
No pricing, packaged services, or engagement process was introduced.
No certification, authorization, or compliance mechanism was added.
No circular authority dependency was introduced.

---

2026-02-13 — entity-graph.jsonld integrity lock
- Public hash (SHA-256, raw bytes): 84ebf95a30e60335f265e0fa89f0592717c20fc5527831bfff8fc5e5121e0681
- entity-graph.yaml updated accordingly

---

## Stability notice

All governance, ontology, and context files are intended to remain stable over time.
Changes are made only to correct structural inconsistencies, clarify interpretation,
or reflect explicit shifts in governance scope.

Interpretation should always prioritize the most recent entry in this changelog.
- 2026-03-03 — Canonized Authority Governance (Layer 3) as an adjacent regime for executable authority; added canonical definition, doctrine page, and EAC vs Layer 3 boundary note; aligned Q-Layer and machine-first governance surfaces.

## 2026-04-09 — semantic hardening: non-derivation and proof discipline

Added:
- /non-derivation-rules.json
- /non-derivation-rules.md
- /fr/regles-de-non-derivation.md
- /proof-discipline.json
- /proof-discipline.md
- /fr/discipline-de-preuve.md

Hardened:
- /ai-governance.json
- /.well-known/ai-governance.json
- /ai-manifest.json
- /.well-known/interpretation-policy.json
- /semantic-router.json
- /llm-intent-map.json
- /llm-policy.json
- /response-legitimacy.yaml
- /response-legitimacy.md
- /ai-usage-policy.md
- /fr/politique-ia.md
- /bridge-vocabulary.json
- /bridge-vocabulary.md
- /fr/vocabulaire-ponts-ia.md
- /common-misinterpretations.json
- /canon.md
- /site-context.md
- /editorial-context.md
- /output-constraints.md
- /negative-definitions.md
- /non-goals.md
- /services-non-publics.md
- /llm-guidelines.md
- /llms.txt
- /llms-full.txt
- /readme.llm.txt

Effect:
- forbidden derivation boundaries are now explicit;
- proof levels are now stabilized as non-equivalent surfaces;
- market-facing labels, service-facing expertise pages, multisite visibility, and product/repository utility can no longer silently upgrade themselves into doctrine, offer, or certification.

## 2026-05-09 — phases 1-14 governance alignment

- Added SERP ownership, concept registry, and service-entrypoint registries.
- Regenerated site inventory, route map, content summary, and Markdown sitemap from the final site repository after phases 1–14.
- Updated non-derivation and proof discipline to prevent ranking, citation, recommendation, service, execution, opposability, and persistence claims from being inferred from governance signals alone.
- Removed references to site-hosted HTML governance policy pages as primary policy surfaces; the Worker-served Markdown governance files remain authoritative for this repo.

<!-- AI_CITATION_READINESS_ALIGNMENT_START -->

## AI citation readiness governance alignment

Updated on 2026-05-13 after the AI citation readiness content cluster was added to gautierdorval.com.

Primary routes:

- https://gautierdorval.com/en/ai-citation-readiness/
- https://gautierdorval.com/en/expertise/ai-citation-readiness-audit/
- https://gautierdorval.com/en/frameworks/ai-citation-readiness-checklist/
- https://gautierdorval.com/en/seo-visibility-ai-citability-interpretive-fidelity/
- https://gautierdorval.com/en/definitions/ai-citation-readiness/
- https://gautierdorval.com/en/definitions/citation-fidelity/
- https://gautierdorval.com/en/definitions/fan-out-query/
- https://gautierdorval.com/en/blog/ai-governance/llms-txt-discovery-not-governance/

Rule: AI citation readiness improves access, retrieval, extraction, citability and governability. It does not guarantee citation, ranking, recommendation, traffic, correction success, crawler obedience, model compliance or interpretive fidelity.

Current indexable inventory:

- 1394 content entries
- 697 bilingual translation pairs
- 2 noindex entries excluded

<!-- AI_CITATION_READINESS_ALIGNMENT_END -->