Browse documentation

Explanation

The deterministic core

Defined arithmetic and explicit inputs make core decisions repeatable.

The deterministic core executes supported Rust with defined arithmetic and explicit effect boundaries. Reproducing a decision requires the same code, inputs and execution settings.

For an order total, price and quantity are computation inputs. Fetching an exchange rate is an effect. Replay uses the recorded rate under its execution contract; it does not query today’s rate and assume the answer is unchanged.

Arithmetic

The core uses checked integers and exact decimals. Floating-point values and operations are excluded. Code that needs them can run behind an explicit native boundary.

Exact decimals do not choose a financial policy. The application still specifies scale, rounding, range and invalid-input behaviour. Checked arithmetic also needs an explicit response to exhaustion when that is a domain condition.

What repeatability depends on

Function arguments are only part of the input. Code identity, types, effect outcomes, runtime semantics and execution settings can affect a result. External delivery and scheduling have their own contracts.

The checker rejects unsupported code and bounds violations it can establish before execution. Other violations can stop execution with a runtime fault. Determinism does not mean a program cannot fail; see panics and runtime faults.

Tests, replay and proofs

Tests check selected behaviours. Replay reconstructs execution from retained inputs. Formal proofs establish specific properties under stated assumptions.

None of them selects the right business requirement. Deterministic code can repeat an incorrect decision. Review the requirement independently of an agent’s implementation and tests.

Use the profile reference for supported constructs and evidence to interpret recorded test results.

Search concepts, guides and reference.