How Determinism Works | AiVIS Cite Ledger
Technical explainer for AiVIS Cite Ledger determinism gate, evidence provenance, and repeatable citation observability validation.
TLDR
The Determinism route explains why AiVIS Cite Ledger separates evidence extraction from deterministic scoring, what reproducibility requires, and what the system cannot guarantee about external AI-engine behavior.
Why deterministic validation exists
AI systems are inherently non-deterministic: the same query can produce different answers depending on model version, temperature, context state, and sampling strategy. An audit tool that relies on live AI inference for both data collection and scoring would produce different results for the same page on consecutive runs, even when the page has not changed.
AiVIS separates extraction (which may use AI models for query generation and content analysis) from validation and scoring (which apply deterministic rules over recorded evidence). The score is a function of recorded evidence, not of live model inference.
What determinism does and does not guarantee
Deterministic scoring ensures that the same recorded evidence produces the same score under the same versioned rules. It does not ensure that evidence collection is free from upstream variability: crawls, search results, source pages, AI responses, and third-party systems can change between runs. The extraction layer captures these variations as part of the evidence record.
A high Extraction Risk Index score does not guarantee that ChatGPT, Perplexity, Claude, or Gemini will cite a page for any specific query. Citation decisions involve model-level inference that extends beyond what any page-level audit can capture.
Comparability across audits
Results cannot be meaningfully compared across incompatible audit versions, query sets, scoring versions, or evidence schemas. The score snapshot pins each audit to a specific evidence set so that comparisons are valid only when the underlying configuration is compatible.