№ 02 · WORKREC / radium-design-system-integration
candidate

Radium design-system integration

The website integration boundary that consumes Radium CSS, assets, and existing React components without editing design-system source.

Radium source inventory, architecture plan, and adapter source files.

  • Radium
  • adapter layer
  • contracts
  • tokens
Domaindesign-systemVersion0.1.0Updated2026-07-01MaintainerazwerksProofpartial

Overview

01

What it is

The website integration boundary that consumes Radium CSS, assets, and existing React components without editing design-system source.

Canonical facts

Domain
design-system
Version
0.1.0
Updated
2026-07-01
Maintainer
azwerks
Proof
partial
  • Only the components needed by current public surfaces are integrated.
  • Full accessibility, interaction, and visual-regression checks remain quality-phase work.

How the record thinks

02

Key decisions

01

Decision

Should page code import directly from vendor components?

ChosenNo. Page code imports from `src/components/azwerks/`.

A stable adapter boundary keeps source use auditable and allows future compatibility shims outside vendor.

Alternatives considered

  • Direct deep imports in pages — Would spread vendor paths across route code.
  • Local component copies — Would recreate or fork existing coded components.

Consequences accepted

  • Every new component use should extend the adapter and contract record first.
Recorded
2026-06-30
Source
foundation report

Lineage

03

History

Operations

Adapter

  1. Adapter2026-06-30

    current

    Extend component adapter layer

    Expose required Radium components through `src/components/azwerks/`.

    Intent
    Keep pages free from deep vendor paths while preserving existing component behavior.
    Action
    Added group re-exports and matching declaration shims.
    Result
    Page code imports existing components from the website-owned adapter boundary.

    Adapters remain thin and must not become component forks.

How do you know?

04

Evidence

03

Radium component manifest

reviewed

Lists existing design-system components and their intended usage boundaries.

File:
vendor/azwerks-design-system/handoff/design-system/component-manifest.md
State:
source-cited

The manifest is source material; website integration still requires local adapters.

Adapter export boundary

reviewed

Exports Radium components through the website-owned adapter layer.

File:
src/components/azwerks/index.ts
State:
source-cited

Radium stylesheet bridge

reviewed

Documents the website-owned CSS bridge to the read-only vendor Radium distribution.

File:
src/styles/radium.css
Boundary:
site-owned import

The vendor stylesheet itself remains outside the website implementation layer.

Unresolved

05

Open matters

02

Matter ledger

Open matters stay visible and separate from decisions.

Open integration matters

  1. Open questionmat-design-system-lint

    open

    Define full design-system adherence lint

    The repository guard catches raw color literals, but full token-adherence lint is not wired.

    Position
    Add `lint:ds` during quality hardening.

    Until then, token discipline relies on review plus current guard scans.

  2. Open questionmat-radium-visual-regression2026-07-01

    open

    Add visual regression coverage

    The adapter layer consumes existing Radium components, but visual regression coverage for the composed site is not complete.

    Position
    Treat current component integration as partial proof until visual checks are automated.

    Component preservation is source-backed; pixel stability still needs a quality gate.

Links

06

Relations

Relations

How Radium design-system integration relates to the rest of the register.

Integration dependencies

COLOPHON · № 02REC / radium-design-system-integration
Created
Updated
Record ID
REC / radium-design-system-integration
Version
0.1.0
State
candidate
Maintained by
azwerks
Derived from
Radium source inventory, architecture plan, and adapter source files.

LimitsIntegration record for current site usage; it does not replace the Radium design-system documentation.