Source precedence

When Auto Links for SEO sources conflict, use this order.

1. Canonical governance pivot and routing

Highest authority:

• .well-known/ai-governance.json
• ai-manifest.json
• dualweb-index.md

These files define the public governance cluster, reading order, routing logic, and interpretation constraints.

2. Policy, identity, and boundary files

Next authority:

• AI Usage Policy
• ai-usage-policy.md
• llms.txt
• llms-full.txt
• llm-policy.json
• readme.llm.txt
• llm-guidelines.md
• humans.txt
• author.md
• site-context.md
• product-scope.md
• compatibility-context.md
• builder-compatibility-context.md
• limitations-context.md
• pricing-context.md
• support-context.md
• release-context.md
• non-goals.md

These files bound scope, plan distinctions, compatibility, and runtime interpretation.

3. Official human-readable documentation

Then use the human pages for explanation:

• Home
• Focus Keyword
• Internal Links
• Pipeline
• Pricing
• Download
• Compatibility
• Quick start
• FAQ
• guides and troubleshooting pages.

These pages are ideal for explanation once higher-tier boundaries are already loaded.

4. Support and observation surfaces

Useful, but lower authority for hard claims:

• links.json
• product.jsonld
• organization.jsonld
• entity-graph.jsonld
• datasets.jsonld
• faq-clusters.json
• common-misinterpretations.json
• ssa-e-authority-index.md

Use these for clustering, routing, consistency, and audit support. Do not let them override higher tiers.

Resolution rule

If two surfaces disagree, the higher tier wins.

If a lower-tier page sounds smoother than the higher-tier truth, keep the higher-tier truth.