Skip to main content

Crate dive_runtime

Crate dive_runtime 

Source
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:

  • CheckOptions and the CheckResult it produces, with its Verdict, 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::CheckOptions and crate::CheckResult. The stores themselves belong to the engines.

Structs§

CheckOptions
How to run a check.
CheckResult
The result of a check.
Collision
The fingerprint-collision figures TLC prints on success, as their text.
Counterexample
A counterexample: a finite behavior prefix.
DiagnosticWitness
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.
PartialState
The observed incomplete candidate and the action that actually emitted it.
PredecessorUsage
Evidence for the separately budgeted transient predecessor log.
Stats
State-space statistics.
TlcClass
How TLC classifies a result: its observable primary code, EC name, and physical process exit status. A source-qualified Init replay may retain GENERAL as primary while its diagnostic context supplies exit 75.
TraceState
One state of a counterexample.
Workers
Worker threads requested and used.

Enums§

ErrorSite
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 = v per variable in TLC’s variable order, or x = v for 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, tlaplus 94d0c50).