Registry & source ownership
Registry & source ownership
Section titled “Registry & source ownership”The BeeUI Registry is the machine-readable map that powers source ownership. A Registry item points to public source, transitive BeeUI dependencies, external package requirements and integrity information. It is not a remote code marketplace and it is not a second package manager.
Registry item lifecycle
Section titled “Registry item lifecycle”- Inspect the requested item and resolved dependency closure.
- Dry-run the copy plan before mutation.
- Copy source into the consumer paths configured by
beeui.config.json. - Commit the copied source in the consumer repository: it is now consumer-owned.
- Diff local files against the current Registry snapshot before an update.
- Update only after reviewing local/upstream changes and re-running consumer verification.
The CLI does not fetch or execute remote code. Its Registry snapshot is bundled with the CLI/package build and verified by integrity metadata.
Dependencies and setup
Section titled “Dependencies and setup”BeeUI-to-BeeUI source dependencies are closed transitively by the Registry. External requirements remain explicit consumer responsibilities. For example, an overlay or native sheet may require provider/native peers that should be installed and configured deliberately; the CLI reports those requirements rather than silently changing your app.
Component reference pages read Registry identity/dependency metadata from the same registry/registry.json authority. If a component is removed, renamed, or its dependency closure changes, the public Web gate must fail until docs and Registry truth agree.
Collision and local-edit policy
Section titled “Collision and local-edit policy”A normal add/update must not silently destroy a differing destination file. Use dry-run/diff first. The update flow distinguishes unchanged files, upstream-only changes, local-only changes and true conflicts. Forceful replacement is explicit because, after copying, the consumer owns the source.
Package boundary vs Registry
Section titled “Package boundary vs Registry”Registry ownership is not inherently “better” than package consumption. It trades centralized upgrades for source visibility and customization. See CLI & source ownership for the decision table and commands, and Examples for buildable consumers of both models.