Skip to content

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 13 Sep 12:39
· 71 commits to main since this release

Canonical output changes for some inputs (v0.2 integral-float thresholds), hence a
minor bump, not a patch. The reference canonicalizer now implements the §3.6 grammar's
C6 rule for v0.2 and ships with the grammar, the 92-vector edge suite and the
implementer's guide.

Fixed

  • examples/template.yaml no longer reads as a PRML manifest. It is the
    workflow engine schema and always was, but it sat unlabelled among the PRML
    examples and the header told readers to run falsify lock on it — which exits 2
    with "missing required field: version / claim_id / created_at". The header now
    names the right tool and the right flow (falsify-engine init <name>, which takes
    a claim NAME, not a file path), and points PRML users at falsify init or
    examples/first-manifest/accuracy.prml.yaml.
  • README.md called falsify.py the Python reference implementation. It is not;
    falsify_prml.py is. falsify.py is the workflow engine, a different tool with a
    different schema, installed as falsify-engine. Two places corrected.

Added

  • examples/README.md — routes a reader to the right tool in one table. Every
    command in it was executed before the file was committed.
  • README.md reference-implementation section now states which implementations are
    distributed (Python on PyPI, JavaScript on npm) and which exist in-repo only
    (Go, Rust), with each one's command set. Go and Rust implement the verification core
    and deliberately omit authoring commands; there is no Go module and no crates.io
    crate, and none is planned for the 0.x line. Previously a reader had to guess.
  • pyproject.toml description now says the package also ships falsify-engine.
  • §3.6 Formal Grammar (spec/grammar/): an ABNF for the canonical byte
    sequence plus constraints C1–C7, normative. Verified in both directions by
    spec/grammar/check_grammar.py, an emitter and recogniser written from the
    grammar alone (no PyYAML): 21/21 conformance vectors reproduced byte-for-byte,
    16 malformed canonical texts rejected. tests/test_grammar.py runs the same
    checks in CI. No canonical byte or digest changes.
  • spec/grammar/candidate-vectors-2026-09-13.json: 83 inputs at the edges of
    the plain-scalar predicate and the float rule, with expected bytes and hash
    and each reference implementation's agreement on 2026-09-13 — kept as the
    dated pre-correction snapshot; 82 of the 83 were promoted to the edge suite the
    same day (see below).

Changed

  • §3.5 no longer calls the reference canonicalizer "normative for this
    rendering"; constraint C4 of the grammar is normative and the canonicalizer
    conforms to it. Recorded as a dated erratum in the spec.
  • multi-lang-conformance.yml summary notice said "14 reject-vectors"; the
    suite has 20 (16 for the JSON-only implementations) since 0.3.13.

Fixed (cross-language, same day as the grammar)

  • JavaScript, Go and Rust reference implementations corrected to the §3.6
    grammar.
    The 83-input battery run through all four implementations gave 62
    agreements and 21 divergences — none covered by a conformance vector, so the
    daily CI had stayed green. The three hand-rolled plain-scalar predicates
    (ported from one another) over-quoted ?x :x y n 1e5 0o17 and
    under-quoted - << = 1_000 1:30 0b101; Rust rendered a threshold
    of 1e-05 as 0.00001. All three predicates are now transcriptions of README
    §C5 (P1–P6 plus the YAML 1.1 resolver patterns verbatim); Rust's float
    rendering implements §C4 from the exponent rather than from ryu's choice of
    notation (Rust gains the regex crate). The registry's canonical.js was
    corrected in step; all six publicly listed registry records re-derive their
    stored hash under the corrected canonicalizer. Result: Python 83/83, Go 83/83,
    Rust 83/83, JavaScript 82/83 — 83/83 in all four after the v0.2 decision below.
  • Edge suite spec/test-vectors/edge/edge-vectors.json (92 vectors,
    EV-001..EV-092) added and wired into multi-lang-conformance.yml for all four
    implementations. Separate from the 21 normative vectors of Appendix B by
    design (spec/test-vectors/edge/README.md). FACTS.env gains
    VECTORS_EDGE=92.

Changed (specification, v0.2)

  • v0.2 threshold canonicalizes by value (RFC "Post-freeze clarification
    (2026-09-13)"): integral and below 2^53 → integer digits, otherwise the §3.6 C4
    float. 1300.0 and 1300 are one manifest. The frozen RFC had never stated a
    rule; the ROADMAP proposed the opposite of what the vectors did; JavaScript and
    the registry could not observe the type distinction at all. Python, Go and Rust
    now render 1300.0 as 1300; no published digest changes (no vector spelled an
    integral threshold as a float). falsify_prml.canonicalize applies the rule at
    the root mapping only, like the v0.1 float rule.
  • Edge suite grows to 92 (EV-083..EV-092 pin the boundaries: -0.0→0,
    2^53-1, 2^53→9007199254740992.0, 1e16/10000000000000000→1.0e+16,
    1300.5, 1e-05). FACTS.env VECTORS_EDGE=92. All four implementations and
    the registry pass 92/92.