Skip to content

Skill Provenance 5.1.0

Choose a tag to compare

View all tags
@snapsynapse snapsynapse released this 16 Jul 17:40
v5.1.0
c037e15

validated_against: release-bound attestation records

MANIFEST.yaml now takes an optional validated_against block. Each entry binds a validation event — harness, model, date, result, method — to the exact bundle_version it validated:

validated_against:
  - bundle_version: 5.1.0
    harness: Anthropic Claude Code
    model: claude-fable-5
    date: 2026-07-16
    result: pass

This is a different claim from compatibility.tested_on (design-time compatibility, not bound to a release) and a different concern from hash (integrity). An attestation for 5.0.0 says nothing about 5.1.0, and the tooling treats it that way.

validate.sh reports attestation after the hash results — entries matching the current bundle version, or a stale flag when none match — and never changes its exit code over attestation state. That is the design rule this release encodes: integrity gates, attestation informs. The same pinned bytes can behave differently as harnesses and models move, so a stale attestation means re-validate, not reject.

Also in this release

  • 2 new core evals covering attestation reporting and stale-attestation semantics (35 core / 52 total)
  • Regression tests asserting attestation state (matching, stale, absent) never changes validate.sh exit codes
  • SKILL.md manifest schema + rules coverage; README section "Attestation: validated_against"

Full details in CHANGELOG.md.

Assets 2
Loading