 lilleman
|
590681ed24
|
Answer stability and product-owner: New's godoc says where the load lands, plainer Performance wording, regenerate before re-pinning, and no redundant sort
|
2026-10-03 20:37:07 +02:00 |
|
|
lilleman
|
cc8797744b
|
Answer architecture round 3: the generated header names go generate, one sorted-keys helper everywhere, one site constructor, and an inline folder reference refused before anything loads
|
2026-10-03 20:37:07 +02:00 |
|
|
lilleman
|
3bb8628e39
|
Answer architecture round 2: one folder walk and one sorted-keys helper, REGENERATE for the index, and the held decisions naming the items that end them
|
2026-10-03 20:37:07 +02:00 |
|
|
lilleman
|
c3b462ec0a
|
Answer architecture round 1: one inline load-and-bind, go generate for the index, sorted unloaded names, item 79 named in the decision, and the audit's other findings filed
|
2026-10-03 20:37:07 +02:00 |
|
|
lilleman
|
8b3bbc4003
|
Load shipped categories before binding, panic on an index that misses a read, and name the index entry and unloaded category plainly
|
2026-10-03 20:37:07 +02:00 |
|
|
lilleman
|
5667cd5dc3
|
Load a shipped category on the first call reaching it, from an index generated from data/
|
2026-10-03 20:37:07 +02:00 |
|