Memory-first persistence of network-learned state.
The engine’s tables are the truth; a host flushes sealed snapshots of them to a PersistedStore and seeds the tables from it at the next boot; destination identities deliberately retain RNS’s historical known_destinations filename and their existing Prns region tag.
Config-derived state (held identities, registered destinations, group keys) is never snapshotted — the identity vault and the host recipe re-supply it at boot.
Compose route types into a RequestEndpointSet value, e.g., request_endpoints![Health, Echo, Status]. Each arm awaits
a concrete handler future, so the set is monomorphized. There’s no boxing and it’sno_std-clean.
The explicit “I wire interfaces myself” answer to the recipe’s interfaces field: attach everything after construction through the node handle (or, on a board, at slot activation).
Heap-host limits for the transfer, part-name, and part-state buffers owned by
active Resources. Incoming and outgoing traffic have independent budgets;
zero disables Resource buffers in that direction.
The control/observability plane: what the engine did, not what arrived. Fully owned —
no borrow into the inbound frame, so it can outlive the reaction if an app buffers it.
RNS 1.4.2 Destination.enable_ratchets / Destination.enforce_ratchets.
One enum where the reference has two bool flags, so enforcing without ratchets (which would refuse every single packet) is unrepresentable.
RNS 1.4.2 Link.resource_strategy, engine-gated: the reference’s unbounded ACCEPT_ALL becomes an accept with enforced bounds, refused at the advertisement gate before a single part moves.
The high-level API shared by every platform’s node handle. Tokio carries commands over an unbounded channel with per-command oneshots; Embassy uses a bounded channel and static completion pool.