azwerkswerkregister
azwerks werkregisterpublic register
№ 02 · WORKazw-rec-002
candidate

Radium design-system integration

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

Public record · partial proof

  • Radium
  • adapter layer
  • contracts
  • tokens
Domaindesign-systemPublished2026-06-30Updated2026-07-01Proof3Relations2

Record metadata

Record ID
azw-rec-002
Slug
radium-design-system-integration
Visibility
public
Classification
visual-system
Domain
design-system
Type
work
Maintainer
azwerks
Version
0.1.0
Created2026-06-30Updated2026-07-01Strengthlimited
partial

First recorded and last updated . The current content is conservative, evidence-backed, and bounded by caveats.

Claims

02

Bound claims

2 caveats

Claims are presented with limited proof posture and explicit caveats.

Claim posturepartial

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

Strength
limited
Proof
partial
Visibility
public

Limits

Only the components needed by current public surfaces are integrated. Full accessibility, interaction, and visual-regression checks remain quality-phase work.

Proof ledger

3

Independent public artifacts that support this record. Missing proof remains visible through caveats.

  • Radium component manifest

    source-cited

    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

    source-cited

    Exports Radium components through the website-owned adapter layer.

    File:
    src/components/azwerks/index.ts
    State:
    source-cited
  • Radium stylesheet bridge

    source-cited

    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.

Radium component manifest

source-cited

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

source-cited

Exports Radium components through the website-owned adapter layer.

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

Radium stylesheet bridge

source-cited

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.

Evidence sequence

3

Ordered path from source contract to demonstrated route behavior.

  1. 01

    Radium component manifest

    source-cited

    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.

  2. 02

    Adapter export boundary

    source-cited

    Exports Radium components through the website-owned adapter layer.

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

    Radium stylesheet bridge

    source-cited

    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.

  4. ConclusionLimited proof onlyThe first surfaces are composed, but record hardening and quality checks remain open.

Capability coverage

Coverage is intentionally conservative; partial means not fully proven.

CapabilitySourceBuildA11y
Adapter compositioncandidateProvenPartialNone
Public filteringreview-requiredPartialPartialNone
Record hardeningopenPartialNoneNone
  • Proven
  • Partial
  • Claimed
  • None

Operation ledger

Authored operations behind this public content record.

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.

Matter ledger

Open matters remain open. Settled decisions are listed separately.

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.

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 pagesWould spread vendor paths across route code.
  • Local component copiesWould 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

Relation trace

Related work is expressed as relation language, not as more projects.

Integration dependencies

COLOPHON · № 02azw-rec-002
Created
Updated
Record ID
azw-rec-002
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.