ميزانMIZAN
VTR-1 · errata register · public
Findings are published,
not silently applied.
The specification is frozen, so a correction to it is published as an erratum rather than edited into the document. An erratum records what was found, who found it, and what followed — no change where the text is defensible as written, an entry here where it is unclear, a numbered successor version where a requirement genuinely changes. Errata are published whether or not the finder is named, and whether or not the finding flatters the standard. Send one to [email protected].
Against the specification
ERR-1.0-001RESOLVED IN 1.1
The Status block treated a differently-hashing copy as a different version.
- found
- Version 1.0 was itself published in more than one rendering, so a hash-based version claim was not sustainable as written.
- resolution
- The claim was removed in 1.1. No requirement was added, removed, or altered in meaning, and all 41 identifiers keep their text.
- affects
- § Status. Non-normative.
ERR-1.0-002RESOLVED IN 1.1
Plural "authors" used where the document has one author.
- found
- §11 and Appendix C referred to authors in the plural.
- resolution
- Corrected to the singular in 1.1.
- affects
- §11, Appendix C. Non-normative.
Against the reference implementation
The same discipline applies to MIZAN's own engine and registry. A finding against the implementation is published here even when the specification is fine and the implementation is not.
IMPL-2026-001OPEN
Credentials do not declare a conformance Level, as R-04 requires.
- found
- 2026-08-09, internal audit. R-04 (MUST): "A credential declares exactly one conformance Level." No credential issued to date carries a Level field — not in the proof object, not in the public registry, and the concept is absent from the engine. R-18, which requires a conforming party to publish the declared Level per credential, is unmet for the same reason.
- impact
- No metric, verdict or proof is affected. Every credential remains cryptographically valid and re-verifiable. The gap is a declaration gap: a reader cannot tell from the credential which Level it claims, and must infer it from what the proof contains.
- what follows
- Levels are introduced in a future era. Under §6 that is a new judge with a new image hash; existing credentials are not re-issued and remain verifiable against their own era permanently.
- status
- Open. The reference implementation is therefore not fully conforming to §3 and §7 of the standard it publishes, and says so here rather than waiting until it is.
IMPL-2026-002RESOLVED 2026-08-08
Two credentials declared 252 periods per year where the committed window supports 251.
- found
- 2026-08-08. The Apple and S&P buy-and-hold credentials of 2026-08-04 declared an annualisation basis of 252 against a 7,184-bar window spanning 28.6 calendar years, which the verifier's C1 bound correctly rejects as an over-count.
- impact
- No metric and no verdict changed. Both credentials remain valid proofs of their committed results and remain verifiable forever.
- resolution
- Both were re-minted at 251 and the originals marked superseded, not withdrawn. Both versions are on the registry.
IMPL-2026-003RESOLVED 2026-08-08
The published verifier reported a valid refusal as a failed verification.
- found
- 2026-08-08. The distributed verifier counted the gate verdict as a trust check, so a cryptographically valid credential attesting an honest FAIL printed VERIFICATION FAILED — do not rely on this credential.
- impact
- Display only. No proof, metric or verdict was ever wrong. But every published refusal read as untrustworthy to anyone who checked it, which inverted the meaning of the registry's most important entries.
- resolution
- The verdict is now reported as an outcome, not a trust check. A valid refusal reads INDEPENDENTLY VERIFIED · GATE VERDICT: FAIL. Rebuilt verifier published and archived as verifier-v11-20260808; the era's trust root is now derived from the archived canonical ELF, so any era's verifier is reproducible from published bytes.
Version history. 1.0 — 1 August 2026, frozen, remains available and verifiable.
1.1 — 1 August 2026, current normative version, frozen, published before any citation of 1.0. Two errata against 1.0 resolved; the remainder editorial. No requirement was added, removed, or altered in meaning. R-01 to R-41 are permanent identifiers: a retired requirement keeps its number and is marked retired.
Governance and era law →