README.md

@@ -1230,6 +1230,10 @@ the Development section below, and who ships a register the four above then draw
   every value names a row instead. A territory the register records no state for
   stands alone, which is `EH` alone, and naming one for it would be a claim
   fejkdata has no business making.
+- **`misc.tld` keys carry the leading dot, where other tables key on a bare code.**
+  The register spells a TLD `.se` and `misc.territory.tld` already ships it so, which a
+  bare key would make two spellings of one fact; `{/misc.tld}` also composes onto a
+  host with no separator. `misc.tld[se]` misses for it, which `todo.md` carries.
 - **`misc.tld` is a table of its own, and `misc.territory.tld` stays a column.** A
   `parent` demands a child for every parent row, so linking them would drop every root
   zone row naming no territory, which is most of them, and goal 10 holds a sourced

todo.md

@@ -110,7 +110,9 @@ by a `data-import/` script, as README goal 10 asks.
 - Name a spelling that works when a row selector misses: `misc.protocol[tcp]`,
   `misc.httpmethod[get]` and `misc.territory[se]` all answer "no row … has key or name"
   and stop there, where a case-insensitive match could name the row that exists, and a
-  table with no `name` column could say it selects by key alone.
+  table with no `name` column could say it selects by key alone. `misc.tld[se]` misses
+  on the leading dot its keys carry rather than on case, so the near miss is worth
+  naming whatever shape it takes.
 - Let a table column carry a `datatype`, so `--format json` writes
   `"safe": true` and `--format sql` a boolean rather than the text `'true'`. Today only
   a JSON field takes one, so `misc.httpmethod`'s booleans are typed in Go and text