# Fyronyx interface guidance

Edition 04.2 · Neutral material direction · 9 November 2026

Jeremy accepted the ocean-glass interaction study and instructed that its neutral
colour balance, compact controls and dynamic refraction become a coherent brand
for future work. This document adopts those application rules. It grants no
publication, product migration, installation or standing execution authority.

## Authority and provenance

1. Current explicit human direction and this application guidance.
2. Current identity masters and the retained September 17 palette in
   `styles/design-system/colors.css`, plus the additive neutral application roles
   below. Imported palette names and source values remain immutable.
3. The affected product's authorized scope, interaction contract and evidence.
4. Versioned portable package and installed implementation aids.
5. Historical specimens and archive commentary, as provenance only.

This edition supersedes the universal blue environment, compulsory crystal
opening, 90%-blue glass fill and automatic accent outline prescriptions of earlier
application guidance. It retains the Balance identity and adopts Geist-only
presentation. Plex remains a historical licensed asset. Functional material
hierarchy, readable content and accessible interaction remain required.
Existing products remain on their own adopted contracts until their migration
is explicitly authorized. Older specific OS/workplace rules are evidence of
those products, not requirements to copy into every future website.

The accepted reference implementation is
`docs/brand/prototypes/ocean-glass/`: the compact 6px menu inset, subdued neutral
shell, natural image colour, travelling selection and interactive edge refraction
were reviewed in this chat. The ocean is one subject used to establish material
quality; it is not a mandatory Fyronyx wallpaper. A working prototype and an
accepted direction do not establish tested production performance or accessibility.

Historical source evidence remains the Fyronyx OS commits
`f24396bf9aa99229a9d7a203a510a62ea09237a1`,
`01ae623d084e2764899798b2c0322564576d576f` and
`47556d770baf9e5280134cb7aa01d8735c9e9dad`, plus the dated October 20/21 and
November 3 guidance. Their device, release and acceptance claims do not transfer
to this edition or another consumer.

## Current identity presentation

Use the neutral everyday Cut for routine headers, navigation, UI and documents.
The supplied silhouette, viewBox and geometry remain fixed. The current neutral
asset is `fyronyx-balance-cut-ink.svg`; `fyronyx-balance-cut-blue.svg` is the
deliberate Current Blue presentation. An inline Cut can inherit the current
neutral ink or approved blue role without changing its path. Choose the supplied
light/dark presentation that remains readable; never recolour a separate product
or redraw the bird to make it match.

Expressive Facet is a tonal interpretation of that same bird, derived from
Current Blue rather than an unrelated cyan/green or legacy spectrum. Use
`fyronyx-balance-facet-blue.svg` or `fyronyx-balance-facet-blue-light.svg` for its
intended field, at generous scale. Current ink/blue wordmarks and lockups carry
the same visual roles. Identity source edition 04.1 remains unchanged in application
edition 04.2; its provenance records the same SVG bytes and geometry. Keep
historical coloured masters intact as provenance;
their presence in an archive does not make them the current application default.

The Brand/UI switch, tabs, buttons, fields, feedback and identity must look like
one family. A selected segment uses a quiet tonal area with correct semantics,
not a saturated badge or an extra nested glass slab. Preserve the same Geist
weight, optical alignment, icon scale and resting/hover/press hierarchy.

## Character and composition

Make the work feel attentive, precise and materially credible. A neutral field,
clear reading hierarchy and one useful focal point carry recognition. Give a
real subject room to be understood. Colour and optical effects should be noticed
because they serve that subject or an interaction.

- Let structural surfaces, typography and spacing establish the page before
  adding glass. Prefer unboxed editorial flow; group only what belongs together.
- Group with space and alignment before adding a boundary. Do not outline
  every card, construct decorative border grids or repeat rules around prose.
  Keep borders that identify a field, focus, state, necessary table division or
  actual glass rim.
- Use one deliberate photographic or material moment when the content benefits.
  Other pages may be entirely typographic, diagrammatic or data-led.
- Keep the main proposition concrete. Do not substitute a huge slogan, repeated
  badges, abstract crystal sculpture or ornamental gradients for useful content.
- Retain the supplied Balance Cut/Facet geometry, proportions and clear space.
  Cut is functional identity; Facet is a deliberate large identity expression.
  Neutral application does not authorize inventing a new logo.

## Colour roles and neutral balance

Preserve the retained palette file and its SHA-256:
`7e4b82bc3222cb6f0b072c2d3a81b30a85d5ae0e8ff33b367b3e9a0c02385755`.
Edition 04.2 adds scoped `--fy-*` application aliases; it does not rewrite the
immutable `--fynx-*` source tokens. The portable CSS and resolved token manifest
own the complete implementation mapping. Dark values are an adapter starting
point and require rendered consumer proof; the accepted ocean study was light.

| Role | Light starting value | Dark starting value | Purpose |
| --- | --- | --- | --- |
| `--fy-shell` | Frost `#f4f7fb` | Charcoal `#18202a` | Main surrounding field |
| `--fy-ink` | Charcoal `#18202a` | Soft white `#f4f7fb` | Primary reading |
| `--fy-surface` | Cool white `#fcfdfe` | Slate `#222d38` | Opaque reading and forms |
| `--fy-muted`, `--fy-line` | Resolved neutral roles | Resolved neutral roles | Secondary reading and restrained structure |
| `--fy-accent` | Current Blue `#245f9e` | Pale blue `#8abbe8` | Primary action fill |
| `--fy-accent-hover` | Deep blue `#1c4d82` | Pale blue `#e5effa` | Primary hover fill |
| `--fy-accent-ink` | Deep blue `#1c4d82` | Pale blue `#8abbe8` | Accent text and links |
| `--fy-accent-on` | Frost `#f4f7fb` | Charcoal `#18202a` | Ink on the primary fill |
| `--fy-accent-soft` | Pale blue `#e5effa` | Pale blue `#e5effa` | Quiet accent grouping |
| `--fy-accent-soft-ink` | Tonal blue ink `#204e7d` | Tonal blue ink `#204e7d` | Readable ink on pale accent in either theme |
| `--fy-focus` | Current Blue `#245f9e` | Pale blue `#8abbe8` | Visible keyboard focus |
| `--fy-glass-*` | Context-bounded neutral material | Context-bounded neutral material | One functional control plane |

Neutrals dominate the interface. Current Blue is the current application accent:
use it for the main decision, a meaningful link or a selected data series.
Secondary actions and ordinary selection stay neutral. Do not repeat Current Blue
across every border, heading, card or icon. Existing cobalt/indigo source tokens
and master assets remain historical imports, not the current application accent.
Photograph-derived colours stay in the image; signal colours retain their
established meaning and labels.

In light mode the primary Current Blue fill uses off-white `--fy-accent-on` ink and
deep Current Blue carries accent text. In dark mode pale Current Blue carries the primary
fill, text and focus, with charcoal ink on the fill and pale `#e5effa` on hover.
Do not place the dark fill colour directly on charcoal or add an ornamental
border to rescue an unsuitable role. On opaque sRGB fields,
Frost on `#245f9e` is about 6.10:1, `#1c4d82` on Frost is 8.03:1, and `#8abbe8`
on charcoal `#18202a` is 8.10:1. These calculations are starting pairs, not proof
of a glass composite. Keep action, hover, text, tonal and focus roles distinct.

Optical RGB separation is a temporary material response at a refracting edge,
not a new brand palette. Do not use it as text colour, a status indicator, a
permanent rainbow border, or an excuse for purple/neon decoration. A neutral
image-free surface should still look recognizably Fyronyx.

Jeremy’s subsequent colour correction removes beige and warm greys: the light
canvas is cool off-white Frost `#F4F7FB`, with cool white reading surfaces and
blue-grey structure. Do not reinterpret neutral as cream, ivory, sand or taupe.
Natural imagery may keep its own colour; this correction governs interface
surfaces, not a tint imposed on the subject.

## Typography and reading rhythm

- Geist for reading, interface and display. Use restrained 400–500 weight for
  spacious editorial openings; a working app may use 500–600 for hierarchy.
  Avoid making every headline oversized and heavy.
- Geist is the only current presentation family, including figures, dates, IDs
  and metadata. Use tabular numerals where comparison needs aligned digits.
  Plex Mono stays in historical font assets but is not a current UI default.
- Do not add overlines, eyebrows or uppercase chapter labels above headings.
  Put a useful date or category in ordinary sentence-case text only when needed.
  Never use monospaced labels to imply technical depth.
- Body: 16px with 1.6–1.65 leading. Dense records: 14–15px with at least 1.5
  leading. Supporting metadata: 12px; essential reading remains at least 14px.
- Product titles start around 30–40px; sections around 24px. A short marketing
  opening may use 42–76px when its actual content and viewport support it.
  Scale down through reflow, not squeezed letterforms or clipped text.
- Bound prose around 65–72 characters, allowing up to 78 for long records.
  Use sentence case, concrete nouns and verbs. Preserve evidence and uncertainty.
  Do not use em dashes in authored copy; write a full sentence, comma, colon or
  parentheses instead. Avoid slogan fragments, decorative labels and repeated
  arrow marks on links.
- Use 8px within related detail, 16px between groups and 24px between independent
  blocks. Larger editorial spacing is deliberate; one owner controls each gap.

## Material roles and compact geometry

**Persistent content:** dense reading, records, tables and sustained editing stay
on stable opaque surfaces. **Functional glass:** buttons, navigation groups,
menus, popovers, short context panels and drawers may carry the material. A
requested glass panel is not prohibited merely because it contains text. Keep
its information bounded and readable, with opaque fields or dense reading
regions inside when necessary. **Feedback:** labels, selection, focus and status
communicate state whether optical effects are enabled or not.

- Give each functional material root one owner. A button can have its own optical
  surface; a menu or drawer can have another when it performs a different task.
  Do not multiply filters or optical canvases within the same shared surface.
  Controls placed on an existing glass plane use local light/selection on that
  plane, rather than a second backdrop filter. Separate floating roots are not
  a ban on functional menus, panels or drawers.
- A glass button needs transmitted/scattered backdrop detail, a refracting rim
  and state-dependent optical response when the renderer is available. A flat
  Current Blue fill with a shine overlay is an ordinary accent button, not proof of
  refraction. Both roles are supported; name the material truthfully.
- Compact glass groups start with a **6px inset** between the outer edge and the
  controls, plus a 1px rim. Start at 52px control height on wide screens and 46px
  on narrow screens; never reduce a required web target below 44×44 CSS px.
- Related corners are concentric: inner radius is `max(0, outer − inset − border)`.
  A capsule is appropriate for a compact linear control group. Other containers
  use geometry suited to their content; capsules are not a universal card style.
- A control label should sit comfortably inside its own target; reducing the
  outer group's padding must not collapse that target or the label's inset.
- Ordinary content panels retain 16px desktop / 12px narrow corners; independent
  fields and buttons start at 8px. Floating content or settings panels can use
  16–20px as appropriate. Do not copy a hero canvas radius into every component.
- On narrow layouts, reflow or disclose navigation before shrinking essential
  labels. Remove a redundant next arrow if all destinations remain available.

The portable API provides `.fy-glass` and `.fy-glass-control`; `.fy-floating`
remains a compatibility name for the neutral floating role. These CSS primitives
provide the base/fallback material, not automatic optical rendering. The richer
functional reference is owned by `docs/brand/prototypes/material-controls/`,
with integration at `/ui/material-controls/` and inline guide controls.
It covers real glass buttons, a context menu, a short note panel and a modal
drawer. Source presence, rendered behavior and human feel are separate proof
states; do not call an intended integration implemented until exercised.

## Refraction and interaction

Apple guidance informs the distinction between functional controls and content.
The browser optical layer is Fyronyx's artistic interpretation, not native Apple
Liquid Glass or a physically calibrated renderer. Native apps use supported
system structures and materials rather than stacking this web effect over them.

The visual ideal is **transparent glassmorphism with gentle frosting**: the
image remains perceptible through the material, with slight haze, small light
bending, a thin rim and soft shadow. Keep the body tint low. It should not read
as a dark opaque plate, a thick polished chrome border or a saturated luminous
capsule. Dynamic RGB separation is a secondary interaction response, not the
main character of the resting surface.

The known-image optical adapter must preserve transmitted detail and alignment.
Generic unknown-backdrop CSS can use a bounded reading-guard fill
(`--fy-glass-fill`, `rgba(39,59,68,.88)`) when readability needs it. That guard is
not the visual ideal and must not be presented as transparent refraction. For
sustained reading, choose an honest opaque content region instead of increasing
glass tint until it becomes an opaque card. The photograph treatment is opt-in
only after the actual supported composite is reviewed. Use CSS haze and solid
fallbacks when the optical input cannot be mapped.

On hover, focus or press, local light and lensing give the surface presence
without moving the page or blurring its labels. Press may show a clearer colour
split, then settle back to the quietly frosted rest. A short menu/panel/drawer
keeps its material through closing; canceling state must not make its optical
canvas vanish before its shell has left the screen.

| State | Required treatment |
| --- | --- |
| Rest | Quiet neutral material; thin rim; restrained edge dispersion; clear labels and current selection |
| Hover | A restrained local white light travels briefly, with a little spectral separation at the curved edge; keep labels and the frosted interior quiet. No essential information is hover-only. |
| Press | Stronger local bending and dispersion than hover, with immediate restrained compression/feedback; release returns to hover or rest |
| Selected | Tonal selection plus correct semantics; bounded stretch during travel, then settle; colour alone does not establish state |
| Keyboard focus | Visible non-optical focus indicator and equivalent discoverability; optional material light never replaces the indicator |
| Disabled | Native/ARIA state plus suppressed activation and clear distinction; never light up as an available action |
| Loading/error | Real request-linked feedback, stable target geometry, useful retry/recovery; never fabricated activity |
| Reduced effects | Static or opaque material; immediate usable selection; no springs, drift, press scaling or animated spectral travel |

Use the packaged glass reference for reproducible edge displacement, local RGB
sample offsets and the reviewed interaction profile. The illustrative ocean
renderer samples its known local image; it does not refract arbitrary DOM,
video or other windows. A new background needs explicit texture/geometry mapping
or the CSS material fallback. Keep labels as sharp semantic foreground content.

Keep optical effects confined to functional roots. Bound canvas resolution and
frame rate; pause hidden/offscreen work and stop optical interpolation under
reduced motion. No full-screen optical renderer is required for family resemblance.
At depth zero refraction and spectral splitting are off; the material and
control group remain usable.

Transitions explain continuity. The accepted selection profile uses a damped
spring; content exits briefly and enters gently, without delaying activation.
Interrupt older motion on rapid input, hide/inert outgoing content appropriately,
and settle to one active view. Do not queue decorative transitions behind intent.
A static and solid implementation is a complete brand expression.

## Functional glass roles and motion choreography

The intended feel is responsive and alive, with clear rest between interactions.
Use GSAP for coordinated, interruption-safe sequences where supplied by the
consumer, and CSS for local states. One coordinator owns each transition; do not
stack a CSS animation, GSAP timeline and independent spring on the same property.
The shared known-image optical renderer owns lens/dispersion parameters, while
GSAP/CSS drive semantic opening, local lift, pressure and return.

| Functional role | Choreography and required behavior |
| --- | --- |
| Glass button | On pointer entry, local light follows with a small bounded lift. Hover bends the mapped backdrop; held press deepens the lens and RGB separation. Release restores hover or rest without delaying the action. Labels and hit regions remain stable. |
| Shared toolbar/navigation | Selection moves and settles within the same plane. Individual items may brighten or refract locally; do not create nested glass owners. Keyboard selection and focus are immediate and intelligible. |
| Menu/popover | The material reveals from its trigger with a short clip/scale/translation and restrained content follow-through. The actual menu works by keyboard and touch. Escape/outside dismissal and focus return follow its semantics. |
| Short context panel | A bounded note, explanation or tool context may use glass. The shell has real transmitted backdrop and edge behavior; text remains crisp. Changing context preserves current input and does not cover the initiating task. |
| Drawer | Reveal from the logical edge with coordinated material, scrim and short content entrance. Reverse smoothly from the current state on dismissal. Modal drawers manage focus and return it; nonmodal drawers do not trap focus merely because they look substantial. |
| Non-optical primary action | Current Blue fill remains appropriate for a direct primary decision. It is an explicit non-optical role, not a substitute when the requested surface is a glass button. |

Start ordinary state feedback around 160ms, small material reveals around 200–280ms
and a drawer around 280–420ms, then tune to its actual distance and content. These
are product starting points, not an Apple timing specification. Short grouped
content follow-through may begin 40–70ms after its material, without a long serial
stagger or a delay before the control becomes usable. Keep text unwarped.

Fast re-entry, repeated clicks, reversal, resize and route changes must cancel or
retarget old work from the current rendered state. No queue of entrances, stale
press state or jump back to an initial pose. Interactions must still act while
visual return is settling. Do not add perpetual hover-like drift, decorative
particle motion or false progress to make the page appear alive.

Reduced motion commits the correct semantic end state immediately and stops
GSAP timelines, CSS transitions, springs and optical interpolation. Solid mode
removes the optical layer and filters without removing the button, menu, panel
or drawer. GPU/image failure uses the CSS material; generic DOM frosting is a
fallback, not a claim of known-image refraction. Budget active canvases and
suspend hidden/closed roots; do not render invisible menus and drawers.

## Selected-area cursor field

The cursor-responsive field is opt-in on selected areas, not a replacement mouse
cursor or a page-wide idle effect. Initialize only `[data-magnetic-field]` roots.
`data-field-density` accepts `low|medium|high`, `data-field-theme` accepts
`auto|light|dark`, `data-field-strength` is bounded 0..1 and `data-field-align` is
`left|right|full`. `data-field-static="true"` forces its static treatment. Keep the field low-opacity and local to its root; protect text,
controls and the ordinary pointer. There is no autonomous idle movement.

The runtime/CSS are `scripts/magnetic-field.js` and
`styles/magnetic-field.css`; detailed integration is in
[the magnetic-field adapter](magnetic-field.md). Defaults are medium density,
right alignment, automatic theme and strength 0.6.

Reduced motion disables cursor-field interpolation, and coarse/touch input must
not leave a stale pointer trace. Clear on exit/cancel, stop when hidden/offscreen
and do not let a response cover or alter a focus target. Reduced transparency,
increased contrast, explicit solid material and ancestor reduced/paused flags
also select static treatment; forced colours and print hide the decoration.
The field is expressive
background feedback; no data or essential state depends on it. This adapter
needs its own runtime/CSS and rendered consumer checks; a CSS declaration alone
does not implement it.

## Layout, controls and appearance

- Begin with up to a 1440px frame, 28px desktop and 16px narrow gutters; adapt a
  marketing canvas deliberately. Content panels typically have 20–28px padding.
- Preserve ordinary document flow for long content. Floating or sticky controls
  must not cover the last item, focused target, composer or virtual keyboard.
  Use coordinated scroll padding/margins once, not two stacked offsets.
- Keep controls semantic: links navigate, buttons act, fields have labels. Tabs
  support arrow/Home/End navigation; selected/current/expanded states follow the
  actual application. A styled surface is not working interaction.
- Visible selection may use a neutral fill, outline, marker or other sufficiently
  clear cue. A Current Blue outline is not compulsory on every selected item. Focus
  and essential boundaries
  need measurable contrast independent of refractive highlights.
- Disclosures use one right/down chevron (closed/open), a 44px total row and an
  8px following gap. Selects use one down chevron with reserved trailing inset.
  Native multiple selects are not popup controls. Keep long paths and labels
  wrap-safe with `min-width:0` / `minmax(0,1fr)` where needed.
- Focused text inputs/selects/textareas use one fine 1px boundary, a restrained
  surface change and a visible caret. No thick outer glow/halo or doubled border.
  Buttons/links keep an independent visible keyboard indicator; high-contrast
  system modes may strengthen focus.
- Settings and drawers may use a bounded glass shell when requested. Long
  reading and dense form regions retain stable opaque interiors as needed;
  this is not a blanket requirement to replace a glass panel with a flat card.
  Provide reachable reduce-transparency
  and reduce-motion choices when relying on optical effects. System reduction,
  increased contrast and forced colours win over an aesthetic preference.
- Theme/background choices are product decisions, not mandatory options on every
  site. If preferences persist, allowlist presentation values and handle storage
  failure. Product data and authorization are separate from appearance state.

## Photography and imagery

Choose one relevant subject because it explains or expresses the actual work.
A credible instrument, process, material, environment or person doing something
specific is stronger than a generic technology metaphor. Show enough context to
understand what is being observed. Do not imply ownership of a facility,
partnership, delivered project or measured result through an attractive image.

| Decision | Current direction |
| --- | --- |
| Subject | A real setting, useful process, material behavior, observed detail or person engaged in credible work. Landscapes belong when the context makes them relevant. |
| Light | Natural or plausible editorial light, visible material texture and controlled highlights. Preserve skin, metal, paper and glass as believable materials. |
| Colour | Cool natural whites and balanced exposure. Preserve the subject's own colour; do not apply a blue wash, Current Blue tint, duotone or warm beige grade to force a match. |
| Composition | One clear subject, deliberate negative space, an understandable scale and enough environmental context. Avoid a visual collage competing with the headline. |
| Crop | Keep a high-resolution uncropped master. Define subject/focal point and wide, portrait and small-thumbnail crops. Inspect each at real placement sizes; do not stretch, crop off essential evidence or assume a desktop crop works on a phone. |
| Reading overlay | Place text in genuine quiet space or a bounded readable treatment. A theme wash cannot excuse poor contrast; allow a separate opaque reading area when needed. |
| Provenance | Record source URL or local source, creator, license/permission, acquisition date, alterations and generated status. Retain source pixels and revision/crop choices. |
| Documentary use | Use genuine sourced imagery for claims about people, premises, processes or delivered work. A generated photorealistic scene is never documentary proof. |
| Generated concept | Use only when it helps explain a proposed form or environment; label it nearby as generated and preserve its prompt/source record. Do not invent a photographed team or facility. |

Vary subjects with the work. Water is one accepted material study, not a brand
requirement. Avoid macro texture wallpaper without an explanatory subject,
robot/brain/handshake stock motifs, default crystals, floating abstract objects
and photorealistic AI imagery passed off as evidence. A page can be entirely
typographic or diagrammatic when that is the clearest expression.

The ocean and selected crystal remain retained reference assets, not default
heroes. Preserve an asset's actual geometry when used; optional placement does
not permit redrawing approved identity. Diagrams must explain a relationship,
with labels and a text equivalent, rather than decorate the background.

## Iconography

Use the existing **Phosphor Regular** family. Choose one consistent weight and
optical construction across the interface. Start at 20px for a compact action
and 24px where the surrounding control calls for it; 16px is reserved for a
small inline symbol with adequate legibility. Interactive regions stay at least
44×44 CSS px, independently of the drawing's size.

Close controls use a clear glyph within a 44px target, with no permanent thick
white enclosure. Hover/press can change a quiet fill; keyboard focus remains
discreet and visible, with stronger system contrast when requested. Centre the
Phosphor three-dot overflow drawing optically in its 20/24px box; do not repair
alignment with arbitrary nudges or inherit a hollow-circle stroke style.

Icons identify an action or state. Do not add emojis, decorative icons beside
every heading, mixed filled/outline families or redundant arrows after every
link. An external-link indicator is useful only when destination behavior needs
clarification. Use one disclosure chevron or one state symbol, not duplicates.
The Balance bird identifies Fyronyx; it is not a substitute for an action icon.

Provide visible labels where an action is ambiguous, including on touch. Icon-only
controls need an accessible name and a desktop tooltip where useful; a tooltip
is never the only explanation. Keep icons single-colour and optically aligned,
with no spectral effect on the glyph. Test focus, disabled and high-contrast
states without relying on hover or colour alone.

## Digital reports, presentations and charts

Design the working digital view first: responsive reports, readable figures and
presentation navigation that actually changes the view. Let a reader inspect a
figure, switch a relevant period/view and return to the argument without losing
context. Presentation controls support keyboard/touch and clear progress; they
are real controls, not decorative dots. Keep sustained reading and plotted data
stable, with source, units, uncertainty and a readable value/table equivalent.

An optional finite attention light may travel from white into a restrained
spectrum along material edges or non-data framing on input/replay. It never
recolours an encoded series, axis, value or status. No perpetual shimmer, white
bloom over labels or rainbow data semantics. Print/PDF is a secondary export:
use opaque ink, still figures, useful pagination and no interactive chrome.
Email and native views keep their own platform constraints.

The identity stays static by default. An optional Facet flight study can move the
intact supplied form along one gentle bounded path, with a brief surface shimmer
and a settled end pose. Do not move feather geometry, reshape facets, animate the
wordmark or turn the header logo into a looping ornament. Replay is optional;
reduced motion shows a still, and the flight never crosses required reading.

## Accessibility, fallbacks and verification

1. Verify immutable palette/master integrity and the current neutral role mapping.
   Check actual composite text contrast: at least 4.5:1 for normal text, 3:1 for
   qualifying large text and applicable essential non-text indicators.
2. Test glass over light, dark and detailed backgrounds. Bound interior brightness
   separately from highlights. A token pair or shader clamp is not rendered proof.
3. WebGL/texture/shader failure uses CSS material; missing backdrop filtering uses
   an opaque surface. Reduced transparency disables the optical canvas and both
   standard/WebKit backdrop filters. A 20% fill is still transparent.
4. Reduced motion stops CSS and JavaScript animation, including drift, springs,
   pressure scaling and spectral interpolation. Increased contrast and forced
   colours receive stable usable controls. Essential content survives image failure.
5. Inspect default/hover/press/release/focus/selected/disabled and real pending/error
   states. Check fast repeated input, keyboard recovery, Escape/outside dismissal,
   history and focus return. Wait for transitional content to settle before auditing.
6. Exercise actual glass buttons, menu actions, context panels and drawers, not
   just a background, link or documentation card. Verify rest/hover/held-press/
   release, rapid reversal, keyboard/touch, scrim dismissal and focus recovery.
   Check GSAP/CSS state ownership, reduced end states and closed-root rendering.
7. Check authored copy for em dashes, decorative eyebrows and uppercase labels;
   inspect all metadata and figures in Geist. Check imagery provenance, natural
   colour, wide/portrait/thumbnail crops and actual subject relevance. Verify
   consistent Phosphor Regular icons, clear touch labels and purposeful borders.
8. Inspect built CSS, route load order and computed styles. Check desktop, tablet,
   390px/320px web layouts, long labels and 200% zoom. Test Safari, Chromium and
   Firefox where available; record untested browsers and physical devices.
9. Inspect motion/frame cost in the actual consumer. State the backdrop renderer's
   supported inputs and fallback; never claim arbitrary-content refraction from
   the ocean example. Check resource cleanup and hidden/offscreen behavior.
10. Separate source implementation, automated checks, visual review, device/assistive
   technology proof, human acceptance and release. No citation or lint score
   certifies HIG/WCAG conformance or authorizes publication.

## Reference and maintenance routing

Use the current Apple [Materials](https://developer.apple.com/design/human-interface-guidelines/materials),
[Meet Liquid Glass](https://developer.apple.com/videos/play/wwdc2025/219/) and
[Adopting Liquid Glass](https://developer.apple.com/documentation/technologyoverviews/adopting-liquid-glass)
for platform intent. `apple-hig` can route detailed lookup; native work uses the
matching existing platform skill. `apple-hig-liquid-glass` guides the explicit
web interpretation. Composition critique may use `design-taste-frontend`; its
house style does not override this accepted direction or establish compliance.

The INTO [research appendix](../../../../into-consulting-brand-system/research/benchmarks/2026-10-30-web-library/appendix-apple-hig.md)
and [runtime notes](../../../../marketing-studio/packages/consulting-ui-proposal/rollout/README.md)
remain optional local implementation evidence. They are not portable dependencies,
Fyronyx identity sources or authority to transfer every consumer exception.

Canonical application rules live here. Portable guidance and primitives are
versioned together; existing consumers opt into edition 04.2 / package 2.2.0.
The installed `fyronyx-design` aid must be updated deliberately in both Claude
and Codex mirrors, with byte parity verified. Old specimens remain historical
until regenerated. Preserve unrelated work and the distinction between adopting
these rules, migrating a product and publishing it.

### Quiet field focus and cursor light

Focused text fields use one clear 1px boundary with a restrained surface change
and visible caret. Avoid stacking a thick outer attention ring over the field
border. Keep button and navigation keyboard focus independently visible; a
material highlight never substitutes for focus. High-contrast modes may restore
stronger system indicators. Cursor light on glass stays diffuse and low-opacity;
keep the edge dispersion expressive without washing the label in a white bloom.
Retain the optical surface throughout an exit, then release its renderer only
after the overlay is hidden. Note feedback must return to an edited state after
new input, and preview-only storage must state its reload boundary.

Current Blue primary actions may use a subtle tonal finish: a small neutral
highlight above the blue and a darker lower edge, with a restrained hover lift
and finite white-to-spectrum press light. Keep text contrast across the full
gradient, preserve plain disabled states and strong keyboard focus. This is an
ordinary action finish, not a claim of backdrop refraction and not permission
to fill whole pages with decorative gradients.
