Skip to content

v0.2.0 — evidence-schema check #10

Choose a tag to compare

View all tags
@anrasi anrasi released this 02 Jul 01:58
v0.2.0
784e9fb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Check #10: evidence-schema

Validates evidence.v1 records (the canonical SliceOps evidence record format, ratified in spec DR-2026-07-02) against the canonical JSON Schema.

  • Discovery: files ending .evidence.json / .evidence.v1.json under --root; filenames containing .example. are golden fixtures and are never picked up. Zero records → SKIPPED (green).
  • Full JSON Schema draft 2020-12 validation when jsonschema is importable; otherwise a documented stdlib subset (required fields, schemaVersion const, enums, ID/hash patterns, top-level additionalProperties, and the P6 slice-merge completeness rule) — same optional-dependency policy as PyYAML. Enums/patterns are read from the vendored schema at run time.
  • The vendored schema (templates/consistency-validators/schemas/evidence.v1.schema.json) is byte-compared against the spec canonical on every CI run; drift fails the build.
  • 20 new tests (54 total), green with and without the optional deps.

The toolkit now ships 10 checks.

Assets 2
Loading