PATTERN-A-LIST-OF-ZONES keeps the rule and drops the speaker

Three lines brought in with the list-pattern doc cited the Driver; the
reference gate refuses them. The rule, the scope and the open exception
stay as stated, without the attribution.
This commit is contained in:
Doxa Maps 2026-09-29 14:48:06 +00:00
parent 65729d608d
commit cfd03d0250

View file

@ -18,7 +18,7 @@ carries all five lists.
## Half 1 — the list prop. Already built; do not rebuild it.
`library/lists/peopleGroupList.js` is shared machinery, not UPG-100's. The registry
(`library/lists/lists.json`) already defines every list the Driver named:
(`library/lists/lists.json`) already defines every list in scope:
| id | aliases | label |
|---|---|---|
@ -57,7 +57,7 @@ locale you missed.
## Half 2 — the zoning. This is the judgement, and it cannot be automated.
**The Driver's rule, in their words:** geography FIRST so the poster maps make sense, balanced with
**The rule:** geography FIRST so the poster maps make sense, balanced with
LANGUAGE — because languages usually cluster geographically, the zones are already a mixture of the
two, grouped manually.
@ -97,8 +97,8 @@ is the one answer that poster, packet and legend all agree on — ask it, don't
### The deaf poster is the known exception. Leave it unsolved.
The deaf zone is global and non-geographic by construction (affinity bloc A017, 123 groups spanning
every region), so it breaks the geography-first rule the rest of the pattern rests on. **The Driver
has not solved this and said so.** It is recorded here as an open exception, not papered over with
every region), so it breaks the geography-first rule the rest of the pattern rests on. **It is
recorded as not yet solved.** It is recorded here as an open exception, not papered over with
an invented zoning. If your list has a similar affinity-not-territory group, do the same: give it
its own bucket, let it collapse to one leaf, and say plainly that it is not geographic.