@heroiclands/package-build 23.8.0 → 23.9.0

package/docs/authoring/links-and-markup.md

@@ -334,7 +334,7 @@ A column's heading is its SQL alias, so `AS "Name"` is what a reader sees. A cel
 | `glossary`         | One row per entry a culture or an affiliation writes in `data.glossary`, with the `note` it belongs to and the `language` it resolves to.                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
 | `language_lineage` | One row per language note and each language it inherits words from through `data.family`, itself included at `depth` 0. Join it to `words` for a language's words with inherited ones.                                                                                                                                                                                                                                                                                                                                                                                                             |
 | `dictionary`       | One row per word per language it is listed under, inherited words included, with its `depth`. See [dictionaries and glossaries](#dictionaries-and-glossaries).                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| `terms`            | One row per glossary entry, rank or office per note that owns it, with the `cultures` it reaches. See [dictionaries and glossaries](#dictionaries-and-glossaries).                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `terms`            | One row per glossary entry, rank or office per note that owns it, with its `cultures` associations. See [dictionaries and glossaries](#dictionaries-and-glossaries).                                                                                                                                                                                                                                                                                                                                                                                                                               |
 | `register`         | One row per name a language note writes in `data.register`, with its `tongue`, `kind`, `gloss` and `why`, its pieces as `built_text`, and the `notes` carrying the name, derived from the index.                                                                                                                                                                                                                                                                                                                                                                                                   |
 | `tongues`          | One row per tag a language note writes in `data.tongues`: `tag`, `meaning` and `tongue_language`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | `retired`          | One row per form a language note writes in `data.retired`: `form`, `instead` as a list, and `why`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
@@ -840,12 +840,12 @@ See [a language's register, sounds and history](../reference/format-details.md#a
 
 A braced list may follow the language on the opening fence. Four attributes are accepted, and anything else is reported by name.
 
-| Attribute       | Value                               | Default | What it does                                                                                                                                                                                                                           |
-| --------------- | ----------------------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `allow-empty`   | `true` or `false`                   | `false` | Whether a query selecting no rows is allowed. A zero-row result is a finding otherwise, because a table that silently prints nothing is the commonest way a query goes wrong unnoticed.                                                |
-| `section-level` | an integer from 1 through 6         | `2`     | The heading level given to each group a `_section` column creates, and to each letter of a dictionary or a glossary.                                                                                                                   |
-| `key`           | `true`, `false` or `only`           | `true`  | Whether a dictionary or a glossary prints its key. `false` leaves it out; `only` prints the key for the fence's rows and no letter or entry, so a page with one `key=false` fence per heading states its key once. Refused on a table. |
-| `layout`        | `table`, `dictionary` or `glossary` | `table` | How the result is set: as a table, as a dictionary of words, or as a glossary of terms — see [dictionaries and glossaries](#dictionaries-and-glossaries).                                                                              |
+| Attribute       | Value                               | Default | What it does                                                                                                                                                                                          |
+| --------------- | ----------------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `allow-empty`   | `true` or `false`                   | `false` | Whether a query selecting no rows is allowed. A zero-row result is a finding otherwise, because a table that silently prints nothing is the commonest way a query goes wrong unnoticed.               |
+| `section-level` | an integer from 1 through 6         | `2`     | The heading level given to each group a `_section` column creates, and to each letter of a dictionary or a glossary.                                                                                  |
+| `key`           | `true`, `false` or `only`           | `true`  | Whether a dictionary or a glossary prints its key. `false` omits the key and any dictionary verb table; `only` prints the key for the fence's rows and no table, letter or entry. Refused on a table. |
+| `layout`        | `table`, `dictionary` or `glossary` | `table` | How the result is set: as a table, as a dictionary of words, or as a glossary of terms — see [dictionaries and glossaries](#dictionaries-and-glossaries).                                             |
 
 ````markdown
 ```sql {allow-empty=true section-level=3}
@@ -873,81 +873,165 @@ See [SQL details](../reference/format-details.md#content-tables) for query optio
 
 ### Dictionaries and glossaries
 
-Two layouts set a result as paragraphs under letter headings rather than as a table. **`layout=dictionary` sets words**, read from the `dictionary` relation: each with its class, its etymology, its senses, numbered where a word's `gloss` lists several, and the notes it is cited from — every note whose prose marks the word in italics. **`layout=glossary` sets terms**, read from the `terms` relation: a culture's or an affiliation's own glossary entries and an affiliation's ranks and offices, each sense tagged with the body or culture it comes from. Each needs the `name`, `senses` and `usage` columns, and a query that leaves one out is reported, naming the column.
+The build supplies a note's dictionary or glossary from its frontmatter on
+every surface: the site, the Foundry journal and the book.
 
-**The query decides what appears**, and any note may carry either fence. These are the common ones:
+- **A language note with nonempty `data.words` receives a Dictionary section.** It
+  contains the language's full dictionary as one alphabetical list, with
+  letter headings, each word's field beside it and the key printed once. A
+  language with absent or empty `data.words` receives no Dictionary section.
+- **A culture or affiliation with nonempty `data.glossary` receives a Glossary
+  section.** It contains only the entries that owner declares. Ranks and
+  offices stand in the affiliation's own sections; they enter its glossary
+  only when an explicit glossary entry names them. A note with absent or
+  empty `data.glossary` receives no Glossary section.
 
-| What                                      | Layout       | Query                                                                             |
-| ----------------------------------------- | ------------ | --------------------------------------------------------------------------------- |
-| A language's dictionary                   | `dictionary` | `SELECT * FROM dictionary WHERE language = '<the language's Address>'`            |
-| A language's common words, on any page    | `dictionary` | `SELECT * FROM dictionary WHERE language = '<the language's Address>' AND common` |
-| A culture's glossary                      | `glossary`   | `SELECT * FROM terms WHERE list_contains(cultures, '<the culture's Address>')`    |
-| An affiliation's glossary                 | `glossary`   | `SELECT * FROM terms WHERE owner = '<the affiliation's Address>'`                 |
-| The setting's _Dictionary of the Tongues_ | `dictionary` | `SELECT * EXCLUDE (common) FROM dictionary WHERE depth = 0`                       |
-| The setting's _Glossary_                  | `glossary`   | `SELECT * EXCLUDE (common) FROM terms`                                            |
+The sections follow the note's authored text. An existing heading with
+`{#dictionary}` or `{#lexicon}` receives the dictionary after its authored
+text; `{#glossary}` does the same for a glossary. The heading and its
+introduction stay in place, with one generated list under it:
 
-A language's dictionary lists the words it inherits through `data.family` beside its own; `depth = 0` lists each word once, under the language that states it. A culture's glossary holds the culture's own terms and the ranks, offices and glossary terms of every affiliation that reaches it. The two setting pages leave out `common`, so they mark no entry: which words are common is a culture's judgement.
-
-The most common Vylari words, on the Vylarian culture's page:
+```markdown
+## Lexicon {#lexicon}
+
+The tongue of Provenzia, whose _solmère_ is its own word.
+```
+
+A dictionary belongs to a language; a glossary belongs to one culture or
+affiliation. A glossary entry belongs for one of three reasons: a common word
+in the owner's core vocabulary, a dictionary word with a context meaning,
+or a phrase, compound or term of art outside the dictionary with its own
+gloss. The [worked culture glossary](../reference/format-details.md#glossary-terms)
+selects `solmère` as a common word, gives `amère` a context meaning and glosses
+`blood-field` as a term outside the dictionary. Its frontmatter supplies the
+whole default Glossary section. There are no setting-wide dictionary or
+glossary pages.
+
+A dictionary noun prints its gender from its existing class and its plural
+where one is available: **marendos** _n. m., pl. marendoi_. An explicit
+word plural wins; otherwise the language's optional `grammar.plural` rule
+replaces the first matching literal ending. The language's optional
+`grammar.verbs` pattern prints once as a small head table, after the key and
+before the letters. Empty verb endings print as "unchanged". Grammar is
+never inherited through `family`, and absent grammar leaves the dictionary
+unchanged. The [worked noun and verb example](../reference/format-details.md#optional-noun-and-verb-forms)
+shows both declarations. Only supplied shapes are checked; words are never
+checked against the rule, and no language must state grammar.
+
+An entry naming a word of its resolved language without a `definition`
+carries the word's dictionary senses and class, with a link to the word's
+entry on its language page. An entry with a `definition` carries that meaning
+instead, retaining its word link and class when it names a dictionary word.
+Ranks, offices and definitions carry their source body or culture beside
+their senses. Common choices belong to each owner: a culture and an
+affiliation using the same language choose independently, and a word may be
+common in one glossary and absent from another. Dictionaries mark nothing
+common.
+
+Public dictionaries omit citations to GM-only notes. `links` checks generated
+tables in the source note's audience: public notes use public rows, and GM
+notes retain GM citations. An authored link from a public note to a GM-only
+note is still reported.
+
+#### Custom views
+
+An `sql` fence with `layout=dictionary` or `layout=glossary` sets a custom view
+of the same relations. A dictionary view reads `dictionary`; a glossary view
+reads `terms`. Each needs the `name`, `senses` and `usage` columns; a query
+that leaves one out is reported, naming the column.
+
+The optional `plural` and `verbs` columns supply noun plurals and the head
+table in a custom dictionary view; `SELECT *` includes both. A projection
+that omits these columns omits that presentation, as omitting `class` omits
+word classes. With the default or `key=true`, each selected language's pattern
+appears once per dictionary result, even when no abbreviation key is needed.
+`key=false` omits both the key and the verb table from a fragment;
+`key=only` prints only the abbreviation key. Separate head-enabled fences
+each print their own tables.
+
+For a custom list of one culture's common entries:
 
 ````markdown
 ## Words Everyone Knows {#common-words}
 
-```sql {layout=dictionary section-level=3}
-SELECT * FROM dictionary WHERE language = 'thalorna-note-skill-vylarilng' AND common
-```
-````
-
-A culture's glossary:
-
-````markdown
-## Glossary {#glossary}
-
 ```sql {layout=glossary section-level=3}
-SELECT * FROM terms WHERE list_contains(cultures, 'thalorna-note-lore-provenzianclt')
+SELECT * FROM terms WHERE owner = 'thalorna-note-lore-provenzianclt' AND common
 ```
 ````
 
-A page that sets several fences, one per heading, states its key once: a `key=only` fence at the head over all the rows the page sets, then `key=false` on each fence below it, so the abbreviations are not repeated under every heading. The `key=only` fence prints the key for its rows and no letter heading and no entry:
+A custom dictionary view can select one field from the language's dictionary:
 
 ````markdown
-## Words {#words}
-
-```sql {layout=dictionary key=only}
-SELECT * FROM dictionary WHERE language = 'thalorna-note-skill-vylarilng' AND depth = 0
-```
-
-### Love and its conduct
+## Love and its conduct
 
-```sql {layout=dictionary key=false section-level=4}
-SELECT d.* FROM dictionary d JOIN words w ON w.language = d.language AND w.form = d.name
-WHERE d.language = 'thalorna-note-skill-vylarilng' AND w.field = 'Love and its conduct'
+```sql {layout=dictionary section-level=3}
+SELECT * FROM dictionary
+WHERE language = 'thalorna-note-skill-provnzlng' AND field = 'Love and its conduct'
 ```
 ````
 
-`key`, whatever its value, sets a dictionary's or a glossary's key, so it is refused on a fence set as a table.
+A custom view with several fences can print its key once: a `key=only` fence
+over all selected rows, then `key=false` on each fence below it. The
+`key=only` fence prints only the abbreviation key. `key`, whatever its value,
+is refused on a fence set as a table. The automatic Dictionary section
+prints its own key once for the full alphabetical list.
 
 Either layout prints, in order:
 
-- **a key**, once, unless the fence sets `key=false`, and nothing else where it sets `key=only`, listing only the abbreviations the result uses — a language's tag, and for words a class or a modifier — each with what it stands for, and the common mark where an entry carries it;
-- **a heading per letter**, at `section-level`, accents taken off and apostrophes skipped, so `'ostal` files under O and `Écuyer` under E;
-- **one paragraph per entry**: `•` for a common entry, the headword in bold, its pronunciation between slashes, its language tag in italics, the senses, and after a dash the notes it is cited from, as links.
+- **a key**, once, unless the fence sets `key=false`, and nothing else where
+  it sets `key=only`, listing the abbreviations the result uses — a language's
+  tag, a word's class or a modifier — each with its expansion; a glossary also
+  explains the common mark where an entry carries it;
+- **a heading per letter**, at `section-level`, accents taken off and
+  apostrophes skipped, so `'ostal` files under O and `Écuyer` under E;
+- **one paragraph per entry**: a glossary's `•` for a common entry, the
+  headword in bold, its pronunciation between slashes, its language tag and
+  word class in italics where present, its senses, and after a dash the notes
+  it is cited from, as links.
 
-A word also carries its class beside the tag and its etymology in brackets:
+A dictionary entry gives its field in italic parentheses and its etymology
+in brackets:
 
 ```markdown
-• **solmère** /sol-MEH-reh/ _n. m._ [fr. Élav. _sólmerë_] Longing; the ache for a time that is gone. — [[thalorna-note-lore-lastshrine|The Song of the Last Shrine]]
+**solmère** /sol-MEH-reh/ _n. m._ (_Love and its conduct_) [fr. Élav. _sólmerë_] Longing; the ache for a person, a place or a time that is gone. — [[thalorna-note-lore-lastshrine|The Song of the Last Shrine]]
 ```
 
-A term carries no class, and each of its senses names its source. A glossary sets the rows sharing a headword and a language as one entry, numbering their senses in the order the rows arrive and printing a sense several bodies give once, with all of them:
+A glossary entry naming a dictionary word uses the word's senses when
+`definition` is absent; a list of dictionary glosses supplies every sense.
+Those senses carry no body label. An entry with a `definition` uses that
+meaning and labels it with the owner, retaining its word link and class
+where it names a dictionary word. On the owner's own page, a sense attributed
+only to that owner omits the repeated label; other bodies and shared senses
+keep their labels. A glossary sets the rows sharing a headword
+and a language as one entry, numbering their senses in query order and
+printing a sense several bodies give once, with all of them:
 
 ```markdown
-**Sworn Knight** **1** (_Duchy of Aubrac_) Holds land of the duke. **2** (_Kingdom of Provenzia_) Holds land of the crown. **3** (_Provenzia_) A knight bound by oath to a lord. — [[thalorna-note-affiliation-duchy|Duchy of Aubrac]], [[thalorna-note-affiliation-kingdom|Kingdom of Provenzia]], [[thalorna-note-lore-provenzianclt|Provenzia]]
-```
-
-The entries are ordered by the layout, not by the query: by letter, then by `name_sort`. **The language tag prints where the entry's language is not the page's own**: a language note's own language, a culture's `data.language`, or the language an affiliation's glossary resolves to. It is the language note's `data.abbreviation`, or its full name where it states none. The etymology never repeats the entry's own language: a borrowed word prints `[fr. Élav. _sólmerë_]`, a built word its pieces each with its gloss, `[_am-_ "love" + _-ère_ "one who"]`, an inherited word its older form, `[*_hur_]` or `[Hel. *_thalass_]`, and a root word its root and pattern. A citation of a note with no published page prints as its name.
-
-A culture's or an affiliation's `data.glossary` shapes both: an entry without a definition marks a word or a rank common, gives it a sort key or a respelling, and lets in a rank whose title is a single word; an entry with a definition replaces the senses of the owner's own rank or office, or is a term of the owner's own. The [format reference](../reference/format-details.md#dictionaries-and-glossaries) gives every column and rule.
+**Sworn Knight** **1** (_Duchy of Aubrac_) Holds land of the duke. **2** (_Kingdom of Provenzia_) Holds land of the crown. **3** A knight bound by oath to a lord. — [[thalorna-note-affiliation-duchy|Duchy of Aubrac]], [[thalorna-note-affiliation-kingdom|Kingdom of Provenzia]], [[thalorna-note-lore-provenzianclt|Provenzia]]
+```
+
+The layout orders entries by letter, then by `name_sort`. **The language tag
+prints where the entry's language is not the page's own**: a language note's
+own language, a culture's `data.language`, or the language an affiliation's
+glossary resolves to. It is the language note's `data.abbreviation`, or its
+full name where unstated. Etymology never repeats the entry's own language:
+a borrowed word prints `[fr. Élav. _sólmerë_]`, a built word its pieces each
+with its gloss, `[_am-_ "love" + _-ère_ "one who"]`, an inherited word its
+older form, `[*_hur_]` or `[Hel. *_thalass_]`, and a root word its root and
+pattern. A citation of a note with no published page prints as its name.
+
+A built piece can name a language element by its `form` or one of its
+`variants`; its `sense` prints beside the piece. An affix can also be named by
+its `front` form. Words and affixes take precedence over elements in the same
+language, and the language is searched before its ancestors. Exact spellings
+are checked before ignoring joining hyphens; case and accents are preserved.
+
+A glossary entry may give its own sort key or respelling. A reference to a
+rank or office inherits its descriptions and admits a title of one word; its
+`common` value belongs to the entry's owner. A definition replaces the senses
+of the owner's own rank or office, or supplies an entry of the owner's own.
+The [format reference](../reference/format-details.md#dictionaries-and-glossaries)
+gives every column and rule.
 
 ## Page lists
 
@@ -987,7 +1071,7 @@ That list names the `lore` notes tagged `key-concept`, grouped by type and alpha
 
 **A tag no page carries is a finding** at the fence's own line, naming the tag it looked for. A misspelled tag is the whole of what goes wrong here, and a heading with an empty list under it is how one goes unnoticed. Write `{allow-empty=true}` where a group that is genuinely empty is intended; the directive then leaves nothing behind rather than an empty list.
 
-A page list names this package's own pages. A **stub** — a note with an empty body — publishes no page, so it joins no list. A note tagged `gm` is listed in Foundry and left out of the website and the book, exactly as it is left out of a content table's relations.
+A page list names this package's own pages. A **stub** — a note with neither an authored body nor automatic lexical content — publishes no page, so it joins no list. A note tagged `gm` is listed in Foundry and left out of the website and the book, exactly as it is left out of a content table's relations.
 
 See [page-list details](../reference/format-details.md#page-lists) for the directive's full behaviour.
 

package/docs/commands.md

@@ -2182,6 +2182,9 @@ wikilink at all. Also reports a vendored foreign-package content index that
 has drifted out of reach, naming `package-build deps fetch` as the fix. Resolves
 address-valued SoHL system fields declared by the installed schema against this
 package and its declared dependencies.
+An anchored reference to a dependency's readable note must name a prose anchor
+in its fetched content index. A missing section is an error even when the page
+address resolves. Event ids are not prose sections and cannot be wikilink targets.
 Reads the content tree named by `root`, defaulting to `paths.content`, and
 the cached content indexes of any declared dependency; writes nothing.
 
@@ -2342,16 +2345,22 @@ package-build content-index [root] [--out <dir>]
 
 **DESCRIPTION**
 
-Emits this package's note index as JSON Lines — one record per note,
-carrying its full frontmatter plus its place in the tree. Every build
-already walks the tree and parses every note's frontmatter and then throws
-the result away; this publishes that walk so anything outside a build can
-query the content without paying for a second walk. Its own command rather
-than only a build step, because the point is that anyone can regenerate it
-at will — the artifact costs a frontmatter parse, not a build, which is
-also what lets it stay uncommitted. Reads the content tree named by `root`,
-defaulting to `paths.content`; writes `<contentPackage>-metadata.jsonl`
-into `--out`, defaulting to the configured `paths.contentIndex`.
+Emits this package's note index as JSON Lines, carrying full frontmatter,
+tree positions, prose and event anchors, and document targets. Reads the
+content tree named by `root`, defaulting to `paths.content`; writes
+`<contentPackage>-metadata.jsonl`, `<contentPackage>-dictionary.jsonl` and
+`<contentPackage>-terms.jsonl` into `--out`, defaulting to the configured
+`paths.contentIndex`.
+
+The command prepares SQL tables, page lists, automatic sections and scalar
+expressions before publishing their prose targets. Each source uses its own
+audience for prose declarations: public notes use public providers and usage,
+and GM notes use the complete corpus. Native target maps use the compendium's
+complete SQL corpus and expose only declared prose slugs present there, with
+their actual native page targets. Readable item documentation targets its
+documentation journal. An empty published prose-anchor list declares no prose targets,
+including for pages without a Foundry document. Preparation errors leave all
+three output files untouched.
 
 **OPTIONS**
 

package/docs/content-format.md

@@ -9,7 +9,7 @@ subType: userguide
 
 A content package begins with Markdown notes under `assets/content/`. Each note has YAML frontmatter describing its identity and data, followed by prose. Folder names beneath `assets/content/` are for authors; `type`, `subType`, and Addresses determine what the build creates.
 
-Every typed note requires a nonempty body, including drafts, folders and homepages. An empty or whitespace-only body is an error. A nonempty body with fewer than 25 prose words warns unless tagged `draft`; the tag never exempts an empty body. A `folder` note needs only a nonempty body: any content passes, with or without `draft`.
+Nonempty `data.words` on a language note (`type: skill`, `subType: language`), or `data.glossary` on a culture or affiliation, supplies page content without an authored body. Every other typed note requires a nonempty body, including drafts, folders and homepages. An empty or whitespace-only body is otherwise an error. A nonempty body with fewer than 25 prose words warns unless tagged `draft`; the tag never exempts an empty body. A `folder` note needs only a nonempty body: any content passes, with or without `draft`.
 
 Start with [your first note](authoring/first-note.md). It explains the smallest valid note and shows the JournalEntry, web page, book entry, and content-index record made from it. Then use the chapters below in the order your note needs them.
 
@@ -166,6 +166,6 @@ Places, affiliations, lore and beings may name their culture in `data.culture`,
 
 An affiliation may name the trade, temple or order tongue it keeps in its own `data.language`. An affiliation that reaches no culture is a warning, in a tree holding a culture note. A language needs no culture and no affiliation. See [type: affiliation](reference/format-details.md#type-affiliation).
 
-A language note (`type: skill`, `subType: language`) states its words in frontmatter: `data.words` states each word as a map of its form, class, field and gloss — one sense or a list of them, which a dictionary numbers — with its source, its variant forms, the pieces it is built from and a note, beside `data.classModifiers`, `data.fields` and `data.affixes`, each affix with the `kind` it makes, for a given name's ending who the name is `given` to, and the stem closes it is barred after; a zero affix states `zero: true` and no form. The notes a word is cited from are derived, not written: a note cites a word by marking it in italics in its prose, matched by form or a variant with diacritics and case set aside. The language of a word is the note it sits on, and none of it reaches the compiled Item. A daughter language names its parent in `data.family` and reads the parent's words as its own; the `language_lineage` relation joins a language to its ancestors. Classes come from the [master word classes](reference/format-details.md#word-classes). A culture or an affiliation states its own glossary terms in `data.glossary`, and every entry resolves to a language — its own `language`, else the affiliation's, its parents' or its culture's, else the culture's — or is an error at the entry. The `words`, `affixes`, `fields`, `glossary` and `language_lineage` relations hold them for `sql` fences, the `dictionary` relation lists each word under every language that has it, inherited words included, and the `terms` relation each glossary entry, rank and office with the cultures it reaches; a fence sets them with `layout=dictionary` or `layout=glossary`. A language note names the tag a dictionary prints for it in `data.abbreviation`. Every fact a check reads about a language's names, sounds and history is frontmatter too: `data.tongues` and `data.register` (every name the setting gives in the language's reach, the notes carrying each derived from the index), `data.retired`, `data.scope`, `data.sounds` (letters with their place, word edges from a closed list, the cluster limit and the groups of clusters inside a word, the stress rule, syllable finals, syllable rules and vowel harmony with each vowel's front partner, the joining of parts, written marks, a root's skeleton vowel and frames, the spellings read past, and named mutations such as wearing and voicing), `data.soundChanges` (named sets of ordered steps), `data.elements` (each standing `opening`, `closing`, `either` or `link`, for one kind of name, with the word it is the stem of and its genitive), `data.roots`, `data.cognates` (with a reconstructed `proto` form), `data.callingNames`, `data.older` (the forms older than the rules), `data.negation` (the negative particle and the mutation it brings) and `data.naming` (how long each class of name runs, the edges names keep that words do not, the element kinds each kind of name draws on, what a place name takes from what it is held from, and the near name), each a relation — `sounds` as `letters`, `edges`, `clusters`, `cluster_groups`, `stress`, `finals`, `syllables`, `joining`, `joins`, `marks`, `skeleton`, `frames`, `read_past` and `mutations`, `soundChanges` as `sound_changes`, `callingNames` as `calling_names` — that a fence sets back on the page. A word's citations also come from a note whose name, alias or rank or office title spells it whole. See [a language's words](reference/format-details.md#a-languages-words), [a language's register, sounds and history](reference/format-details.md#a-languages-register-sounds-and-history), [glossary terms](reference/format-details.md#glossary-terms) and [dictionaries and glossaries](reference/format-details.md#dictionaries-and-glossaries).
+A language note (`type: skill`, `subType: language`) states its words in frontmatter: `data.words` states each word as a map of its form, class, field and gloss — one sense or a list of them, which a dictionary numbers — with its source, its variant forms, the pieces it is built from and a note, beside `data.classModifiers`, `data.fields` and `data.affixes`, each affix with the `kind` it makes, for a given name's ending who the name is `given` to, and the stem closes it is barred after; a zero affix states `zero: true` and no form. The notes a word is cited from are derived, not written: a note cites a word by marking it in italics in its prose, matched by form or a variant with diacritics and case set aside. The language of a word is the note it sits on, and none of it reaches the compiled Item. A daughter language names its parent in `data.family` and reads the parent's words as its own; the `language_lineage` relation joins a language to its ancestors. Classes come from the [master word classes](reference/format-details.md#word-classes). A culture or an affiliation states its own glossary entries in `data.glossary`: common words in its core vocabulary, dictionary words with a context meaning, or phrases, compounds and terms of art outside the dictionary with their own gloss. An entry naming a word of its resolved language takes the word's senses and class and links to its language entry; a `definition` supplies the entry's meaning instead. Common marks belong to the glossary's owner. A language note with nonempty `data.words` receives its full Dictionary section automatically: one alphabetical list with field tags and one key. A culture or affiliation with nonempty `data.glossary` receives only its explicitly declared entries in its Glossary section; ranks and offices stand in the affiliation's own sections. A note without the relevant frontmatter receives no such section. All surfaces show these sections after the authored text, or under an existing `{#dictionary}`, `{#lexicon}` or `{#glossary}` heading after its introduction. There are no setting-wide dictionary or glossary pages. Every entry resolves to a language — its own `language`, else the affiliation's, its parents' or its culture's, else the culture's — or is an error at the entry. The `words`, `affixes`, `fields`, `glossary` and `language_lineage` relations hold them for `sql` fences, the `dictionary` relation lists each word under every language that has it, inherited words included, and the `terms` relation each glossary entry, rank and office with its culture associations; a fence sets custom views with `layout=dictionary` or `layout=glossary`. A language note names the tag a dictionary prints for it in `data.abbreviation`. Every fact a check reads about a language's names, sounds and history is frontmatter too: `data.tongues` and `data.register` (every name the setting gives in the language's reach, the notes carrying each derived from the index), `data.retired`, `data.scope`, `data.sounds` (letters with their place, word edges from a closed list, the cluster limit and the groups of clusters inside a word, the stress rule, syllable finals, syllable rules and vowel harmony with each vowel's front partner, the joining of parts, written marks, a root's skeleton vowel and frames, the spellings read past, and named mutations such as wearing and voicing), `data.soundChanges` (named sets of ordered steps), `data.elements` (each standing `opening`, `closing`, `either` or `link`, for one kind of name, with the word it is the stem of and its genitive), `data.roots`, `data.cognates` (with a reconstructed `proto` form), `data.callingNames`, `data.older` (the forms older than the rules), `data.negation` (the negative particle and the mutation it brings) and `data.naming` (how long each class of name runs, the edges names keep that words do not, the element kinds each kind of name draws on, what a place name takes from what it is held from, and the near name), each a relation — `sounds` as `letters`, `edges`, `clusters`, `cluster_groups`, `stress`, `finals`, `syllables`, `joining`, `joins`, `marks`, `skeleton`, `frames`, `read_past` and `mutations`, `soundChanges` as `sound_changes`, `callingNames` as `calling_names` — that a fence sets back on the page. A word's citations also come from a note whose name, alias or rank or office title spells it whole. See [a language's words](reference/format-details.md#a-languages-words), [a language's register, sounds and history](reference/format-details.md#a-languages-register-sounds-and-history), [glossary terms](reference/format-details.md#glossary-terms) and [dictionaries and glossaries](reference/format-details.md#dictionaries-and-glossaries).
 
 Blockquote alerts use `[!NOTE]`, `[!TIP]`, `[!IMPORTANT]`, `[!WARNING]`, or `[!]`, with optional attributes after the marker. They replace the former info and warn div fences; secret blocks remain supported. See [alerts](authoring/links-and-markup.md#alerts).

package/docs/diagnostics.md

@@ -170,7 +170,7 @@ package-build.config.yaml:382:64: error: package-build config: `site.sections.be
 
 ## A worked case: the three states of a note
 
-A note with an empty body is a **stub**, and the diagnostics about one show each
+A place note with an empty body is a **stub**, and the diagnostics about one show each
 rule above in turn.
 
 An empty body must be deliberate, so a stub that says nothing about itself is an

package/docs/guides/packs.md

@@ -20,7 +20,8 @@ Start with one pack for each document class the notes produce. An Item, Actor,
 Macro, Scene, or Adventure note can also produce a JournalEntry for its prose,
 so a package with those notes generally needs a JournalEntry pack. A missing
 pack for a document a note actually produces is a finding on that note. An
-empty body produces no prose journal and needs no pack for it.
+empty body without automatic Dictionary or Glossary content produces no prose
+journal and needs no pack for it.
 
 ```yaml
 packs:

package/docs/guides/reference-pages.md

@@ -62,10 +62,10 @@ takes.
 
 `data.pack: none` is appropriate when the page belongs on the site and in the
 index but does not need a Foundry compendium entry. A documentation package
-has no packs at all. A page with an empty body is a stub: it remains in the
-index for data references, but publishes no page address or anchors. Write a
-description for a stub and leave off the `draft` tag; use `draft` for a page
-with prose still in progress. The [stub rules](../reference/format-details.md#a-stub-is-a-note-with-an-empty-body)
+has no packs at all. A page with neither an authored body nor automatic
+Dictionary or Glossary content is a stub: it remains in the index for data
+references, but publishes no page address or anchors. Supply content before
+publishing; use `draft` for prose still in progress. The [stub rules](../reference/format-details.md#a-stub-is-a-note-with-an-empty-body)
 and [pack routing](packs.md) cover these cases.
 
 ## Link to the intended target
@@ -165,92 +165,115 @@ reconstructing them from filenames.
 
 ## Set words as a dictionary and terms as a glossary
 
-A language's words and a people's terms are each one `sql` fence, and nothing
-is copied into the note: the words come from the language notes' `data.words`,
-the terms from the `data.glossary` entries of cultures and affiliations and
-from the affiliations' ranks and offices, and a section changes when they do.
-`layout=dictionary` sets rows of the `dictionary` relation and
-`layout=glossary` rows of the `terms` relation. The query decides what
-appears, so any note may carry either.
+A language note's `data.words` supplies its Dictionary section automatically
+on the site, in the Foundry journal and in the book. The dictionary is the
+language's full word list, including inherited words, in one alphabetical
+sequence with letter headings, field tags and one key. A language with absent
+or empty `data.words` receives no Dictionary section.
 
-A language note lists its words, with the words it inherits from its parent
-language:
+The frontmatter states the words:
 
-````markdown
-# Dictionary {#dictionary}
-
-```sql {layout=dictionary section-level=2}
-SELECT * FROM dictionary WHERE language = 'thalorna-note-skill-provnzlng'
+```yaml
+shortcode: provnzlng
+name: { full: Provenzal Language }
+type: skill
+subType: language
+data:
+  classModifiers: [f, m]
+  fields:
+    - { name: Love and its conduct, holds: "Longing, courtship and the courts of love." }
+  words:
+    - {
+        form: solmère,
+        class: n m,
+        pronunciation: sol-MEH-reh,
+        field: Love and its conduct,
+        gloss: "longing; the ache for a person, a place or a time that is gone",
+      }
+    - {
+        form: amère,
+        class: n f,
+        field: Love and its conduct,
+        gloss: ["a beloved", "a sweetheart, in the songs"],
+      }
 ```
-````
 
-A culture note lists the words of its tongue a player is expected to know, and
-its glossary: its own terms and the ranks, offices and terms of every
-affiliation that reaches it.
+A culture or affiliation's `data.glossary` supplies its Glossary section. It
+contains only that owner's declared entries, so each culture and affiliation
+using a language chooses its own common words and context meanings. Ranks
+and offices stand in the affiliation's own sections; an explicit glossary
+entry can name one, but a glossary does not draw in the whole ladder or list
+of offices. A note with absent or empty `data.glossary` receives no Glossary
+section.
 
-````markdown
-# Words Everyone Knows {#common-words}
+The [worked culture glossary](../reference/format-details.md#glossary-terms)
+uses all three reasons for an entry:
 
-```sql {layout=dictionary section-level=2}
-SELECT * FROM dictionary WHERE language = 'thalorna-note-skill-provnzlng' AND common
+```yaml
+data:
+  language: skill-provnzlng
+  glossary:
+    - { name: solmère, common: true }
+    - { name: amère, definition: "a sweetheart, in the songs" }
+    - {
+        name: blood-field,
+        definition: "ground where a battle tore the boundary with the spirit world, and it did not close",
+      }
 ```
 
-# Glossary {#glossary}
-
-```sql {layout=glossary section-level=2}
-SELECT * FROM terms WHERE list_contains(cultures, 'thalorna-note-lore-provenzianclt')
-```
-````
+`solmère` is part of this culture's core vocabulary: the words a player needs
+to adventure there. With no `definition`, it carries the senses and class of
+the dictionary word and links to that word's entry. `amère` supplies a context
+meaning, which takes the place of its dictionary senses while retaining the
+word link and class. `blood-field` supplies a gloss for a term outside the
+dictionary. Common marks belong to the glossary's owner; dictionaries mark
+nothing common. There are no setting-wide dictionary or glossary pages.
 
-The glossary renders as a key, a heading per letter and one paragraph per
-term, each sense tagged with the body or culture it comes from and each term
-in another tongue tagged with it:
+The generated sections follow the note's authored text. A heading with
+`{#dictionary}` or `{#lexicon}` receives the Dictionary list, and a heading
+with `{#glossary}` receives the Glossary list, after the authored text in
+that section. This preserves an introduction or loanword discussion under
+an anchored heading:
 
 ```markdown
-**Key:** _Lit._ Liturgic Language; • a common word, which a player is expected to know by heart.
+# Lexicon {#lexicon}
 
-## K
-
-**Knight-Captain** **1** (_Kingdom of Provenzia_) A knight who leads a company. **2** (_Kingdom of Provenzia_) Commands the guard in the field. — [[thalorna-note-affiliation-kingdom|Kingdom of Provenzia]]
-
-## O
-
-**Ordained Priest** _Lit._ (_Church of the Rite_) Ordained to serve a parish. — [[thalorna-note-affiliation-church|Church of the Rite]]
+The tongue of Provenzia, whose _solmère_ is its own word.
 ```
 
-The culture shapes both through its own `data.glossary`.
-`{name: solmère, common: true, pronunciation: sol-MEH-reh}` marks a word of its
-tongue common, so the first fence lists it, and gives it a respelling;
-`{name: Subject, common: true}` marks a rank and lets in a title of one word,
-which no glossary holds unless an entry names it; and
-`{name: blood-field, definition: …}` is a term of the culture's own.
+The list is generated once under that heading. Without such a heading, the
+build supplies **Dictionary** or **Glossary** at the end of the note.
 
-An affiliation lists its own terms with `WHERE owner = '<its Address>'`. The
-setting's two pages list everything, each word once and each term under every
-owner that holds it:
+### Custom views
 
-````markdown
-```sql {layout=dictionary}
-SELECT * EXCLUDE (common) FROM dictionary WHERE depth = 0
-```
-````
+An `sql` fence with `layout=dictionary` or `layout=glossary` can add a custom
+view of the same `dictionary` and `terms` relations. This one selects only a
+culture's common entries:
 
 ````markdown
-```sql {layout=glossary}
-SELECT * EXCLUDE (common) FROM terms
+# Words Everyone Knows {#common-words}
+
+```sql {layout=glossary section-level=2}
+SELECT * FROM terms WHERE owner = 'thalorna-note-lore-provenzianclt' AND common
 ```
 ````
 
-`package-build content-index` also writes both relations beside the index, for
-reading with `jq`:
+The `terms` relation also holds ranks and offices for custom queries. The
+default Glossary section selects only rows arising from its owner's explicit
+`data.glossary` entries, including an entry naming a rank or office. The
+[layout guide](../authoring/links-and-markup.md#dictionaries-and-glossaries)
+describes query options and rendering.
+
+`package-build content-index` writes both relations beside the index. To
+read a culture's own entries with `jq`:
 
 ```bash
-jq -r 'select(.cultures | index("thalorna-note-lore-provenzianclt")) | .name' \
+jq -r 'select(.owner == "thalorna-note-lore-provenzianclt") | .name' \
   build/content-index/thalorna-terms.jsonl
 ```
 
 The [format reference](../reference/format-details.md#dictionaries-and-glossaries)
-gives every column and every rule.
+gives every column and rule.
 
 ## Resolve another package