The steward asked for links between the week's daily notes, weekly and monthly
ids, and rollups that show progress. Three of those already existed in the vault
and had lapsed: 01. Weekly/2025-W15..W21 (7 notes, ISO YYYY-Www), 02. Monthly/
2025.05 (dots, not dashes), a quarterly, and templates for all of them. The old
daily template already carried week: gggg-[W]WW and month: YYYY-MM fields.
So nothing here is invented. The hook now writes his week/month frontmatter and
creates the week and month notes in his folders, in his filename formats.
LINK UPWARD ONLY, and this is the load-bearing design decision. An unresolved-
link census of the vault the same day found 4,799 unresolved targets across
1,366 distinct names, with 56% of notes carrying no link in or out. A nav line
with a "tomorrow" link manufactures ~365 more unresolved links a year, and a
weekly note hard-linking its seven days manufactures ~5 a week for days that
never happened. So: the week note always resolves because the hook creates it;
Previous is written only when yesterday's note actually exists on disk; tomorrow
is never written; and the weekly note hard-links no dailies at all — the dailies
link up, so Obsidian's backlinks pane lists exactly the days that exist.
Two controls carry that: Previous appears when yesterday exists, and is absent in
a fresh directory — proving the check reads the disk rather than the calendar.
The weekly note carries a Work heading and keeps a Personal review heading. The
2025 weekly practice was personal — intentions, patterns, task migration — and
the work rollup sits beside it under its own heading rather than displacing it,
which is the same instruction the steward gave for the daily note.
17 selftest checks, up from 7.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JQKeKY9T9d95KpvHwwok8T
