Components architecture decisions

These accepted decisions explain why Components owns its public React and DOM contracts while keeping implementation libraries, optional peers, and unstable renderer machinery behind explicit boundaries.

Decisions

• DOM-coupled public component contract — React, native HTML, refs, events, and form semantics are intentional public contracts.
• Public component classification — distinguishes primitives, composites, and interop-only surfaces.
• Repository-owned kernel boundary — keeps optional and renderer-specific dependency graphs out of the setup-only root.
• Stable presentation renderer profile — promotes the exact nine-slot stable-presentation/v1 adapter boundary while broader machinery remains unstable.

Read UI foundation for the current architecture and capability matrix.