@heroiclands/package-build 23.12.5 → 23.12.6

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # @heroiclands/package-build
 
+## 23.12.6
+
+### Patch Changes
+
+A package can name a default calendar with `defaultCalendar` in its configuration, and it replaces the world note's calendar as the one dates fall back to.
+
+A note's dates print in its own `data.calendar`, which any note may now set, else its culture's, else for a place its parents', else the default. A place whose parents keep different calendars is a build error until it names its own.
+
+Chronologies and the other event sections print every date in the calendar of the page showing them, and `dateformat` with no calendar named uses the note's.
+
 ## 23.12.5
 
 ### Patch Changes

package/content-config.mjs

@@ -571,6 +571,10 @@ export function publishesContentPages(config) {
  *                                          resolved against it, so the build never
  *                                          depends on the working directory.
  * @property {string} [currentDate] Setting-wide neutral current date; defaults to "720.1".
+ * @property {string} [defaultCalendar]     Shortcode of the `lore` note with
+ *                                          `subType: calendar` that prints the
+ *                                          dates of a note no other rule gives a
+ *                                          calendar.
  * @property {string} contentPackage        Content package name — the address
  *                                          namespace every note in this
  *                                          repository is published under.
@@ -646,6 +650,8 @@ export function publishesContentPages(config) {
  *
  * @typedef {object} ContentBuildConfig
  * @property {string} currentDate Setting-wide neutral current date.
+ * @property {string|null} defaultCalendar The calendar of last resort's
+ *                                     shortcode, `null` when none is named.
  * @property {string} rootDir
  * @property {string} contentPackage
  * @property {string|null} foundryPackage  `null` for a `documentation`
@@ -730,6 +736,7 @@ const CONFIG_KEYS = [
     "rootDir",
     "contentPackage",
     "currentDate",
+    "defaultCalendar",
     "foundryPackage",
     "homepage",
     "authors",
@@ -912,6 +919,24 @@ function fail(field, problem) {
     throw Object.assign(new TypeError(`package-build config: \`${field}\` ${problem}.`), { field });
 }
 
+/**
+ * The configured `defaultCalendar`: a calendar note's shortcode, or `null`.
+ * Whether it names a calendar note is checked against the content tree when
+ * the content index is built.
+ *
+ * @param {unknown} value - The configured value.
+ * @returns {string|null} The shortcode.
+ */
+function normalizeDefaultCalendar(value) {
+    if (value === undefined || value === null) return null;
+    if (typeof value !== "string" || !isAddressSegment(value))
+        fail(
+            "defaultCalendar",
+            "must be the shortcode of a calendar note — lowercase letters and digits",
+        );
+    return /** @type {string} */ (value);
+}
+
 /**
  * @param {object} object
  * @param {readonly string[]} allowed
@@ -2973,6 +2998,7 @@ export function defineConfig(config) {
                 fail("currentDate", error.message);
             }
         })(),
+        defaultCalendar: normalizeDefaultCalendar(input.defaultCalendar),
         contentPackage: requireContentPackage(input.contentPackage, docEntryTypes, {
             rootDir,
             packageKind,

package/docs/api.md

@@ -723,7 +723,7 @@ resolved value: the culture a place or affiliation inherits through
 
 ### `engine.markdownExpressions`
 
-`renderMarkdownExpressions(body, { fm, dates, sqlResults, figures, file, bodyLine })` expands scalar frontmatter references and registered Handlebars helpers outside Markdown code. The `dateformat` helper uses `formatDateInCalendar`; `gt`, `gte`, `lt`, `lte`, `eq`, `and`, `or`, and `not` evaluate explicit comparisons. The `sql` helper reads a prepared scalar result, which must contain one row and one column. The `ref` helper links to a captioned item by its anchor — `"#thorn"` on the same note — in `number` (the default, and admitted explicitly), `full` or `title` form; `figures` is a `Map` of this note's own figures, by id, to `{label, caption, hasCaption}`, and an address naming another note is reported as unresolved rather than looked up. `sqlQueriesInMarkdown` discovers SQL calls, including nested calls; `prepareInlineSqlExpressions` evaluates them through the same DuckDB connection as SQL tables. `EXPRESSION_HELPERS` is the one list of helpers: the engine registers from it and the authoring document is checked against it, so each name there carries the parameters it takes and a sentence on what it does. The renderer returns `{ markdown, findings }`, with source positions for invalid expressions. Site, Foundry and PDF passes invoke it after generated tables expand and before links resolve. Hugo shortcodes remain literal for the site renderer.
+`renderMarkdownExpressions(body, { fm, dates, sqlResults, figures, file, bodyLine })` expands scalar frontmatter references and registered Handlebars helpers outside Markdown code. The `dateformat` helper uses `formatDateInCalendar`, in the calendar it names or else the note's resolved calendar, which it reads from `dates.noteCalendars` — the map a reckoning context built over content-index records carries; `gt`, `gte`, `lt`, `lte`, `eq`, `and`, `or`, and `not` evaluate explicit comparisons. The `sql` helper reads a prepared scalar result, which must contain one row and one column. The `ref` helper links to a captioned item by its anchor — `"#thorn"` on the same note — in `number` (the default, and admitted explicitly), `full` or `title` form; `figures` is a `Map` of this note's own figures, by id, to `{label, caption, hasCaption}`, and an address naming another note is reported as unresolved rather than looked up. `sqlQueriesInMarkdown` discovers SQL calls, including nested calls; `prepareInlineSqlExpressions` evaluates them through the same DuckDB connection as SQL tables. `EXPRESSION_HELPERS` is the one list of helpers: the engine registers from it and the authoring document is checked against it, so each name there carries the parameters it takes and a sentence on what it does. The renderer returns `{ markdown, findings }`, with source positions for invalid expressions. Site, Foundry and PDF passes invoke it after generated tables expand and before links resolve. Hugo shortcodes remain literal for the site renderer.
 
 | Export                      | Signature                                  | Returns                | Use it when                                      |
 | --------------------------- | ------------------------------------------ | ---------------------- | ------------------------------------------------ |
@@ -736,10 +736,13 @@ resolved value: the culture a place or affiliation inherits through
 
 The corpus registry anchors each calendar's year 1, day 1 to its canonical `data.epoch` and maps every declared era to that calendar. Exactly one `start: null` era covers earlier years and counts backwards; exactly one `start: 1` era begins the forward count. Other starts are distinct positive calendar years. Numeric order determines bounds, irrespective of array order. Duplicate starts and markers, missing required eras, and invalid epochs are findings. Short qualifiers are ambiguous when they name eras in several packages; a full Address selects one.
 
-| Export                    | Signature                                     | Returns                                  | Use it when                                                 |
-| ------------------------- | --------------------------------------------- | ---------------------------------------- | ----------------------------------------------------------- |
-| `resolveReckoningMarkers` | `resolveReckoningMarkers(index, daysPerYear)` | `{eras, markers, findings}`              | resolving authored eras, their markers, and their bounds    |
-| `reckoningContext`        | `reckoningContext(index)`                     | `{eras, markers, daysPerYear, findings}` | sharing one resolved date context across checks on a corpus |
+| Export                    | Signature                                     | Returns                                                 | Use it when                                                                                           |
+| ------------------------- | --------------------------------------------- | ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| `resolveReckoningMarkers` | `resolveReckoningMarkers(index, daysPerYear)` | `{eras, markers, findings}`                             | resolving authored eras, their markers, and their bounds                                              |
+| `reckoningContext`        | `reckoningContext(index)`                     | `{eras, markers, daysPerYear, findings, noteCalendars}` | sharing one resolved date context across checks on a corpus                                           |
+| `noteCalendarMap`         | `noteCalendarMap(notes)`                      | `Map<string, string>`                                   | reading each record's `resolvedCalendar` by note, as `reckoningContext` carries it in `noteCalendars` |
+| `noteCalendarKey`         | `noteCalendarKey(fm)`                         | `string \| undefined`                                   | finding a note's entry in `noteCalendars` by its type and shortcode                                   |
+| `calendarAddress`         | `calendarAddress(value)`                      | `string \| undefined`                                   | reading a record's `resolvedCalendar`, tuple or string, as its canonical Address                      |
 
 ### `engine.calendarNotes`
 

package/docs/authoring/dates-and-calendars.md

@@ -84,7 +84,35 @@ package-build dateto commoncal 326.114 --format long
 
 The CLI `datefrom` command requires a day and reads the default (`std`, or first) pattern. `dateto` prints the era covering the canonical day. A clock time makes a date exact; a year or day without one spans the stated interval. `data.epoch` and `data.moon.newOn` require a day. The [detailed date rules](../reference/format-details.md#dates-and-calendars) describe precision and bounds.
 
-In prose, `{{dateformat "commoncal" data.born}}` prints a date in the chosen calendar. `{{dateformat data.calendar data.born}}` uses the note's calendar Address. A third argument chooses another named pattern. A being or place can set `data.calendar`; its infobox uses that calendar for dates.
+In prose, `{{dateformat "commoncal" data.born}}` prints a date in the chosen calendar, and `{{dateformat data.born}}` prints it in the note's own calendar. A last argument chooses another named pattern: `{{dateformat "commoncal" data.born "long"}}`, or `{{dateformat data.born "long"}}`.
+
+## Choose the calendar a note's dates print in
+
+Every note reads its dates in one calendar. The infobox's birth and death dates, `dateformat` with no calendar named, and every date in the event sections the build adds to the note's page all print in it. It is the first of:
+
+1. the note's own `data.calendar`, which any note may set and which always wins;
+2. its culture's calendar — the `data.calendar` of the culture note its `data.culture` names;
+3. for a place, its parents' calendar — the calendar each place in its `data.parents` reads in, by these same rules;
+4. the package's `defaultCalendar`, set in the [configuration](../configuration.md#defaultcalendar);
+5. otherwise none, and a date prints as it was written.
+
+```yaml
+# package-build.config.yaml
+defaultCalendar: commoncal
+```
+
+```yaml
+# A town in a province that keeps the Vylarian count
+type: place
+subType: settlement
+shortcode: brenford
+data:
+  parents: [vylaria]
+```
+
+Brenford names no calendar and no culture, so it reads in Vylaria's. A place whose parents read in **different** calendars is a build error at its `data.parents`, naming the place and each calendar; give the place its own `data.calendar` to settle it. A parent, or a culture, that only reaches the default counts for nothing, so a place among parents that all fall through to `defaultCalendar` takes the default without an error.
+
+An event section prints every date in the calendar of the page showing it, whichever note the event is written on: Brenford's chronology reads in Vylaria's count even where an event comes from a history kept in the common calendar. The [format reference](../reference/format-details.md#a-notes-calendar) gives the rules in full.
 
 ## Write a recurring date
 

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

@@ -1342,7 +1342,7 @@ The first call lists every page tagged `key-concept` alphabetically by title. Th
 An expression in `{{ }}` is replaced by a value, inline in a sentence. The note's own frontmatter is the context, so a field is read by the path a note writes it at.
 
 ```markdown
-{{name.full}} was born on {{dateformat data.calendar data.born}}.
+{{name.full}} was born on {{dateformat data.born}}.
 There are {{words (sql "SELECT COUNT(*) FROM notes WHERE type = 'being'")}} beings.
 ```
 
@@ -1373,14 +1373,14 @@ There are {{words (sql "SELECT COUNT(*) FROM notes WHERE type = 'being'")}} bein
 | `words`      | `number`                                                                                               | The number spelled out for running prose — `1200` becomes one thousand two hundred. Whole numbers only; a decimal is a finding, and `digits` takes one.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | `digits`     | `number`                                                                                               | The number as a grouped numeral — `1200` becomes 1,200, and a fractional part is kept.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 | `sql`        | `"query"`                                                                                              | The single value a query returns, for use inside a sentence. The query is a quoted string, the same SQL a table fence takes.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| `dateformat` | `calendar date ["format"]`                                                                             | A date written in a calendar. The calendar is an Address or its shortcode, the date is the value a note carries, and the optional third argument names an output pattern.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `dateformat` | `[calendar] date ["format"]`                                                                           | A date written in a calendar. The calendar is an Address or its shortcode; left out, it is the note's own calendar — its `data.calendar`, else its culture's, else for a place its parents', else the configured `defaultCalendar` — and a note with none prints the date as written. The date is the value a note carries, and the optional last argument names an output pattern.                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | `ref`        | `address [form="number"\|"full"\|"title"] \| address field="when"\|"until"\|"kind"\|"summary"\|"name"` | A link to a captioned item, by its anchor — `"#thorn"` on this note, `"note-address#thorn"` on another. `form` is `number` (the default, and admitted explicitly), rendering "Figure 13"; `full`, the number and the caption; or `title`, the caption alone. Always renders as a link to the figure, and a link inside the caption contributes only its label text. The number rendered is the one the figure carries on the surface doing the rendering, whichever note names it. With `field` in place of `form`, the address names an event — `"place-ironfells#sack"`, `"#sack"` on this note, or `"lore-founding"` for a note holding one event — and the reference prints that event's `when`, `until`, `kind`, `summary` or `name` as plain text, never a link; a date prints as the note format prints any date. |
 
 <!-- expression-helpers:end -->
 
 A helper that is given the wrong kind of value reports it rather than printing something wrong: `words` refuses a decimal, the four comparisons refuse anything that is not a finite number, and `dateformat` refuses a date it cannot resolve in the calendar it was given.
 
-See [date rules](dates-and-calendars.md) for what `dateformat` accepts and the patterns its third argument names.
+See [date rules](dates-and-calendars.md) for what `dateformat` accepts, the calendar it uses when none is named, and the patterns its last argument names.
 
 ### An event's date, inline
 

package/docs/configuration.md

@@ -54,7 +54,7 @@ around its own evaluation.
 
 ### Quick reference
 
-24 top-level keys. `rootDir` is not one of them — a data configuration never
+25 top-level keys. `rootDir` is not one of them — a data configuration never
 writes it — and is documented under [Derived values](#derived-values) instead,
 alongside `foundryPackage`, `homepage`, `author` and `itemBuilders`, whose
 data-configuration behaviour is also derivation rather than ordinary
@@ -63,6 +63,7 @@ authoring.
 | Key                                         | Type                                                                       | Required                                                                                           | Default                   |
 | ------------------------------------------- | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ------------------------- |
 | [`currentDate`](#currentdate)               | quoted neutral date string                                                 | no                                                                                                 | `"720.1"`                 |
+| [`defaultCalendar`](#defaultcalendar)       | calendar note shortcode                                                    | no                                                                                                 | —                         |
 | [`contentPackage`](#contentpackage)         | string                                                                     | yes                                                                                                | —                         |
 | [`foundryPackage`](#foundrypackage)         | string                                                                     | yes (`.mjs` only — derived in YAML); refused in a `documentation` package                          | —                         |
 | [`homepage`](#homepage)                     | string                                                                     | no (`.mjs` only — derived in YAML)                                                                 | `null`                    |
@@ -88,7 +89,7 @@ authoring.
 
 Any key outside this list is refused:
 
-> `` `<key>` is not a recognized option (expected one of: rootDir, contentPackage, currentDate, foundryPackage, homepage, authors, packageKind, stats, itemBuilders, paths, skipDirectories, forbidGeneratedArt, icons, packs, docs, site, pdf, compatibility, relationships, systems, requiresSystem, packageBuild, publish, changelog). ``
+> `` `<key>` is not a recognized option (expected one of: rootDir, contentPackage, currentDate, defaultCalendar, foundryPackage, homepage, authors, packageKind, stats, itemBuilders, paths, skipDirectories, forbidGeneratedArt, icons, packs, docs, site, pdf, compatibility, relationships, systems, requiresSystem, packageBuild, publish, changelog). ``
 
 (`rootDir` appears in that list because it is a key `defineConfig` itself
 accepts — an `.mjs` configuration authors it directly. A YAML configuration
@@ -195,7 +196,7 @@ build writes its `name` as `params.author`. `null` when `authors` is empty.
 as an unknown key, at the key's own line, because `authors` is the one list a
 package names its people in:
 
-> ``package-build config: `author` is not a recognized option (expected one of: rootDir, contentPackage, currentDate, foundryPackage, homepage, authors, packageKind, stats, itemBuilders, paths, skipDirectories, forbidGeneratedArt, icons, packs, docs, site, pdf, compatibility, relationships, systems, requiresSystem, packageBuild, publish, changelog).``
+> ``package-build config: `author` is not a recognized option (expected one of: rootDir, contentPackage, currentDate, defaultCalendar, foundryPackage, homepage, authors, packageKind, stats, itemBuilders, paths, skipDirectories, forbidGeneratedArt, icons, packs, docs, site, pdf, compatibility, relationships, systems, requiresSystem, packageBuild, publish, changelog).``
 
 `package.json`'s own `author` is npm's and is not read.
 
@@ -313,6 +314,29 @@ day. Named calendars, `unknown`, numeric YAML values and malformed dates are
 configuration errors located at `currentDate`. Birth dates can still use named
 calendars when the output has the relevant calendar context.
 
+### `defaultCalendar`
+
+**Type:** string · optional · no default.
+
+The shortcode of the `lore` note with `subType: calendar` that prints the dates
+of every note no other rule gives a calendar. A note reads its dates in its own
+`data.calendar`, else its culture's, else — for a place — its parents', and
+only then in this one; with no `defaultCalendar` and nothing else to go on, a
+date prints as it was written. The
+[format reference](reference/format-details.md#a-notes-calendar) gives the
+rules in full.
+
+```yaml
+contentPackage: thalorna
+defaultCalendar: commoncal
+```
+
+A value that is not a lowercase alphanumeric shortcode is a configuration
+error at load. A shortcode that names no calendar note in the package is a
+build error located at `defaultCalendar`:
+
+> `defaultCalendar commonkal names no calendar note in thalorna; name the shortcode of a lore note with subType: calendar`
+
 ### `contentPackage`
 
 **Type:** string · **Required** · no default.

package/docs/guides/module-project.md

@@ -275,7 +275,7 @@ Five keys, and each answers a question the build cannot answer for itself:
 Everything omitted has a default, and the defaults are the conventional
 HeroicLands layout: the content tree at `assets/content`, the compiled packs at
 `build/stage/packs`, the intermediates and caches elsewhere under `build/`.
-[`configuration.md`](../configuration.md) documents all eighteen top-level keys,
+[`configuration.md`](../configuration.md) documents every top-level key,
 what each refusal message means, and the five values that are derived rather
 than authored.
 

package/docs/reference/format-details.md

@@ -432,17 +432,55 @@ A named date uses `datefrom <calendar> <date>`, where the final text follows the
 
 `package-build datefrom <calendar> <date>` reads the default calendar pattern and prints a canonical day. `package-build dateto <calendar> <canonical-date>` prints the day in the covering era; `--format <name>` chooses another named output pattern. The [authoring guide](../authoring/dates-and-calendars.md) gives a complete example.
 
+##### A note's calendar
+
+A note's dates print in one calendar, the first of:
+
+1. its own `data.calendar`, which every note type accepts, and which always
+   wins;
+2. its culture's calendar: the culture note its `data.culture` names, resolved
+   by these same rules — in effect that culture's own `data.calendar`;
+3. for a `place`, its parents' calendar: each note its `data.parents` names,
+   resolved by these same rules;
+4. the package's [`defaultCalendar`](../configuration.md#defaultcalendar);
+5. otherwise none, and a date prints as it was written.
+
+Steps 2 and 3 take only a calendar that some note states. A culture or a
+parent that itself falls through to `defaultCalendar` contributes nothing, so a
+place whose parents all fall through takes the default. Parents that resolve to
+**two or more distinct calendars** are a build error at the place's
+`data.parents`, naming the place and each calendar with the parent it came
+through:
+
+```text
+Places/Edge.md:6:3: error: place edge: data.parents resolve to different calendars (thalorna-note-lore-commoncal via north, thalorna-note-lore-vrcal via south); state data.calendar
+```
+
+Stating `data.calendar` on the place settles it. A cycle through
+`data.parents` or `data.culture` contributes nothing, and the chain goes on to
+`defaultCalendar`. A culture or parent in another package contributes the
+`data.calendar` its published entry states, and nothing else.
+
+The calendar decides what a reader sees wherever the note prints a date: the
+infobox's `born` and `died`, `dateformat` with no calendar named, the `events`
+relation's `whenText`, and every date in the [event views](#event-views) the
+note's page shows.
+
 Markdown prose accepts inline `{{...}}` expressions. A property path reads
 the note's frontmatter, and `dateformat` converts a date to the reckoning used by a
-specified calendar. The first argument names a calendar note by shortcode or
-Address, or one of its eras by `<calendar>.<era>`. Use a full Address when a
-short name is ambiguous. The second argument is a canonical date or a
-frontmatter property holding a date. An optional third argument names an output
-format from the calendar note. An explicit era that does not cover the date is an error.
+calendar. The first argument names a calendar note by shortcode or Address, or
+one of its eras by `<calendar>.<era>`; left out, the calendar is
+[the note's own](#a-notes-calendar), and a note with none prints the date as
+written. Use a full Address when a short name is ambiguous. The date is a
+canonical date or a frontmatter property holding a date. An optional last
+argument names an output format from the calendar note. With two arguments,
+the first is the calendar unless it is a date that names no calendar, so
+`{{dateformat data.born "long"}}` prints the note's date in its own calendar's
+`long` format. An explicit era that does not cover the date is an error.
 
 ```markdown
 {{name.full}} was born on {{dateformat "vrcal" data.born}}.
-{{dateformat data.calendar data.born}}
+{{dateformat data.born}}
 The event fell on {{dateformat "vrcal" "300.25"}}.
 {{and (gt 3 5) (lt 4 2)}}
 {{sql "SELECT COUNT(*) FROM notes WHERE type = 'being'"}}
@@ -870,6 +908,7 @@ noticed:
 | `seeAlso`              | list of `{ address, gloss? }` | Deliberate cross-references in reading order, shown on the site, in journals and in books. |
 | `seeAlso[].address`    | a note `Address`              | Required; the whole note to read next.                                                     |
 | `seeAlso[].gloss`      | `string`                      | An optional short phrase saying why to follow the reference.                               |
+| `calendar`             | `Address`                     | The calendar note this note's dates print in — see [a note's calendar](#a-notes-calendar). |
 | `id`                   | `string`                      | A pinned document identity.                                                                |
 | `pack`                 | `string`                      | The shared compendium route.                                                               |
 | `packFolder`           | `Address` or pack map         | The shared compendium folder Address.                                                      |
@@ -2972,14 +3011,22 @@ ORDER BY whenSort
 ```
 ````
 
-| Column                   | What it holds                                                                                                                                                                                                                                                                                  |
-| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `note`                   | The canonical Address of the note the event is written on.                                                                                                                                                                                                                                     |
-| `address`                | The event's own Address: `note#id` where the event has an `id`, the note's Address alone where it has none.                                                                                                                                                                                    |
-| `id`, `kind`, `depth`, … | Every key of an event, each its own column under its own name — `id`, `kind`, `depth`, `when`, `until`, `recurs`, `summary`, `standing`, `names`, `where`, `who`, `follows`, `accounts`, `unresolved`, `sources`, `stated`.                                                                    |
-| `whenSort`, `untilSort`  | The date's position on the canonical axis: the canonical year, with a day as its fraction of the year where the calendar states the year's length. `ORDER BY whenSort` is date order.                                                                                                          |
-| `whenText`, `untilText`  | The date as a reader sees it, printed as `dateformat` prints it in the calendar the owning note names in `data.calendar`, else the one the world note names, else in the era the date itself names; `~` marks an approximate date. A date that does not resolve keeps the text its note wrote. |
-| `whenYear`, `untilYear`  | The canonical year alone, for a filter such as `whenYear BETWEEN 200 AND 299`.                                                                                                                                                                                                                 |
+| Column                   | What it holds                                                                                                                                                                                                                                                            |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `note`                   | The canonical Address of the note the event is written on.                                                                                                                                                                                                               |
+| `address`                | The event's own Address: `note#id` where the event has an `id`, the note's Address alone where it has none.                                                                                                                                                              |
+| `id`, `kind`, `depth`, … | Every key of an event, each its own column under its own name — `id`, `kind`, `depth`, `when`, `until`, `recurs`, `summary`, `standing`, `names`, `where`, `who`, `follows`, `accounts`, `unresolved`, `sources`, `stated`.                                              |
+| `whenSort`, `untilSort`  | The date's position on the canonical axis: the canonical year, with a day as its fraction of the year where the calendar states the year's length. `ORDER BY whenSort` is date order.                                                                                    |
+| `whenText`, `untilText`  | The date as a reader of the owning note sees it, printed as `dateformat` prints it in [the owning note's calendar](#a-notes-calendar), else in the era the date itself names; `~` marks an approximate date. A date that does not resolve keeps the text its note wrote. |
+| `whenIn`, `untilIn`      | The date in every calendar: a struct keyed by each calendar note's canonical Address, holding the date as `dateformat` prints it there. `whenIn['thalorna-note-lore-commoncal']` reads it in that calendar; a date that calendar cannot print reads as in `whenText`.    |
+| `whenYear`, `untilYear`  | The canonical year alone, for a filter such as `whenYear BETWEEN 200 AND 299`.                                                                                                                                                                                           |
+
+A fence chooses which calendar its dates print in. `whenText` prints each
+row in the calendar of the note that owns the event, so a table gathering the
+events of notes with different calendars reads in more than one count;
+`whenIn['<calendar Address>']` prints every row in one. The generated [event
+views](#event-views) do the second, in the calendar of the page showing the
+view.
 
 `when` and `until` read as the text the note wrote, `~` included. The sort
 keys and years are positions on the canonical axis, which counts a year `0`
@@ -3777,7 +3824,7 @@ The build appends sections to the end of a note's body that list the events conc
 | Accounts      | `accounts`   | an `affiliation`, a `place`, a `lore` note of `subType: culture` | each `accounts[]` entry the note gives, with the event it concerns                                                                                                                | When, Event, What they say, Agrees |
 | What followed | `followed`   | a note holding events                                            | events whose `follows[].event` names one of this note's events, with how                                                                                                          | When, What followed, How           |
 
-- **Every view's first column is When**, the event's date written in the setting's calendar — the `events` relation's `whenText` column. An event whose date does not resolve shows the text its note wrote.
+- **Every view's first column is When**, every row's date written in [the calendar of the page showing the view](#a-notes-calendar), whichever note owns the event, so one table reads in one count. The fence reads `whenIn['<calendar Address>']` for that calendar; on a page with no calendar it reads `whenText`, each date in its owning note's calendar. An event whose date does not resolve shows the text its note wrote.
 - **A chronology's Felt here column appears only where some row is felt in the place.** A place whose rows are all events that happened there, or world events, has the When and What happened columns alone.
 - **A chronology is always set across the full page width in a PDF book**, whatever its columns.
 - **The views follow everything the author wrote**, in the order of the [generated sections](#generated-sections).
@@ -4080,7 +4127,6 @@ See [a being's subtype describes the subject](#a-beings-subtype-describes-the-su
 | `gender`                           | `male \| female \| nonbinary \| none \| other` | Gender of the being — see [a being's look](#a-beings-look)                                                                                            |
 | `species`                          | `Address`                                      | Being's species (lore)                                                                                                                                |
 | `born`                             | `date \| unknown`                              | When the being was born; absent, it was never born                                                                                                    |
-| `calendar`                         | `Address`                                      | Calendar note that prints the being's dates                                                                                                           |
 | `died`                             | `date \| unknown`                              | When the being died; absent, it is alive                                                                                                              |
 | `age`                              | `34 \| ~34`                                    | Age in years, stated only to override what `born` says; `~` marks an estimate                                                                         |
 | `ageYears`                         | `number`                                       | Written by the compiler beside an `age` estimate — the `~` stripped; a note never authors this                                                        |
@@ -6982,7 +7028,6 @@ level with no background prints nothing.
 | `data` property                   | Values                                                                           | Description                                                                                               |
 | --------------------------------- | -------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
 | `events`                          | event entries — see [Events](#events)                                            | What happened to or at this subject: dated, attributed events                                             |
-| `calendar`                        | `Address`                                                                        | Calendar note that prints this place's dates                                                              |
 | `demonym`                         | `string`                                                                         | What a person from this place is called — a Vylarian                                                      |
 | `purpose`                         | `placeCharacter` tag                                                             | The reason a settlement, site, or structure exists                                                        |
 | `lore`                            | `Address[]`                                                                      | Lore concerning this place — its peoples, its law, its calendar, its history                              |

package/docs/reference/note-types.md

@@ -32,14 +32,15 @@ These are the only keys a note writes at its top level, in the order the formatt
 
 These fields are accepted by every note type. A field's value can still be irrelevant to a particular output; the build reports that where it can. `data.icon` is not shared: it is listed under each type whose document carries art.
 
-| Field             | Shape                                           | Meaning                                                                                                                       |
-| ----------------- | ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| `data.seeAlso`    | list of `{ address, gloss? }`                   | Deliberate cross-references in reading order, with optional glosses; shown on the site, in journals and in books.             |
-| `data.id`         | string                                          | A fixed document identity when the derived identity is unsuitable.                                                            |
-| `data.pack`       | string                                          | The shared compendium route, with a system block overriding it.                                                               |
-| `data.packFolder` | an Address, or a map of Addresses keyed by pack | The shared compendium folder Address, with a system block overriding it.                                                      |
-| `data.harnworld`  | `{ realm?, ritual? }`                           | HârnWorld source details shared by every system — `realm` and `ritual`.                                                       |
-| `data.banner`     | an Address                                      | The page's hero image — an `image` address, cut to 1792×768, or `none` to decline a hero image. Reaches no compiled document. |
+| Field             | Shape                                           | Meaning                                                                                                                                                                                    |
+| ----------------- | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `data.seeAlso`    | list of `{ address, gloss? }`                   | Deliberate cross-references in reading order, with optional glosses; shown on the site, in journals and in books.                                                                          |
+| `data.calendar`   | an Address                                      | The calendar this note's dates print in, as a calendar lore note. Absent, the note takes its culture's calendar, then — for a place — its parents', then the configured `defaultCalendar`. |
+| `data.id`         | string                                          | A fixed document identity when the derived identity is unsuitable.                                                                                                                         |
+| `data.pack`       | string                                          | The shared compendium route, with a system block overriding it.                                                                                                                            |
+| `data.packFolder` | an Address, or a map of Addresses keyed by pack | The shared compendium folder Address, with a system block overriding it.                                                                                                                   |
+| `data.harnworld`  | `{ realm?, ritual? }`                           | HârnWorld source details shared by every system — `realm` and `ritual`.                                                                                                                    |
+| `data.banner`     | an Address                                      | The page's hero image — an `image` address, cut to 1792×768, or `none` to decline a hero image. Reaches no compiled document.                                                              |
 
 **Inner keys** — a key a field's value does not declare is an error at its own line and column.
 
@@ -71,7 +72,6 @@ These fields are accepted by every note type. A field's value can still be irrel
 | `data.gender`                    | string                                         | One of `female`, `male`, `nonbinary`, `none` or `other`. `none` says the being has no gender; an absent field says its gender is unrecorded. See [a being's look](format-details.md#a-beings-look) for what each word means.                                                                                                                                                                                                                                                                                                                                                           |
 | `data.species`                   | an Address                                     | The being's species, as a lore note.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 | `data.born`                      | string                                         | When the being was born — a date, or `unknown` where the birth is unrecorded. Absent, the being was never born.                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| `data.calendar`                  | an Address                                     | Calendar that displays this being's dates.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
 | `data.died`                      | string                                         | When the being died — a date, or `unknown` where the death is unrecorded. Absent, the being is alive.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | `data.age`                       | string                                         | Age in years, stated only to override what `born` says — `34`, or `~34` for an estimate. Unstated beside a dated `born` it is computed; unstated beside an unknown or absent `born` the age is unknown.                                                                                                                                                                                                                                                                                                                                                                                |
 | `data.ageYears`                  | number                                         | Written by the compiler beside an `age` estimate — the `~` stripped, the magnitude alone. A note never authors this.                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
@@ -867,7 +867,6 @@ Lore records in-world knowledge. A `culture` describes a people; a `custom` desc
 | Field                                  | Shape                                                             | Meaning                                                                                                                                                                             |
 | -------------------------------------- | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `data.events`                          | list of event entries                                             | What happened to or at this subject — each entry one dated, attributed event: a founding, a war, a fall, or an occasion that recurs.                                                |
-| `data.calendar`                        | an Address                                                        | Calendar that displays this place's dates.                                                                                                                                          |
 | `data.demonym`                         | string                                                            | What a person from this place is called — a Vylarian.                                                                                                                               |
 | `data.purpose`                         | string                                                            | The reason this settlement, site, or structure exists, selected from its placeCharacter tags.                                                                                       |
 | `data.lore`                            | list of Addresses                                                 | Lore concerning this place — its peoples, its law, its calendar, its history.                                                                                                       |

package/engine/content-format.yaml

@@ -15,7 +15,6 @@ types:
             - gender
             - species
             - born
-            - calendar
             - died
             - age
             - ageYears
@@ -315,7 +314,6 @@ types:
     place:
         data:
             - events
-            - calendar
             - demonym
             - purpose
             - lore

package/engine/content-index.mjs

@@ -86,6 +86,7 @@
  */
 
 import { isAddressSegment } from "./address-charset.mjs";
+import { configFileIn, resolveNoteCalendars } from "./note-calendars.mjs";
 import { cultureInheritance, reportCultureParents } from "./culture-parents.mjs";
 import {
     formatDiagnostic,
@@ -162,7 +163,7 @@ import { resolveNoteId } from "./note-ids.mjs";
 // The `package:` refusal, so a note declaring one is reported where it is
 // rather than as a bare abort.
 import { assertNoDeclaredPackage } from "./note-package.mjs";
-import { loadPackConfig } from "./pack-config.mjs";
+import { CONFIG_FILENAMES, loadPackConfig } from "./pack-config.mjs";
 // The record accessors, which live apart so that a module the compilers load
 // can read a record without importing this one and closing a cycle.
 // Re-exported because this is where callers have always addressed them.
@@ -1062,6 +1063,10 @@ export function resolveCultures(
  *   reader receives each as a finding, and the emitter throws once, listing
  *   every one.
  * @param {string} [options.currentDate="720.1"] - Setting-wide neutral current date.
+ * @param {string} [options.defaultCalendar] - The calendar of last resort, a
+ *   calendar note's shortcode; see {@link module:engine/note-calendars}.
+ * @param {string} [options.configFile] - The configuration file, where an
+ *   unknown `defaultCalendar` is reported.
  * @param {(key: string) => ({culture?: unknown}|undefined)} [options.foreignRecord] -
  *   Another package's entry for a canonical address, read for a parent that
  *   package publishes; see {@link resolveCultures}.
@@ -1079,6 +1084,8 @@ export function collectContentIndex(
     {
         contentPackage,
         currentDate,
+        defaultCalendar,
+        configFile,
         skipDirectories,
         assetsBase,
         manifest,
@@ -1234,7 +1241,17 @@ export function collectContentIndex(
 
     // Every note record exists and every Address in it is a tuple, so a parent
     // is found by its canonical address. Before the sort, which reads nothing
-    // the pass writes.
+    // the pass writes. Calendars first: they read the culture a note states,
+    // which the culture pass then replaces with the one it resolves.
+    resolveNoteCalendars(records, {
+        contentPackage,
+        defaultCalendar,
+        configFile,
+        contentBase,
+        foreignRecord,
+        problems,
+        parsed,
+    });
     resolveCultures(records, { contentPackage, contentBase, foreignRecord, problems, parsed });
     const cultureNotes = records
         .filter((record) => isNoteRecord(record) && record.type === "lore")
@@ -1459,6 +1476,8 @@ export function indexRecordsFor({
     return collectContentIndex(tree, {
         contentPackage: resolved.contentPackage,
         currentDate: resolved.currentDate,
+        defaultCalendar: resolved.defaultCalendar ?? undefined,
+        configFile: configFileIn(resolved.rootDir, CONFIG_FILENAMES),
         addressContext: {
             ...noteAddressContext(resolved),
             declaresAddress: dependencyAddresses(resolved),

package/engine/content-links.mjs

@@ -239,6 +239,9 @@ export function buildLinkIndex(
         const body = splitFrontmatter(raw)?.body ?? raw;
         const type = record.type.toLowerCase();
         const note = { file: absPath, rel, fm, body, raw, type };
+        // The calendar the index resolved, which the reckoning context built
+        // over these notes hands to every date printed for this note.
+        if (record.resolvedCalendar) note.resolvedCalendar = record.resolvedCalendar;
         const hierarchyProblems = cultureRecordProblems(record);
         note.inheritedCultureFields = cultureInheritedFields(record);
         if (hierarchyProblems)