Expand description
Framework core schema. Covers the wire envelope (WireEnvelope,
OpsetId, WireCorrelation, CorrelationKind), data-plane
batching (SlotFillBatch, SlotFill), peer identity
(PeerProto), and snapshots (NodeSnapshotProto,
ComponentSnapshotProto). Matches package bb.core;.
Structs§
- Component
Snapshot Proto - Snapshot of a single Component’s state, opaque to the framework.
- Edge
RttReport - PLAN tender-noodling-sky Phase 3e-iv — per-edge RTT report
piggybacked on a response envelope. The sending peer reports its
observed SRTT/RTTVAR for its outgoing edge to
next_hop_site_idin chainchain_id. The caller writes the report intoAddressBookEntry.reported_outgoing\[(next_hop, chain_id)\]so a multi-hop chain budget can be composed from a single direct neighbor’s address-book entry. - Node
Snapshot Proto - Top-level snapshot of a Node’s state. Produced by
Node::snapshot(); consumed byNode::restore(snap). See ENGINE.md §15 and AUTHORING_COMPONENTS.md §14 for the lifecycle. - Peer
Proto - Peer identity record. Used inside snapshots + by the framework’s AddressBook primitive (ENGINE.md §3 framework primitives).
- Slot
Fill - One slot-fill record carried inside a
WireEnvelope. Each fill names its destination via a multiaddr suffix that’s appended to the receiver’s self-identity to form the full address. - Wire
Correlation - Correlation header. Empty
wire_req_id(= 0) is valid only whenkind == NONE. - Wire
Envelope - The unit of wire delivery — one delivery to one peer. Per the
analyzer’s batching (ANALYSIS.md §9 analyze_wire_edges), a Send
op with N typed inputs packs all N as
fillsso one envelope completes the data-plane DAG.
Enums§
- Correlation
Kind - Request/response correlation discriminator.