Determinism and Guarantees

Source: docs/03-determinism-and-guarantees.md

Determinism and Guarantees

Commitment Radar is deterministic by construction: the same inputs produce the same boundary maps every time.

Deterministic inputs

  • artifact_text (raw bytes, no normalization)
  • artifact_type
  • lens_id + lens_version
  • ruleset_id + ruleset_version

Deterministic outputs

  • Boundary map fields and template selection
  • Canonical ordering within boundary maps
  • Producer hashing (if producer metadata is present)

Non-deterministic by design

  • analysis_run_id
  • started_at / completed_at
  • Database record IDs

What determinism guarantees

  • Repeatable boundary maps for identical inputs
  • Stable replays across time for the same signature hash
  • No dependence on vendor/model metadata for interpretation

What determinism does not guarantee

  • Stability across ruleset or lens upgrades
  • Matching timestamps or run IDs across requests

How determinism is enforced

  • Fixed template registry (no probabilistic logic)
  • Canonicalization of list ordering
  • Explicit schema validation for inputs