Skip to content

v0.7.4 — trusted verification profiles

Latest

Choose a tag to compare

@xenups xenups released this 14 Nov 23:50
· 5 commits to main since this release
13924c1

Asha 0.7.4 — trusted verification profiles

Fixes the policy-model gap where a project that deliberately gates on neither
ruff nor mypy was permanently BLOCKED: the S3 matrix is repository-agnostic,
so a missing executable became a skipped required check, and a skip is never
a pass.

A verification profile now states the authoritative checks per service, in
an operator-signed, repository-bound, digest-bound file:

{
  "schema": 1,
  "id": "detailist",
  "repository": {"remotes": ["github.com/void-detailist/detailist"],
                 "ci_workflows": [".github/workflows/ci_compiler.yml"]},
  "services": {
    "compiler": {
      "root": "compiler", "timeout_s": 1200,
      "checks": {"pytest": ["-m", "pytest", "tests", "-q"]},
      "not_configured": {"ruff": "<provenance>", "mypy": "<provenance>"}
    }
  },
  "provenance": {"declared_by": "operator"}
}

Selected with ASHA_VERIFICATION_PROFILE=/path/to/profile.json — never from a
task-spec field, so a worker cannot widen or narrow its own matrix. Loading
fails closed on an invalid schema, an origin the profile does not name, or an
undeclared service; the file is hashed before the first check and re-read
before sealing, so a candidate that edits it cannot change the run it is in.

NOT_CONFIGURED is a distinct verdict: reported, excluded from the required
set, never counted as a pass, and never inferred from a missing executable. An
inventory of nothing but NOT_CONFIGURED entries is BLOCKED — nothing was
verified. Without a profile, behaviour is byte-for-byte the old matrix
(ruff + pytest + mypy, skip → BLOCKED).

Shipping authority is unchanged: worker evidence still seals
authorized_to_ship: false; a profile changes which checks are required,
never who authorizes shipping.

Included

  • asha/verification_profile.py — schema, trust rules, digest, statement
  • check_runner — profile-planned per-service commands, explicit
    NOT_CONFIGURED entries, one resolution point for DAG, single-worker/MCP and
    tip-verification paths
  • validation — not_configured excluded from the required set; all-unverified
    inventories stay BLOCKED
  • worker_execution — snapshot before checks, verify_unchanged before the
    diff, verification_profile (id, digest, source, remotes, CI sources) in the
    sealed evidence
  • docs/verification-profiles.md — schema, verdicts, fail-closed rules
  • 22 regression tests, including "worker spec cannot weaken the matrix",
    "profile cannot be replaced after snapshot" and DAG/single-worker parity

Verification

  • CI verify (3.10/3.11/3.12: ruff + mypy + pytest) — pass
  • CI fail-closed governance gate — pass
  • Local full suite: 34 failed / 1490 passed / 3 skipped — the v0.7.3 baseline's
    exact pre-existing failure set (no new failures; +22 new tests)
  • Wheel asha-0.7.4-py3-none-any.whl
    sha256 6aba37221ff29608c6a6a67a7720b3aa049f951be483a3876992c58e145e872e
    (359634 bytes, 84 members, RECORD verified 83/83, contents = exactly the four
    changed modules + the new one vs 0.7.3)

Full changelog: v0.7.3...v0.7.4