Shared language
Terms used across Brand Core, product SDKs, accessibility evidence, release provenance, and the preview protocol. Hover marked terms throughout the Portal for this context in place.
The practice of making interfaces perceivable, operable, understandable, and robust for people with varied abilities.
Why it matters hereFrauthy treats accessibility behavior and evidence as part of the public component contract.
Open related reference ↗Web Content Accessibility Guidelines: the testable international criteria used to evaluate accessible web content.
Why it matters hereThe Portal targets WCAG 2.2 level AA and supplements automation with manual assistive-technology checks.
Open related reference ↗Human verification with assistive technology such as screen readers, voice control, magnification, and switch input.
Why it matters hereAutomation cannot prove interaction quality, so releases retain a visible manual-evidence state.
Open related reference ↗A versioned software development kit that packages public components and contracts for a specific consumer.
Why it matters hereProduct SDKs own product nouns while Brand Core remains universal.
Open related reference ↗The public names, props, events, states, and behaviors consumers are allowed to depend on.
Why it matters hereVersion comparison is based on these contracts rather than incidental implementation details.
Open related reference ↗A versioning contract using major, minor, and patch numbers to communicate compatibility and change scope.
Why it matters hereEvery Portal snapshot resolves an exact SDK version instead of a mutable latest tag.
Open related reference ↗A version published before stable availability so contracts and evidence can be evaluated without implying final compatibility.
Why it matters hereFrauthy uses exact next/RC versions while behavior and manual evidence are still being promoted.
Open related reference ↗A published bundle whose bytes, version, and checksum do not change after admission.
Why it matters hereThe Portal renders the exact artifact it verified, preventing documentation from drifting from released code.
Open related reference ↗The verifiable chain connecting repository, commit, tag, workflow, package version, and checksum.
Why it matters hereProvenance lets users establish exactly where a documented component came from.
Open related reference ↗A machine-readable declaration of an SDK, its components, fixtures, versions, and accessibility contracts.
Why it matters hereThe Portal validates manifests before admitting product-owned previews.
Open related reference ↗The exact-version registry that unifies independently owned SDK component manifests.
Why it matters hereFederation keeps product dependencies separate while making their contracts discoverable in one Portal.
Open related reference ↗Rendering component HTML on the server before browser JavaScript runs.
Why it matters hereStable server output improves first paint, resilience, and hydration correctness.
Open related reference ↗Attaching client behavior to server-rendered HTML without replacing or contradicting the existing document.
Why it matters hereHydration requirements are recorded per component so consumers understand the runtime cost.
Open related reference ↗Hot Module Replacement updates modules during development without a full page reload.
Why it matters hereHMR soak checks expose state and cleanup defects that cold builds can miss.
Open related reference ↗A sandboxed, versioned iframe surface that renders product-owned components without leaking product CSS or runtime state into Portal chrome.
Why it matters hereThe host and frame exchange validated messages for fixtures and reader preferences.
Open related reference ↗A separate document boundary used to isolate style, script, and accessibility state.
Why it matters hereProduct previews retain their own visual ownership while the Portal controls verification and navigation.
Open related reference ↗A perceivable indicator showing which interactive element will receive keyboard input.
Why it matters hereEvery keyboard-operable control must preserve a high-contrast focus state.
Open related reference ↗The documented keys, focus movement, selection, dismissal, and activation behavior of a component.
Why it matters hereKeyboard behavior is versioned alongside props because consumers depend on both.
Open related reference ↗A named design decision—color, spacing, type, motion, or geometry—exposed as a reusable variable.
Why it matters hereTokens keep the visual system cohesive without coupling products to Portal CSS.
Open related reference ↗Relationship-Based Access Control models authorization through relationships between subjects and resources.
Why it matters hereFrauthy product interfaces surface relationships, checks, and decision evidence rather than hiding them behind roles.
Open related reference ↗OpenID Connect is an identity layer over OAuth 2.0 used to authenticate users and obtain verifiable identity claims.
Why it matters hereFrauthy maps verified identity claims into authorization relationships.
Open related reference ↗OpenTelemetry Protocol transports traces, metrics, and logs between instrumented services and observability backends.
Why it matters hereFrauthy uses lifecycle telemetry to explain authorization decisions across service boundaries.
Open related reference ↗A cryptographic digest used here to identify exact artifact bytes.
Why it matters hereAny byte change produces a different checksum, so the Portal can fail closed on drift.
Open related reference ↗A content-oriented web framework that renders HTML by default and hydrates only selected interactive islands.
Why it matters hereThe Portal uses Astro for static exact-version documentation with bounded client JavaScript.
Open related reference ↗A fine-grained reactive UI framework used by Frauthy interactive components and Portal islands.
Why it matters hereBrand Solid adapters expose typed accessible components without a virtual-DOM runtime.
Open related reference ↗The development server and build pipeline used by the Frauthy web applications.
Why it matters herePackage and Portal gates verify that compiled imports behave under the consumer build tool.
Open related reference ↗The JavaScript runtime and package tooling used across Frauthy TypeScript repositories.
Why it matters hereScripts, tests, builds, and exact dependency workflows share one fast runtime.
Open related reference ↗A promoted contract whose API, behavior, and required evidence are ready for supported consumption.
Why it matters hereStable is an evidence state, not simply a visual badge.
Open related reference ↗A prerelease contract whose names and intended behavior are substantially defined while some promotion evidence may remain.
Why it matters hereConsumers can evaluate the API but should pin exact versions and review known gaps.
Open related reference ↗An early contract that may still change materially before promotion.
Why it matters hereAlpha components remain visibly marked so experimental behavior is never mistaken for stable support.
Open related reference ↗A component that communicates visual structure or meaning without owning an interaction model.
Why it matters herePresentational components still require semantic markup and accessible names where meaning is conveyed.
Open related reference ↗A component that receives input, changes state, moves focus, or triggers an action.
Why it matters hereInteractive components require explicit keyboard, focus, dismissal, and assistive-technology contracts.
Open related reference ↗