Live-tree restructure reference, four-column effects index, sensitivity-shelf template (field-tested)

[micahvv]

What this method needed after a full home-directory restructure across a dozen repositories and
several agent accounts, four repository system maps, and a nightly drift report — done with the
tree in use throughout.

references/live-tree-restructure.md (new). Restructure mode assumes you can move a file and
then check the result. On a live tree the failures are silent — a scheduled job whose input moved
reports success on an empty set. The reference covers what we actually did: a census before any
design (who has the tree open, every working copy mapped to its parent repo, every
credential-shaped name recorded and never opened, what runs on a schedule); moving the method's
own corpus first; a consumers register where any task writing a path a later phase renames appends
a row, and a phase closes only when every row is DONE or explicitly re-registered; one guarded move
primitive that halts rather than guess; the gates; the worktree convention; the grep gate for
shared repositories; the drift report that catches the decay.

references/system-map.md — four amendments, each from something that failed in the field:

• The change-impact index is a FOUR-column table. A three-column index cannot answer the walk
  test's own step 4, which asks for hits AND does-not-hit.
• Every link in an authored map file resolves. A noun with no card links its own _index.md line
  via an anchor and reads (stub). Mechanical existence check over the diff, before every commit.
• New "Generated nodes" section. A committed generated graph's built-at is by construction the
  PARENT of the commit that adds it, so sha equality can never mean "current" once a map lands;
  every consumer testing it that way calls every real map stale, forever. Record a content hash of
  the parsed source set beside the graph and test currency by content.
• The walk test's token band counts the entry file's inserted section, not the whole entry file. A
  15k-token house-rules book is out of the map's scope; record it as an observation.

Two templates: the four-column effects-CONTEXT.md, and private-shelf-CONTEXT.md for a
workspace with a sensitivity shelf (tiered, with a load rule an agent can follow).

No scripts and no dependencies. We run a graph generator and two hooks behind this, but they are
Node and Python with a lockfile; the reference is written so the method stands without them.