Installation should end in readable source
An open-code installer is a delivery mechanism. It resolves a known registry record, checks safe target paths, prevents accidental overwrites, and writes the component into the application.
After that, the file belongs to the product. Teams can inspect semantics, remove unused variants, adapt the API, and keep behavior aligned with their own requirements.
Ownership includes the accessibility contract
Owning source does not mean discarding the behavior that made it dependable. Labels, descriptions, focus movement, keyboard input, error announcements, disabled states, and client boundaries are part of the component contract.
- Prefer native semantics before adding ARIA.
- Keep focus visible and reading order predictable.
- Test content at realistic lengths.
- Document client/server boundaries explicitly.
Registries keep customization traceable
A registry lets tools and agents select an exact stable component rather than inventing names or copying an unrelated implementation. It can declare source files, dependencies, usage, stability, and accessibility requirements alongside the visual preview.
The result combines freedom with a reference point: customize what the product needs, and preserve the contract deliberately.