Skip to main content

RuntimeBootstrapPolicy

Trait RuntimeBootstrapPolicy 

Source
pub trait RuntimeBootstrapPolicy {
    type Error;

    // Required methods
    fn validate_allocation(
        &self,
        key: &StableKey,
        slot: &MemoryManagerSlot,
    ) -> Result<(), Self::Error>;
    fn runtime_bootstrap_identity(
        &self,
    ) -> Result<PolicyIdentity, PolicyIdentityError>;

    // Provided method
    fn prepare_bootstrap(
        &self,
        _admission: &mut BootstrapAdmission<'_>,
    ) -> Result<(), Self::Error> { ... }
}
Expand description

RuntimeBootstrapPolicy

Host policy for recovered admission, allocation checks and runtime identity.

The runtime admits host grants and pool eligibility before calling the allocation check for each external declaration. Governance stays private; historical ownership checks still apply to every declaration.

crate::MemoryRuntime binds its successful bootstrap to this identity. Repeated bootstrap is idempotent only when the caller supplies the same sealed declaration snapshot and the same policy identity. Implementations should change the identity whenever policy configuration or semantics change. Configuration-dependent policies should include a digest derived from their effective configuration.

Required Associated Types§

Source

type Error

Policy error type.

Required Methods§

Source

fn validate_allocation( &self, key: &StableKey, slot: &MemoryManagerSlot, ) -> Result<(), Self::Error>

Validate one resolved stable-key and allocation-slot claim. The runtime checks host grants and pool eligibility before this callback; historical ownership checks follow it. Governance bypasses this callback.

Source

fn runtime_bootstrap_identity( &self, ) -> Result<PolicyIdentity, PolicyIdentityError>

Construct the bounded semantic identity of this policy configuration.

Provided Methods§

Source

fn prepare_bootstrap( &self, _admission: &mut BootstrapAdmission<'_>, ) -> Result<(), Self::Error>

Admit recovered identity and complete declarations before resolution.

Runs once per cold bootstrap attempt after validated recovery. Warm bootstrap/adoption does not replay it. The default selects no historical keys. Hosts compose generated consumers here under their existing policy and bucket profile. Include these semantics in the policy identity.

Dyn Compatibility§

This trait is dyn compatible.

In older versions of Rust, dyn compatibility was called "object safety".

Implementors§