@heroiclands/package-build 22.9.1 → 22.10.0

package/docs/content-format.md

@@ -94,6 +94,13 @@ column regardless.
 6. **Order is the toolchain's.** A medium renders boxes, sections and rows in
    the order given.
 
+**Embedded models link to documentation in an infobox.** The model Address
+continues to identify the native Item used for compilation. Its displayed link
+uses that same package, type and Shortcode under `none`, which names the
+corresponding documentation journal. A model with no published documentation
+keeps its known name as plain text; the infobox does not substitute an Actor or
+Item link.
+
 #### What the note box holds
 
 **The note box's fields are the type's own `data:` vocabulary, in its declared
@@ -446,17 +453,11 @@ it _there_, and a system that disagrees is not in error. A weapon weighs what
 This is the same rule as `hm3.type` overriding a derived document type, applied
 to fields: derive from the shared source, and let the system state the exception.
 
-**A shared source and the key a system block still carries are two
-declarations.** The mapping tables name the shared source — `data.species` — and
-the corpus writes the same fact inside the block it has always written it in —
-`hm3.species`. Those are two positions for one field, and both are read while
-the corpus moves, with the block winning. A field says so by naming each: its
-shared source, and the legacy in-block key it is being swept off. Reading it
-from the legacy position is _reported_, so the sweep has a progress signal, and
-the note compiles to the identical document either way — the same read-both,
-report-one shape every other retirement in this format uses. As one
-declaration the two would let a field name only one of them, and a row this
-table states would be reachable only by a note that had already moved.
+**A shared source and an in-block key are separate declarations.**
+`data.gender` is the shared source for HM3 gender; `hm3.gender` is its
+in-block spelling, and `hm3.system.gender` is the native destination.
+The native destination wins, followed by the in-block value and the shared
+source. Field declarations name both source and destination explicitly.
 
 **A field whose spelling means something else at the note level has no shared
 source.** The fallback assumes the two vocabularies agree about what a name
@@ -465,9 +466,8 @@ publishes under, while an `affiliation` item's `system.title` is the style of
 address an office carries. Where they diverge, the field declares what the
 top-level key means instead, and the top level stops being read for it — leaving
 `<system>.system.<field>` and the legacy in-block position, which describe the
-document rather than the note. `title` is the one field this applies to; `subType`
-is the other declared item field spelled like a note-level key, and there the two
-levels mean the same thing by design.
+document rather than the note. Native species is independent of the shared lore Address in `data.species`.
+`subType` has the same meaning at both levels.
 
 **Some of a system's fields are runtime state, and a note may not write any of
 them.** A data model declares everything a document stores, and part of that is
@@ -485,13 +485,24 @@ the field rather than a list of names, so it covers every such field a system
 adds later. The per-type tables below never list one — they are the vocabulary
 an author writes — and each type that has any names them under its table.
 
-**A `WikiLink` becomes a shortcode where the target field expects one.** SoHL
-stores cross-references as shortcode strings, which is what the `Code` suffix
-marks: `data.assocSkill` is a link to a skill note, and `system.assocSkillCode`
-holds that note's shortcode. The resolution happens at build time, and a link
-that resolves to nothing is an error naming the note — never a blank field. Where
-a target field has no `Code` suffix, the link is stored as the reference the
-field expects.
+**An `Address` becomes a `Shortcode` where the target field expects one.** SoHL
+resolves a stored cross-reference among the items one actor holds, and packages do
+not exist there, so the field holds a `Shortcode`. Four `affiliation` fields are
+authored as Addresses and stored that way: `data.seat` becomes `system.seat`,
+`data.parents` becomes `system.parents`, `data.domains` becomes `system.domain`,
+and each authored key of `data.relations` becomes a key of `system.relations`. The
+reduction happens at build time, and two things are errors naming the note: an
+Address whose type the field does not accept, and two Addresses that reduce to one
+shortcode, which the field cannot hold both of.
+
+**A `Code` suffix marks a different thing.** `system.assocSkillCode`,
+`system.assocAffiliationCode` and `system.parentSkillCode` hold a `Shortcode` at
+both ends — each is authored as one, under `<system>.system`, and emitted verbatim
+— so no Address is reduced into them and none of them has a shared source. A value
+carrying a separator is refused there by the shortcode charset rather than read as
+an Address. `data.assocSkill`, `data.assocAffiliation` and `data.parentSkill` are
+properties of the **page**: each is an Address naming the note an infobox row
+links to, and none reaches a compiled document.
 
 ### The note vocabulary, and how it maps
 
@@ -575,7 +586,7 @@ destination, so the resolved value is simply dropped — the note validates, the
 tree compiles, and the value goes nowhere.
 
 **What a note writes is an address; what a document carries is a path.**
-`data.icon` is a `WikiLink` defaulting to type `icon`, so a being writes
+`data.icon` is an `Address` defaulting to type `icon`, so a being writes
 `icon: anvil` and never a file name. The compiler resolves that address to the
 file the owning package ships and writes the resulting path into `img`. The two
 sides of this row are therefore in two different currencies, which is why the
@@ -599,17 +610,17 @@ check.
 #### The four art slots
 
 A note declares the art its document needs, and every other image in it is
-inline. All four slots are ordinary `WikiLink` fields declaring a default type,
+inline. All four slots are ordinary `Address` fields 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.
 
-| field       | default type | resolves into                | on                                        |
-| ----------- | ------------ | ---------------------------- | ----------------------------------------- |
-| `icon`      | `icon`       | `document.img`               | every Actor/Item type, and embedded items |
-| `tokenIcon` | `icon`       | `prototypeToken.texture.src` | Actor types                               |
-| `bgImage`   | `image`      | `background.src`             | map types                                 |
-| `banner`    | `image`      | the site hero image          | any note; not a Foundry field             |
+| field       | default type | accepts         | resolves into                | on                                        |
+| ----------- | ------------ | --------------- | ---------------------------- | ----------------------------------------- |
+| `icon`      | `icon`       | `icon`, `image` | `document.img`               | every Actor/Item type, and embedded items |
+| `tokenIcon` | `icon`       | `icon`, `image` | `prototypeToken.texture.src` | Actor types                               |
+| `bgImage`   | `image`      | `icon`, `image` | `background.src`             | map types                                 |
+| `banner`    | `image`      | `icon`, `image` | the site hero image          | any note; not a Foundry field             |
 
 All four are authored under `data:`:
 
@@ -619,16 +630,37 @@ data:
   banner: packagebuild-none-image-skillbnr
 ```
 
+**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
+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
+twenty times, once per faith tradition, because a deity's profile art is a full
+illustration rather than a game icon:
+
+```yaml
+data:
+  icon: image-kpagrik
+```
+
+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:
+audio-thunder`, say — is an error naming the set the slot accepts, never a
+silent fall back to the note's default art.
+
 **Two of them are legal on _every_ note**, whatever its type. `data:` is a
 closed container and the per-type vocabularies below are the only lists there
 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                                                          |
-| ---------------------- | ---------- | -------------------------------------------------------------------- |
-| `icon`                 | `WikiLink` | The document's profile art — an `icon` address, resolved into `img`. |
-| `banner`               | `WikiLink` | The page's hero image — an `image` address.                          |
+| shared `data` property | Values    | Description                                                          |
+| ---------------------- | --------- | -------------------------------------------------------------------- |
+| `icon`                 | `Address` | The document's profile art — an `icon` address, resolved into `img`. |
+| `banner`               | `Address` | The page's hero image — an `image` address.                          |
 
 `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
@@ -660,7 +692,7 @@ Actor types (`being`, `vehicle`) therefore add one row:
 An actor's two pieces of art are two different questions. `data.icon` is the
 profile art — what a directory listing shows beside the name and what the sheet
 header carries. `data.tokenIcon` is what a token on the canvas wears. Both are
-wikilinks and both resolve the same way; only the destination differs. An Item
+addresses and both resolve the same way; only the destination differs. An Item
 has one piece of art, so this row applies to actor types alone.
 
 **A `data:` source is still read at the top level, for now.** `data:` did
@@ -798,7 +830,7 @@ Foundry destination: searching a built `packs-json` tree for it turns up
 nothing. It reaches the generated page and the book's section plates, and
 nothing else.
 
-It is a `WikiLink` all the same, defaulting to type `image`, so a section note
+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
 `banner: packagebuild-none-image-skillbnr`. The resolved record carries the
 owning package, and each surface joins the suffix onto its own root — the site
@@ -848,7 +880,7 @@ documents in different packs and different folders:
 ```yaml
 sohl:
   pack: characteristics
-  packFolder: miscgear
+  packFolder: none-folder-miscgear
 ```
 
 **`pack: none` compiles the note into no document.** The note is walked,
@@ -1199,10 +1231,30 @@ is where the question _which notes carry no `kbcat`?_ is answered.
 `sql` fence is the ordinary case of _Content tables_ below, and the same
 free-form value decides the headings there.
 
-### WikiLinks
+### Addresses
+
+Three types name one thing from another in a content tree, and they are not
+lengths of one another:
+
+| type        | written                                      | where it is met                                             |
+| ----------- | -------------------------------------------- | ----------------------------------------------------------- |
+| `Address`   | `<package>-<system>-<note_type>-<shortcode>` | a frontmatter field, a `model:`, an art slot, a link target |
+| `Shortcode` | `<shortcode>`                                | a note's own identity, and a key a runtime resolves by      |
+| `Wikilink`  | `[[<Address>[#<anchor>]\|<text>]]`           | body prose                                                  |
 
-Many fields in the tables below take a `WikiLink`, and a link is written
-`[[target]]` or `[[target|label]]`. The target is an **address**.
+An **`Address`** is the tuple below, and it is what every field typed `Address`
+in the tables that follow holds. It is equally what a `model:` names, what an art
+slot points at and what a wikilink resolves through — so an address is the thing
+being named, and the brackets around one in prose are a separate matter. Three
+rules govern it, and the first three subsections below state them in turn: the
+tuple is read by position, any suffix of it may be written, and each omitted
+segment is supplied by a default the position declares.
+
+A **`Shortcode`** is one segment, and nothing expands it — see _A shortcode is
+one segment, and nothing expands it_ below.
+
+A **`Wikilink`** is the prose form, which contains an Address — see _Wikilinks_
+below.
 
 #### The canonical address
 
@@ -1237,6 +1289,26 @@ the canonical address, so naming another package means naming its system too.
 `kethira-place-tashal` is three segments, which reads as system `kethira`, and
 fails.
 
+#### Authored references and generated references
+
+Authored notes may use any permitted suffix. Builds leave those source bytes
+unchanged. Generated content indexes, SQL records, site frontmatter and generated
+Wikilinks contain full `package-system-type-shortcode` Addresses. For example,
+`data.parents: [north]` in the `thalorna` package emits
+`data.parents: [thalorna-none-place-north]`.
+
+SQL queries compare Address-valued fields to full Addresses. A note's `shortcode`
+is a distinct identity component, so it is not equal to an Address stored in
+`data.parents`, `data.domains` or a governance rank's `lore`. Use the target's
+complete identity for that comparison, including its package, system and type.
+A stub has no published page address; its note identity still contains those
+components and its Shortcode.
+
+The toolchain holds parsed Address properties as complete tuples internally.
+Address-keyed relation maps hold typed targets and standing values. Only generated
+output serializes these properties to Address strings. Runtime Shortcodes,
+Foundry UUIDs, file paths and URLs keep their own representations.
+
 #### An omitted segment defaults from where the link is written
 
 It is **not** a wildcard and resolution is not a search. Every short form expands
@@ -1264,15 +1336,11 @@ Only a type whose own document carries a system is redirected this way. A
 documents are core ones already at `none`, so `macro-autoattack` names the Macro
 and `docmacro-autoattack` its journal — two live addresses.
 
-**An address is lowercase throughout**. Every segment — package,
-system, type and shortcode alike — is `^[a-z0-9]+$`, so a capital anywhere in an
-address is an error naming the lowercase form.
-
-The shortcode is the one that would otherwise be case-sensitive and routinely
-mixed (`Clb`, `LtShoe`, `HsTunic`) while the address built from it was lowercased
-wholesale, so the authored name and its address disagreed. Two names differing
-only in case are two names nobody can tell apart, and they collapsed onto one
-address, one `_id` and one URL with nothing to report it.
+**A complete Address is lowercase throughout.** Every segment — package,
+system, type and shortcode alike — contains only lowercase ASCII letters and
+digits (`^[a-z0-9]+$`). Declared Address fields reject uppercase segments.
+A model reference accepts mixed-case Shortcodes and resolves their lowercase
+Address identity; this does not change a native embedded item's Shortcode.
 
 **Parsing is positional counting from the right, and nothing else.** Every
 segment is lowercase alphanumeric — shortcodes, **types** and **subTypes** are
@@ -1312,44 +1380,42 @@ before the vault migrated do not silently die. A slash is _unconditionally_ an
 address separator — pipe or no pipe — so an unknown type before one is an error
 rather than something to guess at.
 
-#### Every link is an address, and every link carries a label
-
-There is one namespace, and the pipe is required:
-
-| written              | resolved as | displays                   |
-| -------------------- | ----------- | -------------------------- |
-| `[[WikiLink\|]]`     | an address  | the target note's own name |
-| `[[WikiLink\|Text]]` | an address  | `Text`                     |
-| `[[Name]]`           | nothing     | a finding                  |
-
-**A link written without a label addresses nothing**, and the correction
-is always the same: write `[[type-shortcode|Text]]`.
-
-The bare form does not name an **alias** — a note's own display name, or one of
-the names it listed in `aliases:` — looked up within the citing note's type. It
-was measured before it was retired, and the namespace was empty in practice:
-across 8,305 wikilinks in three content trees, **not one** bare link resolved to
-a note. What the index behind it did do was fold every note's `name.full` into
-itself, so two notes of one type could not share a display name — a rules page
-and a user guide page both called "Gear" were a build failure whose every
-available fix moved a published URL.
-
-The top-level `aliases:` that fed it is **retired** and refused. The nested
-`name.aliases:` is **not**: it is reserved for a use that does not exist yet, so
-it is permitted and read by nothing — no index, no resolver, no lint rule, no
-derived address. A note carrying one behaves exactly as one without it.
-
-Requiring the label is also what makes positional parsing safe. Note names
-contain hyphens — `Grukar-ahk` is a name, not a `Grukar` of type `ahk` — so a
-target that does not parse as an address is reported as one that does not, rather
-than split at an arbitrary place or quietly looked up somewhere else.
-
-The **empty** label is not a way of writing no label. It says _address this
-target, and show whatever it calls itself_ — so a note renamed later takes its new
-name at every citation with no link edited. `[[x|]]` is labelled; `[[x]]` is not.
+#### A shortcode is one segment, and nothing expands it
+
+A **`Shortcode`** is a single segment of the same charset an address segment is
+held to, and it is a type of its own rather than the shortest `Address`. It
+names a thing's identity, or it is the key something resolves by where the other
+three segments have nothing to say:
+
+| where a `Shortcode` is written               | what it names                                                                       |
+| -------------------------------------------- | ----------------------------------------------------------------------------------- |
+| a note's own `shortcode:`                    | the note's identity — the name every address of it is built from                    |
+| a custom embedded entry's `system.shortcode` | that entry's identity within the actor that holds it                                |
+| an emitted `system.relations` key            | the other body this one has a standing towards                                      |
+| a mystery's `skillAptitudes` keys            | the skill an aptitude weighs, where the key is not a `subType:` selector            |
+| a `Code`-suffixed system field               | what the resolved address is stored as — see _The note vocabulary, and how it maps_ |
+
+**The test is whether the position can take the full four-tuple.** An `Address`
+accepts it by definition, and the positions above cannot: a `system.relations`
+key is read at runtime as `relations[shortcode]`, among the items one actor
+carries, where packages do not exist. So nothing defaults a `Shortcode` out to
+four segments, and a value persisted there as an address names no standing at
+all.
 
-The link part may still be an anchor: `[[#slug|Text]]` addresses a section of the
-page it is written on. It is the label that is required, not a target.
+**The two halves of `relations` are two types.** The key an author writes is an
+`Address` — a body in another package is named in full, and one in this package
+by its shortcode alone — and the key the compiled Item carries is the
+`Shortcode` that address names. The builder performs the reduction, exactly as
+it does for a `Code`-suffixed field, and two authored keys reducing to one
+emitted key is an error naming both addresses: a shortcode is unique within one
+package's address space, so two packages may each declare one, and the compiled
+field holds one of the two.
+
+**A bare shortcode in an `Address` field is not a `Shortcode`.** It is an
+Address written at its shortest, with the package, the system and the type all
+supplied by the position — the same value as the full tuple, spelled shorter.
+Which of the two a field holds is the field's own declaration, stated in the
+`Values` column of the tables below and nowhere else.
 
 #### Every address resolves, and every build says so the same way
 
@@ -1388,9 +1454,9 @@ precisely because an author meets whichever build ran first. Three resolvers rea
 one authored link; they must not describe the same mistake in three ways, and
 they must never disagree about whether it is a mistake at all.
 
-#### In frontmatter, a link is a bare address
+#### In frontmatter, the address is written bare
 
-A `WikiLink` **field** takes the address with no brackets:
+An **`Address` field** takes the address with no brackets:
 
 ```yaml
 data:
@@ -1399,22 +1465,35 @@ data:
   seat: tashal
 ```
 
-not `[[hexhodai]]`. The field is declared as a `WikiLink`, so the schema already
-knows the value is an address and reads it as one; brackets would be punctuation
-the reader has to strip before it can do anything.
+not `[[hexhodai]]`. The field is declared as an `Address`, so the schema knows
+what the value is and reads it as one; brackets are a wikilink's punctuation,
+which the reader would have to strip before it could do anything.
 
 A frontmatter value is parsed by the address grammar above, so a single-segment
-value such as `hexhodai` is a _shortcode_. Frontmatter is structure rather than
+value such as `hexhodai` names the target by its shortcode alone, with every
+other segment supplied by the position. Frontmatter is structure rather than
 prose: a field value is a reference something else will compile against, and it
 should say exactly what it points at.
 
-**The field supplies the type.** Every `WikiLink` field declares the note type it
-targets — `seat` a `place`, `parents` an `affiliation`, `stations` a `lore` — so
+**A field can supply the type.** A field naming one kind of note declares its
+default — `seat` a `place`, `parents` an `affiliation`, `stations` a `lore` — so
 the type segment defaults from the declaration and a bare shortcode is the
 ordinary case, not an abbreviation of one. That is why the examples above read
 `tashal` rather than `place-tashal`: the shorter form carries the same
 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
+reference. Grammar and accepted types are checked independently of whether a
+target exists.
+
+An affiliation's `economy` accepts only `affiliation` and `lore` Addresses.
+Each entry states its type: `affiliation-merchants` or `lore-tanvrcrncy`.
+There is no default type; a bare shortcode is an error.
+Bundle `contents` likewise requires a type for each document.
+
 **The declaration constrains the type; it does not shorten the address.** A field
 value may be written at any length, and every length is equally correct so long
 as the type it names is the one the field declares. All four of these are valid
@@ -1423,14 +1502,32 @@ in a `seat` field:
 ```yaml
 seat: tashal
 seat: place-tashal
-seat: kethira-place-tashal
+seat: none-place-tashal
 seat: kethira-none-place-tashal
 ```
 
+Each is a **suffix** of the canonical address, which is why the third one names
+the system and the fourth cannot omit it — see [Shorter forms](#shorter-forms).
+
 An `affiliation-` prefix there is an **error naming the field and both types** —
 never a silent widening of what the field accepts. Where a field permits more
-than one type, a bare shortcode must resolve to exactly one of them, and an
-ambiguity is an error naming the candidates rather than a first match.
+than one type with no default among them, a bare shortcode is refused
+outright — an error naming the field and the types it accepts, never a
+resolution across them.
+
+**A position's default and its accepted set are two different declarations,
+and most positions are not ambiguous at all.** The paragraph above is about a
+position that permits more than one type with no default among them; `seat` is
+the plainer case, permitting exactly one. Between those sits a third shape,
+and it is the common one: a position that nominates one of its accepted types
+as the default while accepting others besides. There a bare shortcode is never
+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
+declared exactly this way — each one accepts a second type beyond the one a
+bare shortcode takes.
 
 **Only the type segment defaults.** Package and system are not the field's to
 supply — it has no opinion about which package holds the target — so reaching
@@ -1452,6 +1549,67 @@ 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.
 
+### Wikilinks
+
+A **`Wikilink`** is how body prose names something:
+
+```text
+[[<Address>[#<anchor>]|<text>]]
+```
+
+The brackets, the `#<anchor>` and the `|<text>` label are the Wikilink's own.
+What sits inside them is an `Address` like any other — read by the same grammar,
+written at any of its lengths, and taking each omitted segment from where the
+link is written, which for body prose is this package and system `none`. So
+nothing about resolution belongs to the bracketed form: a wikilink and a
+frontmatter field ask the same question of the same value, and the findings above
+are the answers either of them gets.
+
+The anchor is the Wikilink's, not the Address's. It names a section of the target
+by the slug that section's heading declares — `[[place-tashal#market|the
+market]]` — and one naming no section there is the `unknown-anchor` finding.
+Written alone, `[[#slug|Text]]` addresses a section of the page the link sits on,
+which is the one form carrying no address at all.
+
+#### Every wikilink carries a label
+
+There is one namespace, and the pipe is required:
+
+| written             | resolved as | displays                   |
+| ------------------- | ----------- | -------------------------- |
+| `[[Address\|]]`     | an address  | the target note's own name |
+| `[[Address\|Text]]` | an address  | `Text`                     |
+| `[[Name]]`          | nothing     | a finding                  |
+
+**A link written without a label addresses nothing**, and the correction
+is always the same: write `[[type-shortcode|Text]]`.
+
+The bare form does not name an **alias** — a note's own display name, or one of
+the names it listed in `aliases:` — looked up within the citing note's type. It
+was measured before it was retired, and the namespace was empty in practice:
+across 8,305 wikilinks in three content trees, **not one** bare link resolved to
+a note. What the index behind it did do was fold every note's `name.full` into
+itself, so two notes of one type could not share a display name — a rules page
+and a user guide page both called "Gear" were a build failure whose every
+available fix moved a published URL.
+
+The top-level `aliases:` that fed it is **retired** and refused. The nested
+`name.aliases:` is **not**: it is reserved for a use that does not exist yet, so
+it is permitted and read by nothing — no index, no resolver, no lint rule, no
+derived address. A note carrying one behaves exactly as one without it.
+
+Requiring the label is also what makes positional parsing safe. Note names
+contain hyphens — `Grukar-ahk` is a name, not a `Grukar` of type `ahk` — so a
+target that does not parse as an address is reported as one that does not, rather
+than split at an arbitrary place or quietly looked up somewhere else.
+
+The **empty** label is not a way of writing no label. It says _address this
+target, and show whatever it calls itself_ — so a note renamed later takes its new
+name at every citation with no link edited. `[[x|]]` is labelled; `[[x]]` is not.
+
+It is the label that is required, not a target: the anchor-only form above
+carries its pipe like every other link.
+
 ### Assets are types
 
 `icon`, `image` and `audio` are types in the type vocabulary, and an address
@@ -1668,12 +1826,12 @@ type the way a field declaration does — `image`. The short-form ladder, the
 package and system defaults, the lowercase rule, the ambiguity reporting and the
 findings vocabulary all apply unchanged.
 
-| written                        | means                                    |
-| ------------------------------ | ---------------------------------------- |
-| `![[anvil\|]]`                 | decorative — the common case             |
-| `![[anvil\|An anvil]]`         | alt text where it carries meaning        |
-| `![[anvil]]`                   | unlabelled, and a finding like any other |
-| `![[sohl-image-anvil\|Anvil]]` | qualified, reaching another package      |
+| written                             | means                                    |
+| ----------------------------------- | ---------------------------------------- |
+| `![[anvil\|]]`                      | decorative — the common case             |
+| `![[anvil\|An anvil]]`              | alt text where it carries meaning        |
+| `![[anvil]]`                        | unlabelled, and a finding like any other |
+| `![[sohl-none-image-anvil\|Anvil]]` | qualified, reaching another package      |
 
 The parser distinguishes a missing label from an empty one, so _deliberately
 decorative_ and _not written_ differ without an exemption.
@@ -1806,7 +1964,7 @@ so adding a type means answering the question rather than inheriting a default.
 
 #### A stub is still referenceable as data
 
-`borders.to` and `routes.to` name a place by shortcode, and those are **index
+`borders.to` and `routes.to` name a place by `Address`, and those are **index
 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 `domains` for tenure — a stub appears in its region's
@@ -2291,16 +2449,16 @@ Generates a living (or undead, or spirit) being.
 
 | `data` property             | Values                                         | Description                                                                                      |
 | --------------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------ |
-| `tokenIcon`                 | `WikiLink`                                     | What a token on the canvas wears — an `icon` address; defaults to `icon`                         |
+| `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** — `[]` where none apply; `null` is an error. |
 | `occupation`                | `string`                                       | Name of the character's occupation                                                               |
-| `stations`                  | `WikiLink[]`                                   | Name of the stations the character belongs to                                                    |
-| `lore`                      | `WikiLink[]`                                   | Lore concerning this being — the people it is of, the standing it holds, the law it lives under  |
-| `homes`                     | `WikiLink[]`                                   | Place the being calls home                                                                       |
-| `affiliations`              | `WikiLink[]`                                   | Affilliations (e.g., arcane/divine traditions, polities, etc)                                    |
+| `stations`                  | `Address[]`                                    | Name of the stations the character belongs to                                                    |
+| `lore`                      | `Address[]`                                    | Lore concerning this being — the people it is of, the standing it holds, the law it lives under  |
+| `homes`                     | `Address[]`                                    | Place the being calls home                                                                       |
+| `affiliations`              | `Address[]`                                    | Affilliations (e.g., arcane/divine traditions, polities, etc)                                    |
 | `gender`                    | `male \| female \| other`                      | Gender of the character                                                                          |
-| `species`                   | `WikiLink`                                     | Being's species (lore)                                                                           |
+| `species`                   | `Address`                                      | Being's species (lore)                                                                           |
 | `born`                      | `YYYY/MM/DD \| unknown`                        | When the being was born; absent, it was never born                                               |
 | `died`                      | `YYYY/MM/DD \| 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                    |
@@ -2539,10 +2697,15 @@ A SoHL "being" document will be created, as will an "HM3" document.
 
 | shared source     | → sohl | → hm3               |
 | ----------------- | ------ | ------------------- |
-| `data.species`    | NA     | `system.species`    |
+| `data.species`    | NA     | NA                  |
 | `data.gender`     | NA     | `system.gender`     |
 | `data.occupation` | NA     | `system.occupation` |
 
+`data.species` is a lore Address describing the being's species. HM3's
+`hm3.system.species` is independent native text; it does not inherit from
+`data.species`. The in-block `hm3.species` spelling is also accepted, with
+`hm3.system.species` taking precedence.
+
 ### type: homepage
 
 The package's front page, published at `https://www.heroiclands.org/<package>/`.
@@ -2570,10 +2733,10 @@ a card block — the homepage is a page with a body, rendered as one.
 
 Represents a conveyance able to hold goods and people moving from one place to another.
 
-| `data` property    | Values     | Description                                                              |
-| ------------------ | ---------- | ------------------------------------------------------------------------ |
-| `tokenIcon`        | `WikiLink` | What a token on the canvas wears — an `icon` address; defaults to `icon` |
-| `templatePriority` | `number`   | Template priority, _null_ = not a template                               |
+| `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                               |
 
 If `sohl` is present, this becomes a `vehicle` actor.
 
@@ -2650,12 +2813,12 @@ two is the commonest way to get a non-monarchy wrong.
 **Rank**
 Definition of a level within the organization (e.g., Priest, Layperson, Member, Gang Leader, Master, etc.)
 
-| Property      | Values     | Description                                                                                                                          |
-| ------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `level`       | number     | The ranking within the affiliation, increasing values starting with 1, 0 indicates intentional exclusion (expulsion/excommunication) |
-| `title`       | string     | Title associated with the Rank                                                                                                       |
-| `description` | string     | Description of the Rank                                                                                                              |
-| `lore`        | `WikiLink` | The standing this rank _is_ — a `lore` note of subType `law`, shared with every other body that confers the same thing               |
+| Property      | Values    | Description                                                                                                                          |
+| ------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| `level`       | number    | The ranking within the affiliation, increasing values starting with 1, 0 indicates intentional exclusion (expulsion/excommunication) |
+| `title`       | string    | Title associated with the Rank                                                                                                       |
+| `description` | string    | Description of the Rank                                                                                                              |
+| `lore`        | `Address` | The standing this rank _is_ — a `lore` note of subType `law`, shared with every other body that confers the same thing               |
 
 **A rank's `lore` is shared; its `title` is not.** A Normen kingdom calls it
 `Thrall` and a Vylarian province calls it `Slave`, and they mean one standing:
@@ -2671,24 +2834,24 @@ 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>`  | Official offices in the affiliation                                                                        |
-| `commonSkills`       | `WikiLink[]`              | Common skills among members (languages, etc.)                                                              |
-| `seat`               | `WikiLink`                | Where the affiliation's authority sits                                                                     |
-| `domains`            | `WikiLink[]`              | Places over which this affiliation holds sway                                                              |
-| `population`         | `number`                  | Number of people in the affiliation (precision 2 significant digits).                                      |
-| `economy`            | `WikiLink[]`              | Any wikilink referring to the economic activity of the affiliation (produced goods, currency systems, etc) |
-| `lore`               | `WikiLink[]`              | Lore concerning it — the peoples it draws on, the god a faith venerates, its law, its calendar             |
-| `parents`            | `WikiLink[]`              | Affiliations that this affiliation is subordinate to                                                       |
-| `relations`          | `Map<WikiLink, Standing>` | Relations with other affiliations                                                                          |
+| `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>` | Official offices in the affiliation                                                            |
+| `commonSkills`       | `Address[]`              | Common skills among members (languages, etc.)                                                  |
+| `seat`               | `Address`                | Where the affiliation's authority sits                                                         |
+| `domains`            | `Address[]`              | Places over which this affiliation holds sway                                                  |
+| `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                            |
 
 **A faith tradition is not its god.** An `affiliation` of subType
 `faithtradition` is a _religion_ — a practice, with an ordained priesthood, a
@@ -3004,27 +3167,29 @@ if a `hm3` property is present, an HM3 item of type "miscgear" will be created.
 
 **SkillAptitude**: either a single skill
 
-| `data` property    | Values                                  | Description                                                    |
-| ------------------ | --------------------------------------- | -------------------------------------------------------------- |
-| `templatePriority` | `number`                                | Template priority, _null_ = not a template                     |
-| `assocSkill`       | `WikiLink`                              | Associated skill                                               |
-| `assocAffiliation` | `WikiLink`                              | Associated affiliation                                         |
-| `skillAptitudes`   | `WikiLink` or `subType:<skill-subtype>` | Bonuses/penalties to skills (or types of skills)               |
-| `level`            | `number`                                | Magnitude of the mystery                                       |
-| `charges.value`    | `number`                                | Current number of charges available, _null_ = charges not used |
-| `charges.max`      | `number`                                | Maximum number of charges, _null_ = no maximum                 |
+| `data` property    | Values                                                                             | Description                                                    |
+| ------------------ | ---------------------------------------------------------------------------------- | -------------------------------------------------------------- |
+| `templatePriority` | `number`                                                                           | Template priority, _null_ = not a template                     |
+| `assocSkill`       | `Address`                                                                          | Associated skill                                               |
+| `assocAffiliation` | `Address`                                                                          | Associated affiliation                                         |
+| `skillAptitudes`   | `Map<Shortcode, number>`, the key a skill's shortcode or `subType:<skill-subtype>` | Bonuses and penalties, per skill or per kind of skill          |
+| `level`            | `number`                                                                           | Magnitude of the mystery                                       |
+| `charges.value`    | `number`                                                                           | Current number of charges available, _null_ = charges not used |
+| `charges.max`      | `number`                                                                           | Maximum number of charges, _null_ = no maximum                 |
 
 if a `sohl` property is present, a SoHL item of type "mystery" will be created.
 
-| shared source           | → sohl                        | → hm3 |
-| ----------------------- | ----------------------------- | ----- |
-| `subType`               | `system.subType`              | NA    |
-| `data.assocSkill`       | `system.assocSkillCode`       | NA    |
-| `data.assocAffiliation` | `system.assocAffiliationCode` | NA    |
-| `data.skillAptitudes`   | `system.skillAptitudes`       | NA    |
-| `data.level`            | `system.levelBase`            | NA    |
-| `data.charges.value`    | `system.charges.value`        | NA    |
-| `data.charges.max`      | `system.charges.max`          | NA    |
+`system.assocSkillCode` and `system.assocAffiliationCode` are authored under
+`sohl.system` as shortcodes and have no shared source; `data.assocSkill` and
+`data.assocAffiliation` name the same two notes as Addresses, for the page.
+
+| shared source         | → sohl                  | → hm3 |
+| --------------------- | ----------------------- | ----- |
+| `subType`             | `system.subType`        | NA    |
+| `data.skillAptitudes` | `system.skillAptitudes` | NA    |
+| `data.level`          | `system.levelBase`      | NA    |
+| `data.charges.value`  | `system.charges.value`  | NA    |
+| `data.charges.max`    | `system.charges.max`    | NA    |
 
 ### type: mysticalability
 
@@ -3041,29 +3206,31 @@ if a `sohl` property is present, a SoHL item of type "mystery" will be created.
 - alchemy: The preparation of substances imbued with mystical potency.
 - divination: The practice of obtaining hidden knowledge or foreknowledge by mystical means.
 
-| `data` property    | Values     | Description                                                    |
-| ------------------ | ---------- | -------------------------------------------------------------- |
-| `templatePriority` | `number`   | Template priority, _null_ = not a template                     |
-| `assocSkill`       | `WikiLink` | Associated skill                                               |
-| `assocAffiliation` | `WikiLink` | Associated affiliation                                         |
-| `masteryLevel`     | `number`   | Mastery Level                                                  |
-| `level`            | `number`   | Magnitude of the mystery                                       |
-| `charges.value`    | `number`   | Current number of charges available, _null_ = charges not used |
-| `charges.max`      | `number`   | Maximum number of charges, _null_ = no maximum                 |
+| `data` property    | Values    | Description                                                    |
+| ------------------ | --------- | -------------------------------------------------------------- |
+| `templatePriority` | `number`  | Template priority, _null_ = not a template                     |
+| `assocSkill`       | `Address` | Associated skill                                               |
+| `assocAffiliation` | `Address` | Associated affiliation                                         |
+| `masteryLevel`     | `number`  | Mastery Level                                                  |
+| `level`            | `number`  | Magnitude of the mystery                                       |
+| `charges.value`    | `number`  | Current number of charges available, _null_ = charges not used |
+| `charges.max`      | `number`  | Maximum number of charges, _null_ = no maximum                 |
 
 if a `sohl` property is present, a SoHL item of type "mysticalability" will be created.
 
 If an `hm3` property is present, an HM3 item is created, and `hm3.type` states which — `psionic`, `spell` or `invocation`. It is **authored, not derived from `subType`**: the ten mystical-ability subtypes do not partition onto HM3's three documents (a `spiritrite`, an `alchemy` and a `divination` each answer to none of them), so a derivation would be a guess with a plausible shape. A note that omits it is an error naming the note.
 
-| shared source           | → sohl                        | → hm3         |
-| ----------------------- | ----------------------------- | ------------- |
-| `subType`               | `system.subType`              | **see above** |
-| `data.assocSkill`       | `system.assocSkillCode`       | NA            |
-| `data.assocAffiliation` | `system.assocAffiliationCode` | NA            |
-| `data.masteryLevel`     | `system.masteryLevelBase`     | NA            |
-| `data.level`            | `system.levelBase`            | NA            |
-| `data.charges.value`    | `system.charges.value`        | NA            |
-| `data.charges.max`      | `system.charges.max`          | NA            |
+`system.assocSkillCode` and `system.assocAffiliationCode` are authored under
+`sohl.system` as shortcodes and have no shared source; `data.assocSkill` and
+`data.assocAffiliation` name the same two notes as Addresses, for the page.
+
+| shared source        | → sohl                    | → hm3         |
+| -------------------- | ------------------------- | ------------- |
+| `subType`            | `system.subType`          | **see above** |
+| `data.masteryLevel`  | `system.masteryLevelBase` | NA            |
+| `data.level`         | `system.levelBase`        | NA            |
+| `data.charges.value` | `system.charges.value`    | NA            |
+| `data.charges.max`   | `system.charges.max`      | NA            |
 
 ### type: projectilegear
 
@@ -3117,11 +3284,11 @@ HM3 side while remaining distinct on the SoHL side.
 - combat
 - combattechnique
 
-| `data` property    | Values     | Description                                |
-| ------------------ | ---------- | ------------------------------------------ |
-| `templatePriority` | `number`   | Template priority, _null_ = not a template |
-| `masteryLevel`     | `number`   | Mastery Level                              |
-| `parentSkill`      | `WikiLink` | Parent skill this skill specializes        |
+| `data` property    | Values    | Description                                |
+| ------------------ | --------- | ------------------------------------------ |
+| `templatePriority` | `number`  | Template priority, _null_ = not a template |
+| `masteryLevel`     | `number`  | Mastery Level                              |
+| `parentSkill`      | `Address` | Parent skill this skill specializes        |
 
 if a `sohl` property is present, a SoHL item of type "skill" will be created.
 
@@ -3129,11 +3296,14 @@ If an `hm3` property is present, then an HM3 item of type "skill" will be create
 
 Note: `hm3.system.type` (skill types) use the values "Craft", "Physical", "Communication", "Combat", "Magic", and "Ritual". These do not cleanly map to the `subType` values. Because of this, the `hm3.system.type` value must be specified with the appropriate value when defining HM3 skills.
 
+`system.parentSkillCode` is authored under `sohl.system` as the shortcode of the
+skill this one specializes, and has no shared source; `data.parentSkill` names that
+skill as an Address, for the page.
+
 | shared source       | → sohl                    | → hm3                 |
 | ------------------- | ------------------------- | --------------------- |
 | `subType`           | `system.subType`          | See notes above       |
 | `data.masteryLevel` | `system.masteryLevelBase` | `system.masteryLevel` |
-| `data.parentSkill`  | `system.parentSkillCode`  | NA                    |
 
 ### type: trauma
 
@@ -3344,7 +3514,7 @@ The `data:` fields, of which three are required:
 
 | `data` property   | Values           | Description                                                                                                                                                  |
 | ----------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `bgImage`         | `WikiLink`       | **Required.** The map art — an `image` address. Becomes the level's `background.src`, what tokens stand on                                                   |
+| `bgImage`         | `Address`        | **Required.** The map art — an `image` address. Becomes the level's `background.src`, what tokens stand on                                                   |
 | `dimensions`      | `[int, int]`     | **Required.** `[width, height]` in whole pixels, the art's own size                                                                                          |
 | `pxPerGrid`       | `integer`        | **Required.** Whole pixels per grid square; must match the art                                                                                               |
 | `navName`         | `string`         | Short name for Foundry's scene navigation bar                                                                                                                |
@@ -3357,7 +3527,7 @@ The `data:` fields, of which three are required:
 | `tiles`           | `Tile[]`         | List of tiles, each naming its art in `image`                                                                                                                |
 | `sounds`          | `Sound[]`        | List of sounds, each naming its clip in `audio`                                                                                                              |
 | `regions`         | `SceneRegion[]`  | List of scene regions                                                                                                                                        |
-| `place`           | `WikiLink`       | The place this map depicts. Optional, because an encounter map depicts no named place — but that is the exception, and a map without one is a map of nowhere |
+| `place`           | `Address`        | The place this map depicts. Optional, because an encounter map depicts no named place — but that is the exception, and a map without one is a map of nowhere |
 | `notes`           | `NoteLocation[]` | grid coordinates of note markers mapped to anchors in this document                                                                                          |
 
 Everything else a Scene holds is **derived**, not authored: padding, grid type,
@@ -3374,7 +3544,7 @@ compilation, and the server-side migration shim is version-gated on
 single Level is synthesised from `bgImage`, `overlay`, `levelName` and
 `backgroundColor`.
 
-> **`bgImage` is a `WikiLink` under `data:`, as every other type's artwork is.**
+> **`bgImage` is an `Address` under `data:`, as every other type's artwork is.**
 > Art is not system-specific — a Scene is a core Foundry document, and a second
 > system would want the identical art — so the field sits under `data:` rather
 > than inside a system block.
@@ -3455,8 +3625,8 @@ three maps, and none of those maps needs to know it is a keep.
 | `data` property                   | Values                                              | Description                                                                  |
 | --------------------------------- | --------------------------------------------------- | ---------------------------------------------------------------------------- |
 | `demonym`                         | `string`                                            | What a person from this place is called — a Vylarian                         |
-| `lore`                            | `WikiLink[]`                                        | Lore concerning this place — its peoples, its law, its calendar, its history |
-| `parents`                         | `WikiLink[]`                                        | Enclosing places within which this place is located                          |
+| `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)                      |
 | `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       |
@@ -3563,8 +3733,13 @@ data:
     - { to: kethramir, bearing: E, mode: land, days: 30, terrain: [dunes], leagues: 90 }
 ```
 
-- `to` — required; the `shortcode` of a `place` note in this package or in a
-  declared dependency's index. A shortcode, not an address.
+- `to` — required; an `Address` naming the other place. Its type segment defaults
+  to `place` and `place` is the whole of its accepted set, so `vylar`,
+  `place-vylar` and `thalorna-none-place-vylar` name one place and a `to` naming
+  anything else is an error. **A bare shortcode names a place in this package**,
+  which is what the fully qualified form is for: naming a place in a declared
+  dependency's index, so two packages using one shortcode never answer for each
+  other.
 - `bearing` — required; where the neighbour or the destination lies from here.
 - `mode` — required on a route; how the journey is travelled.
 - `days` — required on a route; a marker meaning "about this, under normal
@@ -3591,6 +3766,15 @@ neighbour that states a different bearing, a different `days` or a different
 tell which. Every `to` must resolve to a place, every value must come from its
 closed set, and each finding is located at the entry that states it.
 
+**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
+value is read from — a note of this package's own, or a record a consumer fetched
+out of a dependency's index — so a short `to` names a different place in a
+different build. Only the fully qualified form names one place everywhere, which
+is why the long form is not optional for a border or a route between packages,
+and why a short `to` in a fetched record names the package being built rather
+than the package that wrote it.
+
 | `bearing` value | where the other place lies |
 | --------------- | -------------------------- |
 | `N`             | north                      |
@@ -3749,14 +3933,14 @@ Content prepared to be played — a situation with its cast, places, and possibl
 
 | `data` property    | Values                                       | Description                                                                    |
 | ------------------ | -------------------------------------------- | ------------------------------------------------------------------------------ |
-| `parents`          | `WikiLink[]`                                 | List of parent scenarios of this scenario (campaigns, etc.)                    |
-| `locations`        | `WikiLink[]`                                 | List of locations associated with this scenario                                |
-| `cast`             | `WikiLink[]`                                 | individuals associated with this scenario                                      |
-| `factions`         | `WikiLink[]`                                 | Affiliations associated with this scenario                                     |
-| `follows`          | `WikiLink[]`                                 | Prerequisite scenarios that should be completed before beginning this scenario |
+| `parents`          | `Address[]`                                  | List of parent scenarios of this scenario (campaigns, etc.)                    |
+| `locations`        | `Address[]`                                  | List of locations associated with this scenario                                |
+| `cast`             | `Address[]`                                  | individuals associated with this scenario                                      |
+| `factions`         | `Address[]`                                  | Affiliations associated with this scenario                                     |
+| `follows`          | `Address[]`                                  | Prerequisite scenarios that should be completed before beginning this scenario |
 | `status`           | `draft \| playtested \| published`           | Playability status of this scenario                                            |
 | `party.size`       | `solo \| small \| standard \| large \| host` | Suggested party size (solo=1, small=2-3, standard=4-6, large=6-7, host=7+)     |
-| `party.archetypes` | `Archetype`                                  | Archetypes of characters suitable for completion                               |
+| `party.archetypes` | `Archetype[]`                                | Archetypes of characters suitable for completion                               |
 
 ### type: doc
 
@@ -3859,9 +4043,9 @@ authors none takes Foundry's own `icons/svg/dice-target.svg`.
 
 A bundle of notes to be taken as a single unit — an `Adventure` in Foundry VTT.
 
-| `data` property | Values       | Description                                            |
-| --------------- | ------------ | ------------------------------------------------------ |
-| `contents`      | `WikiLink[]` | The documents the Adventure holds; `[]` when unstated. |
+| `data` property | Values      | Description                                            |
+| --------------- | ----------- | ------------------------------------------------------ |
+| `contents`      | `Address[]` | The documents the Adventure holds; `[]` when unstated. |
 
 ```yaml
 ---
@@ -3944,10 +4128,10 @@ data:
 ---
 ```
 
-| `data` property | Values                                     | Description                                                                    |
-| --------------- | ------------------------------------------ | ------------------------------------------------------------------------------ |
-| `parent`        | `WikiLink`, or a map of them keyed by pack | The folder this one sits in — one address, or one per pack. Unset at the root. |
-| `color`         | `"#RRGGBB"`, a string                      | The folder's colour. Unset for Foundry's default.                              |
+| `data` property | Values                                    | Description                                                                    |
+| --------------- | ----------------------------------------- | ------------------------------------------------------------------------------ |
+| `parent`        | `Address`, or a map of them keyed by pack | The folder this one sits in — one address, or one per pack. Unset at the root. |
+| `color`         | `"#RRGGBB"`, a string                     | The folder's colour. Unset for Foundry's default.                              |
 
 A folder is addressed `<package>-none-folder-<shortcode>` — **`none`**, because a
 `Folder` is a core Foundry document like a `JournalEntry` or a `Scene`, not a