Commit Graph

931 Commits

Author SHA1 Message Date
lilleman 1bd9f58e56 Answer prose round 2 and product-owner round 2: the error shows the spelling to write instead, item 14 only respells the shipped runs, and the key decision says how a code serves goal 5.5 2026-10-05 07:55:01 +02:00
lilleman 2bdbb22499 Say why item 14's repeat over {digits(1)} changes nothing 2026-10-05 07:55:01 +02:00
lilleman 03577ebca2 Answer prose round 1 and product-owner round 1: give goal 5.7 a test a reader can apply, drop the AGENTS.md copy of it, and cite the key decision to goal 5.5 2026-10-05 07:55:01 +02:00
lilleman 0130a46ced Refuse only a spelling that restates another, and drop item 93 2026-10-05 07:55:01 +02:00
lilleman dc9776061c Answer stability round 2, product-owner round 2 and prose round 2: state the calc exception in the Names list without an example that loads either way, and one reading for item 93 2026-10-05 01:23:55 +02:00
lilleman 426517e66d Answer stability round 1, product-owner round 1 and prose round 1: say calc reads names in the Functions table, use shipped data in the examples, plainer comments and item wording, mark items 5 and 90 as decision-cited, and ask whether a field spelling of a calc operand is refused 2026-10-05 01:23:55 +02:00
lilleman 0743a049d7 Answer architecture round 2: refuse by default where a builtin's operand can be a reference, test the flag against each operand grammar, drop a duplicate test, rename allNeverNumeric, rewrap Computation, and order item 91 after item 4 2026-10-05 01:23:55 +02:00
lilleman 94cf741706 Answer architecture round 1: exempt only a calc operand from the read-once refusal, run the name passes from one list, read every operand's leaves, show a name operand in a README example, and plan a path through a name as an operand 2026-10-05 01:23:55 +02:00
lilleman d1b3b05a0c Close item 71, and suspend scoring for items 4 and 90 2026-10-05 01:23:55 +02:00
lilleman b4052f77f9 Accept a name as a calc operand 2026-10-05 01:23:55 +02:00
lilleman 3d320e029c Test that a calc reads a name as an operand 2026-10-05 01:23:55 +02:00
lilleman 19cbbe56f6 Answer prose round 1: show binding a selected sex, split the test-series paragraph, give the birth-number layout both reasons, and say which item the round leaves 2026-10-05 00:50:23 +02:00
lilleman 60b3cb20ca Answer product-owner round 1: show reading a name and a personnummer through one bound sex, say what the locale address prints, and plan the record's one pick in item 4 2026-10-05 00:50:23 +02:00
lilleman b93d47eeb2 Answer stability round 2: let the selector be the assertion 2026-10-05 00:50:23 +02:00
lilleman 38d791d9b1 Re-pin the seeded address examples for the address bound to its locality 2026-10-05 00:50:23 +02:00
lilleman b5be59f180 Re-pin the shape for the address bound to its locality 2026-10-05 00:50:23 +02:00
lilleman 1afcbc1a83 Answer stability round 1: bind the locality so population still weighs an address, test the field paths agree, and restate why birth-number sits under sex 2026-10-05 00:50:23 +02:00
lilleman 06c17411d6 Document the named person and address picks, revise the address decision, and close item 3 2026-10-05 00:50:23 +02:00
lilleman b17f29f983 Re-pin the seeded address examples 2026-10-05 00:50:23 +02:00
lilleman 1cff081f51 Re-pin the shape for the named person and address picks 2026-10-05 00:50:23 +02:00
lilleman 4b80460515 Draw a shipped person from one named first name, and an address from one named street 2026-10-05 00:50:23 +02:00
lilleman 7fd79bb09c Test that a shipped person and address each come from one named pick 2026-10-05 00:50:23 +02:00
lilleman f03a0de42c Answer prose round 2: rewrap the Step up and Linked tables paragraphs 2026-10-05 00:23:18 +02:00
lilleman ec1dcbf9d3 Answer prose round 1: name the parent after .., mark the step down as the one exception to the shared draw, and plainer errors 2026-10-05 00:23:18 +02:00
lilleman 406232e8f9 Answer stability round 1 and product-owner round 1: spell .. in the fence's and the link column's advice, take it in struct tags, and show the whole climb 2026-10-05 00:23:18 +02:00
lilleman 1551087ddf Answer architecture round 2: say the suggested path starts at the data root 2026-10-05 00:23:18 +02:00
lilleman 1ec2bee098 Answer architecture round 1: share a step down's draw per draw group and pick, own descend's pins, name the spelling to write, and record the .. decision 2026-10-05 00:23:18 +02:00
lilleman 4b5506d07b Document .., drop the step-up decision item 2 replaces, and close item 2 2026-10-05 00:23:18 +02:00
lilleman 8b76d51f2c Step up from a row to the row it links to with .. 2026-10-05 00:23:18 +02:00
lilleman 07c66c57fc Test that .. steps up from a row to the row it links to 2026-10-05 00:23:18 +02:00
lilleman 5707c697d8 Answer prose round 3: name the five items the round lets merge 2026-10-04 23:45:29 +02:00
lilleman bad5beb42b Answer prose round 2: items 4 and 90 remove what the earlier items touch, and the scoring run writes the first scores 2026-10-04 23:45:29 +02:00
lilleman e14c9d0f4c Answer prose round 1: item 5 scores the restructure, which is the round the comprehension rule lets merge, and item 90 says what internal/ buys 2026-10-04 23:45:29 +02:00
lilleman d160de3ee1 Scrap the flat-package decision, plan item 90's folder restructure before the panel, and suspend scoring until item 5 2026-10-04 23:45:29 +02:00
lilleman f3d0959cae Answer prose round 3 and product-owner round 3: a module is a Go module or a data folder, a manifest names its fejkdata version, and the Versioning rewrite planned 2026-10-04 23:08:31 +02:00
lilleman b2002bb51d Answer prose round 2 and product-owner round 2: module explained at first use, the seed as item 89, modules in lockstep, and a second break of New for the date 2026-10-04 23:08:31 +02:00
lilleman 9240d90547 Answer prose round 2 and product-owner round 2: flexible and extensible, the date in the seed promise, the custom-CLI builder, and the seed required beside item 77 2026-10-04 23:08:31 +02:00
lilleman eee7572360 Answer prose round 1 and product-owner round 1: modules not packages, goal 13 split, the decisions item 77 ends, and a manifest naming every default it reaches 2026-10-04 23:08:31 +02:00
lilleman 90be0ee6d8 Make everything replaceable goal 9, require changing inputs in the library and default them in the CLI, and record item 77's answers 2026-10-04 23:08:31 +02:00
lilleman dc48ae11a5 Answer prose round 2: state the library's required inputs as a step 2026-10-04 20:30:17 +02:00
lilleman f3fcf569ad Answer prose round 1: say item 26 revises the clock decision, fold the direction into its first step, and leave narrowing and the seed to their own items 2026-10-04 20:30:17 +02:00
lilleman 32c1fb6c26 Record the maintainer's input-data direction in item 26, and the age bands that weigh a birthdate 2026-10-04 20:30:17 +02:00
lilleman 4bf1ee292a Answer prose round 3 and product-owner round 2: one reading per step, no birthdate after the given date, and the 12-digit claim scoped to testpersonnummer 2026-10-04 20:25:54 +02:00
lilleman 84763399aa Answer product-owner round 1: plan the + so it ships before 2030, on request and in a data author's own category, and file the 12-digit form 2026-10-04 20:25:54 +02:00
lilleman ef164354ab Answer prose round 2: state the + for personnummer, as SKV 704 does, and check samordningsnummer when the item is picked 2026-10-04 20:25:54 +02:00
lilleman 4a2e161cfc Answer prose round 1: the + from the year its holder turns 100, in both Swedish ids, from 2030 2026-10-04 20:25:54 +02:00
lilleman 61e759a489 Plan item 26 for 0.2.0: the + separator from a date the caller gives, exploring how a render takes input first 2026-10-04 20:25:54 +02:00
lilleman 663b20b77a Answer prose round 2: say which paragraph item 87 splits, in the words it fixes, under goal 11 2026-10-04 17:53:32 +02:00
lilleman 1af5abf762 Answer prose round 1: say NANPA may assign the codes, spell the test's exchange in full, and file the record paragraph's split 2026-10-04 17:53:32 +02:00
lilleman 965d671707 Re-pin the shape for en_US.phone.exchange 2026-10-04 17:53:32 +02:00