Expand description
Runtime-neutral Lace interlace core.
Core owns interlace state and policy evaluation. When a machine needs store
data or persistence, its one machine-owned StoreCall suspends progress until
the runtime-owned Lace submits the matching result. Rust projects facts
and Datalog bindings above store result data. Stores do not evaluate exchange
policy and do not know what “advertisable” means.
Re-exports§
pub use crate::logic::ExchangePlan;pub use crate::logic::LocalExecutablePolicy;pub use crate::records::Record;pub use crate::records::RecordHash;pub use crate::records::RecordKind;
Modules§
- listing_
symbols - Rateless-IBLT listing symbols for first-round ILTP reconciliation.
Structs§
- Active
Round - Advertisement
Field - Advertisement
Listing - One complete listing: the frozen local listing at its sender and the
complete peer listing at its receiver, with the canonical byte size
Bof the listing rendered as an::offersitem: its label line, every entry’s lines, and the terminating LF. - Advertisement
Record - One immutable listing entry with its canonical listing bytes, measured once when the entry is built.
- Channel
Binding - Binding supplied by the owner of a completed encrypted channel. This value is public transcript data, not an independent authority credential.
- Connected
Carrier - One connected byte carrier above exactly one immutable logical session.
- Connected
Config - Consuming inputs for one connected ILTP stream. Role assigns the operand slot.
- Direct
Config - Same-runtime composition owns two slot-ordered modules and one operation limit.
- Direct
Pair - Fixed
Point Boundary - Fixed
Point Id - Fixed
Point State - Fixed
Point Wake Boundary - Found
Record - Interlace
Id - Interlace
Machine - The sole semantic owner of either a same-runtime pair or one connected carrier.
- Interlace
Resource Limits - Interlace
Round Id - Machine
Error - Nonce
Seed - Zeroizing owner of one connected carrier’s 32-byte nonce seed. Each clone owns and erases an independent copy.
- Operand
Cache - Peer operands received over connected sessions, most recently used first,
at most
capacityof them. Clones share one cache: a Lace hands its cache to every connected operation it runs. Entries are never persisted, admitted, observed, or exposed to policy. - Peer
Output Ref - Protocol
Phase Token - Opaque identity for one stable machine phase and its owning interlace.
- Ready
Effects Ref - Request
Listing - Session
Authority - Session
Machine - One logical session on a connected carrier. The preface nonce pair stays with the session: proof validation reads it during establishment and listing reconciliation derives its session key from it.
- Session
Operand - One logical session’s prepared local operand and optional expected peer By.
- Store
Call - Store
Position - Store
Read Options - Store
Record Id - Store
Record Link Constraint - Store
Record Query - Store
Request
Enums§
- Carrier
Role - Carrier
State - Close
Reason - Connected
Operand - Where a connected carrier’s local operand comes from.
- Core
Error - A failure reported by the machine API without a terminal machine transition.
- Endpoint
Effect Ref - Endpoint
Message - Endpoint
Poll - Endpoint
State - Error
Category - The Lace-100 error category shared by machine, core, and public errors.
- Establishment
Phase - Interlace
Observation - Interlace
Side - Listing
Change - What a complete listing added and withdrew since the previous complete listing of its logical session.
- Load
Record Outcome - Exact-load outcomes are positional against the request retained by StoreCall.
- Logic
Error - Machine
Error Source - Machine
Poll - Machine
Protocol Phase - Peer
Input - One decoded peer input a connected host hands to the carrier.
- Peer
Input Disposition - Whether a decoded peer item can be handed to the carrier immediately.
- Peer
Proof Assurance - Preface
Cause - Record
Destination - Where a record that
RecordIngress::check_startaccepts goes. - Record
Ingress - How a connected host receives the next peer record, by the carrier’s current state. Checked once at the record’s start, when its canonical length is known and before any byte reaches memory, staging or the store.
- Round
Phase - Session
State - One owning connected-session semantic state.
- Store
Error - Store
Field Constraint - StoreOp
- Store
Position Advance - Result of applying a StorePosition notification to an exact fixed point.
- Store
Record Outcome - Store outcomes are positional and carry only newly learned disposition/id.
- Store
Result
Functions§
- record_
matches_ store_ query - Whether
recordsatisfies every constraint ofquery.
Type Aliases§
- Listing
Entries - Hash-ordered listing entries. Entries are shared between the listings and requests that contain them.