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.
Definitions canon
/canon.md
Canonical surface that fixes identity, roles, negations, and divergence rules.
- Governs
- Public identity, roles, and attributes that must not drift.
- Bounds
- Extrapolations, entity collisions, and abusive requalification.
Does not guarantee: A canonical surface reduces ambiguity; it does not guarantee faithful restitution on its own.
Site context
/site-context.md
Notice that qualifies the nature of the site, its reference function, and its non-transactional limits.
- Governs
- Editorial framing, temporality, and the readability of explicit changes.
- Bounds
- Silent drifts and readings that assume stability without checking versions.
Does not guarantee: Versioning makes a gap auditable; it does not automatically correct outputs already in circulation.
Public AI manifest
/ai-manifest.json
Structured inventory of the surfaces, registries, and modules that extend the canonical entrypoint.
- Governs
- Access order across surfaces and initial precedence.
- Bounds
- Free readings that bypass the canon or the published order.
Does not guarantee: This surface publishes a reading order; it does not force execution or obedience.
Evidence layer
Probative surfaces brought into scope by this page
This page does more than point to governance files. It is also anchored to surfaces that make observation, traceability, fidelity, and audit more reconstructible. Their order below makes the minimal evidence chain explicit.
- 01Canon and scopeDefinitions canon
- 02Weak observationQ-Ledger
Definitions canon
/canon.md
Opposable base for identity, scope, roles, and negations that must survive synthesis.
- Makes provable
- The reference corpus against which fidelity can be evaluated.
- Does not prove
- Neither that a system already consults it nor that an observed response stays faithful to it.
- Use when
- Before any observation, test, audit, or correction.
Q-Ledger
/.well-known/q-ledger.json
Public ledger of inferred sessions that makes some observed consultations and sequences visible.
- Makes provable
- That a behavior was observed as weak, dated, contextualized trace evidence.
- Does not prove
- Neither actor identity, system obedience, nor strong proof of activation.
- Use when
- When it is necessary to distinguish descriptive observation from strong attestation.
AI-ready content blocks are compact evidence units designed to survive passage-level retrieval and extraction. They help systems identify the useful claim without forcing them to infer too much from surrounding context.
A strong article can still be weak for AI citation if its core answer is buried, implied or spread across multiple paragraphs. The block solves that problem by making the claim visible, bounded and routeable.
A useful block contains five parts
A strong AI-ready content block should contain:
- a precise heading;
- a direct answer or definition;
- one or two supporting sentences;
- a boundary or exclusion;
- a link to the governing source when needed.
The block should be readable by humans, but it should also work when extracted from the page.
Bad block
“AI visibility is becoming important for brands. Many factors affect whether models mention an entity.”
This is too vague. It does not define the claim, source role or perimeter.
Better block
“AI citation readiness is the ability of a page, passage, entity or source to be accessible, retrievable, extractable, citable and governable inside AI-mediated answer systems. It improves citation conditions but does not guarantee ranking, citation, recommendation or model compliance.”
This version is portable, bounded and safer to cite.
Placement
Place answer-ready blocks near the top of pages that govern important claims. Use them in definitions, service pages, hubs and doctrinal pages. Avoid hiding them in tabs, collapsed sections or late-page summaries.
Governance implication
AI-ready blocks should not replace the canon. They should point toward it. Their purpose is to make the canonical route easier to discover and harder to misread.