README.md

@@ -1341,7 +1341,7 @@ template.go     the {token} grammar: scanning, tokens, operands, validation, com
 hold.go         the hold: one draw per expansion for paths and operands, and the rows it pins
 holdfence.go    the load fences over the hold: the routes and spellings that read one held name two ways
 holdset.go      one reference draw per render and group: the hold set a render reads its paths through
-drawfence.go    the load fences over reference draws: the walk over a render's reads
+drawfence.go    the load fences over reference draws: the drawGroup fences, and the walk over a render's reads
 family.go       a family of linked tables: what a reference path reads of one, the rows a walk enters, and the fences over paths into it
 reference.go    reference sigils, and binding references across the tree
 graph.go        the node graph: tree walks, containment and render edges, and the cycle and repeat fences

todo.md

@@ -303,8 +303,8 @@ because pairing a street with its exact postnummer rewrites shipped rows.
 - Name the draw fences at one level in `doc.go`: the Vocabulary calls them `heldCheck`,
   `drawCheck` and `checkFamilies`, where `checkFamilies` runs under `drawCheck` beside
   `checkOwnFamily` and `checkColumnDraws`, which it names nowhere — so a reader looking
-  for the fence over a record's columns finds no entry reaching it. `holdfence.go` and
-  `drawfence.go` now index the fences by file, so deleting the sentence closes it too.
+  for the fence over a record's columns finds no entry reaching it. `holdfence.go`,
+  `drawfence.go` and `family.go` now index the fences by file, so deleting the sentence closes it too.
 - Cut `AGENTS.md` to the rules only it states: the round procedure stands word for word
   in `todo.md` and the `gh` rule opens with the README's GitHub decision, so each is a
   second copy that drifts. Split the comprehension rule while there, which packs the