Skip to main content

Module compatibility

Module compatibility 

Source
Expand description

Exact compatibility for a separately linked CLI backend executable.

This is separate from the closed presentation/recording BuildInfo schema. Equal ELF build IDs are neither expected nor used: the executables differ, but must contain the same measured core source/API and build cohort. Matching this record is not runtime qualification or publisher attestation.

Structs§

CoreCompatibility
Immutable complete comparison input measured by the core build producer. All dimensions compare exactly; there is no tolerance or missing-field interpretation, and extensions cannot replace the embedded core record.
Probe
Closed identity-only probe response. This is not an execution receipt.

Enums§

ExecutableIdentity
The executable’s compiled selection, independent of any user option or environment value. It does not authorize a private runtime role.

Constants§

API
The statically linked CLI application/adapter API.
HELD_PROBE_ARG
Same identity response while an owned control socket keeps this executable mapped. Only its parent owns the deadline/abandonment; it has no self timer.
MAX_PROBE_BYTES
Both readers and producers enforce the same finite protocol output bound.
PROBE_ARG
This exact single option is handled before ordinary application startup.
PROBE_SCHEMA
Independent framing for the identity-only executable probe.
SCHEMA
Dedicated source/API contract; do not silently accept another version.

Functions§

current
Return only a complete measured identity. Native/export/registry builds without an explicit producer remain usable for builtins, but cannot claim compatibility by substituting BuildInfo, a short revision, or a package name.