2026-10-29 — garden-bundle

The author wanted to talk with claude.ai about one note, with every related note in view, and asked how far the link walk should go. The 2026-09-01 pipeline already brings a conversation back into the vault (2026-09-01-conversation-ingest.md). This session built the outbound half.

PiecePath
The skill.claude/skills/garden-bundle/SKILL.md
The script.claude/skills/garden-bundle/scripts/bundle.py
Outputprivate/bundles/<seed-slug>-<date>.md, gitignored, outside the vault

The script imports the frontmatter and link parser from publish_audit.py, so the vault keeps one parser. It is read-only on the vault and refuses to write into it.

The depth question, answered with numbers

The first measurement was a plain breadth-first walk on the seed How will AI impact Software Engineering?. Depth 1 gave 33 notes. Depth 2 added 131 notes, and 60 of them were journal entries reached through hub notes such as Now.md. A plain walk at depth 2 is mostly noise.

Two rules fix that, and with them depth 2 is mostly on-topic atomic notes:

  1. The walk never expands through a journal entry or a hub. These notes link to everything, so they ship as excerpts and stop the walk.
  2. Excerpts come from the first hop only. A journal entry that links to a neighbour of the seed is about that neighbour, not the seed. The map counts such entries instead of shipping them.

With both rules, a sweep over all 308 notes in Notes/ and Inbox/ on 2026-10-29 gave these token sizes. The estimate is the character count divided by 4.

DepthMedianMaximum
12k61k
26k70k
314k70k

The maximum comes from a closed cluster of about 90 notes on one subject. So depth 2 became the default: every bundle fits in one conversation, and the second hop holds neighbours on the same theme. Past the last hop, the bundle lists the next ring by title, so the conversation can ask for a note by name. --plan prints the real number for any seed. Do not trust the table above after the vault grows.

Folder policy

A backlink from Notes/, Inbox/, Books/, Projects/ or Research/ ships whole. A backlink from Journal/, a vault-root file, misc/ or a folder index (a note named like its folder) ships as an excerpt. The first draft treated Projects/ and Research/ as hubs. The review showed that they hold topic notes, and that only their index notes are lists.

The review

Two agents, chosen for independent angles rather than for coverage:

  • Code correctness. It built 34 synthetic vaults in the scratchpad and ran the script against each one, so every finding came with a repro. It reported 18 findings.
  • Reader. It read the real bundle as the receiving model, and it searched the vault for related notes that the walk missed.

All findings were triaged inline, without a verifier tier: each code finding had a repro, and the fix was checked by running that repro again.

Fixed:

  • Lines inside code fences were read as headings, so a # comment in a bash block cut an excerpt and left an unclosed fence. Excerpts now ignore fenced lines and always ship a fence whole.
  • The output guard compared strings. A different letter case or a symlink wrote the bundle into the vault. It now compares real files with os.path.samefile.
  • The “left out” count missed backlinks to last-hop notes, and it counted journal notes that a shipped note links out to.
  • Multi-line %% comments, links qualified with a folder, [[Note\|label]] in tables, links in double-backtick code, and links to attachment types not in the image list.
  • Excerpt shape: lazy continuation lines, loose-list paragraphs, and two blocks joined into one paragraph.
  • --include lost the relation of a note that the walk had already reached.
  • --plan printed no totals.

Changed from the reader’s findings:

  • The cut marker was [...], which real notes use for quote elisions. It is now <cut/>.
  • The preamble said that every title in the file exists. Links to never-written notes inside the shipped notes made that false. The map now lists every never-written link target, and the preamble restricts the (existing) claim.
  • Notes now come in seed-link order rather than alphabetical order. Excerpts come last, and each note carries hop and modified.
  • A short parent bullet now ships with all its children, so a link in a list of experiments keeps its siblings.
  • The ring lists each title with every included note that reaches it, most connected first.

What the walk cannot see

The reader found strong related notes that have no link path to the seed. Several are orphans with no links at all. A link walk cannot reach them, so the skill has a step for them: grep the seed’s key terms, then propose --include candidates to the author. The walk shows only what the links show, and the links are the author’s own choices.

Open

  • A bullet whose parent wraps lazily onto a line at column 0 loses that parent in its excerpt. No case was found in the vault.
  • A note reached first as an excerpt stays an excerpt, even when a later hop links out to it. SKILL.md records this rule.
  • The bundle has not yet been used in a real claude.ai conversation. How well the receiving model uses the map and the (existing) rule is unverified.