# Create a new member of the family

Start from the communication problem, not the available component library.

## Derivation method

1. Name the job: compare, locate, explain sequence, express uncertainty,
   navigate or act. Name audience and medium constraints.
2. Select the closest existing grammar: editorial reading, data figure,
   compact control, identity composition or digital report/presentation. Reuse its type,
   spacing, neutral colour roles and action hierarchy; do not copy its whole layout.
   A photographic hero or glass menu is not the default answer to every job.
3. List required states. A chart may need empty/missing/negative values,
   uncertainty, long labels, selection and a readable data alternative. A
   form needs validation, pending, failure, success, cancel and recovery.
4. Draw the simplest truthful encoding. Keep structural fields neutral. Allocate
   an accent only when it helps meaning; it is not a requirement. For data, use
   the accent for the selected
   series or important relation; encode the rest with direct labels, shapes,
   line patterns or separate panels. No rainbow palette or decorative 3D.
5. Select scale and composition. Begin with the 8/16/24 rhythm, 16px body,
   14px dense details and 12px ordinary Geist metadata. Increase space for comprehension,
   never shrink essential text to make an arbitrary layout fit.
6. Resolve surface adaptations and write them in the asset contract. Explicitly
   record the unit conversion, export size and any default you changed.
7. Run automated checks, then inspect the result and edge cases. Compare with
   the brand book and one nearby pattern at actual output size. Record findings
   before claiming acceptance.

## Extending material and interaction

Reuse `.fy-glass` for one compact functional group before writing a new material.
Retain the 6px inset and readable targets; derive concentric inner corners from
the outer edge. The selection is a tonal mark within that plane. Dense persistent
reading/content patterns stay opaque; functional buttons, menus, popovers,
short context panels and drawers may use glass. Do not treat a requested glass
panel as prohibited merely because it contains a readable note or controls.

If an optical extension is useful, state the exact supported backdrop, image
source and coordinate mapping. Begin with `examples/glass/` for the reviewed
rest/hover/press/release/selection response. Preserve sharp labels, independent
focus cues, interruption and reduced-effects behavior. A stronger edge split on
press is a product response, not a reason to add a permanent rainbow border.
Do not claim generic DOM refraction from a renderer that samples one texture.
A standalone optical button needs transmitted backdrop/lens behavior, not a flat
Current Blue fill dressed with a shine. A shared toolbar reuses its material plane for
child interaction; distinct menus/drawers may own separate bounded roots.

Require rest and interactive examples, CSS/solid fallbacks, image/renderer failure,
keyboard/touch use and measured rendering bounds. Document frame/canvas limits
and hidden/offscreen behavior. For menu/panel/drawer sequences, coordinate the
supplied GSAP and CSS states with one owner per property. Define press/release,
open/close/reverse, grouped content follow-through and reduced end states; rapid
input retargets current motion rather than queues it. Keep real keyboard/touch
semantics and focus return. A non-optical or native system material is an
intentional adaptation when it better serves the medium.

## Worked extension: an interval chart

Question: how do candidate materials compare when estimates remain uncertain?
An ordinary bar would hide uncertainty. `examples/chart.html` therefore uses a
horizontal estimate-and-range plot: one diamond for the estimate, a line with
end caps for the range, direct candidate labels and a shared numeric axis.

It inherits Geist labels and tabular figures, a neutral opaque surface and selective Current Blue marks,
muted grid and the same reading widths. It adds no brand colour or surface type.
A text summary and table carry the same numbers. The example values are
explicitly illustrative, the scale is 0–100, and the range is described as a
scenario interval, not a measured confidence interval. It is static: no hover
is needed to understand it. This is an extension of the grammar, not a claim
that all uncertainty should use this chart.

## Copy, photography and icon extensions

Use Geist for labels, figures and metadata, with tabular numerals where useful.
No em dashes, overlines, eyebrows, uppercase chapter markers or monospaced
technical styling. Organize with whitespace before rules; no decorative border
grids or outlined cards. Keep required input, focus and state boundaries.

A new photograph needs a relevant subject, plausible editorial light and natural
cool whites, with no blue wash. Record creator/source/license, alterations
and generated status, retain an uncropped master and define wide/portrait/small
crops with focal-point intent. Do not use photorealistic AI as evidence of real
work. Water, robots, crystals and macro texture wallpaper are not default subjects.

A new icon must resolve within existing Phosphor Regular before adding another
family: consistent 20/24px optical size, at least 44px action region, accessible
name and visible touch label where ambiguous. No emoji or decorative icon
substitutes, redundant link arrows, mixed weights or spectral glyph effects.

## Other extensions

- Relationship diagram: labeled nodes, one clear reading direction, restrained
  connectors and a prose alternative. Use spacing and grouping before boxes.
- Calendar or timeline: distinguish focus, selection and today without colour
  alone. Dates must remain reachable by keyboard; disclose timezone.
- Multi-series chart: first try small multiples. Use line/marker patterns and
  direct labels before proposing extra colours. Never recolour source categories
  whose established meaning is essential without explaining the mapping.
- Map: real geographic coordinates and a stated projection/source. The palette
  expresses evidence, not decoration; preserve boundaries and uncertainty.
- New print asset: work from reading distance, stock/process and safe margins.
  Preserve identity and typography; make a physical proof before certifying it.

Digital reports/presentations should have meaningful working view/step
navigation, responsive figures and readable source/value equivalents. Keep
print as a static export adapter. Optional attention light is finite and local
to material/non-data framing, never an encoded spectrum. The default identity
is still; an optional Facet flight moves the intact form once and settles,
without feather/plane reshaping. Derive close nested corners mathematically and
centre icons before adding animation.

## Promote without accumulating exceptions

A one-off asset does not create a new global rule. If a pattern solves a recurring
need, propose its purpose, token mapping, states, accessibility, positive and
negative examples, evaluation evidence and migration impact. Keep the existing
pattern until the owner accepts a replacement. Record an explicit exception
rather than teaching the next AI that accidental styling is canonical.
