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.