dotfiles/obsidian/vault-round3-archive-and-relations-2026-08-19.md

name, description, type

name	description	type
obsidian-vault-round3-archive-and-relations-2026-08-19	Read-only round 3 — related's person-targets, Atlas of Roots context, what already distinguishes 99. Archive, and the search for the Chamber library-curation pattern-language document. Findings only.	reference

Round 3 — relations, Atlas of Roots, and what Archive already is

2026-08-19. Read-only. Nothing in the vault was changed. Findings only.

---

1 · related's person-targets — narrower than I implied

Every one of the 442 related targets was matched mechanically against a People index built from all 21 People notes and every identity string they answer to (filename stem, title, full_name, alias, aliases — 32 identity strings in total). No judgement about which "look like" people.

	count
resolves to a note, and matches a People note	5
resolves to a note, no People match	210
resolves to nothing, no People match	227

⚠ This corrects the impression I left in round 2. I reported that related carries "a third job — relating to a person rather than a document," generalising from Divorce.md's three targets. Run across the full set, the person-targets are those three and essentially nothing else. A person-name-shaped filter over the unresolvable targets returns 79 distinct strings, but almost all are title-case document names, not people: Presence Before Performance ×14, Pattern ×12, Practice ×12, Look Again, Limits Are Sacred, The Chamber Standard Protocol. The third job is real but rare — one note, not a pattern.

The three, individually:

target	status
Lune	⚠ A People note exists — 03. People/Lune Polymnie Marie Glidden.md — but its alias: is [Lulu]. The short name actually used in related is not among its registered identities, so the link fails on a note that is present.
Marie	No People note. She is declared elsewhere: Lune's own note carries family: [[Marie]], [[DFG]], [[Kai…|Kai]] — so Marie is a linked family member with no note behind the link.
Briac Prud'homme	No note, no reference anywhere else in the vault.

The source is 06. Projects/Divorce-transition/Divorce.md, whose related: is [Lune, Marie, Briac Prud'homme] — three bare strings, no wikilinks.

2 · Atlas of Roots — context only

09. Atlas of Roots/00. Atlas of Roots — Index.md — created 2025-09-29, mtime Sep 28 2025, and it appears in the mirror's history exactly once: first and last commit are the same sync. Untouched for ~11 months.

The section contains exactly one note — this index. Nothing was ever filed under it.

What it says about itself (verbatim):

A codex of places, people, and meanings that formed my roots. This work is both a vessel for grief and a durable inheritance for Kai and Lune.

Purpose — To codify grief into form: no longer carried loosely, but tended as lineage. To preserve roots in words, images, and rituals. To offer inheritance: not nostalgia, but living soil for Kai, Lune, and future descendants.

Its frontmatter carries status: living, version: 0.1.0, and next_review: 2026-01-15 — a review date seven months past.

⚠ Its own assurance.risk_flags name what happened to it: nostalgic distortion · isolation from Compass · unreviewed grief. And its stated assumptions include "Placement at top-level ensures visibility and prevents siloing." The note predicted its own failure mode in the same frontmatter block that has now sat unread for eleven months.

Its declared children:

declared	exists?
places/pine-street	no note anywhere
places/salmon-lake	no note anywhere
people/moy-glidden	exists elsewhere — 03. People/Moy Glidden.md
people/abg	no note under that name (03. People/Arthur Boyntin Glidden Jr..md exists)
GLOSSARY.md (peer)	exists elsewhere — …/Animal Rationis Capax/docs/context/GLOSSARY.md.md

Its own canonical: 09. Atlas of Roots/index.md points at a filename that does not exist; the note is 00. Atlas of Roots — Index.md.

Inbound: exactly two non-Atlas notes mention "Atlas of Roots", and both are in 99. Archive/99. chatgpt-conversations/ — one of them dated 2025-09-28, the conversation from which it was conceived. No live note in the working vault links to it.

3 · What already distinguishes 99. Archive (1,070 notes, 42% of the vault)

3a · Frontmatter presence

	with frontmatter
Archive	120 / 1,070	11%
non-Archive	668 / 1,449	46%

3b · ⚠ canonical's pointer form is NOT concentrated in Archive — the hypothesis tests negative

	self-descriptive	pointer-elsewhere	bool flag	total
Archive	8	2	0	10
non-Archive	83	65	3	151

65 of the 67 pointer-form instances are outside Archive. If "the current version lives elsewhere" were already functioning as an archival marker, the pointers would cluster in Archive. They do the opposite.

The finding this does support is narrower and, if anything, more useful: 65 notes sitting in the live vault declare that their live version is somewhere else, and none of them was moved. The declaration exists; it has never been acted on. Whether that makes it a latent archival signal or merely an unmaintained field is not something this check can settle — but it is not currently doing archival work, because the population it marks is precisely the population that was left in place.

3c · status

Archive (32 of 1,070 carry status — 3%)		non-Archive (273 carry it)
archived	25	active	97
Active	5	living	71
active	2	canonical	20
		draft	13
		in_progress / stable / private / exploratory — pre-proposal / pointer / complete	4–6 each

status: archived exists and is used on 25 notes — 2.3% of the Archive. No note outside Archive carries it. Seven notes inside Archive still declare themselves Active/active, in two capitalisations.

3d · Inbound links — do archived notes go quiet?

Counting wikilinks from non-Archive notes into Archive notes:

• 97 of 1,449 live notes contain at least one link into Archive.
• 105 of 1,070 Archive notes (9%) receive such a link.
• 965 Archive notes (90%) receive no wikilink from any live note.

The 9% that stay linked are concentrated: 06. Projects/…/03. GPT-Archeologist alone accounts for 39 links, then 07. Learn/Reading/00. Master_Reading_Index (10), Lune — Updates Log (7), 03. People/DFG (5), and the two vault indexes (5 each).

3e · An existing archival policy note

None found. No note in the vault states an archival rule, criterion, or policy. Searched by filename and by content across the whole vault.

4 · ⚠ The Chamber library-curation pattern-language document does not exist

Searched ~/_Dev/chamber-library, ~/_Dev/studium-engine, ~/_Dev/animal-davidglidden-eu, ~/_Dev/CapableMind-AI and the whole vault, by filename and by content, including a search for Alexander's pattern form (a **Therefore** invariant clause) applied to curation. The two hits for that form are ordinary prose.

Three real things exist that the name could be resolving to, and they are different from each other:

1. Christopher Alexander's books are chamber library SOURCES — canonical_texts/traditions/contemporary_voices/environmental/a-pattern-language-christopher-alexander.md and …/The_Timeless_Way_of_Building/the-timeless-way-of-building.md, catalogued as title: A Pattern Language · author: Christopher Alexander. PENDING-146's "Pattern 26's bold invariant slot" refers to this — Alexander's book as a text under citation, not to a framework for curating the library.
2. Pattern, Presence, Practice (P3) — 177 notes in 06. Projects/, the steward's own pattern language, explicitly "inspired by Christopher Alexander's The Timeless Way of Building" and Zehetmair's Systematische Violintechnik. Its subject is violin pedagogy — "a way to think, feel, and teach music through pattern languages, dimensional awareness, and symbolic gesture." It is Alexander-modelled and it is a real framework; it is not a Chamber document and not about curation.
3. ARC chamber-generated essays about Alexander — e.g. content/chamber/canon/chamber-generated/alexander-pattern-languages-minds.md. These are outputs of the Chamber, not frameworks for it.

The Chamber's own governing documents are of a different kind entirely: Vision & Charters (Hermetic, Editorial, Epistemic; The Chamber — Complete Living Amphitheatre V2.1) and Schemas & Protocols (first-light / standard / shadow). None is a pattern language.

Nothing was substituted. Naming the closest candidates is not the same as relaying the requested document, and the request was specific enough that the difference matters.

---

Findings only. Nothing proposed, nothing decided, nothing changed.