TallyLock 0.1.0a4

TallyLock 0.1.0a4 is an alpha for Linux with Python 3.11 through 3.14, published with trusted publishing and signed provenance.

pipx install tallylock==0.1.0a4    # or: uv tool install tallylock==0.1.0a4

A new Receipts Board

tallylock board now builds a page you can read on a phone. See it live: https://triplepasslabs.com/tallylock/board/

• One ladder per benchmark. Entries are ranked only against others with the same dataset, harness, prompt template and decoding settings, and that shared setup is shown once.
• Each entry is a pill with its score, its 95% range and its best single run on a shared scale, so you can see the gaps and the overlaps.
• Tap an entry and it opens to every run (failed runs marked), the record (plan locked, runs, instant timestamps, the Bitcoin blocks), how it stands against each other entry, and the claim line and recheck command with copy buttons.
• Each entry has its own link, for example #quentin. Esc closes it.
• The page is still one static file with no remote assets. A short inline script adds the animation, links and copy buttons. Without it, entries still open and close.

Fixes

• Board ties are now reported pair by pair. A tie is not transitive: A can tie B and B tie C while A beats C. The old board could group all three as tied, which contradicted tallylock compare.
• tallylock upgrade on a receipt that is pre-registered but not sealed yet no longer fails with a generic error. Plain upgrade means the manifest when there is no result yet, and --target result says plainly that the result is not sealed.

Small changes

• Ledger verification reports the Bitcoin block heights each head proof names, in a new heights field on each anchors item.
• entries.json rows gain attempts, setup, head, argv, instant_timestamps and bitcoin. Existing fields are unchanged.

TallyLock 0.1.0a3

Install: pipx install tallylock or uv tool install tallylock. Linux, Python 3.11 to 3.14.

What is new since 0.1.0a2

• Python 3.14 is supported.
• run now exits with your command's own exit code (128 plus the signal for a killed command), so a failing eval still fails your CI. With --repeat, every attempt runs and the first failure's code is returned.
• check --online and score --online check the Bitcoin timestamps of a plan's ledger against two public block header services, without running a node.
• Windows: commands that write files now say plainly that they need Linux and suggest WSL, and tallylock doctor reports it.
• The Receipts Board shows the "other plans" note only when it applies.

Product page: https://triplepasslabs.com/tallylock/
PyPI: https://pypi.org/project/tallylock/0.1.0a3/ (trusted publishing with signed provenance).

TallyLock 0.1.0a2

First full Phase 1 alpha. Install: pipx install tallylock or uv tool install tallylock. Linux, Python 3.11 to 3.13.

What is new since 0.1.0a1

• verify --online checks a receipt's Bitcoin timestamp without a node: the block and 100 later blocks are checked against Bitcoin's real difficulty, and two public services must agree.
• run now adds instant RFC 3161 timestamps from two services by default, checked offline against bundled roots (--no-tsa turns them off, --tsa picks services). refresh finishes the Bitcoin proof later.
• run --setup and compare say whether two results used the same dataset, harness, prompt and decoding settings, and whether the gap is just noise.
• export, registry and board publish a static Receipts Board where every entry is rechecked.
• adapters import reads Inspect AI logs and proofbundle files. export --format intoto produces statements cosign can sign.
• capabilities --json and agent-guide let AI assistants drive the CLI.

Limits: an online check trusts two public services plus local proof-of-work checks, not full Bitcoin consensus, and the output says so. Exported bundles include your runs' full output.

PyPI: https://pypi.org/project/tallylock/0.1.0a2/ (trusted publishing with signed provenance).