What Golden Fixture Co. lists as services

The header nav and every route’s own `meta` are what tell a visitor, and a crawler, where they are. Neither is guessed from the file path.

• –Nav labels live in chrome content, not hard-coded in layout.tsx.
• –Every page exports its own title and description; nothing falls back to a site default silently.

A page is a stack of bands built from catalog primitives and blocks. Nothing on this route is a bespoke component — there is no `components/` directory to put one in.

• –Each band picks one of the catalog’s named surfaces, never a raw color.
• –A block is used as shipped; a band around it is composed inline when the block has no slot for something new.

A page module names its own canonical path with no trailing slash. The builder matches on that literal string; it does not infer a route from a file’s location in the tree.

• –This route’s own `route` export reads `/services`, never `/services/`.
• –An unmatched path falls to the reserved 404 page, not a platform default.

Section spacing and container widths come from one tuning surface the site’s own theme.css sets — `py-section`, `max-w-content`, and the rest — never a one-off pixel value at the call site.

• –The same six-name rhythm scale is reused on every route in this fixture, this one included.
• –Radii follow the same rule: the derived `rounded-panel` step, never a fixed literal value.

This entry describes itself: the list you are reading is the one genuine collection on this route, and it is allowed to grow.

• –Reworking this sentence is an instant edit — no rebuild required.
• –Adding a sixth entry to this very list would be a rebuild — see the note below.