Release record

RJV-DD-2026-06-19 r1 — the Determinism Doctrine is published

The RJV Determinism Doctrine (RJV-DD-2026-06-19 r1) is now published. This document defines the engineering principles that govern every system RJV builds an...

Published
21 October 2026
Status
Working document
Author
RJV Technologies Ltd

The RJV Determinism Doctrine (RJV-DD-2026-06-19 r1) is now published. This document defines the engineering principles that govern every system RJV builds and operates. It is the single source of truth for what deterministic means in the context of the RJV Platform.

What the doctrine says

The doctrine establishes five operating principles that apply to every system component, every service, and every product:

  • Owned runtime — The customer controls the executing system. No third-party runtime dependencies. No data leaving the estate unless explicitly sent.
  • Visible controls — Each control is enumerated, configurable, auditable. No hidden logic. No black-box decisions.
  • Evidence over assertion — Every claim resolves to a verifiable record. Claims that cannot be evidenced are removed.
  • Zero is not null — Zero is asserted only where it has been measured. The absence of evidence is not evidence of absence.
  • Build and transfer — You own your deployed instance, its configuration, data and outputs; deployment and maintenance are paid services. The deliverable is a codebase, a test suite, a runbook, and a recovery procedure.

Why it matters

Without a written doctrine, engineering decisions are made ad hoc. Each team member applies their own judgement. Over time, the platform accumulates inconsistencies: some components have audit trails, others do not. Some systems are deterministic, others are probabilistic without disclosure. The doctrine eliminates this ambiguity by establishing a single standard that every commit, every deployment, and every operational decision must satisfy.

How it is enforced

The doctrine is enforced through the Determinism Validation Gate, an automated checker that runs hourly. The gate verifies four things: audit chain integrity (the SHA-256 hash chain is unbroken), evidence coverage (every published claim has a linked record), determinism compliance (AI responses are cached by input hash and replayable). ownership verification (no third-party runtime dependencies in production code). If a change violates the doctrine, the gate fails and the deployment is blocked.

Read the full doctrine