Normative standard
Bounded interpretation.
Governed output.
Interpretive Governance: canonical doctrinal surface for bounded interpretation, source precedence, proof of fidelity, and public machine-readable governance.
01 · Interpret
Only within declared scope and provenance.
02 · Authorize
Only answer when response-legitimacy conditions are satisfied.
03 · Constrain
Keep the answer inside declared output constraints.
04 · Refuse
When legitimacy fails, the correct behavior is clarification, abstention, or legitimate non-response.
Foundational corpus
Core principles of Interpretive Governance: separate claims from inferences, apply constraints before optimization, and require auditability.
Why interpretation precedes response, why silence can be correct, and why canonical reading is a governance problem rather than a style preference.
Governance layer that qualifies which external authorities are admissible, on what scope, and under what claim and time conditions.
Proposed core doctrinal layer that governs the triggering situation, latent need, intended consequence, and forbidden derivations attached to public surfaces.
Proposed boundary layer separating semantic proximity from equivalence, causality, proof, recommendation, and authorization.
Doctrine requiring a public governance package to include policy, machine files, discovery links, route maps, context layers, boundaries, and validation evidence.
Multisite doctrine for assigning doctrinal, product, institutional, commercial, and probative authority roles without letting internal surfaces compete interpretively.
Why observation must distinguish signals, logs, derived metrics, and proof without collapsing them into one authority surface.
Operational framework for classifying one ecosystem’s surfaces by role, authority level, dependencies, and non-override limits.
Method for documenting whether an answer remains inside the canon rather than merely sounding plausible or technically justified.
Minimum public protocol for testing canon-output fidelity, documenting gaps, and escalating toward correction or legitimate non-response.
Machine-first entrypoints
/ig-manifest.jsonManifest/.well-known/ai-governance.jsonAI governance/data/terms.jsonRegistry/entity-graph.jsonldGraph/llms.txtllms.txt/llms-full.txtllms-full.txt/doctrine-index.jsonDoctrine index/site-route-map.jsonRoute map/site-coherence-map.jsonCoherence map/search-index.jsonSearch index/.well-known/q-ledger.jsonQ-Ledger/.well-known/q-metrics.jsonQ-Metrics/sitemap.xmlSitemapEcosystem role
Interpretive Governance is the canonical public doctrinal surface for a bounded subset of the broader corpus authored by Gautier Dorval. It is designed to be colder, stricter, and more machine-readable than the parent site.
This site is therefore not a portfolio, not a product surface, and not a sales front. It is the external canonical layer for doctrine, boundary conditions, and public governance files.
What changed in doctrine 0.5
- stronger coverage of interpretation, authority allocation, observability, and proof-of-fidelity
- a new frameworks layer that operationalizes doctrine without disclosing private execution
- a new evidence layer that groups auditability, observability, Q-Ledger, and Q-Metrics
- multisite governance surfaces that clarify the role of this site relative to gautierdorval.com
- expanded machine-first entrypoints for route mapping, coherence mapping, search, and public attestability
Doctrine 0.5 proposed upgrade
This version expands the public corpus from a governance-file cluster into a maximalist governance package. It adds CCL, semantic-boundary separation, interpretive false neighbors, a behavioral testset scaffold, completeness rules for governance deployment, and explicit HTML plus HTTP Link discovery surfaces.
The upgrade does not claim that all proximity or false-neighbor behavior has already been measured. It publishes the doctrine, the boundaries, the proposed artifacts, and the validation gates required before future measurement can become evidence.
Reading order
- Start with the canonical governance cluster under
/.well-known/. - Read the doctrine hubs and the pages on interpretation, source precedence, response legitimacy, and authority.
- Use the frameworks hub when doctrine must be translated into public operating models.
- Use the evidence hub when the question concerns proof, observability, logging, or contestability.
- Defer upward to
gautierdorval.comonly for higher-order multisite authority allocation or broader corpus context.
Public boundary
This site does not disclose private execution logic, calibrated thresholds, client methods, private datasets, or deployment procedures. It publishes only the public doctrine necessary to constrain interpretation and make public outputs contestable.