Read-only. Nothing in the vault changed.
The canonical-as-archival-signal hypothesis tests NEGATIVE: 65 of the 67
pointer-form instances sit OUTSIDE Archive, 2 inside. If "the live version is
elsewhere" were functioning as an archival marker the pointers would cluster in
Archive; they do the opposite. What it does support is narrower — 65 notes in
the live vault declare their live version is somewhere else and none was moved.
Archive, measured: 11% frontmatter vs 46% outside; status:archived used on 25
notes, 2.3% of the Archive, with 7 archived notes still declaring themselves
Active; 90% of Archive notes receive no wikilink from any live note, and the 9%
that stay linked are concentrated in six notes. No archival policy note exists
anywhere in the vault.
related's person-targets are 3, not a pattern — correcting round 2, where I
generalised from Divorce.md. Lune has a People note whose registered alias is
Lulu, so the short name actually used does not resolve; Marie is linked from
Lune's family field with no note behind it; Briac Prud'homme appears nowhere.
Atlas of Roots: one note, untouched 11 months, next_review 7 months past, two
of four declared children never created, and inbound mentions only from the
archived ChatGPT conversation that conceived it. Its own risk_flags name
"isolation from Compass".
The Chamber library-curation pattern-language document does not exist. Three
real things could be resolving to that name — Alexander's books as chamber
SOURCES, the 177-note Pattern Presence Practice violin-pedagogy framework, and
ARC's chamber-generated essays about Alexander. Nothing substituted.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
owner: 3 distinct values across 153 notes, all one person spelled three ways —
the opposite shape to canonical, less than its count suggested, not more.
change_log: 38 empty / 51 real, and the real half carries FOUR incompatible
entry schemas plus one malformed instance where the date became the key.
related: 48% of 442 targets resolve by name, 47% unresolvable — and 385 of 442
are bare strings rather than wikilinks, so ~87% produce no clickable relation
whatever they resolve to. Some targets are people who have no note.
links: six dict schemas, and it carries sub-keys canonical and related that
duplicate two top-level governance fields. 31% unresolvable — a first pass
without an alias/title tier said 57%, the same resolver-too-strict error as this
morning's canonical number, caught before quoting this time.
Also relayed: a faithful section-by-section account of AldineXXI's OPERATIVE
frontmatter specification, including its W1.12 prune of four unread fields and
its §3 translation table, which rules by name on canonical, assurance,
change_log, author, version, type, status, tags and review_cycle.
Findings only. Nothing proposed, nothing decided, nothing changed in the vault.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
At the jurist's request. Nothing changed in the vault.
canonical is the substantive one: 157 path-like / 3 boolean / 1 pointing at a
non-markdown file, and the path-like set splits 91 self-descriptive ('I am
canonical, here') against 66 pointers ('canonical is over there') — two large
jobs that are not variants of each other.
Pointer integrity, tested at four strictnesses: 6 correct as written, 88 stale
paths to notes that still exist, 63 naming nothing. This corrects the executor's
own earlier '151 do not resolve', which was right about paths and wrong about
notes — the field is stale, not dead.
Also: the 8 assurance strings (7 high / 1 medium, 5 of them one Reading cluster,
and evidence_level has no slot for a confidence scale); the prose tag, which is
a scope disclaimer on a note carrying no tags key at all; and the three pairs —
domains/domain is one thing inconsistently typed, periods/period is two things,
and linked_note's nearest neighbour is linked_daily_note, not linked_notes.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Every .md parsed (2,519 files, no sampling), parser carrying four controls.
400 distinct keys over 5,867 instances; 68% of notes have no frontmatter at all.
Consumption cross-referenced against 357 dataview/tasks blocks, 23 templates
and all 39 .obsidian configs: 66 keys consumed (62% of instances), 29 written
by template and read by nothing, 305 orphaned. The Compass governance block —
canonical/owner/assurance/change_log/links/related — is in the written-not-read
set on 67-161 notes each.
Method correction recorded in the report: the first template pass matched key
names anywhere in a file containing Templater syntax, which tests whether the
word occurs in prose rather than whether a template writes the key. Redone
against each template's own frontmatter block.
Inventory only — no proposed schema, per the brief.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
