docs: cut the glossary to terms the repo actually contests; drop the census

Auditing the ten terms against real usage found most of the _Avoid_ lists banning
words that have a legitimate independent meaning here, which would make the glossary
wrong to follow:

- `icon` is `geometry.icon()`, plus favicon and apple-touch-icon.
- `glyph` is what `text.py` means by it — an outlined character from the font.
- `theme` is the mkdocs config key; `variant` is the light/dark image pair and the
  padded circular-crop mark; `title` is front matter; `header` is the site header and
  Boosty's header slot; `banner` is the README banner.
- `logo` is right to reject for our own assets, but a third party's logo is a logo —
  `symbols.py` draws from Flask's and FastStream's, and ADR 0004 is about exactly that.
- `logotype`, `combo mark`, `highlight` and `cutout` appear nowhere in the repo. A
  synonym nobody has used is not a synonym to reject.

Three entries went the other way and were dropped as derivable: Brand kit (it is
`brand/`), Social card (`project_social_card` and the filenames), and the three
metadata surfaces, which restated the AGENTS.md section that owns them.

The audit did find one live split worth ruling on: `colourway` in prose, `colorway` in
two docstrings and the apparel README. British spelling wins for this one word, since
the assets and the docs describing them already read `colour`; the three sites are
corrected here so the glossary is true when it says so.

Ten terms become seven.

tests/test_invariant_census.py is removed on request. AGENTS.md now says plainly that
nothing enforces the INVARIANT: shape and nothing checks a cited ADR path, so both are
review-time reads — the ADR links in AGENTS.md and brand/README.md go back to failing
silently on a rename, which mkdocs --strict cannot see.

Verification: uv run pytest — 123 passed, 5 failed, 26 skipped; the five are the
pre-existing rsvg-convert failures. uv run mkdocs build --strict is clean.

Author: lesnik512

AGENTS.md

@@ -114,11 +114,10 @@ comment, or `mkdocs.yml` costs every turn and rots in two places at once.
 
 An invariant is a test whose name is the claim, with a docstring opening `INVARIANT:`
 and a second paragraph naming **what breaks it** — design rationale, not a report of
-what this one test catches. `tests/test_invariant_census.py` enforces that shape, and
-checks that every test name and ADR path cited from the source or from the Markdown
-outside `docs/` resolves. Both ADRs and
-`INVARIANT:` docstrings ratchet: nothing prunes a record once its call is settled.
-Keeping them lean is a standing habit.
+what this one test catches. Nothing enforces that shape, and nothing checks that an ADR
+path cited from code or from this file still resolves; both are read at review time.
+Both ADRs and `INVARIANT:` docstrings ratchet: nothing prunes a record once its call is
+settled. Keeping them lean is a standing habit.
 
 ## Agent skills
 

CONTEXT.md

@@ -18,45 +18,34 @@ heavily this repo uses it.
 A square logo drawn from vector geometry, with no type. The *org mark* is the interlocked-snakes
 pinwheel with a chevron; a *project mark* is the green+gold snake frame around one repo's inner
 symbol.
-_Avoid_: logo, icon
+_Avoid_: logo — for our own assets. A third party's logo is a logo (`symbols.py` draws from
+Flask's and FastStream's), and `icon` is the right word for a favicon or the `icon()` full-bleed
+square.
 
 **Inner symbol**:
 The gold shape inside a project mark's frame, one per repo, chosen in `projects.py::MANIFEST`. It
 is the only thing that distinguishes one project mark from another.
-_Avoid_: glyph, badge
+_Avoid_: glyph — which `text.py` needs for its real meaning, an outlined character from the font.
 
 **Wordmark**:
 The `MODERN`/`PYTHON` crop-mark type, outlined to paths. Type only, no mark.
-_Avoid_: logotype, title
 
 **Lockup**:
 A mark and a name composed into one fixed arrangement — the org wordmark, or a project's
-mark-plus-repo-name banner.
-_Avoid_: header, combo mark
+mark-plus-repo-name banner. Named in the files themselves: `lockup-light.svg`, `lockup-dark.svg`.
 
 **Colourway**:
 One named ink pair an asset renders in: *light* is green-ink + gold-light, *dark* is cream +
 gold-dark. Every asset ships both, and which one a surface loads is a `prefers-color-scheme` or
 `data-md-color-scheme` swap, never a separate design.
-_Avoid_: theme, variant, colour scheme
+_Avoid_: colorway — the repo has spelled it both ways; British spelling wins for this one word,
+because the assets and the docs that describe them already read `colour`.
 
 **Knockout**:
 Cream painted **on top of** a gold shape to cut a hole in it. Cream is never ink in its own right:
 on a transparent background it is invisible on light surfaces and stray white on dark ones.
-_Avoid_: highlight, cutout
-
-**Brand kit**:
-The generated tree under `brand/` — the whole output of `brand.build.render`, and the source of
-truth every other surface copies or hotlinks from.
-
-**Social card**:
-The 1280×640 `og:image` for a repo with a docs site: mark panel plus name, tagline, and URL.
-_Avoid_: banner, preview image
 
 **Org profile**:
 `profile/README.md`, the landing page GitHub renders at github.com/modern-python. Distinct from the
-**org site**, `modern-python.org`, built from `docs/`.
-
-**The three metadata surfaces**:
-A repo's one-liner, written once and kept identical in the GitHub description, the pyproject
-`description`, and its org-profile row. Naming fewer than three of them is the usual way they drift.
+**org site**, `modern-python.org`, built from `docs/` — the two carry different content and drift
+apart if the names are used loosely.

brand/apparel/README.md

@@ -7,7 +7,7 @@ Print-ready artwork for the **black** modern-python org t-shirt, generated by
 uv run python -m brand.build.render
 ```
 
-## Colorway
+## Colourway
 
 Two-ink spot print, cream + gold-dark (the on-dark org treatment):
 

brand/build/geometry.py

@@ -85,7 +85,7 @@ def mark(*, struct: str, gold: str) -> str:
 
 def apparel_back(*, struct: str, gold: str) -> str:
     """Back-of-shirt lockup: the MODERN/PYTHON wordmark with the full domain
-    outlined beneath it, transparent, for the cream+gold-dark colorway. Extends
+    outlined beneath it, transparent, for the cream+gold-dark colourway. Extends
     the `wordmark` viewBox downward to seat the URL centered on the same axis."""
     url, _ = outline_text(
         "modern-python.org",

brand/build/render.py

@@ -72,7 +72,7 @@ def render() -> None:
         height=640,
     )
 
-    # Boosty profile cover (green colorway) — brand/org/boosty-cover.*
+    # Boosty profile cover (green colourway) — brand/org/boosty-cover.*
     _write(
         ORG / "boosty-cover.svg",
         g.boosty_cover(bg=t.GREEN_SURFACE, struct=t.CREAM, gold=t.GOLD_DARK),

docs/agents/domain.md

@@ -33,7 +33,7 @@ whose docstring opens `INVARIANT:`.
 
 When your output names a domain concept (in an issue title, a proposal, a hypothesis, a test name),
 use the term as defined in `CONTEXT.md`. Don't drift to synonyms the glossary explicitly avoids:
-write `mark` and not `logo`, `colourway` and not `theme`, `inner symbol` and not `glyph`.
+write `mark` and not `logo`, `colourway` and not `colorway`, `inner symbol` and not `glyph`.
 
 If the concept you need isn't in the glossary yet, that's a signal: either you're inventing language
 the project doesn't use (reconsider) or there's a real gap (note it for `/domain-modeling`).