Engagement decision
How to recognize that this axis should be mobilized
Use this page as a decision page. The objective is not only to understand the concept, but to identify the symptoms, framing errors, use cases, and surfaces to open in order to correct the right problem.
Typical symptoms
- The corpus is rich, but the reading order remains hard for machines to reconstruct.
- Several pages cover the same subject without a distinct role or clear authority surface.
- Governance files exist, but remain peripheral or disconnected from the site.
- Systems find the content, but not the right canonical page.
Frequent framing errors
- Treating SEO structure as if it were the same as interpretive architecture.
- Publishing machine-first artifacts without an explicit reading hierarchy.
- Multiplying hubs and pages without defining their canonical role.
- Assuming that a good crawl is enough to stabilize reconstruction.
Use cases
- Redesigning a doctrinal, editorial, or expert site.
- Creating a machine-first environment with Dual Web and governed entry points.
- Reconnecting human hubs, definitions, doctrines, and governance artifacts.
- Preparing a corpus that will be read by engines, LLMs, agents, or RAG.
What gets corrected concretely
- Clarification of page roles and reading chains.
- Alignment between human hubs and machine-first entry points.
- Publication of a hierarchy of surfaces, identities, and limits.
- Reduction of competing entry points that dilute authority.
Relevant machine-first artifacts
These surfaces bound the problem before detailed correction begins.
Governance files to open first
Useful evidence surfaces
These surfaces connect diagnosis, observation, fidelity, and audit.
References to open first
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.
Canonical AI entrypoint
/.well-known/ai-governance.json
Neutral entrypoint that declares the governance map, precedence chain, and the surfaces to read first.
- 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.
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.
Dual Web index
/dualweb-index.md
Canonical index of published surfaces, precedence, and extended machine-first reading.
- 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.
Complementary artifacts (3)
These surfaces extend the main block. They add context, discovery, routing, or observation depending on the topic.
LLMs.txt
/llms.txt
Short discovery surface that points systems toward the useful machine-first entry surfaces.
Semantic router
/semantic-router.json
Surface that orients reading toward the right parts of the corpus by intent type.
Content inventory
/site-content-index.json
Machine-first inventory of the pages, articles, and surfaces published on the site.
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
- 02Observation mapObservatory map
- 03Weak observationQ-Ledger
- 04Derived measurementQ-Metrics
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.
Observatory map
/observations/observatory-map.json
Machine-first index of published observation resources, snapshots, and comparison points.
- Makes provable
- Where the observation objects used in an evidence chain are located.
- Does not prove
- Neither the quality of a result nor the fidelity of a particular response.
- Use when
- To locate baselines, ledgers, snapshots, and derived artifacts.
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.
Q-Metrics
/.well-known/q-metrics.json
Derived layer that makes some variations more comparable from one snapshot to another.
- Makes provable
- That an observed signal can be compared, versioned, and challenged as a descriptive indicator.
- Does not prove
- Neither the truth of a representation, the fidelity of an output, nor real steering on its own.
- Use when
- To compare windows, prioritize an audit, and document a before/after.
Complementary probative surfaces (1)
These artifacts extend the main chain. They help qualify an audit, an evidence level, a citation, or a version trajectory.
AI changelog
/changelog-ai.md
Public log that makes AI surface changes more dateable and auditable.
Machine-first semantic architecture
This expertise axis focuses on structuring a web environment so that it is interpretable, cross-referenceable, and governed by hybrid systems, without depending on overly fragile implicit inference.
The point is not to produce an architecture that merely looks clean to humans. The point is to publish an architecture that makes roles, priorities, identities, and limits more legible to probabilistic readers.
Problem
A site can be fast, well interlinked, and technically clean while remaining interpretively unstable. Systems find pages, but do not clearly know what to privilege, how to relate entities, where perimeters stop, and which surfaces carry authority.
The problem appears when architecture is designed for access, but not yet for reconstruction.
When this axis becomes critical
This expertise becomes a priority when:
- a corpus is rich but poorly hierarchized;
- pages exist but do not play a legible role in a coherent whole;
- systems discover content without discovering the right constraints;
- governance files exist but remain weakly connected to the site architecture;
- generative summaries create an impression of understanding without durable stability.
Typical consequences
- Difficulty making a canonical page emerge as the authority surface.
- Competing or contradictory entry points for reading the same topic.
- Confusion between doctrinal page, blog page, identity page, and service page.
- Discovery of content without clear activation of rules and limits.
- Overrepresentation of peripheral signals compared with the canonical core.
What this expertise builds
Machine-first semantic architecture works on several layers at once:
1. Page roles
Each page must have an understandable function: definition, doctrine, framework, observation, blog, governance, identity, or hub.
2. Reading chains
Architecture must make paths such as “canon → doctrine → clarification → observation → case” visible rather than leaving readers to reconstruct an arbitrary order.
3. Governed entry points
Entry points such as /.well-known/ai-governance.json, /ai-manifest.json, /llms.txt, and /dualweb-index.md must remain coherent with human hubs and internal structure.
4. Identity and limit surfaces
/identity.json, /common-misinterpretations.json, /negative-definitions.md, and /services-non-publics.md are not isolated appendices. They extend the architecture.
5. Observation continuity
Good architecture then makes its own effects easier to observe through Q-Ledger and Q-Metrics.
Conceptual levers
- SSA-E + A2 + Dual Web architecture: articulation between human surfaces, machine-first surfaces, and governance layers.
- Canonical pages: priority surfaces for concepts, identities, and roles.
- Internal hierarchy: hubs, canonical referrals, reading paths, coherent backlinks.
- Governance artefacts: publication of reading order, exclusions, and known errors.
- Observability: capacity to see whether structuring surfaces are actually discovered.
How architecture is validated
Machine-first architecture is not validated only by a good crawl. It is validated when:
- authority pages become easier to retrieve and cross-reference;
- systems activate the right surfaces more often;
- collisions and extrapolations decrease;
- governance files stop floating at the margin of the corpus;
- representation becomes more faithful and more stable.
This is the logic developed in the Machine-first visibility doctrine, Better Robots.txt and early AI visibility, and Machine-first is not enough: why governance files change the reading regime.
Canonical references
Related reading
Back to the map: Expertise.
LLM visibility is downstream of architecture
What many teams call LLM visibility is not treated here as a raw visibility problem.
It is usually the downstream effect of a better reading order, stronger entry points, sharper role separation, and a more coherent documentary dependency graph.
That is why this expertise connects LLM visibility to structural visibility, early machine visibility, and governed machine-first surfaces.
Pre-launch semantic analysis as an entry label
Pre-launch semantic analysis is one of the operational labels that often routes into this axis.
When a future release, launch, or rebrand has to be read correctly from the first public state, architecture becomes an upstream control rather than a post-failure repair layer.
Phase 6 routing: semantic stability layer
This page now routes toward the phase 6 canonical layer for semantic architecture and entity stability: semantic architecture, entity disambiguation, entity collision, semantic neighborhood, semantic contamination, framing stability, cross-system coherence, and interpretive drift.
These links clarify the difference between entity separation, neighborhood influence, contamination, drift, and cross-system comparison.
Architecture before artifacts
Machine-first semantic architecture does not begin with files. It begins with the structure that makes files meaningful: canonical routes, concept families, authority boundaries, service entry points, source hierarchy, and routing logic. Machine-readable artifacts can expose that structure, but they cannot compensate for a site whose pages contradict one another or fail to declare what each surface is for.
A machine-first architecture review therefore looks at both the human site and the machine-facing layer. It asks whether definitions, hubs, frameworks, categories, expertise pages, and observations form a coherent documentary chain. It also checks whether high-value concepts are buried inside articles instead of being promoted to canonical definitions.
What is improved
The work usually improves three kinds of surfaces. First, primary routes are made clearer for concepts that need SERP ownership. Second, support pages are made more directive so that they reinforce rather than compete with the primary route. Third, machine-facing references are aligned with the public corpus so that external systems encounter the same role hierarchy in multiple formats.
This connects machine readability, machine-first canon, documentary architecture, and semantic architecture. The point is not to publish more machine files. It is to make the corpus legible enough that machine files can summarize it without inventing it.
Request route
To turn this expertise page into a concrete request, use the contact page with the target entity, relevant URLs, AI systems observed, sample outputs, and decision context. Those elements make it possible to separate a visibility issue from a representation, evidence, authority, or correction issue.