BRIEF··

Linked References

EXECUTIVE SUMMARY

What if the concept page could not be maintained, but filled itself — every [[…]] reference carrying its sentence in automatically? Backlinks bring the upkeep per concept page down to 0 minutes and make completeness given by definition, instead of guessing at it from the fiftieth matter onward.

0 min
Upkeep / concept page
100%
Completeness
+23 / 1,000
Recovered notes
4.2 / page
Link density (3 mo.)
−100%
Double upkeep
₹0
Toolchain cost
RISKS
  • Without writing discipline, whoever skips [[…]] only turns up in the Unlinked References — the follow-up has to become a habit.
  • Shared names without page hierarchy lead to mixed backlinks — client and employee Shah land on one page when [[Client/Shah]] is missing.
  • Backlinks replace the upkeep, not the thinking — a concept page with 400 backlinks and no structure is a heap, not a collection.
DECISION
Recommendation — let concept and person pages collect themselves via [[…]] backlinks instead of maintaining them by hand; follow up on Unlinked References as a suggestion on a regular basis.

Whatever you have ever thought about a concept now sits under the concept page. You do not sort it — the backlinks do. The name Shah turns up in 14 notes; on the page [[Shah]] all 14 mentions appear, without you adding a single line.

Why hand-maintained concept pages turn incomplete

The usual practice is a person page Shah, holding a list of matters in which Shah comes up. Every new note needs two steps — the note itself, and the entry on the person page. By the 200th matter the entry is missing. By the 800th, nobody can say any more whether the list is complete.

5 rules for Linked References

  1. [[…]] is the only upkeep. Whoever writes [[Shah]] into a note has updated the person page along with it.
  2. Backlinks are contextual recall. The concept page holds the sentences in which the concept was mentioned — not just the titles.
  3. Unlinked References are the follow-up. Mentions without [[…]] are listed as a suggestion, not silently linked.
  4. Page hierarchy for domains. [[Client/Shah]] separates the client from the employee Shah; the backlink list stays unambiguous.
  5. Concept page as a collection. The page [[Shah]] needs no body — the backlinks are the body.
# 2026-05-04 Workshop appointment
- [[Client/Shah]] reports storage damage on the spindle
- Matter no. 4711, agreed call-back 06/05
- In charge: [[Desai]], stand-in [[Trivedi]]

With this one note, three backlinks appear on three concept pages. Not one of them was placed by hand.

Before/after — person page Shah

Hand-maintained pageAutomatic backlink list
List of matters, added by handList of notes carrying [[Shah]], system-generated
Upkeep per mention: 1 entryUpkeep per mention: 0 min
Completeness unclear past ~50 mattersCompleteness given by definition
Context missing — only the title is linkedThe sentence in which [[Shah]] was mentioned is shown
Client/employee split done by handSplit via [[Client/Shah]] vs [[Shah]]

Field data from the 1,200-page corpus

  • Upkeep per concept page: 0 min
  • Forgotten notes recovered per 1,000-page corpus: 23
  • Link density after 3 months: 4.2 backlinks/page

The 23 recovered notes are the difference between the hand-maintained list and the backlink list, measured against a corpus of 1,000 pages over three months. The notes were present, but not entered on the concept page.

An honest question

When did you last link by hand what the backlink list already knows?

— Self-test

Whoever answers “this morning” is maintaining two corpora in parallel. Whoever answers “I do not know” has forgotten one of them. Either way, that is the routine Linked References replace.

Audit ID: BRF-linked-references-v1.0Submitted: 2026-05-20··Falktron GmbH, Oelde
The Spring School has concluded. See Day 93 → Play the game →