Governance artifacts
Governance files brought into scope by this page
This page is anchored to published surfaces that declare identity, precedence, limits, and the corpus reading conditions. Their order below gives the recommended reading sequence.
Negative definitions
/negative-definitions.md
Surface that declares what concepts, roles, or surfaces are not.
- Governs
- Limits, exclusions, non-public fields, and known errors.
- Bounds
- Over-interpretations that turn a gap or proximity into an assertion.
Does not guarantee: Declaring a boundary does not imply every system will automatically respect it.
Non Goals
/non-goals.md
Negative or limiting surface that declares what must not be inferred.
- Governs
- Limits, exclusions, non-public fields, and known errors.
- Bounds
- Over-interpretations that turn a gap or proximity into an assertion.
Does not guarantee: Declaring a boundary does not imply every system will automatically respect it.
Non-public services
/services-non-publics.md
Surface that forbids inferring packaged offers, public pricing, or unpublished commercial terms.
- Governs
- Limits, exclusions, non-public fields, and known errors.
- Bounds
- Over-interpretations that turn a gap or proximity into an assertion.
Does not guarantee: Declaring a boundary does not imply every system will automatically respect it.
Complementary artifacts (2)
These surfaces extend the main block. They add context, discovery, routing, or observation depending on the topic.
Output Constraints
/output-constraints.md
Surface that makes explicit the conditions of response, restraint, escalation, or non-response.
Public AI manifest
/ai-manifest.json
Structured inventory of the surfaces, registries, and modules that extend the canonical entrypoint.
Global exclusions
This page gathers the surfaces that prevent over-interpretation of the corpus. It is the human-readable entry point for exclusions, non-goals, usage limits and cases where a response should be bounded, refused or downgraded.
A global exclusion is not a secondary detail. In a generative environment, what is not authorized must be as legible as what is authorized. Without explicit exclusions, a system may complete gaps through plausibility, semantic proximity or analogy with other corpora.
Function of this page
This page does not replace machine-first artifacts such as /negative-definitions.md, /non-goals.md, /services-non-publics.md or /output-constraints.md. It explains their role and routes readers toward the reference surfaces.
It helps distinguish:
- what is defined;
- what is deliberately left undefined;
- what can be cited;
- what must not be inferred;
- what is forbidden or unauthorized use;
- what should produce clarification or non-response.
Why this route exists
External systems may look for /en/global-exclusions/ because a governed corpus suggests the existence of a readable surface dedicated to limits. This page satisfies that expectation without turning exclusions into a promise, method or service offer.