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.

The pattern

"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

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

Where it applies

Reusable elements

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 in xlab-co-toolkit) — the one-carrier drift-guard; wire it into gfcx_subdomain_new.py under --strict so 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-08 mouthful. 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).