lilleman
|
2132bde2ba
|
Record the shares, the capitals' source and the measured cost, and close items 199 and 200
|
2026-10-11 19:13:48 +02:00 |
|
lilleman
|
7f5a0cb63c
|
Answer prose round 1: one name for a place holding most of a postal code's land, the decision leaves the seeding to the code, and the test says what it checks
|
2026-10-11 16:42:23 +02:00 |
|
lilleman
|
9360447254
|
Answer stability round 2: the test names a missing population column
|
2026-10-11 16:42:23 +02:00 |
|
lilleman
|
66b5d699fa
|
Answer stability round 1: each US place's draw is seeded by its GEOID, so a changed source moves only the places near the cut; item 78 leaves the plan and the multi-county fetch is filed
|
2026-10-11 16:42:23 +02:00 |
|
lilleman
|
63a7ac156e
|
Record the reading cost of the last chunk and refresh item 167
|
2026-10-11 16:42:23 +02:00 |
|
lilleman
|
5db699469b
|
Record the shipped places and streets as a decision, and say so in the README and changelog
|
2026-10-11 16:42:23 +02:00 |
|
lilleman
|
2f8fffd237
|
Record the maintainer's decision to ship item 182 over the ruling at a632a92 with Shape fallen, and file item 197 to replace the namespace mount
|
2026-10-11 16:02:48 +02:00 |
|
lilleman
|
33ddb49127
|
Answer architecture round 12: the namespace mount serves what a walk asks of a tree, a folder's entries and a file's bytes, so the folders above it need no file of their own
|
2026-10-11 16:02:48 +02:00 |
|
lilleman
|
d157e4526a
|
Answer architecture round 10: the paired ruling at fb2c809 is better; a mounted module names its manifest from its files' root, and the mount wrapper returns nothing beside an error
|
2026-10-11 16:02:48 +02:00 |
|
lilleman
|
d242466859
|
Answer architecture round 9: each data package exports Modules, a locale's importing its country's geo package as a bench chose, and a namespace mounts a tree through an fs.FS wrapper, so internal/datafiles walks file-system folders alone
|
2026-10-11 16:02:48 +02:00 |
|
lilleman
|
203486a9d3
|
Answer architecture round 8: a shipped package's folder spells its namespace (data/sv_SE, data/geo/SE) under its lowered Go name, as a second bench chose, a mounted root folder reads as its namespace, and item 196 cites goal 9.2
|
2026-10-11 16:02:48 +02:00 |
|
lilleman
|
cc1c3bbc7d
|
Answer architecture round 7: reads and its note move to item 196, a mounted module's errors read sv_SE (address.json), internal/datafiles handles namespace folders in one form, and a folder outside the mount is a broken invariant
|
2026-10-11 16:02:48 +02:00 |
|
lilleman
|
89cafb1a21
|
Answer architecture round 6: a manifest's reads names namespaces, loadReached notes only those nothing loaded provides, a mounted module labels its files by its namespace, Source.Load checks its mount, and the README keeps namespace and reads in an edited copy
|
2026-10-11 16:02:48 +02:00 |
|
lilleman
|
7b70530a8a
|
Answer architecture round 5: the shipped packages are enus, svse, geose, geous and misc, each holding its files at its root under its manifest's namespace, and the errors use the wording a bench of the Audience chose
|
2026-10-11 16:02:48 +02:00 |
|
lilleman
|
7f7d260f83
|
Answer prose round 1: errNoData, the reads paragraph and the changelog entry read in one pass, the Library section shows the import block for one locale, and the decisions state why New checks no reads and which goal the embed serves
|
2026-10-11 16:02:48 +02:00 |
|
lilleman
|
949d2709da
|
Answer architecture round 3: the paired ruling at 70e552c against bf1becb is same
|
2026-10-11 16:02:48 +02:00 |
|
lilleman
|
3da487f8ea
|
Answer architecture round 2: each category site carries its source's default modules, set where the walk or the index loads it, and the note is written beside the resolve that finds the read; the decision states why New checks no reads
|
2026-10-11 16:02:48 +02:00 |
|
lilleman
|
50e1a9fb22
|
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-11 16:02:48 +02:00 |
|
lilleman
|
d79be8b50a
|
Record the reading cost of the last chunk, and refresh item 167's figures
|
2026-10-11 16:02:48 +02:00 |
|
lilleman
|
b8eba1eb35
|
Ship en_US, sv_SE, misc, geo/SE and geo/US as Go packages exporting FS, listed by data.Modules(), and fail a bare New naming WithDataFS
|
2026-10-11 16:02:48 +02:00 |
|
lilleman
|
bf1becbb59
|
Rescore: the paired ruling at b77ec94 against 2652779 is better
|
2026-10-10 11:24:32 +02:00 |
|
lilleman
|
13e3de39fe
|
Answer product-owner round 1: the parent error and the README name the way to link under another source's table, a missing indexed file names the manifest, the README warns a copied data/ carries its index, and the docs say what a load failure and a replacement do
|
2026-10-10 11:24:32 +02:00 |
|
lilleman
|
a6d9623383
|
Record the paired ruling at d34cc42, move jsonKind's comment onto Kind, name the manifest in Layout, and note the normalised manifest in item 185
|
2026-10-10 11:24:32 +02:00 |
|
lilleman
|
55d503317d
|
Answer architecture round 3: New loads only sources without an index and what they read, an entry drops reads, ErrLoad sits beside New, the manifest decoder moves to manifest.go and names each mistake once as jsonvalue.Kind words it
|
2026-10-10 11:24:32 +02:00 |
|
lilleman
|
aafcbd9025
|
Record the paired ruling at 0bdb100, and mark item 194 as the decision log cites it
|
2026-10-10 11:24:32 +02:00 |
|
lilleman
|
498f81075e
|
Answer architecture round 2: a first reach checks only a table's parent, loadReached splits into a batch that loads, runs and puts back, the manifest decodes strictly and reports every mistake, and ErrLoad marks a load failing in New too
|
2026-10-10 11:24:32 +02:00 |
|
lilleman
|
c783d4af23
|
Answer architecture round 1: one owner keeps a folder's loaded and unloaded names apart, each loaded category is checked against its index entry, addSource returns what it replaced, the manifest cache goes, ErrLoad exits 1, and the docs say what New and Fake now refuse
|
2026-10-10 11:24:32 +02:00 |
|
lilleman
|
2e56af5d63
|
Record the reading cost of the last chunk
|
2026-10-10 11:24:32 +02:00 |
|
lilleman
|
c320344fac
|
Load each category of a source whose manifest carries an index on first reach, and move the shipped index into data/.fejkdata.json
|
2026-10-10 11:24:32 +02:00 |
|
lilleman
|
8d309cd827
|
Rescore: the paired ruling at 8b5a972 against 2652779 is the same
|
2026-10-09 18:57:01 +02:00 |
|
lilleman
|
f663e1af1e
|
Record the maintainer's answers: a manifest names no fejkdata version and item 183 goes, and the shipped data is held under 100 MiB by item 192, past which item 193 carves out Go modules
|
2026-10-09 18:57:01 +02:00 |
|
lilleman
|
687a3d37bf
|
Answer prose round 1: module means fejkdata's unit and Go module the Go one, only anyone else's manifest names a version, goal 2.3 says a program links what it imports, and a carved-out module requires the core release that drops its package
|
2026-10-09 18:57:01 +02:00 |
|
lilleman
|
22ca7caa40
|
Record the reading cost of the last chunk
|
2026-10-09 18:57:01 +02:00 |
|
lilleman
|
3e12849f65
|
Ship the data as Go packages in the core's module: goal 2.3 and the shipped-data decision say packages, item 179 goes, items 180 to 186 follow, and item 191 files the release tag-guard bug
|
2026-10-09 18:57:01 +02:00 |
|
lilleman
|
b08b3e94d5
|
Answer prose round 1: the exact-match reason reads one idea a sentence, and item 180 says its goal-13 effect once
|
2026-10-09 15:00:50 +02:00 |
|
lilleman
|
c597d0a2e0
|
Record the maintainer's answers: an exact version match, goal 6.3 for modules that load on first reach, and items 79 and 54 folded into items 180 and 179
|
2026-10-09 15:00:50 +02:00 |
|
lilleman
|
24a30161f7
|
Answer prose round 1: the decision keeps only what the goals leave open, and the new items' taglines read once
|
2026-10-09 14:43:13 +02:00 |
|
lilleman
|
65ccc132ae
|
Record the reading cost of the last chunk
|
2026-10-09 14:43:13 +02:00 |
|
lilleman
|
9558472c96
|
Split item 77 into items 179 to 189, and record its module decision in docs/decisions.md
|
2026-10-09 14:43:13 +02:00 |
|
lilleman
|
fa734fda3c
|
Answer prose round 1: AGENTS.md names the paired ruling as what still blocks a 0.1.0 merge, item 107 promises what item 178 plans, and the floor entry says one thing a sentence
|
2026-10-09 14:14:59 +02:00 |
|
lilleman
|
30a4445a47
|
Ship 0.1.0 under the comprehension floor, drop item 176, and plan item 107 for 0.2.0 behind an architect's plan for grouping and untangling the engine
|
2026-10-09 14:14:59 +02:00 |
|
lilleman
|
265277953c
|
Rescore: the paired ruling at 344023d against 1c342bc is better
|
2026-10-09 13:11:50 +02:00 |
|
lilleman
|
edec28f58f
|
Answer prose round 1: the Data paragraph names the set first, the choice comment says what shared counts, and the plan's new items read once
|
2026-10-09 13:11:50 +02:00 |
|
lilleman
|
3d62683c69
|
Move the scoring runs of ad59967 and b9d1af6 into the comprehension history
|
2026-10-09 13:11:50 +02:00 |
|
lilleman
|
f30bdc1380
|
Record the reading cost of the chunk before item 153
|
2026-10-09 13:11:50 +02:00 |
|
lilleman
|
5d85944359
|
Record the 2026-10-09 panel's scores, file what it named as items 170 to 177, and correct four claims it found false
|
2026-10-09 13:11:50 +02:00 |
|
lilleman
|
51c0bd518e
|
Record the reading cost of the chunk before item 151
|
2026-10-09 12:43:20 +02:00 |
|
lilleman
|
1c342bc2af
|
Rescore: the paired ruling at 8433689 against d74c0ed is better
|
2026-10-09 12:35:12 +02:00 |
|
lilleman
|
b49e0cac6e
|
Rescore: the paired ruling at c27e8b7 against d74c0ed is better
|
2026-10-09 12:35:12 +02:00 |
|
lilleman
|
4f369b961c
|
Record the reading cost, and refresh item 167's figures
|
2026-10-09 12:35:12 +02:00 |
|