Answer architecture round 1: a module's reads sits on its index entry or, for a source without an index, in the load that walks it, the note names default modules, the shipped modules are listed by name, datafiles drops its unused base, and item 195 files the builtins' second parse

2026-10-10 13:16:59 +02:00
parent e8b7d95559
commit 50e1a9fb22
14 changed files with 120 additions and 59 deletions
@@ -163,7 +163,8 @@ it to a name and read the name
 The shipped data comes in modules, each a Go package under [`data/`](data) that embeds
 its files, so nothing is read from disk: one per locale (`en_US`, `sv_SE`), one per
 country's tree of places (`geo/SE`, `geo/US`), and the locale-neutral `misc`. The CLI
-carries every module, and a library loads those it imports ([Library](#library)). A
+carries every module, and a library loads those it passes to `WithDataFS`
+([Library](#library)). A
 directory is a namespace: each JSON file is a category named after the file, each
 subdirectory a dot-path segment, so `mydata/sv_SE/person.json` is `sv_SE.person` and
 replaces the shipped one. A module's tree spells its namespace the same way, so