Module messages 

Wire messages: typed builders for what an adapter sends, checked parsers for what it receives.

The adapter pushes commits, the driver issues requests, and either side may send an error and close. Everything is validated against the active limits before it is retained; failures are returned, never raised.

Structs

AdapterInfo

Identifies the adapter implementation to the driver.

EvidenceProviderRegistration

Application evidence producer frozen into hello negotiation.

Hello

The adapter’s handshake: sent exactly once, before anything else.

HelloAck

The driver’s reply: session id, negotiated limits, what to push.

LogBudget

The log-channel allowance, sent only when the adapter announced the logs capability. Absent means logs are disabled: an adapter that receives no budget must not emit log messages at all.

LogMessage

Carries one application log record to the driver.

MarkerConfig

Whether the adapter should emit render markers.

ProbeInfo

What a probe says about itself when it attaches.

ProbeInstrumentation

Runtime attachment facts declared in a first-party probe handshake.

ProtocolErrorMessage

Terminal error: the sender closes after emitting it.

RevisionCommit

Announces that a render was committed to the terminal.

SemanticFullMessage

Carries a full tree for one revision.

Enums

DegradedSessionCapability

Closed session-capability vocabulary used for named runtime degradation.

ProbeIdentityKind

How an object’s identity behaves across frames.

ProbeInjectionTier

Strongest injection tier that actually engaged for this probe run.

ProbeSemanticClass

Whether the semantic tree includes authoritative framework geometry.

Constants

PROTOCOL_ID

The wire protocol identifier both sides must agree on.

PROTOCOL_VERSION

The current major version.

Functions

default_capabilities

Capabilities for a tree-publishing adapter with qualified geometry.

parse_adapter_message

Validate one adapter → driver message.

parse_driver_message

Validate one driver → adapter message.