@heroiclands/package-build 23.1.1 → 23.2.0

package/docs/reference/format-details.md

@@ -104,6 +104,11 @@ A note profile begins with `Name`. For a being with a top-level `subType`, it
 follows with `Type: Character`, `Type: NPC`, or `Type: Creature`. A being with
 no subtype has no `Type` row.
 
+The `Culture` row shows the note's resolved culture, so a place or an
+affiliation shows the culture it inherits. A culture note has no `Culture` row:
+its resolved culture is its own Address, whether it leaves the field out or
+names itself. See [Culture in the index](#culture-in-the-index).
+
 **Embedded models link to documentation in an infobox.** The model Address
 continues to identify the native Item used for compilation. Its displayed link
 uses that same package, type and Shortcode under `note`, which names the
@@ -135,7 +140,7 @@ or it is a **source system's own detail**, which no surface's box shows:
 | a calendar's `months`, `weekdays`, `seasons`, `namedDays`, `eras`, `formats` | calendar machinery, not a summary row                      |
 | a map's `scene`, `fixup`                                                     | canvas machinery, not a summary row                        |
 | `harnworld`                                                                  | HârnWorld source detail, which no surface's box shows      |
-| the art slots                                                                | an image, which rule 2 keeps out of the box                |
+| the art slots, and a map's `thumbnail`                                       | an image, which rule 2 keeps out of the box                |
 
 **A field whose value holds maps is drawn by what its declaration says the
 maps are**, and a map is never set as text:
@@ -735,14 +740,14 @@ no SoHL form, so its SoHL column is. Nothing else varies — which is why these
 rows are worth stating once: repeated sixteen times they buried the differences
 that matter.
 
-**`data.icon` maps onto a document that has one, and not every type's does.**
-The row is shared because the key is legal on every note whatever its type, not
-because every document carries artwork: `doc`, `place`, `lore` and `scenario`
-compile into a JournalEntry, which has no image of any kind, and a `folder`
-compiles into a Foundry `Folder`, which has none either. A `homepage` compiles
-into no compendium document at all. On any of those the mapping has no
-destination, so the resolved value is simply dropped — the note validates, the
-tree compiles, and the value goes nowhere.
+**`data.icon` is declared only for the types whose document carries art.**
+The row is not shared: `being`, every Item type, `macro` and `bundle` compile
+into a document with an image, and only those declare `icon`. `doc`, `place`,
+`lore` and `scenario` compile into a JournalEntry, which has no image of any
+kind; a `map` compiles into a Scene whose art is its own; a `folder` compiles
+into a Foundry `Folder`; and a `homepage` compiles into no compendium document
+at all. On any of those `icon` is not a declared property, so the note is
+refused at the key's own line rather than compiled with the value dropped.
 
 **What a note writes is an address; what a document carries is a path.**
 `data.icon` is an `Address` defaulting to type `icon`, so a being writes
@@ -751,20 +756,13 @@ file the owning package ships and writes the resulting path into `img`. The two
 sides of this row are therefore in two different currencies, which is why the
 row reads `data.icon → img` rather than naming one thing twice.
 
-Since a dropped value looks exactly like a value never written, the frontmatter
-lint **reports it**: an art key authored on a type whose passes emit none is a
-warning naming the note and the key. A warning rather than an error, because the
-note still compiles correctly and the key is not certainly unwanted — a note's
-top level is the generated page's front matter as well, so a site template may
-read there what no document carries. `null` is never reported: that is the
-blessed way to say "this note names no art", and on a type with no art it is a
-true and harmless thing to say.
-
-Which types those are is **not a list**. It is asked of the passes: a type routes
-to a document, a document to the pass that compiles it, and each pass declares
-the art it writes (`emitsArt`). A second table of iconless types would be a table
-free to drift from what is actually emitted, which is the defect rather than the
-check.
+Which types declare `icon` is **not a list**. It is asked of the passes: a type
+routes to a document, a document to the pass that compiles it, and each pass
+declares the art it writes (`emitsArt`). A pass that emits `icon` is a type that
+declares the key. Any other art key authored where no pass emits it, such as a
+`tokenIcon` on an Item type, is a warning naming the note and the key, because
+the note still compiles correctly and a site template may read there what no
+document carries. `null` is never reported.
 
 #### The art slots
 
@@ -774,11 +772,14 @@ exactly as `seat` declares `place` — a bare shortcode takes its type from the
 declaration, and qualification climbs the same short-form ladder every other
 link uses.
 
-| field       | default type | accepts         | resolves into                 | on                                        |
-| ----------- | ------------ | --------------- | ----------------------------- | ----------------------------------------- |
-| `icon`      | `icon`       | `icon`, `image` | `document.img`                | every Actor/Item type, and embedded items |
-| `tokenIcon` | `icon`       | `icon`, `image` | `prototypeToken.texture.src`  | Actor types                               |
-| `banner`    | `image`      | `icon`, `image` | the site hero image, 1792×768 | any note; not a Foundry field             |
+| field       | default type | accepts         | resolves into                 | on                                          |
+| ----------- | ------------ | --------------- | ----------------------------- | ------------------------------------------- |
+| `icon`      | `icon`       | `icon`, `image` | `document.img`                | `being`, every Item type, `macro`, `bundle` |
+| `tokenIcon` | `icon`       | `icon`, `image` | `prototypeToken.texture.src`  | Actor types                                 |
+| `banner`    | `image`      | `icon`, `image` | the site hero image, 1792×768 | any note; not a Foundry field               |
+
+A map's `thumbnail` is not an art slot. It is a map field resolved into the
+Scene's `thumb` as a fixup — see [the thumbnail](#the-thumbnail).
 
 Every slot is authored under `data:`:
 
@@ -788,6 +789,11 @@ data:
   banner: packagebuild-none-image-skillbnr
 ```
 
+**An empty value is an error.** `icon: ""`, `tokenIcon: ""` and `banner: ""`
+are each a finding at the key, in `data:` or in a system block. A slot names an
+image, or the key is removed and the document takes its type's default;
+`icon: null` says the same as removing it.
+
 **Every slot accepts a second type beyond the one it defaults to**, and the two
 defaults pair with the same accepted set: `icon` and `tokenIcon` default to
 `icon`, `banner` defaults to `image`, and every slot accepts `icon` **and**
@@ -815,16 +821,15 @@ are, so a key legal everywhere is stated once here rather than repeated in
 twenty-five tables where the one that was mistyped would be the one nobody
 noticed:
 
-| shared `data` property | Values                | Description                                                          |
-| ---------------------- | --------------------- | -------------------------------------------------------------------- |
-| `id`                   | `string`              | A pinned document identity.                                          |
-| `pack`                 | `string`              | The shared compendium route.                                         |
-| `packFolder`           | `Address` or pack map | The shared compendium folder Address.                                |
-| `harnworld`            | `{ realm?, ritual? }` | HârnWorld source details.                                            |
-| `harnworld.realm`      | `string`              | The HârnWorld realm the subject belongs to.                          |
-| `harnworld.ritual`     | `string[]`            | The HârnWorld religions the subject observes.                        |
-| `icon`                 | `Address`             | The document's profile art — an `icon` address, resolved into `img`. |
-| `banner`               | `Address`             | The page's hero image — an `image` address, cut to 1792×768.         |
+| shared `data` property | Values                | Description                                                  |
+| ---------------------- | --------------------- | ------------------------------------------------------------ |
+| `id`                   | `string`              | A pinned document identity.                                  |
+| `pack`                 | `string`              | The shared compendium route.                                 |
+| `packFolder`           | `Address` or pack map | The shared compendium folder Address.                        |
+| `harnworld`            | `{ realm?, ritual? }` | HârnWorld source details.                                    |
+| `harnworld.realm`      | `string`              | The HârnWorld realm the subject belongs to.                  |
+| `harnworld.ritual`     | `string[]`            | The HârnWorld religions the subject observes.                |
+| `banner`               | `Address`             | The page's hero image — an `image` address, cut to 1792×768. |
 
 `data.harnworld` takes two keys and nothing else: `realm`, a string naming the
 HârnWorld realm the subject belongs to, and `ritual`, a list of strings naming
@@ -837,10 +842,9 @@ data:
     ritual: [Larani, Peoni]
 ```
 
-`icon` is legal everywhere because most types compile into a document that
-carries one; where a type's passes emit none, the lint says so and the value is
-left alone, because a page template may still read it. `banner` reaches no
-compiled document at all, and a page is what every note publishes.
+`icon` is declared only for the types whose document carries art; see
+the art slots below. `banner` reaches no compiled document at
+all, and a page is what every note publishes, so it is legal everywhere.
 
 `tokenIcon` is narrower, and the Actor types' own tables name it. A map takes
 no art slot: its Scene is exported from Foundry and names its own art.
@@ -870,12 +874,9 @@ header carries. `data.tokenIcon` is what a token on the canvas wears. Both are
 addresses and both resolve the same way; only the destination differs. An Item
 has one piece of art, so this row applies to actor types alone.
 
-**A `data:` source is still read at the top level, for now.** `data:` did
-not invent the facts it holds — it gathered them out of the top level — so every
-key it collected has a **pre-`data:` spelling** that is read after the declared
-one and reported as retiring. This is the shared level's counterpart to the
-in-block `<system>.<key>` retirement, and the two are separate: a note may have
-moved one and not the other.
+**A `data:` source is authored in `data:` alone.** The same key written at the
+top level is outside the closed top-level region, and written inside a system
+block it is reported at its own line with the `data:` key it belongs to.
 
 **No image key is one of those.** A top-level `img:` is not authored at all:
 `data.icon` is a different key holding a different kind of value, and a note
@@ -1006,10 +1007,10 @@ nothing of (`/systems/dnd5e/icons/spell.webp`).
 replacement. It is a Foundry address written where an ownership statement
 belongs: it resolves for Foundry and for nothing else, because neither the
 website nor the book has any such directory. `systems/sohl/assets/ui/logo.webp`
-is written `sohl/assets/ui/logo.webp`, and `systems/hm3/images/svg/sword.svg` —
+is written `sohl/assets/ui/logo.webp`, and `systems/hm3/assets/icons/sword.svg` —
 where the package serves its pictures from its own root — is written
-`hm3/assets/images/svg/sword.svg`, because `assets/` is where a package's files
-sit in every derived form.
+`hm3/assets/icons/sword.svg`, because `assets/` is where a package's files sit
+in every derived form.
 
 `worlds/` is not a Foundry root for this purpose. A package may not ship files
 out of a world, so a note writing one has made a different mistake and gets the
@@ -1052,8 +1053,11 @@ writes `banner: skillbnr` and a note borrowing another package's plate writes
 owning package, and each surface joins the suffix onto its own root — the site
 onto `site.assets`, the book onto the directory it stages banners into.
 
-**`banner: null` is how a note says it wants no plate.** It is a true statement
-on any type, and the frontmatter lint never reports it.
+**`banner: none` is how a note declines its hero image.** The word is never
+read as an Address: it resolves to no image, the page publishes a blank
+`data.banner`, and the theme draws the band with no picture and no warning. An
+Address that names no image is a finding at its own line and column, and `""`
+is an error. `banner: null` names no art and the page takes its type's default.
 
 #### The pack a note compiles into
 
@@ -1147,20 +1151,9 @@ which of several competing templates a player is actually offered.
 The shared mapping table above names it `data.templatePriority`, targeting
 `system.templatePriority` in SoHL and `flags.hm3.templatePriority` in HM3.
 
-> **`archetype` is the retiring spelling.** It is still read, in the `sohl:`
-> block and at the top level, so a tree sweeps on its own schedule
-> — but the frontmatter linter refuses it, and
-> what is compiled and emitted is `templatePriority` on all three sides.
->
-> It is more than a rename, and the collision is **already live** rather than
-> pending: `archetypes` is specified above as the _sort_ a character is, and a
-> being's row declares it. So a number deciding which template wins and a list of
-> what sort of character this is would otherwise be distinguished **only by a
-> plural `s`**.
->
-> A note carrying both spellings with **different** values is refused rather than
-> resolved quietly — `templatePriority: null` and `archetype: 0` say opposite
-> things, and picking either silently would decide it on the author's behalf.
+> `archetypes` is a different field: specified above as the _sort_ a character
+> is, and declared by a being's row. The priority that decides which template
+> wins is always `templatePriority`, on all three sides.
 
 ```yaml
 data:
@@ -1311,8 +1304,7 @@ the journals pack having to declare anything. A folder nothing references
 materialises nowhere.
 
 One folder note and one Address supply every pack that references it.
-`data.packFolder` names a folder by Address. A top-level `folder:` key is
-refused with a finding that names `data.packFolder` and the authored line.
+`data.packFolder` names a folder by Address.
 
 #### The knowledgebase category
 
@@ -1472,9 +1464,25 @@ note, while `[[none-macro-autoattack|Automated Attack]]` names the Foundry Macro
 
 **A complete Address is lowercase throughout.** Every segment — package,
 system, type and shortcode alike — contains only lowercase ASCII letters and
-digits (`^[a-z0-9]+$`). Declared Address fields reject uppercase segments.
-A model reference accepts mixed-case Shortcodes and resolves their lowercase
-Address identity; this does not change a native embedded item's Shortcode.
+digits (`^[a-z0-9]+$`). Every Address is validated as written, whether a field
+declares it or a wikilink or embed writes it, so a capital in any segment, the
+shortcode included, is an error at the value or at the link. Nothing is
+lowercased on the author's behalf. Where the lowercase spelling is a declared
+shortcode, the error names it:
+
+```text
+Beings/Guard.md:8:15: error: `sohl.items.0.model` shortcode `LLeg` must be lowercase; the declared shortcode is `lleg`
+```
+
+A link is reported the same way, at its own line and column:
+
+```text
+Skills/Jumping.md:10:5: error: address [[skill-Clmb]] shortcode `Clmb` must be lowercase; the declared shortcode is `clmb`
+```
+
+Each such reference in a note's frontmatter is reported at its own position,
+and the note is left out of the index, so the build fails rather than
+compiling without it.
 
 **Parsing is positional counting from the right, and nothing else.** Every
 segment is lowercase alphanumeric — shortcodes, **types** and **subTypes** are
@@ -1546,18 +1554,18 @@ A `draft` note exists, resolves, compiles and publishes; a link to it renders
 visibly marked. An Address landing nowhere is a typo or an omission and earns
 an error.
 
-There are six ways a link can fail, and each is one **error** with one message
-wherever it is met:
+Each way a link can fail is one **error** with one message wherever it is met:
 
-| finding          | what it means                                 | the fix                                                |
-| ---------------- | --------------------------------------------- | ------------------------------------------------------ |
-| `unlabelled`     | no `\|`, so the link addresses nothing        | write `[[type-shortcode\|Text]]`                       |
-| `not-an-address` | labelled, but the target is not an address    | write the address, not the name                        |
-| `not-lowercase`  | any segment of the address is capitalised     | lowercase it — every segment is lowercase              |
-| `unknown-type`   | qualified, but names no type this build knows | correct the type segment                               |
-| `unresolved`     | parses as an address; nothing publishes it    | fix the shortcode, or qualify to reach another package |
-| `ambiguous`      | _unreachable; kept for the manifest_          | —                                                      |
-| `unknown-anchor` | the address resolves; the `#section` does not | correct the anchor                                     |
+| finding                   | what it means                                                                                             | the fix                                                |
+| ------------------------- | --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ |
+| `unlabelled`              | no `\|`, so the link addresses nothing                                                                    | write `[[type-shortcode\|Text]]`                       |
+| `not-an-address`          | labelled, but the target is not an address                                                                | write the address, not the name                        |
+| `not-lowercase`           | a package, system or type segment is capitalised                                                          | lowercase it — every segment is lowercase              |
+| `shortcode-not-lowercase` | the shortcode is capitalised; the message names the declared shortcode when the lowercase spelling is one | lowercase it — a shortcode is lowercase                |
+| `unknown-type`            | qualified, but names no type this build knows                                                             | correct the type segment                               |
+| `unresolved`              | parses as an address; nothing publishes it                                                                | fix the shortcode, or qualify to reach another package |
+| `ambiguous`               | _unreachable; kept for the manifest_                                                                      | —                                                      |
+| `unknown-anchor`          | the address resolves; the `#section` does not                                                             | correct the anchor                                     |
 
 `ambiguous` is a reserved reason in the result vocabulary. An omitted segment
 defaults rather than wildcarding, so each written target expands to one
@@ -1590,7 +1598,7 @@ prose: a field value is a reference something else will compile against, and it
 should say exactly what it points at.
 
 **A field can supply the type.** A field naming one kind of note declares its
-default — `seat` a `place`, `parents` an `affiliation`, `stations` a `lore` — so
+default — `seat` a `place`, `parents` an `affiliation`, `lore` a `lore` — so
 the type segment defaults from the declaration and a bare shortcode is the
 ordinary case, not an abbreviation of one. That is why the examples above read
 `tashal` rather than `place-tashal`: the shorter form carries the same
@@ -1747,7 +1755,6 @@ is always the same: write `[[type-shortcode|Text]]`.
 
 The bare form does not resolve by display name or alias. `name.aliases` is
 indexed for search and completion, while an authored link names an Address.
-A top-level `aliases:` key is refused.
 
 Requiring the label is also what makes positional parsing safe. Note names
 contain hyphens — `Grukar-ahk` is a name, not a `Grukar` of type `ahk` — so a
@@ -1755,7 +1762,7 @@ target that does not parse as an address is reported as one that does not, rathe
 than split at an arbitrary place or quietly looked up somewhere else.
 
 The **empty** label is not a way of writing no label. It says _address this
-target, and show whatever it calls itself_ — so a note renamed later takes its new
+target, and show whatever it calls itself_ — so a note whose name changes takes its new
 name at every citation with no link edited. `[[x|]]` is labelled; `[[x]]` is not.
 
 It is the label that is required, not a target: the anchor-only form above
@@ -2611,7 +2618,9 @@ documentation entry, so `type = 'miscgear'` selects the items and never their
 journals. A nested field is addressed exactly as a note authors it —
 `sohl.weight`, `name.full`, `file.path` — because the index is read as JSON and
 every nested object is inferred as a struct. A field a note type does not carry
-reads `NULL` rather than failing.
+reads `NULL` rather than failing. `data.culture` is the one field that reads as
+a derived value: the note's own culture, or the one it inherits. See
+[Culture in the index](#culture-in-the-index).
 
 **`notes` leaves out stubs; `entries` does not.** Both carry a derived `state`
 column — `stub`, `draft` or `full` — and `notes` is exactly
@@ -2706,6 +2715,136 @@ table would otherwise need: the authored `ORDER BY` decides the section order to
 **Beware `packFolder`.** It is a note's _pack_ folder, not its directory — the
 directory is `file.folder`.
 
+##### Culture in the index
+
+`data.culture` in the index is the note's **resolved** culture, which is its
+authored value where it states one and a derived value where it does not. The
+resolved value is written into the index as a canonical Address string, such as
+`reedflats-note-lore-reedfolk`, so a table selects by it directly.
+
+The culture of a note, in order:
+
+1. Its own `data.culture`, when it states one.
+2. For a `lore` note of `subType: culture`: itself. A culture note may leave the
+   field out or state it as its own Address, and its resolved culture is its own
+   Address either way.
+3. For a `place` or an `affiliation`: the resolved cultures of its
+   `data.parents` — places through their parent places, affiliations through
+   their parent affiliations — found recursively, so a culture stated three
+   levels up reaches the bottom.
+4. For an affiliation of `subType: polity` that still has none: the resolved
+   cultures of its places, pooled as one set — its `data.seat` and every place
+   whose `data.government` names the polity.
+5. Otherwise none. A parent or place that resolves to nothing contributes
+   nothing.
+
+A `being` and a `doc` of `subType: settingguide` read as the value they state and
+nothing more; every other `lore` note reads as its own value, and every other
+note type reads as none.
+
+Sources that agree give that culture. Sources that name different cultures, on a
+note that states none of its own, are an **error**, and that note gets no
+culture. The error is located at the `parents:` key; for the pooled places of a
+polity it is located at the `seat:` key, or at the `data:` line when the polity
+states no seat. Stating `data.culture` on the note settles the matter, because
+an own value is never compared with its sources. A note whose parent raised the
+error reads that parent as resolving to nothing, so one disagreement is reported
+once, at the note where the sources meet.
+
+Here a region states a culture and the places inside it carry it down:
+
+```markdown
+---
+shortcode: reedflats
+name: { full: Reed Flats }
+type: place
+subType: region
+description: A marsh region.
+data:
+  culture: lore-reedfolk
+---
+```
+
+```markdown
+---
+shortcode: saltmarsh
+name: { full: Saltmarsh }
+type: place
+subType: district
+description: A salt marsh.
+data:
+  parents: [place-reedflats]
+---
+```
+
+```markdown
+---
+shortcode: eelwick
+name: { full: Eelwick }
+type: place
+subType: settlement
+description: A fishing village.
+data:
+  parents: [place-saltmarsh]
+---
+```
+
+`saltmarsh` and `eelwick` state no culture and index as `reedflats-note-lore-reedfolk`.
+Because the index carries the resolved value, one query selects the region and
+everything beneath it, and `IS NULL` selects the notes that have no culture:
+
+````markdown
+```sql
+SELECT address.slug AS _ref, name.full AS "Name"
+FROM notes
+WHERE type = 'place' AND data.culture = 'reedflats-note-lore-reedfolk'
+ORDER BY name.full
+```
+````
+
+````markdown
+```sql
+SELECT address.slug AS _ref, name.full AS "Name"
+FROM notes
+WHERE type = 'place' AND data.culture IS NULL
+```
+````
+
+A place whose parents sit in different cultures must say which it belongs to.
+With a second region `stonecrest` that states `culture: lore-hillfolk`, a place
+on the border between the two:
+
+```markdown
+---
+shortcode: causeway
+name: { full: The Causeway }
+type: place
+subType: site
+description: A road between marsh and ridge.
+data:
+  parents: [place-reedflats, place-stonecrest]
+---
+```
+
+fails the content-index build with one located error per conflict:
+
+```text
+assets/content/Places/Causeway.md:8:3: error: data.parents resolve to different cultures (reedflats-note-lore-reedfolk via reedflats, reedflats-note-lore-hillfolk via stonecrest); state data.culture
+```
+
+The conflict fails the content-index build, and every other command that reads
+the index without collecting problems, listing every conflict in one run. Adding
+`culture: lore-reedfolk` under `data:` on `causeway` removes it. A fetched
+dependency's index carries each note's resolved culture, so a parent in another
+package contributes the culture that package resolved for it.
+
+The index record carries the resolved culture, and every pass that reads the
+record reads it too: lint, the pack compile and the site build all see a
+place's inherited culture, and a culture note's own Address, as its
+`data.culture`. A resolved value always passes the checks that scope the field,
+because a culture note resolves to itself and an inherited value names a culture
+note. The infobox shows a note's resolved culture, except a culture note's own.
+
 ##### Reading another package's notes
 
 Each package this one **depends on** is attached as a schema named after it, so
@@ -3352,35 +3491,35 @@ Generates a living (or undead, or spirit) being.
 
 See [a being's subtype describes the subject](#a-beings-subtype-describes-the-subject).
 
-| `data` property                 | Values                                         | Description                                                                                                                                           |
-| ------------------------------- | ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `tokenIcon`                     | `Address`                                      | What a token on the canvas wears — an `icon` address; defaults to `icon`                                                                              |
-| `templatePriority`              | `number`                                       | Template priority, _null_ = not a template                                                                                                            |
-| `archetypes`                    | `Archetype[]`                                  | What sort of character this is. **Always an array** — character and npc require at least one; creature may omit it or write `[]`; `null` is an error. |
-| `occupation`                    | `string`                                       | Name of the character's occupation                                                                                                                    |
-| `stations`                      | `Address[]`                                    | Name of the stations the character belongs to                                                                                                         |
-| `lore`                          | `Address[]`                                    | Other lore concerning this being, such as social standing or law                                                                                      |
-| `culture`                       | `Address`                                      | Primary culture, naming a lore note with `subType: culture`                                                                                           |
-| `homes`                         | `Address[]`                                    | Place the being calls home                                                                                                                            |
-| `affiliations`                  | `Map<Address, Membership>`                     | Bodies the being belongs to, keyed by Address, each entry the standing it holds there                                                                 |
-| `affiliations.<Address>.rank`   | `integer`, required                            | The level on that body's own `governance.ranks` ladder; `1` is an ordinary member, `0` someone cast out                                               |
-| `affiliations.<Address>.office` | `string`                                       | A post that body names in its `governance.offices`, where the being holds one                                                                         |
-| `socialTies`                    | `Map<Address, Tie>`                            | Defining support and opposition, directed from this being to others                                                                                   |
-| `gender`                        | `male \| female \| other`                      | Gender of the character                                                                                                                               |
-| `species`                       | `Address`                                      | Being's species (lore)                                                                                                                                |
-| `born`                          | `date \| unknown`                              | When the being was born; absent, it was never born                                                                                                    |
-| `calendar`                      | `Address`                                      | Calendar note used to print the being's dates                                                                                                         |
-| `died`                          | `date \| unknown`                              | When the being died; absent, it is alive                                                                                                              |
-| `age`                           | `34 \| ~34`                                    | Age in years, stated only to override what `born` says; `~` marks an estimate                                                                         |
-| `ageYears`                      | `number`                                       | Written by the compiler beside an `age` estimate — the `~` stripped; a note never authors this                                                        |
-| `height`                        | `1.91m \| 6' 3"`                               | Height in metres or feet and inches                                                                                                                   |
-| `weight`                        | `85kg \| 187 lbs`                              | Body weight in kilograms or pounds                                                                                                                    |
-| `frame`                         | `scant \| light \| medium \| large \| massive` | Relative frame size                                                                                                                                   |
-| `appearance.eye_color`          | `string`                                       | Eye color                                                                                                                                             |
-| `appearance.hair_color`         | `string`                                       | Hair color                                                                                                                                            |
-| `appearance.skin_color`         | `string`                                       | Skin color                                                                                                                                            |
-| `appearance.complexion`         | `string`                                       | Complexion                                                                                                                                            |
-| `appearance.extra_features`     | `string[]`                                     | Extra features                                                                                                                                        |
+| `data` property                    | Values                                         | Description                                                                                                                                           |
+| ---------------------------------- | ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `tokenIcon`                        | `Address`                                      | What a token on the canvas wears — an `icon` address; defaults to `icon`                                                                              |
+| `templatePriority`                 | `number`                                       | Template priority, _null_ = not a template                                                                                                            |
+| `archetypes`                       | `Archetype[]`                                  | What sort of character this is. **Always an array** — character and npc require at least one; creature may omit it or write `[]`; `null` is an error. |
+| `occupation`                       | `string`                                       | Name of the character's occupation                                                                                                                    |
+| `lore`                             | `Address[]`                                    | Other lore concerning this being, such as social standing or law                                                                                      |
+| `culture`                          | `Address`                                      | Primary culture, naming a lore note with `subType: culture`                                                                                           |
+| `homes`                            | `Address[]`                                    | Place the being calls home                                                                                                                            |
+| `affiliations`                     | `Map<Address, Membership>`                     | Bodies the being belongs to, keyed by Address, each entry the standing it holds there                                                                 |
+| `affiliations.<Address>.rank`      | `integer`, required                            | The level on that body's own `governance.ranks` ladder; `1` is an ordinary member, `0` someone cast out                                               |
+| `affiliations.<Address>.office`    | `string`                                       | A post that body names in its `governance.offices`, where the being holds one                                                                         |
+| `affiliations.<Address>.societies` | `string[]`                                     | The societies the membership is held in, by name; SoHL carries the first as `system.society`                                                          |
+| `socialTies`                       | `Map<Address, Tie>`                            | Defining support and opposition, directed from this being to others                                                                                   |
+| `gender`                           | `male \| female \| other`                      | Gender of the character                                                                                                                               |
+| `species`                          | `Address`                                      | Being's species (lore)                                                                                                                                |
+| `born`                             | `date \| unknown`                              | When the being was born; absent, it was never born                                                                                                    |
+| `calendar`                         | `Address`                                      | Calendar note that prints the being's dates                                                                                                           |
+| `died`                             | `date \| unknown`                              | When the being died; absent, it is alive                                                                                                              |
+| `age`                              | `34 \| ~34`                                    | Age in years, stated only to override what `born` says; `~` marks an estimate                                                                         |
+| `ageYears`                         | `number`                                       | Written by the compiler beside an `age` estimate — the `~` stripped; a note never authors this                                                        |
+| `height`                           | `1.91m \| 6' 3"`                               | Height in metres or feet and inches                                                                                                                   |
+| `weight`                           | `85kg \| 187 lbs`                              | Body weight in kilograms or pounds                                                                                                                    |
+| `frame`                            | `scant \| light \| medium \| large \| massive` | Relative frame size                                                                                                                                   |
+| `appearance.eye_color`             | `string`                                       | Eye color                                                                                                                                             |
+| `appearance.hair_color`            | `string`                                       | Hair color                                                                                                                                            |
+| `appearance.skin_color`            | `string`                                       | Skin color                                                                                                                                            |
+| `appearance.complexion`            | `string`                                       | Complexion                                                                                                                                            |
+| `appearance.extra_features`        | `string[]`                                     | Extra features                                                                                                                                        |
 
 Author `data.height` as a string of decimal metres (`1.91m` or `1.91 m`) or
 whole feet with optional inches (`6'`, `6'3"`, or `6' 3"`). Inches must be
@@ -3406,14 +3545,15 @@ data:
 
 #### The bodies a being belongs to, and its standing in each
 
-**Membership**: `{rank: number, office: string}` — `rank` required, `office` not.
+**Membership**: `{rank: number, office: string, societies: string[]}` — `rank`
+required, `office` and `societies` not.
 
 `data.affiliations` is a **map keyed by the body's Address**, and each entry is
 the standing the being holds in that body. The key is what makes the pair
 expressible: a being in two bodies holds a standing in each, and two bodies may
 call a rung the same word.
 
-An entry carries two keys and nothing else:
+An entry carries three keys and nothing else:
 
 - **`rank`** — **required**, a **number**, the level on that body's own
   `governance.ranks` ladder. The body declares `{level, title, description}` for
@@ -3421,6 +3561,9 @@ An entry carries two keys and nothing else:
   for what its level 5 is called.
 - **`office`** — optional, a **string**, matched against the keys of that body's
   `governance.offices` map.
+- **`societies`** — optional, a **list of names**, the societies the membership
+  is held in. It is always a list, even with one name; a bare string is an
+  error at the key.
 
 **Every entry states a `rank`**, because belonging to a body is holding some
 standing in it. Where nothing more is known the rung is `1`, the ordinary
@@ -3438,15 +3581,15 @@ An entry carrying a rank and no office is complete.
 ```yaml
 data:
   affiliations:
-    affiliation-vrystwldtrbs: { rank: 5, office: War Chief }
+    affiliation-vrystwldtrbs: { rank: 5, office: War Chief, societies: [Vrystwald] }
     affiliation-greenwardens: { rank: 1 }
     affiliation-silverguild: { rank: 0 }
 ```
 
 Both values are checked against the body the entry is keyed by. A `rank` that
 is not a level the body confers and an `office` that is not one of its keys are
-each an error naming the file, line and column — so a renamed rung or a renamed
-post fails on every being pointing at it. Naming one body twice, by its short
+each an error naming the file, line and column — so a rung or a post that does
+not exist fails on every being pointing at it. Naming one body twice, by its short
 and full Address, still names one body and is an error.
 
 The infobox prints one line per membership, in the order the note writes them,
@@ -3456,14 +3599,16 @@ Vrystwald Tribes`, or `Hárár (5), of Vrystwald Tribes` with no office. The tit
 is read from the body's own `governance.ranks`; where the body declares no rung
 at that level, or its ladder is not available, the rung reads as `Rank 5` —
 `Rank 5, of Vrystwald Tribes`. The body's name links to its page, and is plain
-text where it publishes none. A membership written in the list form, with no
-standing, is the body's name alone. The lines are the same on the website, in
+text where it publishes none. A membership stating no
+standing is the body's name alone. The lines are the same on the website, in
 a Foundry journal and in the book. On the body's own page each office is a row
 anchored by its name, so the post a being holds is described where the body
 declares it.
 
 For SoHL, a being embeds one affiliation item per entry: `rank` **is** that
-item's `system.level` and `office` its `system.office`. A standing is a fact
+item's `system.level`, `office` its `system.office`, and the first name in
+`societies` its `system.society`. The SoHL item holds one society, so only the
+first name reaches it. A standing is a fact
 about the setting rather than about one system, so the `sohl:` block states
 none of it.
 
@@ -3546,7 +3691,7 @@ absent `born` — there is nothing there to disagree with — and silent whereve
 the package declares no present, for the same reason no age is computed at
 all.
 
-Use `born:` for a being's birth date. The `birthday:` spelling is accepted with a diagnostic; `born` takes precedence when both are written.
+Use `born:` for a being's birth date.
 
 #### The lead image
 
@@ -3666,8 +3811,7 @@ embedded document has no page for.
 `model:` carries the catalogue item's art, and an entry copying nothing takes
 the default its type pairs in `itemBuilders` — the same default an item note of
 that type compiles with. An entry naming an address of its own overrides either.
-Writing `icon: ""` ships the document blank on purpose, and no default replaces
-it.
+An empty `icon: ""` is an error, as it is on a note.
 
 **`data:` reaches no compiled document.** It is where a note names art, and a
 compiled Item has `img` instead; the container is read and goes no further.
@@ -3919,9 +4063,16 @@ rank names the standing, and the standing says.
 | `economy`                                       | `Address[]`                                        | Economic life: `affiliation` or `lore` Addresses, with an explicit type and no default         |
 | `lore`                                          | `Address[]`                                        | Lore concerning it — the peoples it draws on, the god a faith venerates, its law, its calendar |
 | `parents`                                       | `Address[]`                                        | Affiliations that this affiliation is subordinate to                                           |
+| `culture`                                       | `Address`                                          | The people this affiliation belongs to, naming a lore note with `subType: culture`             |
 | `relations`                                     | `Map<Address, Standing>`                           | Standing with other affiliations, keyed by the other body's Address                            |
 | `relations.<Address>`                           | `aligned`, `unaligned`, `rival` or `nemesis`       | The standing this body holds toward that one; any other value is an error at the value         |
 
+**An affiliation names the people it belongs to in `data.culture`.** An
+affiliation that names none takes its culture from its `data.parents`. A
+`polity` that still has none takes the culture of its places: its `data.seat`
+together with every place whose `data.government` names it. See
+[Culture in the index](#culture-in-the-index).
+
 **A faith tradition is not its god.** An `affiliation` of subType
 `faithtradition` is a _religion_ — a practice, with an ordained priesthood, a
 calendar and a body of observance — and it can outlive belief in the god
@@ -4556,44 +4707,48 @@ data:
 The saga lists under **In song and story** on `place-ironfells`, which holds the
 sack, on `place-east` and on `lore-fords`.
 
-Calendar fields are written only on a `calendar` note, and `culture`, `form`, `subjects` and
-`language` only on a `literature` note; written on any other lore subType, each is an error at
-its own key.
-
-| `data` property            | Values                                                                        | Description                                                                                                           |
-| -------------------------- | ----------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
-| `epoch`                    | canonical `<year>.<day>`                                                      | The canonical day that equals calendar year 1, day 1                                                                  |
-| `months`                   | `{ name, abbreviation?, days }[]`                                             | Ordered months; their days sum to the world's year                                                                    |
-| `months[].name`            | `string`, required                                                            | The month's name                                                                                                      |
-| `months[].abbreviation`    | `string`                                                                      | Its short form, for a compact date                                                                                    |
-| `months[].days`            | `integer`, required                                                           | How many days the month holds                                                                                         |
-| `weekdays`                 | `{ name, abbreviation? }[]`                                                   | Ordered week days, indexed from zero; weeks run continuously                                                          |
-| `weekdays[].name`          | `string`, required                                                            | The day's name                                                                                                        |
-| `weekdays[].abbreviation`  | `string`                                                                      | Its short form, for a compact date                                                                                    |
-| `seasons`                  | `{ name, abbreviation?, start }[]`                                            | Seasons starting on one-based days of year                                                                            |
-| `seasons[].name`           | `string`, required                                                            | The season's name                                                                                                     |
-| `seasons[].abbreviation`   | `string`                                                                      | Its short form, for a compact date                                                                                    |
-| `seasons[].start`          | `integer`, required                                                           | The one-based day of the year it begins; starts increase down the list                                                |
-| `namedDays`                | `{ name, abbreviation?, day }[]`                                              | Names assigned to one-based days of year                                                                              |
-| `namedDays[].name`         | `string`, required                                                            | The day's name                                                                                                        |
-| `namedDays[].abbreviation` | `string`                                                                      | Its short form, for a compact date                                                                                    |
-| `namedDays[].day`          | `integer`, required                                                           | The one-based day of the year it names, distinct within the calendar                                                  |
-| `eras`                     | `{ shortcode, name, abbreviation?, marker?, proclaimedBy?, start, label? }[]` | Year counts; `start` is `null` or an in-calendar year                                                                 |
-| `eras[].shortcode`         | `string`, required                                                            | The era's own segment of `<calendar>.<era>`, unique within the calendar                                               |
-| `eras[].name`              | `string`, required                                                            | The era's name                                                                                                        |
-| `eras[].marker`            | `string`                                                                      | Uppercase letters and digits, beginning with a letter, unique across the corpus; an authored date names the era by it |
-| `eras[].abbreviation`      | `string`                                                                      | Its short form, for a compact date                                                                                    |
-| `eras[].proclaimedBy`      | `Address`                                                                     | The body that began the reckoning                                                                                     |
-| `eras[].start`             | `null` or `integer`, required                                                 | The calendar year the era begins; `null` for the era before year 1                                                    |
-| `eras[].label`             | `string` or `{ after?, before? }`                                             | How a date in the era reads, around one `{date}` slot; a string is `after`                                            |
-| `eras[].label.after`       | `string`                                                                      | How a date from the era's start reads, with exactly one `{date}`                                                      |
-| `eras[].label.before`      | `string`                                                                      | How a date before the era's start reads, with exactly one `{date}`                                                    |
-| `formats`                  | map of names to Calendaria patterns                                           | Named date formats; `std` is the preferred default                                                                    |
-| `culture`                  | `Address`                                                                     | `literature` only: the people whose work it is, naming a lore note with `subType: culture`                            |
-| `form`                     | `string`                                                                      | `literature` only: the kind of work in its people's own terms — `epic`, `saga`, `praise-song`, `elegy`. Free text     |
-| `subjects`                 | `Address[]`                                                                   | `literature` only: the beings, places, gods and other notes the work concerns, and any event, as `note#id`            |
-| `language`                 | `Address`                                                                     | `literature` only: the tongue it is composed in, naming a skill note with `subType: language`                         |
-| `events`                   | event entries — see [Events](#events)                                         | What happened to or at this subject: dated, attributed events                                                         |
+Calendar fields are written only on a `calendar` note, and `form`, `subjects` and `language`
+only on a `literature` note; written on any other lore subType, each is an error at its own key.
+`culture` may be written on any lore subType. A culture note is itself the culture, so it
+leaves the field out or names itself, by its shortcode or by any longer form of its Address;
+naming any other note is an error at the value. A `lore` note that states no culture has
+none, since a `lore` note has no `data.parents` to inherit through; a culture note reads as
+its own Address in the index. See [Culture in the index](#culture-in-the-index).
+
+| `data` property            | Values                                                                        | Description                                                                                                                                                  |
+| -------------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `epoch`                    | canonical `<year>.<day>`                                                      | The canonical day that equals calendar year 1, day 1                                                                                                         |
+| `months`                   | `{ name, abbreviation?, days }[]`                                             | Ordered months; their days sum to the world's year                                                                                                           |
+| `months[].name`            | `string`, required                                                            | The month's name                                                                                                                                             |
+| `months[].abbreviation`    | `string`                                                                      | Its short form, for a compact date                                                                                                                           |
+| `months[].days`            | `integer`, required                                                           | How many days the month holds                                                                                                                                |
+| `weekdays`                 | `{ name, abbreviation? }[]`                                                   | Ordered week days, indexed from zero; weeks run continuously                                                                                                 |
+| `weekdays[].name`          | `string`, required                                                            | The day's name                                                                                                                                               |
+| `weekdays[].abbreviation`  | `string`                                                                      | Its short form, for a compact date                                                                                                                           |
+| `seasons`                  | `{ name, abbreviation?, start }[]`                                            | Seasons starting on one-based days of year                                                                                                                   |
+| `seasons[].name`           | `string`, required                                                            | The season's name                                                                                                                                            |
+| `seasons[].abbreviation`   | `string`                                                                      | Its short form, for a compact date                                                                                                                           |
+| `seasons[].start`          | `integer`, required                                                           | The one-based day of the year it begins; starts increase down the list                                                                                       |
+| `namedDays`                | `{ name, abbreviation?, day }[]`                                              | Names assigned to one-based days of year                                                                                                                     |
+| `namedDays[].name`         | `string`, required                                                            | The day's name                                                                                                                                               |
+| `namedDays[].abbreviation` | `string`                                                                      | Its short form, for a compact date                                                                                                                           |
+| `namedDays[].day`          | `integer`, required                                                           | The one-based day of the year it names, distinct within the calendar                                                                                         |
+| `eras`                     | `{ shortcode, name, abbreviation?, marker?, proclaimedBy?, start, label? }[]` | Year counts; `start` is `null` or an in-calendar year                                                                                                        |
+| `eras[].shortcode`         | `string`, required                                                            | The era's own segment of `<calendar>.<era>`, unique within the calendar                                                                                      |
+| `eras[].name`              | `string`, required                                                            | The era's name                                                                                                                                               |
+| `eras[].marker`            | `string`                                                                      | Uppercase letters and digits, beginning with a letter, unique across the corpus; an authored date names the era by it                                        |
+| `eras[].abbreviation`      | `string`                                                                      | Its short form, for a compact date                                                                                                                           |
+| `eras[].proclaimedBy`      | `Address`                                                                     | The body that began the reckoning                                                                                                                            |
+| `eras[].start`             | `null` or `integer`, required                                                 | The calendar year the era begins; `null` for the era before year 1                                                                                           |
+| `eras[].label`             | `string` or `{ after?, before? }`                                             | How a date in the era reads, around one `{date}` slot; a string is `after`                                                                                   |
+| `eras[].label.after`       | `string`                                                                      | How a date from the era's start reads, with exactly one `{date}`                                                                                             |
+| `eras[].label.before`      | `string`                                                                      | How a date before the era's start reads, with exactly one `{date}`                                                                                           |
+| `formats`                  | map of names to Calendaria patterns                                           | Named date formats; `std` is the preferred default                                                                                                           |
+| `culture`                  | `Address`                                                                     | The people this lore belongs to — for a `literature` note, the people whose work it is — naming a lore note with `subType: culture`; not on a `culture` note |
+| `form`                     | `string`                                                                      | `literature` only: the kind of work in its people's own terms — `epic`, `saga`, `praise-song`, `elegy`. Free text                                            |
+| `subjects`                 | `Address[]`                                                                   | `literature` only: the beings, places, gods and other notes the work concerns, and any event, as `note#id`                                                   |
+| `language`                 | `Address`                                                                     | `literature` only: the tongue it is composed in, naming a skill note with `subType: language`                                                                |
+| `events`                   | event entries — see [Events](#events)                                         | What happened to or at this subject: dated, attributed events                                                                                                |
 
 `data.events` is available on every `lore` subType, and is described in full under [Events](#events).
 
@@ -4700,7 +4855,7 @@ Braced custom forms such as `{era}` are equivalent to bracketed custom forms. A
 
 A map note has its own prose and a Foundry Scene. A map can depict a place or an encounter. Several maps can depict the same place; the map names that place with `data.place`, while the place note does not list its maps.
 
-**The Scene is made in Foundry.** Walls, lights, sounds, regions, levels and pins are drawn in Foundry's Scene editor, exported, and carried by the note at `data.scene`. The build passes the Scene through: it applies `data.fixup`, binds pins marked `#anchor` to this note's pages, and checks nothing else inside it.
+**The Scene is made in Foundry.** Walls, lights, sounds, regions, levels and pins are drawn in Foundry's Scene editor, exported, and carried by the note at `data.scene`. The build passes the Scene through: it applies the fixups — `data.fixup` and `data.thumbnail` — binds pins marked `#anchor` to this note's pages, and checks nothing else inside it.
 
 **subType**:
 
@@ -4718,6 +4873,7 @@ A subtype says what kind of map the note is. Every subtype carries an exported S
 | `fixup[].path`  | `string`, required        | The exported field to replace, as a property path from `data.scene`                                                                                                                                                                                                  |
 | `fixup[].type`  | `address`, required       | What `value` is                                                                                                                                                                                                                                                      |
 | `fixup[].value` | `Address`, required       | The asset Address whose path replaces the exported one                                                                                                                                                                                                               |
+| `thumbnail`     | Address                   | The map's thumbnail, an `image` Address written into the Scene's `thumb` as a fixup — see [The thumbnail](#the-thumbnail)                                                                                                                                            |
 | `place`         | Address                   | Depicted place, when one exists                                                                                                                                                                                                                                      |
 
 `data.scene` must be an object, and that is the only check made of it: its keys
@@ -4775,6 +4931,32 @@ data:
 # Big Bad Wolf {#myanchor1}
 ```
 
+#### The thumbnail
+
+`data.thumbnail` names the picture Foundry shows for the Scene in its
+directory and compendium lists. It is an `image` Address, and a bare shortcode
+reads as one: `thumbnail: wolfdenthumb` names `image-wolfdenthumb`. An Address
+of any other type, `icon` included, is an error at the key.
+
+The thumbnail is a fixup the note does not have to spell. The map vocabulary
+declares that `thumbnail` belongs in the Scene's `thumb`, so the build adds
+`{ path: ".thumb", type: address, value: <thumbnail> }` to the note's fixups
+and applies it with the rest: the Address must resolve, and the exported Scene
+must carry `thumb`, as every Foundry export does. A `data.fixup` entry whose
+`path` is also `.thumb` is an error, because one would overwrite the other.
+The thumbnail is independent of the background art, which keeps its exported
+path or its own fixup.
+
+```yaml
+data:
+  thumbnail: wolfdenthumb
+  scene:
+    name: Wolf Den Scene
+    thumb: null
+    levels:
+      - { _id: defaultLevel0000, background: { src: modules/maps/den.webp } }
+```
+
 When the Scene has pins, its Adventure bundle carries the Scene and the JournalEntry generated from its Markdown. Importing that bundle preserves the IDs the pins address. The maps naming one `data.place` share one Adventure.
 
 #### A map in the book
@@ -4800,11 +4982,12 @@ level with no background prints nothing.
 | `data` property                   | Values                                                                           | Description                                                                                               |
 | --------------------------------- | -------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
 | `events`                          | event entries — see [Events](#events)                                            | What happened to or at this subject: dated, attributed events                                             |
-| `calendar`                        | `Address`                                                                        | Calendar note used to print this place's dates                                                            |
+| `calendar`                        | `Address`                                                                        | Calendar note that prints this place's dates                                                              |
 | `demonym`                         | `string`                                                                         | What a person from this place is called — a Vylarian                                                      |
 | `purpose`                         | `placeCharacter` tag                                                             | The reason a settlement, site, or structure exists                                                        |
 | `lore`                            | `Address[]`                                                                      | Lore concerning this place — its peoples, its law, its calendar, its history                              |
 | `parents`                         | `Address[]`                                                                      | Enclosing places within which this place is located                                                       |
+| `culture`                         | `Address`                                                                        | The people this place belongs to, naming a lore note with `subType: culture`                              |
 | `population`                      | `number`                                                                         | Approximate population (precision 2 significant digits)                                                   |
 | `government`                      | `Address` or `null` (default type: `affiliation`)                                | Governing affiliation; explicit null means complete anarchy. Omission warns only for positive population. |
 | `market`                          | `number`                                                                         | Market class, 1 to 6 — what trade a settlement supports                                                   |
@@ -5102,6 +5285,11 @@ urban.
 
 **A place declares what is true of its ground.** It names its governing affiliation
 in `data.government`; maps name the place they depict through `data.place`.
+A place may name the people it belongs to in `data.culture`. A place that names
+none takes its culture from its `data.parents`, so a region states the culture
+once and the districts and settlements inside it carry it without repeating it;
+[Culture in the index](#culture-in-the-index) gives the rule and a worked
+example.
 The place's `lore` links cover its peoples, calendar, law and history. Political
 languages belong to a polity's `sohl.system.commonSkills`, while the note's
 `description` provides its page summary.
@@ -5136,9 +5324,22 @@ Content prepared to be played — a situation with its cast, places, and possibl
 - reference: Out-of-world lookup material about the setting or system — correspondences, conversions, glossaries.
 - howto: A task with an outcome, written as the steps that reach it.
 - concept: An explanation of how something works and why it is shaped that way, read to understand rather than to follow.
-- settingguide: An orientation to a setting or region, bringing its places, peoples, institutions, and daily life into one usable frame with links to detailed notes.
-
-A `doc` declares no properties of its own.
+- settingguide: A culture's guide to the setting, which names its culture in `data.culture`. It orients a reader to a setting or region, bringing its places, peoples, institutions, and daily life into one usable frame with links to detailed notes.
+
+| `data` property | Values    | Description                                                                                                           |
+| --------------- | --------- | --------------------------------------------------------------------------------------------------------------------- |
+| `culture`       | `Address` | `settingguide` only, and required there: the culture the guide introduces, naming a lore note with `subType: culture` |
+
+A setting guide introduces one culture's view of the setting, so it names that
+culture, and a `doc` of any other `subType` has no culture of its own to name.
+A setting guide without `data.culture` is an error at its `subType:` line;
+`data.culture` on any other `doc` subType is an error at its key. The value
+names a `lore` note of `subType: culture`, and a setting guide's culture is the
+one it states: it inherits nothing, because a `doc` has no `data.parents`. The
+other notes that may state a culture are described under
+[`place`](#type-place), [`affiliation`](#type-affiliation) and
+[`lore`](#type-lore), and [Culture in the index](#culture-in-the-index) gives
+the value each one reads as.
 
 Choose `settingguide` for an entry point that stands on its own while guiding
 players and GMs into a setting. A `concept` explains one subject, a `reference`
@@ -5154,6 +5355,8 @@ name: { full: The Reed Flats Guide }
 type: doc
 subType: settingguide
 description: A starting point for adventures in the Reed Flats.
+data:
+  culture: lore-reedfolk
 ---
 
 The Reed Flats are a network of marsh settlements linked by river trade.