Expand description
Component model, lifecycle, native process isolation, and host authority.
This is the foundation of Frame. A component declares service wiring and
capability needs, then runs in its own isolated process tree. Declarations
never grant authority. The embedding host owns the sole mutable capability
table through capability::HostCapabilityFacade; component-facing
capability::CapabilityChecker values can only evaluate fresh checks.
Native BEAM entrypoints receive only component::ChildArgument values, so
neither facade nor table has a BEAM representation or crossing path. This is
the type-level self-grant exclusion; the separate frame-capability crate
keeps contract values enforcer-agnostic and beamr-free.
Modules§
- capability
- Native host ownership and enforcement of the capability contract.
- component
- Component identity and declarations.
- composition
- Correct beamr scheduler composition for hot-loading hosts.
- error
- Typed registration and lifecycle failures.
- event
- Typed, bounded lifecycle event delivery.
- registry
- Linearized component registration and lifecycle operations.
- runtime
- The composed component runtime — the ONLY composition surface embedding applications touch (scaffold-unification design, §5.2, finding B6).
- status
- Observable component runtime status.
- supervision
- Host-seated native process-tree supervision.