NAME

Data::Shared::Composite - Runtime for composite Data::Shared mounts

DESCRIPTION

Internal to Data::Shared; not a public API. A composite mount keeps one child instance per parent address: children are allocated through a hidden registry, constructed lazily on first write, opened on demand from per-child storage, and cached with LRU eviction, which cache_size bounds for a file-backed root only: an anonymous segment cannot be reopened once evicted, so an anonymous composite keeps every child it has opened. A read, delete or pop at a missing child never creates one, but on a writable root call other than unlink or destroy at a missing address does, because the facade cannot know whether the native method mutates. See the DEEP PATHS section of Data::Shared, which is authoritative for both.

Lifecycle mutations are serialized through allocation, construction, publication, and deletion. Exception rollback preserves existing scores and reservations. Shared counts and cache-order updates take constant time. Legacy readiness flags remain readable. An interrupted mutation leaves a marker, and the count is rebuilt from it on the next writable open or lock. Freezing and flushing walk every registered child, reopening an evicted one read-only where it is already sealed. Unpublished files require explicit recovery; the module does not implement a power-loss transaction journal.