public:99_annexes:annex-b-terms-and-definitions:d:deterministic_execution

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
public:99_annexes:annex-b-terms-and-definitions:d:deterministic_execution [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:d:deterministic_execution [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Deterministic Execution ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Deterministic Execution is execution in which the same controlled inputs, initial conditions, rules, and processing sequence produce the same defined result or an equivalent result within specified tolerances.
 +
 +The controlled inputs may include source revisions, dependencies, configuration, tool versions, environment characteristics, credentials, provider capabilities, and execution parameters.
 +
 +Deterministic Execution reduces unintended variation by eliminating or controlling implicit defaults, mutable references, interactive choices, timing-dependent behavior, and unrecorded environmental influences.
 +
 +Within Crucible, [[public:99_annexes:annex-b-terms-and-definitions:v:version_pinning|Version Pinning]], a [[public:99_annexes:annex-b-terms-and-definitions:p:pull_lock|Pull Lock]], declarative inputs, structured logging, and non-interactive operation support Deterministic Execution.
 +
 +===== Definition =====
 +
 +//execution in which the same controlled inputs, initial conditions, rules, and processing sequence produce the same defined result or an equivalent result within specified tolerances//
 +
 +===== Source =====
 +
 +Generalized from software engineering, reproducible-build, workflow automation, systems engineering, and computational-process usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +Deterministic Execution does not require every generated identifier, timestamp, network address, or provider-assigned value to remain identical. The applicable criteria determine which outputs must be identical and which may be equivalent.
 +
 +Deterministic Execution supports [[public:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], but Reproducibility may also require preservation of inputs, tools, environments, and evidence over time.
 +
 +===== Example =====
 +
 +A Crucible Image Build uses the same pinned repositories, installation medium, package snapshot, tool versions, configuration, and execution rules to produce equivalent hardened Machine Images across repeated pipeline executions.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>