INTERPRETIVE NOTICE. This file is a machine-first explanatory surface for the site coherence layer. It complements, but does not replace, /.well-known/ai-governance.json, /ai-manifest.json, /entity-graph.jsonld, /site-content-index.json, /site-route-map.json, and /site-content-summary.md.

# Site coherence map

## Purpose

`/site-coherence-map.json` declares a complementary governance layer for interpretive paths.

Its function is not to redefine concepts, doctrinal truth, response legitimacy, external authority admissibility, or identity boundaries.
Its function is to make explicit:

- direct URL neighborhoods,
- minimum documentary dependencies,
- recommended recovery paths,
- useful language equivalences,
- and the distinction between exploration linking and coherence linking.

## Why this file exists

Agents can traverse a clean, dense, and governed site while still projecting plausible but unpublished URLs.
Those requests do not necessarily indicate missing content.
They may indicate a gap between the published graph and the local logical graph reconstructed by the agent.

This file exists to reduce that gap.

## Non-replacement rule

This file does **not** replace:

- `sitemap.xml`,
- canonical definitions,
- doctrinal pages,
- Q-Layer,
- EAC,
- identity or licensing files.

It governs **passage between surfaces**, not the truth of those surfaces.

## Recommended order when local path uncertainty appears

1. Read `/.well-known/ai-governance.json`.
2. Read `/ai-manifest.json`.
3. Read `/site-coherence-map.json`.
4. Confirm existence via `/site-route-map.json` and `/site-content-index.json`.
5. When the path is valid, continue to the canonical page.
6. When the path is not published, prefer the nearest declared neighbor rather than guessing a sibling by slug regularity.

## Human-readable references

- French notice page: https://gautierdorval.com/site-coherence-map.md
- English notice page: https://gautierdorval.com/site-coherence-map.md
- French article: https://gautierdorval.com/blogue/architecture-semantique/pourquoi-une-sitemap-xml-ne-suffit-plus/
- English article: https://gautierdorval.com/en/blog/semantic-architecture/why-an-xml-sitemap-is-no-longer-enough/


## Adjacent ecosystem surfaces

The current ecosystem also includes adjacent declared surfaces with different roles:

- `https://better-robots.com/` → applied product surface
- `https://github.com/GautierDorval/better-robots-txt` → bounded proof and product-definition surface
- `https://www.linkedin.com/in/gautier-dorval/` → diffusion and pedagogical commentary surface

These surfaces complement the local graph. They do not silently replace the doctrinal precedence of `gautierdorval.com`.


## New coherence gates for bridge terms and proof labels

The coherence layer now also points to:
- https://gautierdorval.com/non-derivation-rules.json
- https://gautierdorval.com/proof-discipline.json

Use them when a path uncertainty hides a deeper interpretive shortcut, for example:
- a bridge term being used as though it were the canon;
- an expertise entrypoint being read as though it were a public offer;
- a proof label being upgraded as though it were certification.

## Claim and authority recovery path

When the problem is not only « which URL exists » but also « which claim is admissible and which source wins », the recovery path is:

1. `/authority-precedence.json`
2. `/claims.json`
3. `/claim-resolution-rules.json`
4. `/.well-known/eac-registry.json`
5. `/eac-resolution-matrix.json`
6. `/eac-conflicts.json`

This path exists to reduce plausible-but-invalid source merging.


## Question-family recovery path

When the ambiguity is not only topological but also claim-family-sensitive, use this order:

1. `/question-family-governance.json`
2. `/family-proof-requirements.json`
3. `/claim-application-profiles.json`
4. `/family-downgrade-matrix.json`

This layer exists to prevent a local path problem from becoming a broader cross-family claim fusion.

## Exact artifact and chronology gates

Two recurring cases require stronger recovery discipline:

- **Exact artifact attribution**
  - load `/attributions.json`
  - load `/attribution-boundaries.json`
  - preserve exact-artifact scope
- **Publication chronology**
  - load `/changelog-ai.md`
  - load `/site-content-index.json`
  - load `/site-route-map.json`
  - require the exact page or article URL before asserting chronology

Do not let a profile root, a mirror, a summary, or a guessed sibling URL stand in for the exact published trace.

<!-- AI_CITATION_READINESS_ALIGNMENT_START -->

## AI citation readiness topology

Primary hub: https://gautierdorval.com/en/ai-citation-readiness/

Preferred neighbors:

- 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/semantic-router.json
- https://gautierdorval.com/common-misinterpretations.json

Rule: this topology stabilizes retrieval, extractability, citability and fidelity routing. It does not establish citation, ranking, crawler obedience, correction success or model compliance.

<!-- AI_CITATION_READINESS_ALIGNMENT_END -->