Change Control

Updated 2026-01-19

Public change log for registry and doctrine updates that affect deterministic outcomes.

Authority is versioned. Prior bundles remain valid. Replay requires the same registry hash recorded in each bundle.

What is tracked

Registry rule changes and rule schema updates
Decision policy updates that alter GO / NO-GO / REFUSE
Artifact classification changes that affect evidence tiers

What is not tracked

UI copy and layout changes
Offline kit packaging and distribution updates
Documentation edits that do not affect outcomes

Current public versions

Registry: v2.0.0 (recorded in each bundle MANIFEST.json)
Decision doctrine: Standard of Proof v2.0

Recent changes

2026-01-19 — Registry v2.0.0

Decision model is provability-only: boundaries drive NO-GO, missing required artifacts drive REFUSE.
Context does not override boundaries; provability remains absolute.
Non-liftable boundaries are explicitly locked (ALTER, dynamic CALL, assembler, CICS NO_RESP, IMS DL/I).
Fail-closed enforcement added in CI for authority consistency.

Authority impact: GO is issued only when Tier-2 and Not-Provable counts are zero and required artifacts are complete.

How to verify

Open MANIFEST.json and DECISION.json inside a bundle.
Confirm registry_version and rules_manifest_hash (and policy hash if published).
Replay only with a kit that matches the bundle registry hash.

Detailed diffs are available under NDA.