frame-core 0.3.0

Component model, lifecycle, process isolation — hosts components as supervised BEAM process trees
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

//! 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.

pub mod action;
pub mod capability;
pub mod component;
pub mod composition;
pub mod error;
pub mod event;
pub mod fragment;
pub mod registry;
pub mod runtime;
pub mod status;
pub mod supervision;