ARCH-3: Define internal Atomic Design/component registry architecture #60

Merged

jwilger merged 1 commit from issue-3-atomic-design-registry into main

2026-05-07 06:50:33 -07:00

jwilger commented

2026-05-07 06:28:40 -07:00

Owner

Closes #3

Summary

Document daisyUI usage boundaries and compile-time Atomic Design layers for internal Phoenix components.
Define search-first component registry behavior, creation/evolution rules, accessibility contracts, and validation expectations.
Extend the event model design_system schema example/rules with registry evidence, evolution compatibility, and accessibility validation fields.

Verification

npm run check:event-model — passed (ok - 49 slices checked)
Docs/operator review — no findings after fixes
Architecture review — no blocking findings

Mix gates skipped because this repository does not have a mix.exs yet.

Closes #3 ## Summary - Document daisyUI usage boundaries and compile-time Atomic Design layers for internal Phoenix components. - Define search-first component registry behavior, creation/evolution rules, accessibility contracts, and validation expectations. - Extend the event model `design_system` schema example/rules with registry evidence, evolution compatibility, and accessibility validation fields. ## Verification - `npm run check:event-model` — passed (`ok - 49 slices checked`) - Docs/operator review — no findings after fixes - Architecture review — no blocking findings Mix gates skipped because this repository does not have a `mix.exs` yet.

jwilger added 1 commit

2026-05-07 06:28:40 -07:00

docs: define component registry architecture 4ba746f6a1