Phantom URL: canonical definition

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
Weak observationQ-Ledger
03
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.

Observation ledger#02

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#03

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.

Phantom URL

A phantom URL is a non-existent URL that has never been published, is absent from known internal linking, the sitemap, editorial history, and declared routes, yet is requested in a form coherent enough with a site’s documentary architecture to reveal an expectation, projection, or plausible reconstruction of the corpus.

It is not merely an error page. It is an absent but structured surface, meaning a URL that does not exist in the real editorial system but resembles a page the site could have contained.

This definition distinguishes the phantom URL from a broken link, a deleted page, a hostile scan, or a migrated legacy route. The decisive criterion is not only non-existence. The decisive criterion is documentary plausibility.

Short definition

A phantom URL is a URL that has never existed but appears in logs or referrals under a form coherent with a site’s vocabulary, slug conventions, categories, or conceptual dependencies.

Full definition

A phantom URL appears when a system, agent, tool, AI-mediated user, or generative mechanism produces or tests a path that extends the published corpus without matching a real route.

It may be observed in different environments:

server logs;
CDN logs;
404 reports;
referrals from AI assistants;
agent crawls;
tool-assisted navigation traces;
URLs cited or suggested by a generative system.

The phenomenon does not automatically prove that a LLM directly crawled the site. It indicates that a plausible URL was produced, transmitted, tested, or requested in a context where the site’s structure became material for inference.

Minimum criteria

A URL should be qualified as phantom only if several conditions are met:

it has never been published in the CMS, repository, sitemap, or internal history;
it is not a deleted or migrated legacy page;
it does not come from a known broken internal link;
it is not reducible to an obvious technical scan;
it follows a plausible slug, category, or path convention;
it reuses vocabulary already present in the corpus;
it can be connected to an existing family of content, definitions, services, or doctrines;
it appears in an observable trace.

An isolated case may be interesting, but the audit value increases sharply when several phantom URLs belong to the same semantic cluster.

Difference from a classical 404

A classical 404 usually signals a break in the published reality: broken link, old page, missing redirect, typing mistake, missing asset, or migration error.

A phantom URL signals something else: a non-existent route expected by an external logic. The error does not necessarily come from the site. It may come from the way a system reconstructs what the site seems likely to contain.

The requested page is not only absent. It is absent in an interpretable way.

Difference from a phantom citation

A phantom citation concerns a displayed or implied source that does not exist, no longer exists, or does not support the cited claim.

A phantom URL concerns the path itself. It may become a phantom citation if used as a source in an answer. But not all phantom URLs are citations. Some are only access attempts, route projections, or architectural hypotheses.

What a phantom URL can reveal

A phantom URL may reveal:

a latent documentary surface;
an implicit conceptual dependency;
an incomplete editorial family;
a topological coherence deficit;
a zone where the corpus leaves too much room for inference;
an expectation of definition, method, clarification, or evidence;
a gap between the real architecture and the reconstructed architecture.

It does not necessarily mean that the page should be created. It means that the page has become possible inside the documentary space projected by an external system.

Evidence level

A phantom URL should be handled through a hierarchy of evidence:

Observable fact: the URL was requested.
Verified negative fact: the URL has never been published.
Structural coherence: the URL follows the site’s conventions.
Extrapolation hypothesis: the URL may result from documentary projection.
Doctrinal interpretation: the URL reveals a latent expectation.
Editorial decision: create, redirect, clarify, exclude, or monitor.

The discipline is to never jump directly from level 1 to level 6.

Usage rule

The term phantom URL should be reserved for cases where non-existence has been verified and documentary plausibility is sufficient. A random 404 is not a phantom URL. A forgotten legacy page is not a phantom URL. A route scanned by a hostile bot is not a phantom URL.

A phantom URL is an absence that has taken the form of a path.