Expand description
dive-runtime: the run contract every checking engine shares.
The execution core and temporal analysis (dive-liveness) agree on these
pieces, so neither needs the other’s search runtime:
CheckOptionsand theCheckResultit produces, with itsVerdict, statistics, counterexample and storage evidence;- TLC’s error classes (
classify) and human rendering; - time and memory budgets and evaluation control (
budget); - behavior-graph capture types, evidence and admission (
capture); - native checkpoint framing, requests and Core’s archive identity
(
checkpoint); - the run host’s configuration and counters (
run) and pure model admission analysis (admission).
The searches themselves belong to the execution core.
§Example
use dive_runtime::{CheckOptions, Verdict};
let opts = CheckOptions::tlc(0, 7);
assert_eq!(opts.seed, 7);
assert!(Verdict::Success.is_verdict());Re-exports§
pub use usage::FrontierUsage;pub use usage::SeenFailure;pub use usage::SeenOptions;pub use usage::SeenPhase;pub use usage::SeenReplay;pub use usage::SeenUsage;
Modules§
- admission
- Pure admission analysis of a bound model, shared by graph capture and Core. Nothing here evaluates an expression.
- budget
- Run budgets: a wall-clock limit and a whole-process resident-memory ceiling, the runaway guards that replace fixed counts.
- capture
- Bounded behavior-graph capture: the graph, evidence and admission types every producer shares (ADR 0155).
- checkpoint
- Native checkpoint framing, requests, receipts and the owned Core backend’s identity.
- classify
- TLC’s error classes for another engine’s error endings.
- run
- The run host’s
TLCGet("config")and live counters around the search, shared by every engine. - usage
- Storage usage evidence and the disk seen-state policy carried by
crate::CheckOptionsandcrate::CheckResult. The stores themselves belong to the engines.
Structs§
- Check
Options - How to run a check.
- Check
Result - The result of a check.
- Collision
- The fingerprint-collision figures TLC prints on success, as their text.
- Counterexample
- A counterexample: a finite behavior prefix.
- Diagnostic
Witness - The original initial-state diagnostic context, not a formal counterexample. Its values and named underlying error still require independent replay; neither this typed transport nor a reported wrapper supplies proof.
- Partial
State - The observed incomplete candidate and the action that actually emitted it.
- Predecessor
Usage - Evidence for the separately budgeted transient predecessor log.
- Stats
- State-space statistics.
- TlcClass
- How TLC classifies a result: its observable primary code,
ECname, and physical process exit status. A source-qualified Init replay may retain GENERAL as primary while its diagnostic context supplies exit 75. - Trace
State - One state of a counterexample.
- Workers
- Worker threads requested and used.
Enums§
- Error
Site - Where an evaluation error was raised: the phase of TLC’s search it belongs to. TLC’s error class and exit status depend on it.
- Verdict
- The verdict of a check.
Functions§
- format_
trace_ state - A state as TLC prints it in a counterexample (
TLCStateMut.toString):/\ x = vper variable in TLC’s variable order, orx = vfor a single variable. - render_
human - The whole human-readable report.
- tlc_
exit_ status - TLC’s exit status for a deciding message code
(
EC.ExitStatus.errorConstantToExitStatus, tlaplus94d0c50).