Plate № 46 · Routing · naming & taxonomy
A pattern from the gf.cx specimen book
One carrier, not two
A path token that already appears in an ancestor segment says the same thing twice — dead weight paid on every read, type, and spoken aloud. Carry each fact once; prune the echo, keep the anchor.
"Carry each identifying fact in exactly one place along a path — a container never repeats itself in its members. The hierarchy already names the parent; the child restating it is redundant. Prune the echo, but keep one anchor token so the name still self-describes when it travels out of context."
library.gf.cx/psp-discs/psp-2026-08/
library.gf.cx/psp/2026-08/
The worked example → library.gf.cx/psp Kin → memorable URL redirect
The problem
A disc record lived at library.gf.cx/psp-discs/psp-2026-08/. Say it aloud and you stumble: "psp" lands twice — once in the category folder, once in the slug prefix. The folder already establishes that everything inside is a PSP disc; the slug re-stating it is pure friction, and a name gets said, typed, and read hundreds of times more than it gets written. Worse, the redundancy compounds: if the shape is baked into a scaffold, every future record is born with the same stutter, and trimming it later means a breaking rename across whatever already links in.
The shape
- Pick one carrier — the container or the member, never both. Move the identifying token to whichever level owns it, and drop it from the other. Here the
/psp/folder carries the tier; the slug drops its prefix →/psp/2026-08/. "psp" now appears exactly once. - Keep one anchor for out-of-context life. The cross-system canonical slug (
psp-2026-08, used by the id.gf.cx stub and the vault join) stays intact — only the path sheds the prefix. Lean in context; self-describing out of it. - A rename without a redirect isn't lean — it's broken. 301 every old path to the new one, most-specific rule before the catch-all so the prefix isn't silently re-doubled. Inbound links, bookmarks, and printed QR targets must survive the trim.
- Lint it at creation time. A drift-guard (
gfcx_path_lint.py) flags any segment token that repeats an ancestor, so a scaffold gate (--strict) catches the stutter before the directory exists — new surfaces born lean, not trimmed later.
Why it works
The hierarchy is free context — the parent segment is already on screen, already in the URL bar, already spoken. Repeating it in the child buys nothing and costs a token on every encounter. Strip the echo and the name gains rhythm (psp / 2026-08 has a beat; psp-discs/psp-2026-08 stutters), becomes dictatable without "no, dash, then psp again," and stops training everyone who reads it that half the path is noise. Because the fix moves — rather than deletes — the identifying token, nothing loses meaning; the fact simply lives in one place instead of two.
When it breaks
- Stripping the anchor, not just the echo. A bare
2026-08/pasted into an email, landing in~/Downloads, or sitting in a six-month-old bookmark means nothing — it arrives stripped of its parent. Lean in context, self-describing out of it: prune the repeat, never the one token that lets the name stand alone. - Treating disambiguation as redundancy. A token repeated to break a genuine collision, or to keep a name legible in an API response with no path, is load-bearing. The lint warns, never blocks, and honors an explicit allow-marker.
- Renaming without back-compat. Leanness that 404s existing links is a regression. The redirect and the rename are a single move.
- Over-trimming natural language. A word recurring inside a sentence-shaped content slug (
research/2020-…-user-research) is language, not taxonomy friction — leave it. The rule targets designed path segments, not note titles.
Where it applies
- Use on URL taxonomies — any
/<category>/<category>-*/shape where the folder and the slug carry the same token. - Use on filenames that re-carry their directory (
status/status_rfid_report.json→status/rfid.json), and on breadcrumbs / page titles that echo the parent at each crumb. - Use on config keys and metadata that restate a fact the location already fixes — a surface name derivable from the host, a category already in the slug.
- Skip when the repeat is the only thing making a name self-describing out of context, or when it disambiguates a real collision.
Reusable elements
- The rule — "carry each identifying fact in exactly one place; a container never repeats itself in its members." Applies to every path, filename, and key in the portfolio.
- The mouthful test — five fast checks for a bloated name: say it aloud (stumble = weight), no token twice, cover the parent (does the leaf still need its prefix?), dictate it over the phone, rhythm (a lean name has a beat).
- The one-carrier rewrite — move the shared token up into the container, drop it from the member; add the 301 in the same commit.
gfcx_path_lint.py— the creation-time drift-guard: flags a segment token that repeats an ancestor, skips date-led / long content slugs, warns not blocks, honors a repo-root.pathlintallow, and gates a scaffold under--strict.
Reference
- Worked example
- library.gf.cx/psp —
psp-discs/psp-2026-08/→psp/2026-08/; old paths 301 (specific slugs before the catch-all), id.gf.cx manifest repointed, physical QR labels untouched (they encode opaque refs, not the path). - Tooling
gfcx_path_lint.py(mirrored inxlab-co-toolkit) — the one-carrier drift-guard; wire it intogfcx_subdomain_new.pyunder--strictso new paths can't ship a stutter.- Origin
- 2026-09-13 — a Fable + Opus brainstorm on "streamlining removes friction," sparked by the
psp-discs/psp-2026-08mouthful. Dan: "that's a mouthful." - Kin
- memorable URL redirect (short, stable, human URLs) · base-URL one-line swap (one carrier for the origin) · built-with footer (one source, every surface) · edit the generator (single source of truth).