Linting the Graph: Orphans, Dead Links, Ungrounded
Quotes
2026-09-24
Linting
the Graph: Orphans, Dead Links, Ungrounded Quotes
“Information becomes geometry, geometry becomes art.” — SECTOR9 North
Star, PUBLIC brand voice
🔓 PUBLIC — A
clean folder is not a healthy graph
clean folder is not a healthy graph
A knowledge base can look immaculate and still be failing. The files
may sit in sensible folders, carry consistent names, and fill every
template field. Yet three questions remain hidden: Which pages can
nobody reach? Which references point to targets that no longer exist?
Which quotations have no traceable source?
A folder helps a human browse. A graph makes relationships explicit.
An orphan page has no inbound relationship. A dead link promises a path
to a page that does not exist. An ungrounded quote presents borrowed
language without a resolvable source. Each failure is measurable and
repairable.
Graph linting is therefore an integrity layer, not occasional
housekeeping. A knowledge operating system is self-improving only when
new pages strengthen the record instead of multiplying isolation, broken
promises, and unattributed authority.
🔓
PUBLIC — Orphans: real knowledge with no route into context
PUBLIC — Orphans: real knowledge with no route into context
An orphan is a page with zero inbound links from other pages. The
page may contain a valuable concept or a precise operational record, yet
a reader following the graph cannot discover it naturally. Search may
still find the file, but search is not an authored route into
context.
Orphans usually emerge when content migrates, a large note is split,
or a research thread is interrupted before backlinks are added. The file
survives; its place in the corpus does not. Repeated later in another
author’s words, it becomes duplicated authority.
Do not solve the report by deleting every zero. Triage first. Link a
page that belongs in the active topology. Merge a duplicate into the
canonical record while preserving source history. Archive stale work. A
deliberate exception—such as a raw source capture—should declare its
role rather than masquerade as an unexplained orphan.
The useful metric is not the smallest possible count. It is the share
of intentional pages that are reachable from an entry point. Quiet pages
can remain quiet if their status is explicit. Invisible work cannot be
governed.
🔓 PUBLIC —
Dead links: promises the graph cannot keep
Dead links: promises the graph cannot keep
A dead link is an edge whose target cannot be resolved. The failure
is easy to underestimate because the text still reads smoothly. The
citation looks complete, the navigation label useful, and the author
intended a real path. The graph, however, cannot follow it.
Three causes recur. Naming drift creates targets such as
Self-Improving Knowledge Base,
self_improving_kb, and the canonical
self-improving-knowledge-base as if they were
interchangeable. Renames and merges leave inbound references behind.
Manual links point outside the managed graph, where existence is
assumed, not verified.
Repair begins at the source of the edge. Correct naming drift to the
canonical identifier. After a merge, update every inbound reference in
the same change. Convert a missing concept into a real page or an
explicit unresolved item; do not fabricate a target merely to turn the
count green. The linter should report the referring page, target,
location, and proposed action so a maintainer can repair rather than
guess.
A zero dead-link count can be theater if targets are empty shells. A
linter must check useful resolution, not merely matching filenames.
🔓
PUBLIC — Ungrounded quotes: language the system cannot update
PUBLIC — Ungrounded quotes: language the system cannot update
An ungrounded quote is text presented as a citation, excerpt, or
attributed claim without a machine-readable path to an authoritative
source. It may be accurate, stale, truncated, or reconstructed from
memory. The graph cannot tell which. Accuracy is a claim; provenance
makes it inspectable.
The standard check is small: a source field points to an existing
source record, and the body preserves the exact excerpt with resolvable
attribution. If a quote comes from a meeting transcript, paper,
interview, or internal record, that record needs a stable identity. A
plaintext filename is not enough when it can drift or disappear.
This is where “transcription is the first act of power” becomes
operational. Capture the exact words, record where they came from, and
preserve how they may be updated. When the source changes, the system
should identify every downstream claim. Without that path, a quotation
can survive after its context has disappeared.
The safe repair is not to delete an inconvenient citation. Trace it,
qualify it, or replace it with the author’s own statement. If no source
exists, label the sentence as interpretation rather than present it as
borrowed evidence.
🔓 PUBLIC — One
lint pass, three different repairs
lint pass, three different repairs
A useful report separates detection from policy. The scanner says
what is wrong. The operator decides what should happen.
- Orphans: link, merge, archive, or mark
intentional. - Dead links: correct the target, restore a missing
record, or mark the reference unresolved. - Ungrounded quotes: attach a source, qualify the
claim, or rewrite it as original analysis.
The same scan can also check index completeness, required
frontmatter, stale source records, duplicate pages, and unresolved
terminology. The goal is not a clean-looking graph. The goal is truthful
relationships.
Severity should follow consequence. A broken navigation link deserves
faster repair than an archived historical reference. A single-source
quote deserves confidence labeling; a public decision deserves a
complete source chain. Lint output becomes useful only when it helps a
maintainer choose the next action.
🔓 PUBLIC —
Baselines, deltas, and regression gates
Baselines, deltas, and regression gates
Absolute counts are snapshots; trends show whether a knowledge system
is healing. Save each report, compare it with the previous scan, and
label new findings, resolved findings, and unchanged debt separately. A
rising count after adding pages may reflect better detection; a falling
count after a migration may hide a broken index. Context belongs beside
the metric.
Run the linter on a cadence and after high-risk changes: bulk
imports, renames, schema changes, model-assisted rewrites, and publish
operations. Make the scan reproducible. A healthy report identifies the
corpus, rules, timestamp, scanner version, and exceptions.
The strongest gate is incremental. A new page must enter the index,
connect to relevant nodes, and carry valid frontmatter before
publication. A rename must update inbound edges in the same change. A
source-backed quotation must resolve before it enters the public corpus.
Catching drift at the boundary is cheaper than rebuilding trust after
the error compounds.
This is continuity, not perfection. The North Star says everything is
a record. A lint report turns graph health into a record that the next
author—and the next agent—can inherit.
🔓 PUBLIC — Make
integrity part of the publish loop
integrity part of the publish loop
A linted knowledge base reduces broken navigation and gives agents a
safer reading surface. It also gives writers a clearer account of what
the system actually knows. Vague maintenance becomes a sequence: detect,
classify, repair, verify, record.
The minimum useful loop is straightforward:
- Scan every managed page and edge.
- Report orphans, unresolved targets, and unattributed quotations with
locations. - Triage each finding under an explicit policy.
- Apply the smallest repair that restores the intended
relationship. - Run the linter again and preserve the before-and-after record.
- Fail the publish boundary when a new page introduces unresolved
structure.
The graph will still grow. Perfection is not the goal. The goal is a
system that tells the truth about its own state.
A knowledge base without linting eventually claims connections it
does not have, points to pages it cannot reach, and repeats language it
cannot source. A linted graph makes those failures visible, repairable,
and less likely to compound. Scan the nodes. Walk the edges. Ground the
words. Then let the record carry the lesson forward.
🔓 PUBLIC — Relationships
- [[self-improving-knowledge-base]] — provides the long-term knowledge
layer - [[orphan-pages]] — defines the zero-inbound-link failure
- [[dead-links]] — defines unresolved graph edges
- [[ungrounded-quotes]] — defines unattributed evidence
- [[wiki-lint-report]] — records the scan and its trend
- [[council-vault]] — provides the maintained corpus
