v1.6.0 — From claimed to checkable

Every headline feature in this release was designed from external feedback on the 1.5.0 launch — two of the three are credited to community members by name.

New

akf replay — falsifiable evidence (credit: Mike Czerwinski)

Stamps can carry a probe recipe: the command that produced the evidence, its expected result, and an input fingerprint pinned at issuance.

$ akf stamp app.py --evidence "42/42 tests passed" --replay "pytest -q"
$ akf replay app.py          # inspect: recipe + input drift
$ akf replay app.py --run    # execute the probe
CONFIRMED

Verdicts: CONFIRMED · CONFIRMED_DRIFTED (probe succeeded against inputs that diverged since issuance — provably reproducible, possibly reproducibly wrong) · REFUTED · UNREPLAYABLE. A signature proves who said it; a replay proves it could have been true.

Source pinning (credit: Mike Czerwinski)

Claims citing a local file record its content hash; akf check flips STALE reason=source_changed when the cited source moves — the file is untouched, the ground it cites isn't.

Receipt-strength weighting (credit: Dipankar Sarkar)

A green check from a trivial suite no longer outranks a real one: partial pass fractions (40/42) and coverage under 30% drop to the weak trust floor; replayable evidence keeps the strong floor. Bare receipts unchanged.

Dependency-aware staleness (credit: Dipankar Sarkar) — first release

Stamps on Python files record first-degree local import hashes; check flips STALE reason=dependency_changed when a dependency moves.

Also

• MCP server: 11 tools (replay_file added — execution opt-in and labeled)
• All skill listings (ClawHub, Hermes tap, Claude Code plugin) teach the replay verb

Install

pip install akf==1.6.0
npm install akf-format@1.6.0