Home /Modules/registry/REGISTRY-3.0-MODIUM.md

REGISTRY-3.0-MODIUM.md

registry/REGISTRY-3.0-MODIUM.md · 61 line(s) · markdown

Registry 3.0 — Modium Catalog Contract

Responsibility split

Modium owns storage operations and artifact-integrity verification. Registry owns durable catalog identity, classification, lifecycle, and relationships describing those resources.

Registry never mounts a volume, claims a device, formats storage, reads or writes a storage region, or restores data. It stores stable record IDs and descriptive locator metadata. Modium resolves the current host location and returns bounded VM-local handles.

Region record

A Modium region is recorded as:

The native registration API accepts already-inspected metadata only. For removable media it requires a 64-hex device seal. Registration starts unverified and registered. It does not create or initialize storage.

Lifecycle

Expected transitions:

The native record engine enforces allowed state edges and refuses verified/available transitions for a Modium region unless its recorded integrity state is intact.

Important limit: the current in-process C API does not authenticate which caller supplied an integrity status. A program with direct access to the setter can report an arbitrary status. Therefore, the lifecycle check is semantic validation, not a complete security boundary. Production integration must place integrity updates behind a trusted Modium adapter and operating-system/application policy, and should persist verifier evidence before enabling VM-facing mutation.

Read-only discovery

Discovery and inspection are observational. They can create a volume-observation record with discovered/inspected status, but do not create or initialize a storage region. The separate Modium claim operation remains governed by lib/vm/MODIUM-STORAGE-REGION.md.

Registry registration accepts a stable caller-supplied record ID and inspected descriptor fields. It does not call a Modium claim operation. A duplicate ID fails rather than silently rebinding the record to a different device.

Availability is not permanent

An available flag is only the last recorded state. Every actual region open/access must ask Modium to resolve the current region and verify the current descriptor/device seal. If the device is offline, foreign, unreadable, or altered, the runtime receives an explicit failure. It must not fall back to a different device with the same mount path or label.

Required integration tests