Module registry 

Installed-component registry — the single source of truth for what Rusty has installed, where, and whether a core component is sealed against override.

Persisted at ~/.mlstack/installed.json. This module is deliberately self-contained (load / save / mutate) so it can be threaded through the installer dispatch (see installer::run_native_installer) and consulted by:

• dep-sourcing / no-override (refuse to reinstall a sealed core component)
• verification (is this component already known-good?)
• uninstall (enumerate pip packages + locations to remove)

Design notes

• IDs are free-form Strings matching the existing component_status::is_component_installed_by_id identifiers (rocm, pytorch, triton, aiter, …).
• sealed marks a core component (rocm / pytorch / triton) that later installers must reuse, never override. See Stage 3 of the v0.3.0 remediation (tenet: single-source deps / no-override).
• Timestamps are caller-supplied ISO-8601 strings (chrono Utc::now) so the registry stays pure with respect to I/O.

Structs

InstalledComponent

A single installed component record.

InstalledComponentRegistry

The persisted registry of installed components.

Constants

CORE_COMPONENT_IDS

The set of ids treated as core (sealed-on-install) components.

SEALED_INSTALL_ONCE_IDS

Additional install-once components the tenet names (“aiter, flash attention, etc.”) — expensive ROCm builds that, once installed, must be reused and never overridden. Sealed alongside the cores.

Functions

is_core_component

Is the given id a core component?

should_seal_component

Should this component be sealed on install (core OR install-once)?