Not found

Says the page does not exist and lists every section.

Page · stable · v1.0.0 · owner: Site system lead · contract 19 of 20 points (open: figma)

Do and don't

Do: Section map and native recovery actions

Declared by not-found.ts

Authored page specimen; not a captured route or acceptance result. Open associated page (declared association; rendered-page verification is separate).

Open example: Not found · Do: Section map and native recovery actions Use the full-page example to follow page links.

Existing native head/actions and source navigation links offer recovery; this authored main fragment is not a captured 404 document or acceptance result.

Do: Different recovery explanation and destinations

Declared by not-found.ts

Authored page specimen; not a captured route or acceptance result.

Open example: Not found · Do: Different recovery explanation and destinations Use the full-page example to follow page links.

Distinct labelled alternative text and links use the same native template APIs without inventing another route or locale.

Don't: Missing recovery destinations

Declared by not-found.ts

Authored page specimen; not a captured route or acceptance result.

Refused by the element. page-404: page-404.sequence: page-head does not follow page-404 (page-head → tile-grid).

The required TileGrid is missing; native observed composition fails this page's sequence even though the head renders.

Don't: Two missing-page fields touching

Declared by not-found.ts

Authored page specimen; not a captured route or acceptance result.

Refused by the element. page-404: D-SITE-002: compose page-404: a madder field touches a madder field (D-SITE-002: a field is always followed by cotton)

Native composition refuses adjacent fields; a second head does not replace the cotton recovery grid.

Rules

RuleWhyCheck
Built pages follow: header, page-head, tile-grid, footer.A declared composition is what makes the page checkable and the site consistent.Automated: scripts/site/system/check-pages.ts (check_composition per page)

API

No props.

Contract details

The full contract: identity, anatomy, variants, states, tokens, layout, motion, accessibility, content, tests

Identity

AspectValue
Idpage-404
LayerPages
Categorypage
OwnerSite system lead
Statusstable
Version1.0.0
Sourceapps/showcase/site/system/pages/not-found.ts (private repository; the contract and the render function are this one module)
VersionDateChange
1.0.02026-10-26Not found as one module: its markup moved out of the page builder (scripts/site) into the system.

Use when

  • Paths matching /^\/404\.html$/. Why: Every page of this kind is composed the same way, so readers learn it once.

Do not use when

  • For a page with a different job. Why: A new kind of page gets its own declaration and review.

Anatomy

PartWhat it is
1page-head
2tile-grid

Made of: header, page-head, tile-grid, footer.

Used in: pages directly.

Variants

VariantWhenWhy
defaultWherever the page declaration places it.One shape per job keeps pages predictable.

States

StateRendered or not applicable
defaultdefault
hoverNot applicable: The not found is not interactive, so it has no hover state.
focus-visibleNot applicable: The not found does not take focus; links and buttons inside it carry their own focus ring.
activeNot applicable: The not found cannot be pressed.
disabledNot applicable: The not found has nothing to disable.
loadingNot applicable: The not found is rendered at build time and is complete when the page loads.
emptyNot applicable: The not found is not rendered without content; the builder skips it.
errorNot applicable: The not found shows no data that can fail.
currentNot applicable: The not found has no current item.
visitedNot applicable: The not found is not a link.
expandedNot applicable: The not found does not open or close.

Tokens

PartToken
page.ground--cotton

Layout

AspectValue
breakpointsRequired review at 390, 768, 1024 and 1440 px; execution is not implied by this declaration; columns stack under 768 px; the wrap keeps a 16 px gutter on phones.
wrappingText wraps; nothing scrolls sideways.
textExpansionJapanese runs 20 to 40% longer; headings break between phrases (jaBreaks) and blocks grow downwards.

Spacing and rhythm

AspectValue
internalEach template's own padding.
externalNone.
rhythmField, cotton, field: never two fields touching; the woven edge at each join (D-SITE-002, D-SITE-003).

Motion

AspectValue
NoneNo intrinsic element animation. The optional claude-entrance consumer profile may translate below-fold structure once (20px, --dur-weave, --ease-enter, --stagger); reduced motion disables it. This preserved baseline entrance is separate from element playback.

Runtime and reuse

  1. Render-only element; mount any registered child enhancements separately. Preserve required Site CSS, fonts, responsive and locale rules from nativeElement.

Accessibility passport

AspectValue
rolea landmark or list, as stated in its parts
nameIts visible text
keyboardLinks and buttons inside, in reading order.
focusThe --focus ring on every link and button inside.
screenReaderRead in source order; decorative weaving is aria-hidden.
contrastInk on cotton 14:1; text on every dye field 4.5:1 or better (checked by check-brand).
targetLinks and buttons are 44 px tall.

Content

SlotLengthVoice
page-head: missing-page messageOne clear missing-page title and brief recovery explanation; use the native madder state override.State the problem plainly without blame or a false success message.
tile-grid.tiles: recovery destinationsReal section links in the registered tile grid; no article body or additional action field in this page kind.Name destinations so the reader can continue from the site map.

Good: “This page has come loose. Choose a section below to find your way back.”

Bad: “Everything worked! — on a missing-page response.” · “Try again later — with no recovery destination.”

Japanese: The native 404 document is English and has no declared Japanese counterpart. Do not manufacture a Japanese route; a future translation must preserve the missing-page meaning and real recovery links.

Icons and illustrations

None: this element uses no icon or illustration of its own.

Decisions and exceptions

Usage

1 uses across the built pages (measured by npm run site:system).

Tests

AspectValue
unittests/unit/site-system.test.ts: renders every do and don't example through the registry and checks the classes it owns
visualNot yet: there are no screenshot baselines; the Library page is checked for sideways scroll at 1440 px by tests/site/system.spec.ts
a11ytests/site/system.spec.ts: axe (0 serious or critical) on the element's Library page in light and dark
parityscripts/site/system/check.ts: Library examples are rendered by the same render function the site imports

Figma

not-yet: The Loom Site Figma library is the last stage of the plan; this element is not mapped yet.

Open in Storybook

Start with a conversation about your system.

We read your system, show you what we found, and agree with your team what to fix first.