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

README.md

@@ -238,7 +238,17 @@ too, so a person's prefix never contradicts it. A `personnummer`'s birth number,
 for a man, which no real person is ever given.
 
 A person of a chosen sex is assembled from the tables — `sex[f].first-name` beside
-`last-name`. Skatteverket's test series is also small: a personnummer
+`last-name`. `person` and `personnummer` each draw their own sex, so where a name and a
+number must agree, read both through one bound `sex`:
+
+```json
+{ "format": "{first} {last}, {pnr}",
+  "first": "{/sv_SE.sex as s}{s.first-name}",
+  "last": "{/sv_SE.last-name}",
+  "pnr": "{date(1930-01-01,2025-12-31,'060102')}-{s.birth-number.number}{luhn()}" }
+```
+
+Renders e.g. `Anne Grönberg, 011012-2389`. Skatteverket's test series is also small: a personnummer
 is one of about 70,000 values, a day in 1930–2025 against the two birth numbers, so a
 fixture past a few hundred rows repeats one and a `UNIQUE` column needs a category of
 your own. `sv_SE.date` and `en_US.date` are uniform over 1970-01-01 to 2029-12-31,
@@ -249,8 +259,8 @@ inside a sex.
 
 A `geo` folder holds one tree per country under its alpha-2 code: five
 [linked tables](#linked-tables) named alike, and an `address` record binding one locality
-and drawing its street and postal code inside it, which the locale's `address` binds once
-and prints whole.
+and drawing its street and postal code inside it. The locale's `address` prints that
+record, and each of its columns describes the address printed.
 
 | Table | `geo.SE` | `geo.US` | Weight |
 |-------|----------|----------|--------|