@heroiclands/package-build 23.0.0 → 23.1.1

package/docs/reference/format-details.md

@@ -120,20 +120,45 @@ in a compendium journal with no further edit. A `Name` row stands first on
 every note, because every note has one. An `Aliases` row follows it when the
 note names any aliases, preserving their authored order.
 
-A few keys carry no row, and the reason in each case is one of exactly two —
+A few keys carry no row, and the reason in each case is one of exactly three —
 the key is **machinery**, steering a build or an interface rather than
-describing the subject, or it is an **image**, which rule 2 keeps out of the
-box:
-
-| key                      | why it carries no row                            |
-| ------------------------ | ------------------------------------------------ |
-| `templatePriority`       | template machinery, not a fact about the subject |
-| `color`                  | sidebar machinery, not a fact about the subject  |
-| the art slots, `overlay` | an image, which rule 2 keeps out of the box      |
-
-A field whose value is a **mapping** carries no row either — a governance
-ladder or a wall layout has no summary shape — and neither does one the note
-left empty.
+describing the subject; it is an **image**, which rule 2 keeps out of the box;
+or it is a **source system's own detail**, which no surface's box shows:
+
+| key                                                                          | why it carries no row                                      |
+| ---------------------------------------------------------------------------- | ---------------------------------------------------------- |
+| `templatePriority`                                                           | template machinery, not a fact about the subject           |
+| `color`                                                                      | sidebar machinery, not a fact about the subject            |
+| `id`                                                                         | document identity machinery, not a fact about the subject  |
+| `pack`, `packFolder`                                                         | compendium routing machinery, not a fact about the subject |
+| `events`                                                                     | chronology machinery, not a summary row                    |
+| 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                |
+
+**A field whose value holds maps is drawn by what its declaration says the
+maps are**, and a map is never set as text:
+
+- **A map with declared keys** takes one row per key that holds a value, in
+  declared order, labelled by the key and carrying its value. A list of words under a key is one row of
+  them, comma-joined. A key holding nothing — `null`, `""`, `[]` — takes no
+  row, and a map with nothing to show takes none at all.
+- **A map keyed by Address** relates the note to others: `socialTies` and an
+  affiliation's `relations` take one row per term — `Patron`, `Rival`,
+  `Aligned` — whose value is the targets, each linked.
+- **A map keyed by Shortcode** weighs each thing it names: a mystery's
+  `skillAptitudes` is one row, each skill linked with its weight beside it —
+  `Sword (+5)`, `Combat skills (-2)`.
+- **A list of maps** keeps the rendering its field was built for — a place's
+  `borders` and `routes` as linked places with their bearings, an affiliation's
+  `governance.ranks` and `governance.offices` as one row per rung or post — or
+  is withheld above as machinery.
+
+**A being's memberships are a section of their own**, titled
+**Affiliations**, after the profile rows: one line per membership, in the
+order the note writes them — `War Chief, Hárár (5), of Vrystwald Tribes`. See
+[the bodies a being belongs to](#the-bodies-a-being-belongs-to-and-its-standing-in-each).
 
 A being's `age`, `height`, `weight` and `appearance.*` compose into a single
 **Appearance** clause rather than taking six rows of their own: _Age 34, 6′ 1″,
@@ -230,12 +255,12 @@ A section says how it is arranged, and a renderer switches on that and on a
 value's `kind` — never on a field name, which is what keeps a field list from
 leaking back into a template.
 
-| `layout` value | shape                           | what carries it | where it is used           |
-| -------------- | ------------------------------- | --------------- | -------------------------- |
-| `rows`         | label/value pairs, one per line | `rows`          | a profile                  |
-| `grid`         | short label/value cells         | `cells`         | attributes, armour aspects |
-| `runin`        | groups of comma-joined entries  | `groups`        | skills, equipment          |
-| `list`         | one entry per line              | `entries`       | mystical abilities         |
+| `layout` value | shape                           | what carries it | where it is used                          |
+| -------------- | ------------------------------- | --------------- | ----------------------------------------- |
+| `rows`         | label/value pairs, one per line | `rows`          | a profile                                 |
+| `grid`         | short label/value cells         | `cells`         | attributes, armour aspects                |
+| `runin`        | groups of comma-joined entries  | `groups`        | skills, equipment                         |
+| `list`         | one entry per line              | `entries`       | mystical abilities, a being's memberships |
 
 | `kind` value | the value is                    |
 | ------------ | ------------------------------- |
@@ -248,6 +273,9 @@ leaking back into a template.
 A website renders a link by its `url`, a compendium journal by its `uuid`, and
 the book by the `address`, which is the entry's own label in the volume. A
 reference the index could not reach keeps its words rather than being dropped.
+An entry of a `runin` group or a `list` section is a link, and may carry a
+`lead`: plain text set before it, so a membership line — `Captain, Blade (4), of
+The Silent Talon Company` — links the body's name and nothing else.
 
 **Emitted shape**, as a page's front matter carries it:
 
@@ -263,11 +291,18 @@ infoboxes:
           - label: Name
             kind: text
             value: Brànwâal Dôrgaar
-          - label: Affiliations
+          - label: Homes
             kind: links
             value:
-              - text: The Silent Talon Company
-                url: /thalorna/affiliation-slntlncmpny/
+              - text: Vylar
+                url: /thalorna/place-vylar/
+      - id: affiliations
+        label: Affiliations
+        layout: list
+        entries:
+          - lead: "Captain, Blade (4), of "
+            text: The Silent Talon Company
+            url: /thalorna/affiliation-slntlncmpny/
   - id: sohl
     kind: system
     system: sohl
@@ -350,6 +385,27 @@ flow collection is formatted into one of those forms; folded collections are
 not used. `package-build format --write` applies this rule and the top-level
 order without changing the Markdown body.
 
+#### What checks a system block
+
+A system block — `sohl:` or `hm3:` — is checked against that system's own
+field schema: the fields the system declares for each document type, with
+their shapes. None of the `data:` vocabulary applies inside it, the inner-key
+rule included, and a key the system's schema does not declare is an error at
+its own line.
+
+A block is checked only where both of these hold:
+
+- **The package declares the system** — under `systems:`, as a pack's
+  `system:`, or as the system the package is or requires. A block for a system
+  the package does not declare is not checked.
+- **The system's fields are known.** The `sohl:` block is held to the note
+  schemas the build carries; any other system's block is held to the
+  `itemBuilders` registry that declares it. Where a declared system has
+  neither, the lint says that system's block is unchecked, and a key inside it
+  is discarded at compile.
+
+A `dnd5e:` block has no field schema, so nothing checks it.
+
 #### Dates and calendars
 
 A canonical date is `<year>[.<day>[:HHMMSS]]`. The day is one-based within the world's year, bound against `data.year.days` on the world's `place` note. A tree whose notes declare no world year bounds no day: the value is read as written, however large. `720` covers the whole year; `720.136` covers that day; `720.136:143005` identifies one second. Negative years are valid. Prefix either form with `~` to express uncertainty beyond its written interval. `unknown` is allowed only in fields that accept an unknown occurrence.
@@ -408,11 +464,28 @@ subject — a weapon's weight, an affliction's transmission, a being's species
 and every note type declares which keys it may carry. A misspelled key is a
 finding in either region.
 
+**So is every map inside it, at every depth.** A field whose value holds maps
+— a map such as `harnworld`, a list of maps such as `borders` or `months`, a map
+keyed by Address whose values are maps such as `affiliations` — declares the
+keys those maps take, which of them are required, and what each holds. A key a
+field does not declare is an error at that key's own line and column, however
+deeply it is nested: `data.governance.offices.Chancellor.holders[0].stat` is
+refused at `stat`, with the declared key it was probably meant to be. A
+required key left out is an error at the map that should carry it, and a value
+of the wrong kind is an error at the value. A dotted property such as
+`appearance.eye_color` closes its container the same way, so `appearance`
+takes only the keys the type's table lists. The
+[note-type reference](note-types.md) tabulates every inner key, generated from
+the same declarations the lint reads; an event's keys are tabulated under
+[Events](#events). Two things are outside this rule. A system block follows its
+own schema — see [What checks a system block](#what-checks-a-system-block). A
+map note's `data.scene` is an exported Foundry Scene and keeps Foundry's own
+keys; its table row says so, beginning **Keys not declared here:**.
+
 Every note type may put a pinned document id in `data.id`, a shared compendium
-route in `data.pack`, a shared folder Address in `data.packFolder`, and source
-details in `data.harnworld`. A system block's `pack` or `packFolder` overrides
-the shared value for that system. A `being` may also describe its social profile
-in `data.social`.
+route in `data.pack`, a shared folder Address in `data.packFolder`, and its
+HârnWorld source details in `data.harnworld`. A system block's `pack` or
+`packFolder` overrides the shared value for that system.
 
 **Tags are open, except the ones that classify.** A tag naming a theme or a region — `underworld`,
 `byzaria`, `riverlands` — is the author's own and this build has no opinion about it.
@@ -693,10 +766,10 @@ the art it writes (`emitsArt`). A second table of iconless types would be a tabl
 free to drift from what is actually emitted, which is the defect rather than the
 check.
 
-#### The four art slots
+#### The art slots
 
 A note declares the art its document needs, and every other image in it is
-inline. All four slots are ordinary `Address` fields declaring a default type,
+inline. Every slot is an ordinary `Address` field declaring a default type,
 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.
@@ -705,10 +778,9 @@ link uses.
 | ----------- | ------------ | --------------- | ----------------------------- | ----------------------------------------- |
 | `icon`      | `icon`       | `icon`, `image` | `document.img`                | every Actor/Item type, and embedded items |
 | `tokenIcon` | `icon`       | `icon`, `image` | `prototypeToken.texture.src`  | Actor types                               |
-| `bgImage`   | `image`      | `icon`, `image` | `background.src`              | map types                                 |
 | `banner`    | `image`      | `icon`, `image` | the site hero image, 1792×768 | any note; not a Foundry field             |
 
-All four are authored under `data:`:
+Every slot is authored under `data:`:
 
 ```yaml
 data:
@@ -718,8 +790,8 @@ data:
 
 **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`, `bgImage` and `banner` default to `image`, and all four accept `icon`
-**and** `image` regardless of which one they default to. A bare shortcode still
+`icon`, `banner` defaults to `image`, and every slot accepts `icon` **and**
+`image` regardless of which one it defaults to. A bare shortcode still
 takes the slot's default — `icon: anvil` above names an `icon`, not an `image`
 — and it is a **qualified** value, one that states its own type, that the
 accepted set governs. `sohl-kethira-basic` writes an `icon` slot this way
@@ -733,7 +805,7 @@ data:
 
 That value is accepted because `image` is in the slot's accepted set, not
 because it matches the default — `icon` still defaults to `icon`. `audio` is
-refused at all four slots: a sound is not art, and a value naming one — `icon:
+refused at every slot: a sound is not art, and a value naming one — `icon:
 audio-thunder`, say — is an error naming the set the slot accepts, never a
 silent fall back to the note's default art.
 
@@ -743,22 +815,35 @@ 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`            | `Map<string, unknown>` | HârnWorld source details.                                            |
-| `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.                        |
+| `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.         |
+
+`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
+the religions it observes. Both are optional. The infobox does not show either.
+
+```yaml
+data:
+  harnworld:
+    realm: Kaldor
+    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.
 
-The other two are narrower, and each type's own table names them: `tokenIcon`
-on the Actor types, `bgImage` on a map.
+`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.
 
 **A portrait is not one of them.** A picture of the subject is a picture, so it
 is authored in the prose that describes the subject, as an ordinary embedded
@@ -937,8 +1022,8 @@ whole `assets/` tree and the directory names inside it are its own business:
 is that package's by the same rule that claims `icons/…` and `images/…`.
 
 **Where a pathname is still authored, it follows this rule.** That is the
-address of an image in a note's body, and a map note's `overlay`. The art
-fields do not: `icon`, `tokenIcon`, `bgImage` and `banner` name
+address of an image in a note's body. The art fields do not: `icon`,
+`tokenIcon` and `banner` name
 addresses, and the path comes from the record the resolved address points at —
 which already carries the owning package, so there is nothing for a first
 segment to state.
@@ -958,9 +1043,8 @@ exists.
 
 No other art slot states a size, and none of them asks anything of a picture's
 dimensions. An `icon` is drawn at a nominal size per medium whatever its file
-holds; a map's `bgImage` sets its own scene's dimensions, so it is whatever size
-the map is; and a picture written in prose is fitted to the room it has. Those
-three accept whatever they are given.
+holds, and a picture written in prose is fitted to the room it has. Both accept
+whatever they are given.
 
 It is an `Address` all the same, defaulting to type `image`, so a section note
 writes `banner: skillbnr` and a note borrowing another package's plate writes
@@ -1514,8 +1598,9 @@ information, because the field already said what kind of thing it points at.
 
 The frontmatter lint checks scalar Addresses, entries in Address lists, and
 Address map keys at the entry's own location. Segments contain lowercase ASCII
-letters and digits; wikilink brackets, labels, anchors, and spaces do not belong
-in these fields. Optional null values and empty lists or maps express no
+letters and digits; wikilink brackets, labels and spaces do not belong in these
+fields, and an anchor belongs only in a field that accepts one — see _Anchors_
+below. Optional null values and empty lists or maps express no
 reference. Grammar and accepted types are checked independently of whether a
 target exists.
 
@@ -1555,7 +1640,7 @@ a candidate to weigh — it takes the default outright, every time — and the
 accepted set is what a value that states its own type is checked against
 instead: naming any member of the set is as valid as naming the default
 itself, and naming a type outside it is an error against the set, never
-against the default alone. [The four art slots](#the-four-art-slots) are
+against the default alone. [The art slots](#the-art-slots) are
 declared exactly this way — each one accepts a second type beyond the one a
 bare shortcode takes.
 
@@ -1579,6 +1664,52 @@ Brackets belong in prose, where a link sits inside a sentence and needs marking
 off from the words around it. A frontmatter value has nothing to be marked off
 from.
 
+#### Anchors
+
+An Address may end in `#<anchor>`, naming a place inside the note it addresses —
+a section of its prose, or one of its events. Every written form takes one:
+
+```text
+thalorna-note-place-ironfells#sack   the full Address, anchored
+place-ironfells#sack                 type and shortcode, anchored
+ironfells#sack                       a bare shortcode, where the field supplies the type
+```
+
+The anchor is read the same way in a frontmatter field and in a wikilink: it is
+everything after the first `#`, and what precedes it is an ordinary Address.
+
+**Every anchor has one of two kinds**, from what declares it:
+
+| anchor kind | declared by                                                                                     |
+| ----------- | ----------------------------------------------------------------------------------------------- |
+| `prose`     | any `{#slug}` in the note's body — on a heading, a caption, a block, an alert, a poem or a span |
+| `event`     | the `id` of an entry in `data.events` — see [Events](#events)                                   |
+
+**A note's anchors are one namespace.** An event's `id` that equals any other
+anchor slug in the same note is an error at the `id`, as two equal headings
+already are.
+
+**A frontmatter field accepts an anchor only where it declares the kinds it
+takes.** Every other Address field refuses `#<anchor>` with an error at that
+value. A field keyed by Address takes none, so an Address map key is always a
+plain Address. The fields that take one:
+
+| field                                 | anchor kinds | without an anchor                                      |
+| ------------------------------------- | ------------ | ------------------------------------------------------ |
+| `events[].follows[].event`            | `event`      | names a note holding exactly one event                 |
+| `events[].where.reach[].attributedTo` | `event`      | names a lore note, or a note holding exactly one event |
+| `made`, `lost` (every gear type)      | `event`      | names a note holding exactly one event                 |
+| `subjects` (a `literature` note)      | `event`      | names a note of any type, as every subject does        |
+
+An anchored Address resolves when its note resolves, declares that anchor, and
+the anchor's kind is one the field takes. Each failure has its own message: the
+note does not resolve; the note declares no such anchor; or the anchor is a
+`prose` anchor, not an `event` one.
+
+**A wikilink names a `prose` anchor only.** `[[lore-crown#founding|the founding]]`
+where `founding` is an event's `id` is an error at the link, on every surface:
+prose links to the note, not to an event. Write `[[lore-crown|the founding]]`.
+
 ### Wikilinks
 
 A **`Wikilink`** is how body prose names something:
@@ -1900,7 +2031,7 @@ replacement is consulted **before** the local address; a foreign lookup only
 
 **An asset type exists so a note can name a file and a package can substitute
 it.** Nothing about a font answers to either half. No note names a typeface —
-the art slots are `icon`, `tokenIcon`, `bgImage` and `banner` — and substituting
+the art slots are `icon`, `tokenIcon` and `banner` — and substituting
 one package's font for another's is not something anyone wants.
 
 **Neither consumer of a font can use an address.** A stylesheet names a file
@@ -2118,7 +2249,7 @@ so adding a type means answering the question rather than inheriting a default.
 relations rather than page links**: a border with a stub on the far side is a
 valid statement about the world and resolves. So does `parents` for the
 containment tree and `government` for governance — a stub appears in its region's
-`contains` and its governing body's `governed_places`, rendered as plain text. What a stub
+**Within** and its governing body's **Governed places**, as plain text. What a stub
 cannot be is the target of a wikilink, because a wikilink points at a page.
 
 ### What a note produces
@@ -2298,7 +2429,9 @@ The contraband is behind the false wall.
 ```
 
 The section runs from the heading to the next heading that opens a page, which
-is the span Foundry makes one page of.
+is the span Foundry makes one page of. A captioned item inside the section is
+withheld with it in Foundry: its own page and the page that resumes the section
+after it are visible to the GM alone.
 
 | Surface | What a reader meets                                                                                               |
 | ------- | ----------------------------------------------------------------------------------------------------------------- |
@@ -2453,6 +2586,12 @@ resolves it to what that surface serves:
 A fenced `sql` block renders a table from the content index. A query that
 selects no rows is a build error unless its fence states `{allow-empty=true}`.
 
+**An Address is a string in every relation**: the full canonical Address, with
+`#<anchor>` where it carries one. A fence compares one as it is written —
+`list_contains(data.parents, 'thalorna-note-place-xerathia')`,
+`data.government = p.address.canonical` — in this package's `notes` and in each
+dependency's alike, although the published index writes each as an object.
+
 SQL fences query the content index through DuckDB. The SQL dialect is DuckDB's.
 
 ````markdown
@@ -2509,6 +2648,41 @@ The ladder is what makes "how finished is this?" a query:
 SELECT state, count(*) AS n FROM entries GROUP BY state ORDER BY state
 ```
 
+**`events`** is one row per event — per entry of `data.events` on every
+`lore`, `place` and `affiliation` note, stubs included — so a chronology is a
+query rather than a list kept by hand:
+
+````markdown
+```sql
+SELECT note AS _ref, "when" AS "When", summary AS "What happened"
+FROM events
+WHERE kind IN ('war', 'siege', 'battle')
+ORDER BY whenSort
+```
+````
+
+| Column                   | What it holds                                                                                                                                                                                                               |
+| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `note`                   | The canonical Address of the note the event is written on.                                                                                                                                                                  |
+| `address`                | The event's own Address: `note#id` where the event has an `id`, the note's Address alone where it has none.                                                                                                                 |
+| `id`, `kind`, `depth`, … | Every key of an event, each its own column under its own name — `id`, `kind`, `depth`, `when`, `until`, `recurs`, `summary`, `standing`, `names`, `where`, `who`, `follows`, `accounts`, `unresolved`, `sources`, `stated`. |
+| `whenSort`, `untilSort`  | The date's position on the canonical axis: the canonical year, with a day as its fraction of the year where the calendar states the year's length. `ORDER BY whenSort` is date order.                                       |
+| `whenYear`, `untilYear`  | The canonical year alone, for a filter such as `whenYear BETWEEN 200 AND 299`.                                                                                                                                              |
+
+`when` and `until` read as the text the note wrote, `~` included. The sort
+keys and years are positions on the canonical axis, which counts a year `0`
+that written dates do not: a year written after zero keeps its number, and one
+written before zero sits one higher, so `when: -250` has a `whenYear` of
+`-249`. `_ref` takes a note's Address, never an anchored one, so a table links
+each row through `note` rather than `address`. A key no
+event writes is still a column, `NULL` in every row, and so is a sort key for
+a date with no position on the axis — `unknown`, or a year-`0` day that recurs
+every year. Every Address is a string, as in every other relation, and a list
+stays a list: `list_contains("where".locus, 'thalorna-note-place-ironfells')`.
+`when` and `where` are SQL keywords, so a query names those columns in double
+quotes, `"when"` and `"where"`. A note tagged `gm` contributes no row on a
+public surface.
+
 **`market`** is the six-step market scale as a relation — `value`, `name`,
 `trade` — so a table prints `village` beside the number a note wrote without a
 second copy of the scale living in authored content.
@@ -2546,6 +2720,7 @@ ORDER BY name.full
 ```
 ````
 
+Its events are `sohl.events`, read exactly as this package's own `events`.
 This package's own notes stay at the unqualified `notes`, and a query may read
 both at once — joining your beings against the skills they cite is one `FROM`
 clause. It needs no fetch and no configuration: a dependency's published index
@@ -2667,9 +2842,9 @@ Each numbered type has its own counter. Websites and Foundry number within a not
 
 `{{ref "#trade"}}` displays the numbered label as a link. `form="full"` includes caption text and `form="title"` displays the caption alone. Use title form for an unnumbered caption. Cross-note references can name the note address before the anchor, such as `{{ref "place-harbor#trade"}}`; the displayed number belongs to the target on the surface rendering it. Links inside caption text contribute their visible text to references, so the reference does not contain a nested link.
 
-Foundry gives a captioned item its own JournalEntryPage. A solitary image with a plain caption can use an image page; captions with inline markup and other items use text pages. On the website and in the book the item stays in the flow of the surrounding page.
+Foundry gives a captioned item a JournalEntryPage holding the item alone, named for its number or, unnumbered, for the caption's visible text — links and emphasis reduced to the words a reader sees. A solitary image with a plain caption can use an image page; captions with inline markup and other items use text pages. The body after the item resumes on a continuation page carrying the interrupted section's name, level and classes, with its title hidden; nothing is emitted when the next page begins straight after the item. On the website and in the book the item stays in the flow of the surrounding page.
 
-**Migration:** `:::figure` is no longer supported. Move the former `///` caption before the item as `:@ Caption {#id}` and remove the figure wrapper. To caption a group or passage, put it inside a generic fenced div and caption that div with an explicit type if needed. `///` is no longer a caption delimiter.
+To caption a group or passage, put it inside a generic fenced div and caption that div, with an explicit type where the inferred one does not fit.
 
 ##### Fenced divs
 
@@ -2733,8 +2908,6 @@ Attributes follow the marker and apply to the alert:
 
 Use `#id`, `.class` and named attributes in the shared braced grammar. The marker determines the default label, icon and color. An authored `title` replaces the default **Note**, **Tip**, **Important** or **Warning** heading while preserving the alert type’s icon and color. Event-handler attributes, malformed attributes, unknown alert types and empty alert bodies are errors. Ordinary blockquotes and alert examples inside literal code remain unchanged. A leading caption can describe an alert as a quote block, normally with the `prose` type or an explicit `example` type.
 
-Migrate former info blocks to `[!NOTE]` alerts and warn blocks to `[!WARNING]` alerts. The old named fences are errors. `:::secret` remains supported.
-
 ##### Secret blocks
 
 `:::secret` sets GM material apart. Its optional attributes accept an identifier, classes and named attributes. `title` supplies its heading; without a title the heading is **Secret**:
@@ -2792,6 +2965,380 @@ All item types, including affiliation, affliction, armor, armorlocation, attribu
 
 An Item can mark its readable description with `# ... {#description}`. That heading starts a JournalEntryPage even when other pages precede it. Its Address is `<package>-note-<type>-<shortcode>#description`; the compiler resolves it to one `@UUID[...]` pointer. SoHL stores that pointer in `system.docHtml`, and HM3 stores the same pointer in `system.description` for Item subtypes that declare the field. An Item without this anchor points to its first page. Other pages remain addressable by their own anchors.
 
+### Events
+
+An **event** is one dated, attributed record of something that happened in the setting — a founding, a war, a fall, a plague, a birth. It is an entry in `data.events`, and three types carry that list: `lore`, `place` and `affiliation`. There is no event note type. A note holds the events that belong to it: a history note holds the event it describes, a place holds its raising and its ruin, an affiliation its founding and its dissolution. The schema is the same on all three types and on every subType.
+
+Every key of an entry is closed, and so is every key of each map nested in one. A key this section does not list is an error at that key, and a value outside a key's closed list is an error at that value. Every Address an entry writes resolves in this package or a declared dependency, or it is an error at that Address.
+
+An event appears on its note's page and in its Foundry journal as prose the note's body writes, and in the [event views](#event-views) the build appends to the notes it concerns. Nothing derived from it reaches a system field, an infobox row or a page's front matter, which carries `data.events` only as the note wrote it. The content index carries each entry's resolved dates under `resolvedDates.events`, and the [`events`](#content-tables) relation holds one row per entry.
+
+#### The keys of an event
+
+| event key    | shape                                | required  | what it records                                                            |
+| ------------ | ------------------------------------ | --------- | -------------------------------------------------------------------------- |
+| `id`         | address segment                      | see below | The event's name within its note — lowercase letters and digits            |
+| `kind`       | one `eventKind` value                | no        | What sort of thing happened                                                |
+| `depth`      | one `depth` value                    | no        | How far the event's history reaches                                        |
+| `when`       | a date, or `"0.<day>"`               | yes       | When it happened, or the anchor and first instance of an event that recurs |
+| `until`      | a date                               | no        | When a continuous event ended, or where a recurring series stopped         |
+| `recurs`     | `{ every }` or `{ on }`              | no        | How further occurrences are found; absent for an event that happened once  |
+| `summary`    | string                               | yes       | What happened, stated plainly                                              |
+| `standing`   | one `standing` value                 | no        | What the world's evidence supports                                         |
+| `names`      | `{ name, by, gloss? }[]`             | no        | The event's names in the world, each with who uses it                      |
+| `where`      | `{ locus?, reach? }`                 | no        | Where it happened, and where it was felt                                   |
+| `who`        | `{ ref, role }[]`                    | no        | Who took part, and as what                                                 |
+| `follows`    | `{ event, how, note? }[]`            | no        | The earlier events this one follows from                                   |
+| `accounts`   | `{ by, says, agrees, withholds? }[]` | no        | What each people, polity, faith or place says about it                     |
+| `unresolved` | string list                          | no        | What the world itself has not settled                                      |
+| `sources`    | Address list                         | no        | The notes that state or support the event; each resolves                   |
+| `stated`     | `{ calendar, text }`                 | no        | The date as one tradition writes it in its own reckoning                   |
+
+The nested entries, each closed the same way:
+
+| nested key                   | shape                                                                              | required | what it records                                                                           |
+| ---------------------------- | ---------------------------------------------------------------------------------- | -------- | ----------------------------------------------------------------------------------------- |
+| `names[].name`               | string                                                                             | yes      | One name the event goes by in the world                                                   |
+| `names[].by`                 | Address naming an `affiliation`, `lore`, `place`, `being` or `skill` note          | yes      | Who uses that name — a people, a polity, a faith, a place, a tongue; resolves             |
+| `names[].gloss`              | string                                                                             | no       | What the name means, or how it is used                                                    |
+| `where.locus`                | list of Addresses, each defaulting to `place`                                      | no       | Where the event physically happened; each must resolve to a place                         |
+| `where.reach`                | `{ place, how, knowledge, attributedTo? }[]`                                       | no       | Where the event was felt, and whether each place knows why                                |
+| `where.reach[].place`        | an Address, defaulting to `place`                                                  | yes      | A place where the event was felt; must resolve to a place                                 |
+| `where.reach[].how`          | string                                                                             | yes      | One clause: a consequence someone in that place could notice                              |
+| `where.reach[].knowledge`    | one `knowledge` value                                                              | yes      | Whether that place connects what it felt to this event                                    |
+| `where.reach[].attributedTo` | Address, defaulting to `lore`, naming an event or a `lore` note                    | no       | Only beside `knowledge: misattributed` — the cause that place names instead; resolves     |
+| `who[].ref`                  | Address naming a `being`, `affiliation` or `lore` note                             | yes      | A participant — a being, a people, an affiliation; resolves                               |
+| `who[].role`                 | one `role` value                                                                   | yes      | What the participant was to the event                                                     |
+| `follows[].event`            | Address, defaulting to `lore`, anchored to an `event` where its note holds several | yes      | The earlier event; resolves to exactly one event                                          |
+| `follows[].how`              | one `followsHow` value                                                             | yes      | How this event follows from it                                                            |
+| `follows[].note`             | string                                                                             | no       | One clause saying what connects the two                                                   |
+| `accounts[].by`              | Address naming an `affiliation`, `lore`, `place` or `being` note                   | yes      | Who holds the account; resolves                                                           |
+| `accounts[].says`            | string                                                                             | yes      | What they say happened, in their terms                                                    |
+| `accounts[].agrees`          | one `agrees` value                                                                 | yes      | How far their account agrees with `summary`                                               |
+| `accounts[].withholds`       | string                                                                             | no       | What they decline to say                                                                  |
+| `stated.calendar`            | Address, or a lore shortcode                                                       | yes      | The calendar that tradition reckons in — a `lore` note with `subType: calendar`; resolves |
+| `stated.text`                | string                                                                             | yes      | The date as that tradition writes it                                                      |
+| `recurs.every`               | whole number of years, 1 or more                                                   | —        | A period counted on the canonical axis from `when`                                        |
+| `recurs.on`                  | list of dates, strictly increasing, each later than `when`                         | —        | Recorded occurrences beyond the first, in place of a period                               |
+
+`where.locus` and `where.reach[].place` default to `place`, so a bare shortcode there is read as one — `vale` is `place-vale` — and whatever the written form, the Address must resolve to a place note; one resolving to an affiliation, a lore note or anything else is an error at that key. `follows[].event`, `where.reach[].attributedTo` and `stated.calendar` default to `lore` in the same way, so `fallkhazturn` is `lore-fallkhazturn`. `who[].ref`, `accounts[].by` and `names[].by` state their type, and the type must be one their row names; a note of any other type is an error at that key naming the types it takes. `sources` takes a note of any type, written with its type: `lore-khazarfolk`, never `khazarfolk`. No Address is a bare name such as `The Vale`. `where.locus` in particular is never filled in from the note the event sits on — an event on a place is not assumed to have happened there, so a `locus` is written or absent.
+
+#### Identity, and how an event is addressed
+
+An event's `id` is an [anchor](#anchors) of kind `event`, in the one namespace the note's headings and blocks share. An event is addressed as its note's address when the note holds one event, and as `<note address>#<id>` when it holds several: `lore-thebargain`, `place-ironfells#sack`, `affiliation-crown#founding`.
+
+- `id` is an address segment — lowercase ASCII letters and digits, nothing else.
+- `id` is unique within its note, and differs from every heading, caption and block anchor the note declares.
+- `id` is **required on every entry of a note holding two or more events**, and optional on a note holding one.
+
+A note's prose prints one field of an event with an inline reference, `{{ref "place-ironfells#sack" field="when"}}`: the event's `when` or `until` as the note format prints a date, its `kind`, its `summary`, or the first of its `names`, as text and never a link, identically on every surface. The address names one event as a `follows[].event` does, or `"#<id>"` for one of the note's own. An address naming no event, a `prose` anchor, a `field` outside those five, or a field the event does not state is an error at the reference's position. The [authoring guide](../authoring/links-and-markup.md#an-events-date-inline) has examples.
+
+A `follows[].event` resolves to exactly one event: a note holding one event, or `note#id`. Naming a note that holds several events without an `id` is an error, and so is naming an anchor the note does not declare or one that is not an event. An Address into another package is checked the same way against that package's published index, which carries each note's anchors with their kinds and each event's date.
+
+#### Generated sections
+
+The build appends sections to the end of a note's body, after everything the author wrote, each an H1 with a fixed anchor holding Markdown an author could have written. Every surface sets one as it sets an authored section: a page of the Foundry journal, a section of the website page listed in its table of contents, a section of the book.
+
+| Section           | Anchor           | On                                                       | Content                                                                                                                               |
+| ----------------- | ---------------- | -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
+| Within            | `within`         | a `place`                                                | the places whose `data.parents` names it, one paragraph to each kind of place, in the order the place vocabulary lists its `subType`s |
+| Governed by       | `governedby`     | a `place`                                                | the affiliation its `data.government` names, as a list entry with the affiliation's kind                                              |
+| Governed places   | `governedplaces` | an `affiliation`                                         | the places whose `data.government` names it, grouped as **Within** groups them                                                        |
+| Chronology        | `chronology`     | a `place`                                                | an [event view](#event-views)                                                                                                         |
+| Events            | `events`         | a `being`, an `affiliation`, a `lore` note of `culture`  | an event view                                                                                                                         |
+| Accounts          | `accounts`       | an `affiliation`, a `place`, a `lore` note of `culture`  | an event view                                                                                                                         |
+| What followed     | `followed`       | a note holding events                                    | an event view                                                                                                                         |
+| In song and story | `insongandstory` | any note                                                 | the `literature` works whose `data.subjects` name the note or one of its events, as list entries with each work's `data.form`         |
+| From here         | `fromhere`       | a `place` that states, or is named in, a border or route | the map drawn from the place, as an image                                                                                             |
+
+- **Sections follow the author's text in the order of the table.**
+- **A section with nothing to show is not generated.**
+- **An author's own section replaces a generated one.** A note whose body declares a prose anchor with the section's slug — `# Within {#within}`, or a block or span with that `id` — gets no generated section for it, and its own section is left exactly as written. This is the one way to turn a section off, and the way to choose different contents for it.
+- **An entry is a link to the note it names**, written `[[<address>|]]` so each surface resolves it and shows the note's current name. An entry naming a stub, which publishes no page, is its name as plain text. The lists take in the places, affiliations and works a fetched index carries.
+- **The map is a drawing the build makes**, named `generated/from-<shortcode>.svg`. The website sets it inline so its place names are links, the Foundry compile stages it into the module at `assets/generated/`, and the book draws it beside its source. `generated/` is the build's: an authored image addressed there is an error. `site.maps: false` gives no place the section.
+- A stub publishes no page and is given no section.
+
+#### Event views
+
+The build appends sections to the end of a note's body that list the events concerning it — a region's chronology, the events a being took part in, the accounts a people gives, what followed an event. Each is an H1 with a fixed anchor holding a `sql` fence over the `events` relation, the same Markdown an author could write, so every surface sets it as it sets an authored section: a page of the Foundry journal, a section of the website page in its table of contents, a section of the book.
+
+| View          | Anchor       | On                                                               | Rows                                                                                                                                                                              | Columns                            |
+| ------------- | ------------ | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- |
+| Chronology    | `chronology` | a `place`                                                        | events whose `where.locus` names the place or a place below it in `parents`; events whose `where.reach` names one, with that entry's `how`; every `depth: world` event as context | What happened, When, Felt here     |
+| Events        | `events`     | a `being`, an `affiliation`, a `lore` note of `subType: culture` | events whose `who[].ref` names the note, with the role it played                                                                                                                  | What happened, When, Role          |
+| Accounts      | `accounts`   | an `affiliation`, a `place`, a `lore` note of `subType: culture` | each `accounts[]` entry the note gives, with the event it concerns                                                                                                                | Event, When, What they say, Agrees |
+| What followed | `followed`   | a note holding events                                            | events whose `follows[].event` names one of this note's events, with how                                                                                                          | What followed, When, How           |
+
+- **The views follow everything the author wrote**, in the order of the [generated sections](#generated-sections).
+- **A view with no rows is not generated.** A chronology is generated only where the place has rows of its own; the world events beside them are context and make no chronology by themselves.
+- **An author's own section replaces a view.** A note whose body declares a prose anchor with the view's slug — `# Chronology {#chronology}`, or a block or span with that `id` — gets no generated section for it, and its own section is left exactly as written. This is the one way to turn a view off, and the way to choose a different table: write the section and its own `sql` fence.
+- Places below a place are found by walking `parents` down from it, so an event felt in towns under two continents is in each continent's chronology and each region's.
+- A stub publishes no page and gets no view. The views read this package's own events; a dependency's are read with a fence over `<package>.events`.
+
+#### What sort of event: `kind`
+
+`kind` is closed. The groups are for reading; the list is one list.
+
+| `eventKind` value | the event is                                                                         |
+| ----------------- | ------------------------------------------------------------------------------------ |
+| `arrival`         | A people or group comes to live in a land it did not hold                            |
+| `departure`       | A people or group leaves a land it held                                              |
+| `migration`       | A people moves over a long span, through or across several lands                     |
+| `contact`         | Two peoples meet for the first time, or after all memory of each other is lost       |
+| `displacement`    | A people is driven from its land by force or by catastrophe                          |
+| `founding`        | A polity, order, settlement or other body comes into being                           |
+| `charter`         | A body's rights, bounds or constitution are granted or written                       |
+| `accession`       | A ruler or a ruling house takes power                                                |
+| `secession`       | A part breaks away from the body that held it                                        |
+| `conquest`        | One power takes and holds another's land or people by force                          |
+| `treaty`          | Powers bind themselves by agreement — a peace, a league, a lease, a bargain          |
+| `dissolution`     | A body ceases to exist, by decision, absorption or decay                             |
+| `battle`          | One engagement between armed forces                                                  |
+| `war`             | A sustained armed conflict, spanning engagements                                     |
+| `siege`           | A fortified place is invested and held under attack                                  |
+| `revolt`          | Subjects rise against the power that rules them                                      |
+| `fall`            | A city, people or power is destroyed or overthrown                                   |
+| `catastrophe`     | A natural or magical disaster — a flood, an eruption, a working that escapes control |
+| `plague`          | A sickness spreads through a population                                              |
+| `famine`          | Food fails across a land                                                             |
+| `raising`         | A structure or settlement is built — a city, a wall, a temple, a road                |
+| `ruin`            | A structure or settlement falls into ruin or is razed                                |
+| `making`          | An object, work or artefact is made                                                  |
+| `loss`            | An object, work or body of knowledge is lost                                         |
+| `discovery`       | Something is found or first learned — a land, a route, a secret, a working           |
+| `schism`          | A faith, order or school divides                                                     |
+| `law`             | A law, code or decree is made or abolished                                           |
+| `council`         | An assembly meets and decides                                                        |
+| `birth`           | A person is born                                                                     |
+| `death`           | A person dies                                                                        |
+
+A place's raising and its ruin are `raising` and `ruin` events on that place; an affiliation's founding and dissolution are `founding` and `dissolution` events on that affiliation.
+
+#### How far it reaches: `depth`
+
+| `depth` value | the event                                                 |
+| ------------- | --------------------------------------------------------- |
+| `world`       | Has to be accounted for by more than one region's history |
+| `region`      | Is held by one region's history                           |
+| `local`       | Belongs to one place, one being or one legend             |
+
+`depth` is set by hand and never derived. The test for `world` is not importance but reach of accounting: an event is `world` when more than one region's history has to account for it, and anything a single region can hold is that region's. A `local` event is met on the page of the place, being or legend it belongs to.
+
+#### What happened, and how sure the world is: `summary` and `standing`
+
+`summary` states the event plainly, in one or two sentences, with no hedging — not "it is said that", not "may have", not "legend holds". Doubt does not go in the summary. It goes in `standing`, in `accounts` and in `unresolved`.
+
+| `standing` value | the world's evidence                                                        |
+| ---------------- | --------------------------------------------------------------------------- |
+| `attested`       | More than one independent tradition records it                              |
+| `single-source`  | One tradition records it, and nothing contradicts it                        |
+| `reconstructed`  | No tradition states it; it is worked out from other records                 |
+| `disputed`       | Traditions disagree that it happened, or on a particular the event turns on |
+| `legendary`      | What is established is that a story exists, not that the thing happened     |
+
+`legendary` changes what `summary` describes: on a `legendary` event the summary describes the story, truthfully, because the story existing is the fact.
+
+`standing` is independent of how precisely the date is written. A well-attested event can carry an approximate century, and a reconstructed one can carry an exact year because the arithmetic that places it is exact. The date's grain is in how it is written — `280` is the year, `280.25` the twenty-fifth day, `~280` around 280.
+
+#### Where: `where.locus` and `where.reach`
+
+`locus` is where the event physically happened — usually one place, occasionally a few, such as a battle on a border or a treaty signed in two cities. It is not the region that owns the event; no region owns one.
+
+`reach` is where the event was felt, and each entry has to earn its place. **A reach entry exists only when its `how` clause can state a consequence someone in that place could notice.** "It mattered there" is not a reach entry; "the holds lost half their smiths within a generation" is. A place that felt nothing has no entry — there is no value for "unaffected", because an absent row already says so.
+
+| `knowledge` value | in that place                                                                                          |
+| ----------------- | ------------------------------------------------------------------------------------------------------ |
+| `named`           | Its own record names this event as the cause of what it felt                                           |
+| `misattributed`   | Its record names a different cause, given in `attributedTo` — the people there are wrong, not ignorant |
+| `unlinked`        | The consequence is felt, and no tradition there connects it to anything                                |
+
+`attributedTo` is written only beside `misattributed`, and names what that place blames instead: an event — a note holding one, or `note#id` — or a `lore` note, such as a people or a belief.
+
+#### Who: `who`
+
+`who` lives on the event, never on the participant, so a being's or a people's part in events is found by reading the events that name it rather than by listing them on its own note. A people is a legitimate participant: much of a deep past happens to peoples rather than to named individuals. An unnamed participant is not a row — a person the record cannot name is a clause in `summary` and, where who they were is open, a line in `unresolved`.
+
+| `role` value | the participant                                                                                |
+| ------------ | ---------------------------------------------------------------------------------------------- |
+| `actor`      | Did it                                                                                         |
+| `victim`     | Had it done to them                                                                            |
+| `instrument` | Was the means by which it was done, without being its author — a host driven, a weapon wielded |
+| `witness`    | Saw it, and is a source of what is known                                                       |
+| `founder`    | Brought into being what the event founds                                                       |
+| `ruler`      | Held the authority under which it happened, or the authority it confers                        |
+| `author`     | Wrote or composed what the event makes — a law, a charter, a work                              |
+| `signatory`  | Is a party bound by the agreement it records                                                   |
+
+#### Names: one event, several names
+
+An event known by several names in the world is one event with several names, never several events. The note's own `name` is the neutral name the chronology sorts by; `names` carries every in-world name with the people, polity, faith or place that uses it.
+
+`names` and `accounts` vary independently, which is why they are two keys: a people can share an event's name and dispute what happened, or use a name of its own and agree entirely. A defeat in one chronicle and a deliverance in another is one event whose `names` differ and whose `accounts` differ.
+
+#### What is believed: `accounts`, `withholds` and `unresolved`
+
+Each `accounts` entry attributes one reading of the event: who holds it (`by`), what they say (`says`), how far they agree with `summary` (`agrees`), and what they decline to say (`withholds`).
+
+| `agrees` value | the account                                                                      |
+| -------------- | -------------------------------------------------------------------------------- |
+| `full`         | Agrees with the summary                                                          |
+| `partly`       | Agrees in substance and differs in particulars                                   |
+| `disputes`     | Holds that it happened, and otherwise than the summary says                      |
+| `denies`       | Holds that it did not happen                                                     |
+| `silent`       | Says nothing of it where it could — a silence stated as a fact, not an ignorance |
+
+**`withholds` and `unresolved` record different things.** `withholds` is a people declining to say, which is a fact about that people and sits on that people's account. `unresolved` is the world not having settled the question, which is a fact about the world and sits on the event. Who made a weapon is `unresolved`; that the people who used it will not discuss it is `withholds`. Each `unresolved` line is a plain statement of something open, not a hedge.
+
+#### Consequence: `follows`
+
+`follows` is written on the later event only, and names the earlier one. Whoever writes the later event is the one who knows what it follows from, and what followed from an event is found by reading the edges that name it, so nothing is lost by writing each edge once.
+
+| `followsHow` value | this event                                      |
+| ------------------ | ----------------------------------------------- |
+| `caused`           | Would not have happened without the earlier one |
+| `enabled`          | Was made possible by it, not inevitable         |
+| `ended`            | Terminates a state the earlier one began        |
+| `answered`         | Is a deliberate response to it                  |
+
+Two rules hold the graph together, and both are errors when broken:
+
+- **An edge points backward in time.** The event an edge names is no later than the event writing it, comparing the two `when` dates. Two dates that both state a day compare by day; otherwise they compare by year, so a year and a day inside it are never out of order. An edge touching a `when` with no position on the axis — `unknown`, or a year-`0` date — is not ordered.
+- **The graph has no cycle.** No chain of edges leads from an event back to itself, across notes or within one.
+
+A consequence is an edge, not a second event. A consequence with no date of its own is a `reach` entry, if it is felt somewhere, or a `follows` edge, if it is a later event's cause — never a new event recording the same thing twice.
+
+#### Dates: `when`, `until` and `recurs`
+
+An entry reads by what it authors beside `when`:
+
+| authored                          | reads as                                        |
+| --------------------------------- | ----------------------------------------------- |
+| `when`                            | happened once                                   |
+| `when` + `until`                  | ran continuously from then to then              |
+| `when` + `recurs`                 | happened then and happens still                 |
+| `when` + `until` + `recurs.every` | happened then, again on the period, and stopped |
+
+`recurs.every` and `recurs.on` are exclusive — a period with named exceptions is written as an enumeration instead. `recurs` is refused beside a `when` of year `0`, and a being's `born` and `died` take no `recurs`. `until` is refused beside `recurs.on`, whose own last entry already bounds it.
+
+**The period advances the canonical year, never the era-relative year.** There is no year `0` in era-relative numbering — era year `-1` sits immediately before era year `1` — but canonical year `0` is an ordinary integer on the continuous axis `canonicalYear` builds, so a period of whole years steps on it with no special case at an epoch crossing. Precision and approximation carry through untouched: a year-precision anchor yields year-precision occurrences, an approximate anchor's occurrences are approximate too, and an anchor inside a short intercalary month recurs on that same day in every occurrence, with no special case for the month being short. Each occurrence selects its own era by testing its position against the anchor's calendar, so a later occurrence may print in a different era than its anchor, or print bare where no count was proclaimed for that year — neither is ever a finding, since nobody authored the occurrence.
+
+**Year `0` means any year.** An entry whose `when` states year `0` recurs on that day of every year — `when: "0.5"` is the fifth day of the year, in every year. The value must be quoted, for the reason every canonical date stating a day must be: an unquoted `<year>.<day>` reaches the check as a float, and a day's trailing zero is lost before a date is read. Beside a year-`0` entry, `recurs` is refused (the entry is already annual), `until` is allowed and bounds the series, and the entry carries no `canonicalYear`, era or `sort` — it cannot date its own note. A note's date is its first entry stating a real year.
+
+```yaml
+data:
+  events:
+    - id: anniversary
+      when: "412.1"
+      recurs: { every: 1 }
+      summary: The city keeps the day of its founding.
+    - id: harvestrite
+      when: "0.286"
+      until: "940.1"
+      summary: The harvest rite is kept on the two-hundred-eighty-sixth day of the year.
+```
+
+The first entry is an anniversary counted from canonical day `412.1`, recurring every year with no end. The second is an autumn rite — the two-hundred-eighty-sixth day of every year — kept until canonical year 940.
+
+`stated` records the date as one tradition writes it, beside the canonical `when` every event carries: `when` is what sorts and compares, and `stated.text` is what that tradition's own records say, in the calendar `stated.calendar` names.
+
+#### A complete event
+
+One `lore` note, `lore-fallkhazturn`, holding one event with every key written:
+
+```yaml
+shortcode: fallkhazturn
+name: { full: The Fall of Khazarturn }
+type: lore
+subType: history
+data:
+  events:
+    - kind: fall
+      depth: world
+      when: ~-2427
+      summary: >-
+        An outlaw takes up the Second Voice and drives the Grukar against
+        Khazarturn. Every inhabitant is killed, and the Khazari seal the city as
+        a tomb.
+      standing: attested
+      names:
+        - name: The Sealing
+          by: lore-khazarfolk
+          gloss: what the Khazari call it
+        - name: the Outlaw's Work
+          by: lore-sinalefolk
+      where:
+        locus: [khazarturnvale]
+        reach:
+          - place: ironfells
+            how: the holds lose half their smiths within a generation
+            knowledge: named
+          - place: place-grukarholm
+            how: tribes arrive on the coast driven off ground they will not name
+            knowledge: unlinked
+          - place: place-aelwyth
+            how: the joint kingdom's two peoples stop speaking
+            knowledge: misattributed
+            attributedTo: lore-oldcompact
+      who:
+        - { ref: lore-khazarfolk, role: victim }
+        - { ref: lore-sinalefolk, role: actor }
+        - { ref: lore-grukarfolk, role: instrument }
+      follows:
+        - event: place-khazarturn#raising
+          how: ended
+          note: the city stands two and a half millennia before it falls
+      accounts:
+        - by: lore-khazarfolk
+          says: The Sinale did this; one of theirs held the Voice, and they never said it existed.
+          agrees: partly
+          withholds: whether anyone tends the city since it was sealed
+        - by: lore-sinalefolk
+          says: One of ours did it, and we hunted him down ourselves.
+          agrees: partly
+          withholds: the outlaw's name and his fate
+        - by: lore-worldthalorna
+          says: Something shattered the old peace in an age before memory.
+          agrees: silent
+      unresolved:
+        - who made the Second Voice, and why neither people ever said it existed
+        - what remains inside the sealed city
+      sources: [lore-khazarfolk, lore-sinalefolk]
+      stated: { calendar: khazarcal, text: "the 900th year of the Delving" }
+```
+
+#### A note holding two events
+
+A place holds its own raising and its own fall, so each needs an `id`, and an event elsewhere names one of them by `note#id`:
+
+```yaml
+shortcode: khazarturn
+name: { full: Khazarturn }
+type: place
+subType: settlement
+data:
+  events:
+    - id: raising
+      kind: raising
+      depth: region
+      when: ~-4900
+      summary: The Khazari cut the first halls of Khazarturn into the valley wall.
+      where: { locus: [place-khazarturn] }
+    - id: sealing
+      kind: ruin
+      depth: local
+      when: ~-2427
+      summary: The Khazari seal the gates of the dead city.
+      where: { locus: [place-khazarturn] }
+      follows:
+        - event: place-khazarturn#raising
+          how: ended
+        - event: lore-fallkhazturn
+          how: caused
+          note: the dead are laid in their own chambers before the gates are closed
+```
+
+`place-khazarturn#sealing` follows both the city's own raising, inside the same note, and `lore-fallkhazturn`, a note holding one event and so addressed by the note alone. Both edges point backward: the raising is millennia earlier, and the fall shares the sealing's year.
+
 ### type: being
 
 Generates a living (or undead, or spirit) being.
@@ -2805,34 +3352,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                                                                                                                    |
-| `social`                    | `Map<string, unknown>`                         | The being's social profile                                                                                                                            |
-| `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                                                                 |
-| `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                                                                                                                    |
+| `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                                                                                                                                        |
 
 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
@@ -2901,9 +3449,18 @@ each an error naming the file, line and column — so a renamed rung or a rename
 post 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 the standing closing on its body — `War Chief, Hárár, of
-Vrystwald Tribes` — and links an office to the description the body itself
-declares, so recording the post needs no note about the post.
+The infobox prints one line per membership, in the order the note writes them,
+in a section of its own titled **Affiliations**: the office where one is held, then the rung's
+title with its level in parentheses, then the body — `War Chief, Hárár (5), of
+Vrystwald Tribes`, or `Hárár (5), of Vrystwald Tribes` with no office. The title
+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
+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
@@ -3086,7 +3643,7 @@ An embedded custom item writes its identity in `system.shortcode`; a top-level `
 #### An entry's art
 
 An entry is an item in every respect but where it is written, so it carries art
-by the two rules [an item note](#the-four-art-slots) does. It names an `icon`
+by the two rules [an item note](#the-art-slots) does. It names an `icon`
 address under its own `data:`, and that resolves into the embedded document's
 `img`:
 
@@ -3335,22 +3892,35 @@ rank names the standing, and the standing says.
 
 **Standing**: aligned, unaligned, rival, nemesis
 
-| `data` property      | Values                                             | Description                                                                                    |
-| -------------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
-| `templatePriority`   | `number`                                           | Template priority, _null_ = not a template                                                     |
-| `demonym`            | `string`                                           | What a member of this affiliation is called (a Vylarian)                                       |
-| `epithet`            | `string`                                           | The by-name it is known by — a god's, an order's, a company's                                  |
-| `symbol`             | `string`                                           | Its emblem in words: a feather atop a golden scale, a chisel carving a star                    |
-| `governance.model`   | `GovernanceModel`                                  | Type of government structure, if applicable                                                    |
-| `governance.summary` | `string`                                           | summary of the governance situation                                                            |
-| `governance.ranks`   | `Rank[]`                                           | The ranks available to members of the affiliation                                              |
-| `governance.offices` | `Map<name, description \| {description, holders}>` | Official offices and their dated holders                                                       |
-| `seat`               | `Address`                                          | Where the affiliation's authority sits                                                         |
-| `population`         | `number`                                           | Number of people in the affiliation (precision 2 significant digits).                          |
-| `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                                           |
-| `relations`          | `Map<Address, Standing>`                           | Standing with other affiliations, keyed by the other body's Address                            |
+| `data` property                                 | Values                                             | Description                                                                                    |
+| ----------------------------------------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
+| `templatePriority`                              | `number`                                           | Template priority, _null_ = not a template                                                     |
+| `events`                                        | event entries — see [Events](#events)              | What happened to or at this subject: dated, attributed events                                  |
+| `demonym`                                       | `string`                                           | What a member of this affiliation is called (a Vylarian)                                       |
+| `epithet`                                       | `string`                                           | The by-name it is known by — a god's, an order's, a company's                                  |
+| `symbol`                                        | `string`                                           | Its emblem in words: a feather atop a golden scale, a chisel carving a star                    |
+| `governance.model`                              | `GovernanceModel`                                  | Type of government structure, if applicable                                                    |
+| `governance.summary`                            | `string`                                           | summary of the governance situation                                                            |
+| `governance.ranks`                              | `Rank[]`                                           | The ranks available to members of the affiliation                                              |
+| `governance.ranks[].level`                      | `integer`, required                                | The rung's position on this body's ladder; a member's `rank` names it                          |
+| `governance.ranks[].title`                      | `string`, required                                 | What the standing is called                                                                    |
+| `governance.ranks[].description`                | `string`, required                                 | What the standing is                                                                           |
+| `governance.ranks[].lore`                       | `Address`                                          | The `law` lore note stating what the standing is, shared with every body that confers it       |
+| `governance.offices`                            | `Map<name, description \| {description, holders}>` | Official offices and their dated holders                                                       |
+| `governance.offices.<name>`                     | `string` or `{ description, holders }`             | One office, keyed by its name: its description, or a map of description and holders            |
+| `governance.offices.<name>.description`         | `string`, required                                 | What the office is                                                                             |
+| `governance.offices.<name>.holders`             | `{ being, start?, end?, contested? }[]`, required  | Who has held the office, each with the dates of the term                                       |
+| `governance.offices.<name>.holders[].being`     | `Address`, required                                | The `being` who held it                                                                        |
+| `governance.offices.<name>.holders[].start`     | `date`                                             | When the term began; omitted, it began before anything recorded                                |
+| `governance.offices.<name>.holders[].end`       | `date`                                             | When the term ended; omitted, the being holds the office now                                   |
+| `governance.offices.<name>.holders[].contested` | `boolean`                                          | `true` where the term may overlap another holder's                                             |
+| `seat`                                          | `Address`                                          | Where the affiliation's authority sits                                                         |
+| `population`                                    | `number`                                           | Number of people in the affiliation (precision 2 significant digits).                          |
+| `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                                           |
+| `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         |
 
 **A faith tradition is not its god.** An `affiliation` of subType
 `faithtradition` is a _religion_ — a practice, with an ordained priesthood, a
@@ -3405,7 +3975,7 @@ data:
           - { being: being-mara, start: "datefrom vrcal 2 Lusenar 725 VR" }
 ```
 
-**Governed places are derived from place notes.** Each place names one governing affiliation in `data.government`. The website writes the body's `governed_places` list by resolving those explicit references across local notes and fetched indexes. Each entry is `{ title, url, type, subType }`, sorted by `subType` then `title`; an empty list is omitted. No affiliation-side list supplies government, and neither geographic containment nor organizational parents expands it.
+**Governed places are derived from place notes.** Each place names one governing affiliation in `data.government`. The affiliation's **Governed places** [generated section](#generated-sections) lists the places whose explicit references resolve to it, across local notes and fetched indexes, grouped by kind; with none, it has no such section. No affiliation-side list supplies government, and neither geographic containment nor organizational parents expands it.
 
 If `sohl` is present, this becomes an `affiliation` item.
 
@@ -3544,13 +4114,15 @@ for traumas produced by the affliction's outcome. The optional
 
 Note: `data.quantity` may not be specified. Quantity is always 1.
 
-| `data` property    | Values   | Description                                |
-| ------------------ | -------- | ------------------------------------------ |
-| `templatePriority` | `number` | Template priority, _null_ = not a template |
-| `weight`           | `number` | Gear weight                                |
-| `value`            | `number` | Gear value                                 |
-| `quality`          | `number` | Gear quality                               |
-| `durability`       | `number` | Gear durability                            |
+| `data` property    | Values           | Description                                                                   |
+| ------------------ | ---------------- | ----------------------------------------------------------------------------- |
+| `templatePriority` | `number`         | Template priority, _null_ = not a template                                    |
+| `weight`           | `number`         | Gear weight                                                                   |
+| `value`            | `number`         | Gear value                                                                    |
+| `quality`          | `number`         | Gear quality                                                                  |
+| `durability`       | `number`         | Gear durability                                                               |
+| `made`             | an event Address | The event in which it was made — `lore-forging`, or `place-ironfells#raising` |
+| `lost`             | an event Address | The event in which it was lost — `lore-flood`, or `place-ironfells#sack`      |
 
 If a `sohl` property is present, a SoHL item of type "armorgear" is created.
 
@@ -3563,6 +4135,16 @@ The note type is `armorgear` in both systems.
 | `data.quality`    | `system.qualityBase`    | NA              |
 | `data.durability` | `system.durabilityBase` | NA              |
 
+Every gear type — `armorgear`, `concoctiongear`, `containergear`, `miscgear`,
+`projectilegear` and `weapongear` — may name the events of the thing's history:
+`made`, the event in which it was made, and `lost`, the event in which it was
+lost. Each is an Address of exactly one [event](#events): `note#id`, or a note
+holding one event. A bare shortcode is read as a `lore` note, so
+`made: forging` is `lore-forging`. Naming a note that holds several events
+without an `id`, a note holding none, an anchor the note does not declare, or
+a `prose` anchor is an error at that key. Neither reaches a system field, an
+infobox row or a page: each is a fact a content table can read.
+
 ### type: armorlocation
 
 | `data` property    | Values   | Description                                |
@@ -3594,16 +4176,18 @@ if a `sohl` property is present, a SoHL item of type "attribute" is created.
 - exotic: A complex and valuable concoction, often a mixture of different herbs and/or chemicals, with medicinal or other unique properties or effects, but not magical in nature.
 - elixir: An arcane alchemical concoction of great power.
 
-| `data` property    | Values                          | Description                                       |
-| ------------------ | ------------------------------- | ------------------------------------------------- |
-| `templatePriority` | `number`                        | Template priority, _null_ = not a template        |
-| `weight`           | `number`                        | Gear weight                                       |
-| `value`            | `number`                        | Gear value                                        |
-| `quality`          | `number`                        | Gear quality                                      |
-| `durability`       | `number`                        | Gear durability                                   |
-| `quantity`         | `number`                        | Gear quantity (default: 1)                        |
-| `potency`          | `na \| mild \| strong \| great` | Concoction Potency (mundane/exotic concoctions)   |
-| `strength`         | `number`                        | Strength: higher the number, greater the strength |
+| `data` property    | Values                          | Description                                                                   |
+| ------------------ | ------------------------------- | ----------------------------------------------------------------------------- |
+| `templatePriority` | `number`                        | Template priority, _null_ = not a template                                    |
+| `weight`           | `number`                        | Gear weight                                                                   |
+| `value`            | `number`                        | Gear value                                                                    |
+| `quality`          | `number`                        | Gear quality                                                                  |
+| `durability`       | `number`                        | Gear durability                                                               |
+| `made`             | an event Address                | The event in which it was made — `lore-forging`, or `place-ironfells#raising` |
+| `lost`             | an event Address                | The event in which it was lost — `lore-flood`, or `place-ironfells#sack`      |
+| `quantity`         | `number`                        | Gear quantity (default: 1)                                                    |
+| `potency`          | `na \| mild \| strong \| great` | Concoction Potency (mundane/exotic concoctions)                               |
+| `strength`         | `number`                        | Strength: higher the number, greater the strength                             |
 
 if a `sohl` property is present, a SoHL item of type "concoctiongear" is created.
 
@@ -3622,14 +4206,16 @@ if a `sohl` property is present, a SoHL item of type "concoctiongear" is created
 
 Note: `data.quantity` may not be specified; quantity is always set to 1.
 
-| `data` property    | Values   | Description                                |
-| ------------------ | -------- | ------------------------------------------ |
-| `templatePriority` | `number` | Template priority, _null_ = not a template |
-| `weight`           | `number` | Gear weight                                |
-| `value`            | `number` | Gear value                                 |
-| `quality`          | `number` | Gear quality                               |
-| `durability`       | `number` | Gear durability                            |
-| `capacity`         | `number` | HM3 container capacity (in lbs)            |
+| `data` property    | Values           | Description                                                                   |
+| ------------------ | ---------------- | ----------------------------------------------------------------------------- |
+| `templatePriority` | `number`         | Template priority, _null_ = not a template                                    |
+| `weight`           | `number`         | Gear weight                                                                   |
+| `value`            | `number`         | Gear value                                                                    |
+| `quality`          | `number`         | Gear quality                                                                  |
+| `durability`       | `number`         | Gear durability                                                               |
+| `made`             | an event Address | The event in which it was made — `lore-forging`, or `place-ironfells#raising` |
+| `lost`             | an event Address | The event in which it was lost — `lore-flood`, or `place-ironfells#sack`      |
+| `capacity`         | `number`         | HM3 container capacity (in lbs)                                               |
 
 if a `sohl` property is present, a SoHL item of type "containergear" is created.
 
@@ -3647,14 +4233,16 @@ SoHL reads a container’s capacity in pounds from `sohl.maxCapacity`.
 
 ### type: miscgear
 
-| `data` property    | Values   | Description                                |
-| ------------------ | -------- | ------------------------------------------ |
-| `templatePriority` | `number` | Template priority, _null_ = not a template |
-| `weight`           | `number` | Gear weight                                |
-| `value`            | `number` | Gear value                                 |
-| `quality`          | `number` | Gear quality                               |
-| `durability`       | `number` | Gear durability                            |
-| `quantity`         | `number` | HM3 gear quantity (default: 1)             |
+| `data` property    | Values           | Description                                                                   |
+| ------------------ | ---------------- | ----------------------------------------------------------------------------- |
+| `templatePriority` | `number`         | Template priority, _null_ = not a template                                    |
+| `weight`           | `number`         | Gear weight                                                                   |
+| `value`            | `number`         | Gear value                                                                    |
+| `quality`          | `number`         | Gear quality                                                                  |
+| `durability`       | `number`         | Gear durability                                                               |
+| `made`             | an event Address | The event in which it was made — `lore-forging`, or `place-ironfells#raising` |
+| `lost`             | an event Address | The event in which it was lost — `lore-flood`, or `place-ironfells#sack`      |
+| `quantity`         | `number`         | HM3 gear quantity (default: 1)                                                |
 
 if a `sohl` property is present, a SoHL item of type "miscgear" is created.
 
@@ -3764,14 +4352,16 @@ the item’s base mastery and level from `sohl.masteryLevelBase` and
 - dart
 - other
 
-| `data` property    | Values   | Description                                |
-| ------------------ | -------- | ------------------------------------------ |
-| `templatePriority` | `number` | Template priority, _null_ = not a template |
-| `weight`           | `number` | Gear weight                                |
-| `value`            | `number` | Gear value                                 |
-| `quality`          | `number` | Gear quality                               |
-| `durability`       | `number` | Gear durability                            |
-| `quantity`         | `number` | HM3 gear quantity (default: 1)             |
+| `data` property    | Values           | Description                                                                   |
+| ------------------ | ---------------- | ----------------------------------------------------------------------------- |
+| `templatePriority` | `number`         | Template priority, _null_ = not a template                                    |
+| `weight`           | `number`         | Gear weight                                                                   |
+| `value`            | `number`         | Gear value                                                                    |
+| `quality`          | `number`         | Gear quality                                                                  |
+| `durability`       | `number`         | Gear durability                                                               |
+| `made`             | an event Address | The event in which it was made — `lore-forging`, or `place-ironfells#raising` |
+| `lost`             | an event Address | The event in which it was lost — `lore-flood`, or `place-ironfells#sack`      |
+| `quantity`         | `number`         | HM3 gear quantity (default: 1)                                                |
 
 if a `sohl` property is present, a SoHL item of type "projectilegear" is created.
 
@@ -3887,13 +4477,15 @@ build.
 
 Note: `data.quantity` may not be specified. Quantity is always 1.
 
-| `data` property    | Values   | Description                                |
-| ------------------ | -------- | ------------------------------------------ |
-| `templatePriority` | `number` | Template priority, _null_ = not a template |
-| `weight`           | `number` | Gear weight                                |
-| `value`            | `number` | Gear value                                 |
-| `quality`          | `number` | Gear quality                               |
-| `durability`       | `number` | Gear durability                            |
+| `data` property    | Values           | Description                                                                   |
+| ------------------ | ---------------- | ----------------------------------------------------------------------------- |
+| `templatePriority` | `number`         | Template priority, _null_ = not a template                                    |
+| `weight`           | `number`         | Gear weight                                                                   |
+| `value`            | `number`         | Gear value                                                                    |
+| `quality`          | `number`         | Gear quality                                                                  |
+| `durability`       | `number`         | Gear durability                                                               |
+| `made`             | an event Address | The event in which it was made — `lore-forging`, or `place-ironfells#raising` |
+| `lost`             | an event Address | The event in which it was lost — `lore-flood`, or `place-ironfells#sack`      |
 
 if a `sohl` property is present, a SoHL item of type "weapongear" is created,
 carrying every strike mode the weapon has — melee and missile alike — on
@@ -3944,60 +4536,66 @@ the setting itself, rather than instructions or other apparatus for the GM.
 
 Each note a work names in `data.subjects` lists that work on its own site page, under **In
 song and story**, with the work's `form` beside its title; the subject note writes nothing.
+Each subject may name one event, as `place-ironfells#sack`: the anchor must be an `event` anchor
+the note declares, and the work lists on the page of the note that holds the event.
 A work in a fetched index lists on this package's pages when that index carries its
 `subjects`.
 
-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                                                                |
-| `weekdays`              | `{ name, abbreviation? }[]`                                                   | Ordered week days, indexed from zero; weeks run continuously                                                      |
-| `seasons`               | `{ name, abbreviation?, start }[]`                                            | Seasons starting on one-based days of year                                                                        |
-| `namedDays`             | `{ name, abbreviation?, day }[]`                                              | Names assigned to one-based days of year                                                                          |
-| `eras`                  | `{ shortcode, name, abbreviation?, marker?, proclaimedBy?, start, label? }[]` | Year counts; `start` is `null` or an in-calendar year                                                             |
-| `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, events and other notes the work concerns                             |
-| `language`              | `Address`                                                                     | `literature` only: the tongue it is composed in, naming a skill note with `subType: language`                     |
-| `events`                | `{ when, until?, recurs? }[]`                                                 | This note's dated occurrences, each with its own relationships and chronicle fields                               |
-| `events[].when`         | a date, or `"0.<day>"`                                                        | The occurrence's anchor and first instance — required                                                             |
-| `events[].until`        | a date                                                                        | Where the occurrence ran to, or where a recurring series stopped                                                  |
-| `events[].recurs`       | `{ every }` or `{ on }`                                                       | How further occurrences are found, absent for a one-time occurrence                                               |
-| `events[].recurs.every` | whole number of years, 1 or more                                              | A period counted on the canonical axis from `when`                                                                |
-| `events[].recurs.on`    | list of dates, strictly increasing, each later than `when`                    | Recorded occurrences beyond the first, in place of a period                                                       |
-
-`data.events` is available on every `lore` subType. Each entry's `kind`, `depth`, `summary`, `sources`, `standing`, `accounts`, `who`, `where`, `unresolved`, `follows` and `names` hold its chronicle detail; their shapes belong to whatever design governs chronicle records, and this format only asks that they sit inside an entry. The shared format checks `when`, `until` and `recurs`; a content package can check the rest. `events` itself does not appear as an infobox row, but a recurring entry's computed next occurrence does.
-
-An entry reads by what it authors beside `when`:
-
-| authored                          | reads as                                        |
-| --------------------------------- | ----------------------------------------------- |
-| `when`                            | happened once                                   |
-| `when` + `until`                  | ran continuously from then to then              |
-| `when` + `recurs`                 | happened then and happens still                 |
-| `when` + `until` + `recurs.every` | happened then, again on the period, and stopped |
-
-`recurs.every` and `recurs.on` are exclusive — a period with named exceptions is written as an enumeration instead. `recurs` is refused beside `born` or `died`, and beside a `when` of year `0`. `until` is refused beside `recurs.on`, whose own last entry already bounds it.
-
-**The period advances the canonical year, never the era-relative year.** There is no year `0` in era-relative numbering — era year `-1` sits immediately before era year `1` — but canonical year `0` is an ordinary integer on the continuous axis `canonicalYear` builds, so a period of whole years steps on it with no special case at an epoch crossing. Precision and approximation carry through untouched: a year-precision anchor yields year-precision occurrences, an approximate anchor's occurrences are approximate too, and an anchor inside a short intercalary month recurs on that same day in every occurrence, with no special case for the month being short. Each occurrence selects its own era by testing its position against the anchor's calendar, so a later occurrence may print in a different era than its anchor, or print bare where no count was proclaimed for that year — neither is ever a finding, since nobody authored the occurrence.
-
-**Year `0` means any year.** An entry whose `when` states year `0` recurs on that day of every year — `when: "0.5"` is the fifth day of the year, in every year. The value must be quoted, for the reason every canonical date stating a day must be: an unquoted `<year>.<day>` reaches the check as a float, and a day's trailing zero is lost before a date is read. Beside a year-`0` entry, `recurs` is refused (the entry is already annual), `until` is allowed and bounds the series, and the entry carries no `canonicalYear`, era or `sort` — it cannot date its own note. A note's date is its first entry stating a real year.
-
 ```yaml
+shortcode: burningsaga
+name: { full: The Saga of the Burning }
+type: lore
+subType: literature
 data:
-  events:
-    - when: 412.1
-      recurs: { every: 1 }
-    - when: "0.286"
-      until: 940.1
+  culture: lore-ironfolk
+  form: saga
+  subjects: [place-ironfells#sack, place-east, lore-fords]
+  language: skill-ironspeech
 ```
 
-The first entry is an anniversary counted from canonical day `412.1`, recurring every year with no end. The second is an autumn rite — the two-hundred-eighty-sixth day of every year — that was kept until canonical year 940 and no longer is.
+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                                                         |
+
+`data.events` is available on every `lore` subType, and is described in full under [Events](#events).
 
 #### Calendar note structure
 
@@ -4100,39 +4698,40 @@ Braced custom forms such as `{era}` are equivalent to bracketed custom forms. A
 
 ### type: map
 
-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 `sohl.place`, while the place note does not list its maps.
+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.
 
 **subType**:
 
-- `battlemap`: A tactical Scene built in Foundry.
-- `localmap`: A settlement or local-area Scene built in Foundry.
-- `regionalmap`: A large-scale chart with an authored image and scale.
-- `totm`: A gridless image Scene for theatre-of-the-mind play.
-
-| `data` property   | Values       | Description                                                |
-| ----------------- | ------------ | ---------------------------------------------------------- |
-| `scene`           | object       | Exported Foundry Scene for battle and local maps           |
-| `fixup`           | object[]     | Asset address replacements in an exported Scene            |
-| `bgImage`         | Address      | Background image for regional and theatre-of-the-mind maps |
-| `scale`           | object       | Regional distance and unit per grid unit                   |
-| `dimensions`      | `[int, int]` | Optional shared dimensions metadata                        |
-| `pxPerGrid`       | number       | Optional shared grid size metadata                         |
-| `navName`         | string       | Short Scene navigation name                                |
-| `levelName`       | string       | Embedded Level name                                        |
-| `backgroundColor` | string       | Colour outside the art                                     |
-| `overlay`         | string       | Foreground art path                                        |
-| `walls`           | object       | Regional wall geometry                                     |
-| `doors`           | object       | Regional door geometry                                     |
-| `lights`          | object       | Regional light geometry                                    |
-| `tiles`           | object       | Regional tile geometry                                     |
-| `sounds`          | object       | Regional sound geometry                                    |
-| `regions`         | object       | Regional region geometry                                   |
-| `notes`           | object       | Regional pin geometry                                      |
-| `place`           | Address      | Depicted place, when one exists                            |
-
-#### Battle and local maps
-
-Author the Scene in Foundry, export it, convert the export to YAML, and put the resulting object at `data.scene`. Preserve its walls, lights, tiles, regions, levels, environment, flags, and canvas settings. The export can name art from another Foundry package; that path is used as authored in Foundry. The Scene needs positive whole-number `width` and `height`, at least one Level, a valid `initialLevel` when present, and a unique 16-character `_id` on each embedded document. The build derives the top-level Scene `_id` from the map note, adds compendium keys and build metadata, and otherwise preserves the exported fields.
+- `battlemap`: A tactical encounter map.
+- `localmap`: A settlement or local-area map.
+- `regionalmap`: A large-scale chart.
+- `totm`: A single picture for theatre-of-the-mind play.
+
+A subtype says what kind of map the note is. Every subtype carries an exported Scene.
+
+| `data` property | Values                    | Description                                                                                                                                                                                                                                                          |
+| --------------- | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `scene`         | object                    | **Keys not declared here:** the Foundry Scene document, as exported. Its keys are Foundry's Scene schema and are not checked; the build passes the Scene through, and the book reads its levels' background images — see [Exporting the Scene](#exporting-the-scene) |
+| `fixup`         | `{ path, type, value }[]` | Asset address replacements in the exported Scene                                                                                                                                                                                                                     |
+| `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                                                                                                                                                                                                               |
+| `place`         | Address                   | Depicted place, when one exists                                                                                                                                                                                                                                      |
+
+`data.scene` must be an object, and that is the only check made of it: its keys
+are Foundry's Scene schema. A map note declares nothing under its system block.
+
+#### Exporting the Scene
+
+Build the Scene in Foundry, export it, convert the export to YAML, and put the
+resulting object at `data.scene`. Its walls, lights, tiles, sounds, regions,
+levels, environment, flags and canvas settings are preserved as exported. The
+export can name art from another Foundry package; that path is used as authored
+in Foundry. The build derives the top-level Scene `_id` from the map note, adds
+compendium keys to each embedded document that carries an `_id`, adds build
+metadata, and otherwise preserves the exported fields.
 
 A pin's `text` can contain `#anchor`, where the map note has a heading such as `# Big Bad Wolf {#myanchor1}`. With `text: '#myanchor1'`, the compiled pin opens the JournalEntry and page generated from this map note and displays **Big Bad Wolf**. Its position, icon, other settings, and embedded `_id` remain as exported. A missing anchor is a build error. Pins whose text does not use `#anchor` retain their exported text and references.
 
@@ -4166,7 +4765,7 @@ data:
     name: Wolf Den Scene
     width: 1900
     height: 2600
-    grid: { type: 1 size=100 distance: 5 units: ft }
+    grid: { type: 1, size: 100, distance: 5, units: ft }
     initialLevel: defaultLevel0000
     levels:
       - { _id: defaultLevel0000, background: { src: modules/maps/den.webp } }
@@ -4176,20 +4775,15 @@ data:
 # Big Bad Wolf {#myanchor1}
 ```
 
-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.
-
-#### Regional maps
-
-A `regionalmap` uses `data.bgImage`, an image Address, and `sohl.dimensions: [width, height]` plus `sohl.pxPerGrid` to build a gridless Scene. `data.scale: {distance: positive number, unit: nonempty string}` sets the distance per grid unit. Its shared `data` fields can also name `overlay`, `backgroundColor`, `levelName`, `navName`, `walls`, `doors`, `lights`, `tiles`, `sounds`, `regions`, and `notes`; the latter geometry uses the map-note conventions described in the SoHL map authoring guide. `data.scene` is not used for a regional map.
-
-An SVG `data.bgImage` remains vector art on the site and in the book. The Foundry build stages a PNG at the note's stated dimensions with the installed SVG renderer; the source SVG is unchanged. Its aspect ratio must match the stated dimensions. A selected regional SVG map takes a full page in the PDF.
+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.
 
-#### Theatre-of-the-mind maps
+#### A map in the book
 
-A `totm` map names its background with `data.bgImage` and its canvas size with
-`sohl.dimensions: [width, height]`. It builds a gridless Scene with token vision
-off. It needs no `sohl.pxPerGrid` or `data.scale`. The Markdown body remains the
-map's prose.
+A PDF book that selects a map note prints each of its Scene's level backgrounds
+on a landscape page after the entry, titled with the map's name and the level's
+name. The picture is the level's `background.src` with `data.fixup` applied, so
+a level whose background is fixed up to a local asset prints that asset. A
+level with no background prints nothing.
 
 ### type: place
 
@@ -4203,33 +4797,42 @@ map's prose.
 - feature: A place significant by its terrain — forests, rivers, falls, passes, fords.
 - celestial: A body observed from a world rather than located on one — a sun, a planet, a comet.
 
-| `data` property                   | Values                                              | Description                                                                                               |
-| --------------------------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
-| `calendar`                        | `Address`                                           | Calendar note used to print 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                                                       |
-| `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                                                   |
-| `borders`                         | `{ to, bearing }[]`                                 | Places sharing a frontier with this one, and where each lies from here                                    |
-| `routes`                          | `{ to, bearing, mode, days, terrain?, leagues? }[]` | Journeys from this place's centre to another place                                                        |
-| `world.equatorialCircumferenceKm` | `number`                                            | The distance round the body at its equator, in kilometres                                                 |
-| `world.surfaceGravityG`           | `number`                                            | Surface gravity, as a multiple of Earth's                                                                 |
-| `world.axialTiltDegrees`          | `number`                                            | The tilt of the axis, in degrees                                                                          |
-| `year.days`                       | `number`                                            | How many days the body's year holds                                                                       |
-| `year.hoursPerDay`                | `number`                                            | How many hours the day divides into                                                                       |
-| `year.minutesPerHour`             | `number`                                            | How many minutes the hour divides into                                                                    |
-| `year.secondsPerMinute`           | `number`                                            | How many seconds the minute divides into                                                                  |
-| `present`                         | `date`                                              | The day the setting stops and play begins                                                                 |
-| `body.diameterKm`                 | `number`                                            | The body's diameter, in kilometres                                                                        |
-| `body.orbitalRadiusKm`            | `number`                                            | How far it orbits from the body it circles, in kilometres                                                 |
-| `body.orbit`                      | `string`                                            | The orbit's shape — `circular` means the cycle never varies                                               |
-| `body.inclined`                   | `boolean`                                           | Whether the orbit is inclined to the plane the world orbits in                                            |
-| `moon.cycle`                      | `number`                                            | How many days it takes to return to the same phase                                                        |
-| `moon.newOn`                      | day-precision `date`                                | A day it was new, written in the reference calendar                                                       |
-| `moon.eclipses`                   | `string`                                            | `never`, `rare`, `occasional` or `frequent`                                                               |
+| `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                                                            |
+| `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                                                       |
+| `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                                                   |
+| `borders`                         | `{ to, bearing }[]`                                                              | Places sharing a frontier with this one, and where each lies from here                                    |
+| `borders[].to`                    | `Address`, required                                                              | The other place; the type defaults to `place`                                                             |
+| `borders[].bearing`               | `N`, `NE`, `E`, `SE`, `S`, `SW`, `W` or `NW`, required                           | Where the other place lies from here                                                                      |
+| `routes`                          | `{ to, bearing, mode, days, terrain?, leagues? }[]`                              | Journeys from this place's centre to another place                                                        |
+| `routes[].to`                     | `Address`, required                                                              | The other place; the type defaults to `place`                                                             |
+| `routes[].bearing`                | `N`, `NE`, `E`, `SE`, `S`, `SW`, `W` or `NW`, required                           | Where the destination lies from here                                                                      |
+| `routes[].mode`                   | `land`, `boat` or `ship`, required                                               | How the journey is travelled                                                                              |
+| `routes[].days`                   | `1`, `2`, `3`, `5`, `10`, `20`, `30`, `45`, `60`, `90`, `180` or `360`, required | About how many days the journey takes, under normal conditions                                            |
+| `routes[].terrain`                | terrain names, in travel order                                                   | The terrains crossed, each crossable by the mode                                                          |
+| `routes[].leagues`                | `number`                                                                         | The distance, in leagues                                                                                  |
+| `world.equatorialCircumferenceKm` | `number`                                                                         | The distance round the body at its equator, in kilometres                                                 |
+| `world.surfaceGravityG`           | `number`                                                                         | Surface gravity, as a multiple of Earth's                                                                 |
+| `world.axialTiltDegrees`          | `number`                                                                         | The tilt of the axis, in degrees                                                                          |
+| `year.days`                       | `number`                                                                         | How many days the body's year holds                                                                       |
+| `year.hoursPerDay`                | `number`                                                                         | How many hours the day divides into                                                                       |
+| `year.minutesPerHour`             | `number`                                                                         | How many minutes the hour divides into                                                                    |
+| `year.secondsPerMinute`           | `number`                                                                         | How many seconds the minute divides into                                                                  |
+| `present`                         | `date`                                                                           | The day the setting stops and play begins                                                                 |
+| `body.diameterKm`                 | `number`                                                                         | The body's diameter, in kilometres                                                                        |
+| `body.orbitalRadiusKm`            | `number`                                                                         | How far it orbits from the body it circles, in kilometres                                                 |
+| `body.orbit`                      | `string`                                                                         | The orbit's shape — `circular` means the cycle never varies                                               |
+| `body.inclined`                   | `boolean`                                                                        | Whether the orbit is inclined to the plane the world orbits in                                            |
+| `moon.cycle`                      | `number`                                                                         | How many days it takes to return to the same phase                                                        |
+| `moon.newOn`                      | day-precision `date`                                                             | A day it was new, written in the reference calendar                                                       |
+| `moon.eclipses`                   | `string`                                                                         | `never`, `rare`, `occasional` or `frequent`                                                               |
 
 #### Why a place exists
 
@@ -4368,9 +4971,7 @@ a package boundary uses the same terrain and mode rules at both ends.
 For every place that participates in a border or route, the map builder draws
 an itinerary from that place. A site page carries it as a linked SVG. A PDF
 book that includes the place gives its map a separate full page after the
-entry. A configured Foundry Scene pack carries a gridless map backed by a
-generated PNG, with Notes linked to importable place journals. Places with no
-relations create no itinerary output.
+entry. Places with no relations create no itinerary output.
 
 **A relation that crosses a package boundary is written in full at both ends.**
 An omitted `<package>` segment is the package being built, in whatever note the
@@ -4455,7 +5056,7 @@ Write `government: null` for **complete anarchy**. Omitting the key leaves gover
 | Any                   | Explicit `null`     | None; complete anarchy           |
 | Any                   | Affiliation Address | None; the reference must resolve |
 
-These rules apply to every place subtype, including settlements, sites, structures, features, regions and worlds. Empty strings, numbers, lists, maps, references to another note type and unresolved references are errors. They do not declare anarchy. `domains`, `parents`, containment and capitals do not supply a government. Legacy affiliation `data.domains` is accepted temporarily but ignored. Preserve ownership and influence facts in prose; see [government migration](../guides/government-migration.md).
+These rules apply to every place subtype, including settlements, sites, structures, features, regions and worlds. Empty strings, numbers, lists, maps, references to another note type and unresolved references are errors. They do not declare anarchy. `parents`, containment and capitals do not supply a government.
 
 #### Population figures