Canonical Render Page

This page recreates the actual render-page shape used by deterministic review surfaces like the `sub-nav` page you linked. The point is to inspect the page anatomy directly: intro and metadata on the left, one focused render lane on the right, and explicit navigation controls for moving through review states.

Status: Active draft
Primary proof: Dedicated canonical render surfaces under `/design-system/components/*` and pattern-owned render routes
Baseline examples: `sub-nav`, `page-shell-banner`, and `hierarchy-tree` render pages
Viewing circumstances: Desktop review at fixed shell width with URL-owned state and single-surface focus
Render specimen: Desktop viewport, 1180px width, short labels, open state, normal render theme

Canonical Surface

Render Page Anatomy

This stage mirrors the focused single-state review area used by the real render pages.

Render lane

One state at a time

Local specimen

Tenant settings

Renewal strategy workspace

Detail panel with governed header, body, and footer posture

The established design-system detail panel keeps reading length, actions, and footer traversal inside one focused surface instead of letting errors or missing fields collapse the surrounding page rhythm.

Governed Pattern seam Open state

The right column hosts one focused specimen so reviewers can compare screenshots and runtime posture honestly.

Local render controls can reverse direction, change magnification, and pressure-test the specimen without altering the page shell.

Width, viewport, labels, theme, and state stay local to the specimen.
Page-level display settings still affect the surrounding shell.
This panel expands, collapses, disables, or errors without changing the outer page contract.