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 brand appears in AI answers, but its services, roles, or capabilities are extended beyond the canon.
The official site is cited or mobilized, but a third party seems to govern the actual framing of the answer.
Limits, exclusions, conditions, or perimeters disappear under synthesis.
Systems reconstruct the same organization in incompatible ways depending on model, language, or phrasing.

Frequent framing errors

Reducing the problem to a drop in visibility when the representation itself is drifting.
Confusing citations, mentions, or dashboards with proof of fidelity.
Correcting isolated pages without an explicit hierarchy of sources, canon, and perimeter.
Treating a reconstruction gap as a mere tone or reputation issue.

Use cases

Diagnosing a brand that is visible but poorly understood in AI answers.
Qualifying an abusive extension of offer scope, expertise scope, or geographic coverage.
Auditing a mismatch between the official site, third parties, directories, and generative answers.
Prioritizing endogenous and exogenous corrections before a rebrand, redesign, or editorial amplification.

What gets corrected concretely

More explicit declaration of the canon, limits, and governed negations.
Clearer hierarchy of the sources that should prevail in reconstruction.
Separation between visibility, citability, fidelity, and stability.
A correction plan combining architecture, governance, proof, and third-party surfaces.

Relevant machine-first artifacts

These surfaces bound the problem before detailed correction begins.

Governance files to open first

See the full detail in the central artifact block

Useful evidence surfaces

These surfaces connect diagnosis, observation, fidelity, and audit.

See the full detail in the central evidence block

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.

Canon and identity#01

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.

Canon and identity#02

Identity lock

/identity.json

Identity file that bounds critical attributes and reduces biographical or professional collisions.

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.

Boundaries and exclusions#03

Registry of recurrent misinterpretations

/common-misinterpretations.json

Published list of already observed reading errors and the expected rectifications.

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.

Observability#04

Q-Ledger JSON

/.well-known/q-ledger.json

Machine-first journal of observations, baselines, and versioned gaps.

Observability#05

Q-Metrics JSON

/.well-known/q-metrics.json

Descriptive metrics surface for observing gaps, snapshots, and comparisons.

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.

01
Canon and scopeDefinitions canon
02
Response authorizationQ-Layer: response legitimacy
03
Weak observationQ-Ledger
04
Derived measurementQ-Metrics

Canonical foundation#01

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.

Legitimacy layer#02

Q-Layer: response legitimacy

/response-legitimacy.md

Surface that explains when to answer, when to suspend, and when to switch to legitimate non-response.

Makes provable: The legitimacy regime to apply before treating an output as receivable.
Does not prove: Neither that a given response actually followed this regime nor that an agent applied it at runtime.
Use when: When a page deals with authority, non-response, execution, or restraint.

Observation ledger#03

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.

Descriptive metrics#04

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.

Report schemaAudit report

IIP report schema

/iip-report.schema.json

Public interface for an interpretation integrity report: scope, metrics, and drift taxonomy.

Representation gap audit

This page captures a service-facing label. On this site, a “representation gap audit” designates a structured diagnosis of the gap between what an organization publishes and what AI systems understand, reconstruct, and repeat.

The label is intentionally readable for the market. It is then redistributed toward stricter objects: the canon-output gap, proof of fidelity, the authority boundary, and interpretive SEO.

What this entry point names on this site

A representation gap audit asks a question that looks simple and is demanding in practice:

what distance exists between the brand, offer, or entity as published, and the version that AI systems actually reconstruct?

That question may concern:

a badly bounded entity;
an offer extended beyond the canon;
a misattributed category;
a silently displaced hierarchy of authority;
insufficient stability across systems, prompts, or languages.

When this entry point becomes useful

The representation gap audit becomes especially useful when:

the brand is visible but poorly understood;
a third-party source defines the organization more strongly than the official site;
outputs remain plausible while distorting critical attributes;
corrections already applied have not reduced the gap with enough stability;
an AI Search Monitoring setup observes symptoms but no longer explains what actually governs the reconstruction.

When the official site reappears inside the answer without recovering the dominant category, comparison, or temporality, the audit naturally moves upward toward Exogenous governance and Official site visible vs structuring third parties in order to qualify the corrective work outside the strict canon.

What the audit actually examines

On this site, a representation gap audit does not stop at screenshots of answers.

At minimum, it examines:

the published canon and hierarchy of authorities;
the critical attributes that must be preserved;
the negations, exclusions, and boundaries that disappear under synthesis;
the third-party sources that frame or replace the official source;
the observed outputs across systems, phrasings, or windows;
the difference between citation, structural mobilization, fidelity, and stability.

In that sense, the audit often intersects with comparative audits, drift detection, and interpretive governance.

Typical outputs

A representation gap audit generally leads toward:

a map of critical gaps between canon and outputs;
a qualification of the dominant authority sources in each reconstruction;
a separation between local variation, stable drift, and framing substitution;
an order of priority between endogenous corrections and exogenous corrections;
a follow-up protocol to verify whether the gap is actually shrinking.

What this label does not replace

The representation gap audit does not replace:

an explicit canon;
a proof regime;
a governed comparison;
a correction strategy.

It is a diagnostic entry point. It makes the gap readable and governable. It does not claim, by itself, to stabilize reconstruction.

Doctrinal map

On this site, “representation gap audit” redistributes toward:

Back to the map: Expertise.

Phase 5 bridge: from monitoring to governed representation

Phase 5 adds dedicated definition surfaces for the market terms most often used before the deeper governance problem is named: AI search monitoring, AI citation tracking, GEO metrics, AI brand representation, and AI answer audit. These terms should be used to move from symptom observation to evidence, canon comparison, and correction.

Phase 13 routing layer: service audits and market entry points

Phase 13 adds a service-facing routing layer for audit demand: LLM visibility audit, AI answer audit, AI brand representation audit, representation gap audit, AI citation analysis, AI source mapping, comparative audits, drift detection, pre-launch semantic analysis, interpretive risk assessment, and independent reporting.

These terms should be treated as market entry points. They capture real demand, then route the work toward canon, source hierarchy, evidence, answer legitimacy, auditability, and correction resorption.

Phase 13 routing: market audit bridge

This expertise page now sits inside the phase 13 service-market bridge. When the incoming question is phrased as AI visibility, LLM visibility, ChatGPT visibility, citation tracking, GEO, recommendation or brand representation, route first through AI visibility audits and then choose the relevant audit surface.

The useful distinction is simple: market labels capture demand; canonical concepts govern interpretation. No audit label by itself promises ranking, citation, recommendation or third-party correction.

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.

Extension: LLM perception drift audit

This page should now be read with the LLM perception drift and AI perception drift cluster.

The issue is not only whether the brand appears in AI answers, but whether the generated representation remains faithful to the canon over time. A representation audit should therefore distinguish:

visibility without understanding
citation without fidelity
incorrect category
erased differentiators
persistent older version
displaced recommendability
divergence across models

The operational link is the LLM perception drift audit, supported by the AI perception baseline and the AI perception stability matrix.

Representation gap audit: service page