Global exclusions

Global exclusions

This page is the canonical definition of global exclusions within the canon, corpus, and machine readability layer of interpretive governance.

Global exclusions are site-wide negative constraints that define what must not be inferred, attributed, commercialized, generalized, or treated as offered across the entire corpus.

Short definition

Global exclusions are site-wide negative constraints that define what must not be inferred, attributed, commercialized, generalized, or treated as offered across the entire corpus.

Why it matters

They protect the corpus from default inference. A global exclusion applies even when the retrieved page is about a nearby concept and even when a synthesized answer would sound plausible.

In AI search, retrieval-augmented generation, autonomous browsing, and agentic reading, a corpus is not interpreted only by its visible prose. It is interpreted through routes, files, metadata, exclusions, entity relations, sitemap placement, and internal links. Global exclusions names one part of that documentary control layer.

The strategic function is therefore not cosmetic. The concept helps prevent systems from flattening doctrine, service language, proof artifacts, and observations into the same authority level. It also gives search engines a clearer canonical page to associate with the term rather than forcing them to choose between a hub, a category, a blog article, and a machine artifact.

What it is not

They are not decorative disclaimers, not local caveats, and not optional context that can be dropped during summarization.

This distinction matters because machine-readable governance can create false confidence. A structured file, a definition page, or a graph relation should never be treated as proof that external systems comply with the intended reading. It only makes the intended reading more explicit, testable, and auditable.

Common failure modes

• a model infers services from expertise language;
• a doctrine page is turned into a reproducible method;
• a concept is treated as a product feature;
• third-party summaries ignore explicit non-goals;

These failures are typical when the human corpus and the machine-first corpus evolve separately. They increase interpretive risk because models can still produce coherent answers while violating the source hierarchy or ignoring exclusions.

Governance implication

Global exclusions must be visible in human pages, machine artifacts, response-legitimacy surfaces, and internal links. They should be connected to governed negation, mandatory silence, and the non-inference regime.

For SERP ownership, the same principle applies: the canonical page should receive descriptive links, appear in the definitions registry, be discoverable from the glossary, and be reinforced by machine-first artifacts without competing against them.

Related canonical definitions

• Governed Negation
• Mandatory Silence
• Non-inference regime
• Reading conditions
• Response Conditions
• Answer Legitimacy
• Interpretive Risk

Supporting artifacts and surfaces

• /canon.md
• /site-context.md
• /ai-manifest.json
• /.well-known/ai-governance.json
• /entity-graph.jsonld
• Definitions registry

Phase 10 inference-control adjacency

This definition now routes adjacent inference-control questions toward interpretive error space, free inference, default inference, arbitration, indeterminacy, and interpretive fidelity.

This adjacency matters because a system can produce a fluent answer while silently filling gaps, selecting the wrong authority, hiding indeterminacy, or losing fidelity to the canon. The phase 10 layer makes those failure paths explicit.

Reading guidance

Use Global exclusions as a bounded interpretive term. The page should help a reader decide when the concept applies, when it does not apply, and which neighboring concepts should be consulted before drawing a conclusion.

What to verify

• Whether the concept is being used as a precise diagnostic term or as a generic label.
• Whether the statement remains inside the canon and the declared perimeter.
• Whether the output preserves uncertainty, source hierarchy, and response conditions.
• Whether an adjacent concept would describe the situation more accurately.

Practical boundary

This concept should not be isolated from the rest of the corpus. It works best when read with the definitions, frameworks, observations, and service pages that clarify its evidence requirements and operational limits.