Concordius

3 min read

Appendix G — Release Notes

The running record of what changes in the published Concordius, and why. One file per month, one entry per day (newest day first). The work is under constant revision, so this is the place to learn what moved without re-reading the corpus.

Scope — published content only

This log records changes to the published corpus on the website — papers, readings, chapters, and substantive appendix material that a reader can see. An entry is appended whenever such a change reaches website/content/.

It does not record backstage work: the Town Press editorial machinery and its review memos, the character files and the setting, internal ledgers and plans, tooling, repository operations, or edits to this release-notes apparatus itself. If a change never reached the website, it does not belong here. (Everything else is backstage.)

How to use this

  • Reading as a human: open the current month and read top-down — the newest day is first. Each day’s entry lists what changed that day and why, and points at the files.
  • Asking “what changed?” (LLM): point your model at this folder — or at a span of monthly files — and ask for a summary since whatever date you care about. The format is deliberately regular so a model can parse it; see For an LLM below.

For an LLM

Each monthly file (YYYY-MM — Release Notes.md) is a reverse-chronological list of daily entries. One entry = one day; every published-content change that day is grouped under it as a bullet. Backstage work is excluded — see Scope. Each day follows this shape:

### YYYY-MM-DD
- **<Category> — <doc or title>.** One-line summary of the day's net change to that item, with the path. (`series-.../path.md`)
- **<Category> — <other doc>.** …

Two rules keep it clean:

  • One entry per day, not per commit — append to today’s heading as changes publish; never open a second dated heading for the same day.
  • Collapse same-doc edits — if a document is changed several times in a day, its bullet shows the final state at day’s end, never the intermediate steps. Different docs each get their own bullet under the day.

Categories (one per bullet; pick the dominant one):

  • Added — new content (a reading, paper, chapter, character, tool).
  • Changed — existing content revised (re-voiced, edited, restructured).
  • Fixed — an error or defect corrected (content or repo).
  • Removed — content deleted, deprecated, or de-duplicated.
  • Canon — a canon or process decision (naming, structure, a standing rule).
  • Ops — tooling, repository, build, or infrastructure.

To summarise “what changed since <date>”: read every daily entry with date ≥ <date> across the relevant monthly files, newest-first; each day’s bullets are that day’s net changes (no intermediate edits to dedupe); group the bullets by Category for a digest.

Cadence: a new monthly file opens on the 1st; earlier months are frozen (never edited after their month ends, except to fix a typo). The newest file is the only one being appended.

The series

1 item under this folder.