Repository navigation
v0.5.0
v0.5.0: the skill's scripts at TOPAK 6a26310
MINOR: the method pin moves, and no checker or runtime pin moves.
tools/pins.py moved v0.4.0 lists one pin, method writing-tla-specs-and- proofs scripts, TOPAK 5ade81e -> 6a26310 (pull request #32). ADR-0014
item 2's table has no row for a method move; PATCH requires that no pin
moved, so this takes MINOR. Every other pin is v0.4.0's:
| Pin | Value |
|---|---|
| cvc5 | 1.4.0 (b432cd7), static build: zip sha256 61d13483…ec6d, binary sha256 d4c53436…2e5b, kept in release cvc5-1.4.0 |
| ethos | 0.2.4 at 8dc85c4: zip sha256 1582fd32…d8bc, binary sha256 97e95d36…6538, kept in release cvc5-1.4.0 |
| CPC signature | cvc5 1.4.0's proofs/eo/cpc/, 51 files, tree 633f74115700ad32, from cvc5's source kept in release cvc5-1.4.0 |
| TLC, SANY, PlusCal | tla2tools.jar v1.7.4, sha256 936a2620…0e88 |
| TLAPS | tlapm 1.6.0-pre at ff40755: binary sha256 6182df63…5bb2, kept in release tlapm-ff40755 |
| Java | Temurin JRE 25.0.5+8, in the base |
| Base | eclipse-temurin:25-jre-noble, digest 5b5a79b8…f2e5 |
| apt | Ubuntu's snapshot of 2026-11-15T00:00:00Z |
| The skill's scripts | TOPAK 6a26310 |
What is new:
- tla_common.py, which the server imports, says in one line why a
results file could not be written, in place of a Python traceback
(TOPAK's pull request #95). For a refusal by ownership it names the
run's uid and the directory owner's, and suggests
docker run --user "$(id -u):$(id -g)" or --results-dir. This reaches
tlc_rows and proof_results, and the scripts run directly. - A run that reproduces an existing results file byte for byte needs
no write, so it passes in a results directory it may not write to. - spec/PinLifecycle-results-2026.11.19.txt (51 rows) and
spec/ProveRequests-results-2026.11.19.txt (78 rows), generated with
the new scripts, are carried by a release from this one on. - The README gains entries for other MCP clients and for trying the
tools by hand with the MCP Inspector (pull requests #29 to #31).
CI on main at 9508c3c (run 44436850478) passed: records, the image
built from the kept copies with its self-test, the MCP client and
prove tool tests, and both spec row lists reproduced. The commit built
twice from nothing, on two runners, gave one digest,
sha256:5ee10d3e9b761f91020be2c6b11a16a459966a9a4cf5a105c964ae31a49ab59f.
No checker pin moved, so the evidence workflow's TOPAK jobs did not run.
A project that moves from v0.4.0 changes the digest its CI names and
regenerates nothing: TLC, the prover, cvc5, ethos and the runtime are
the same bytes, so no verdict changes. A results file names its
generator by digest, so files written by v0.5.0's scripts differ from
v0.4.0's on their Runner line.
Cite this image by its digest
ghcr.io/scottcochran/tla-kit@sha256:5ee10d3e9b761f91020be2c6b11a16a459966a9a4cf5a105c964ae31a49ab59f
The tag v0.5.0 names the same image, for reading; a results file and a project's CI name the digest (ADR-0010
item 4). Check that it was built here, from this tag, by this workflow:
gh attestation verify oci://ghcr.io/scottcochran/tla-kit@sha256:5ee10d3e9b761f91020be2c6b11a16a459966a9a4cf5a105c964ae31a49ab59f --repo scottcochran/tla-kit
What it holds
The inventory, PINS.json, as committed at the tag, and tla-kit-info --json from the image, are attached. The
prover tarball, with the licence notices and the source of its copyleft parts, is kept in the release
tlapm-ff40755 (ADR-0005 item 2). cvc5's and ethos's zips, with the licence notices,
cvc5's and ethos's source and the source of the copyleft parts linked into them, are kept in the release
cvc5-1.4.0 (ADR-0017 item 1).
checker /opt/tla/tla2tools.jar sha256 936a262061c914694dfd669a543be24573c45d5aa0ff20a8b96b23d01e050e88
tlc TLC2 Version 2.19 of 08 August 2024 (rev: 5a47802)
prover /opt/tlaps/bin/tlapm sha256 6182df63c4513b09c31c8de12c37f8045ace9cab2517c017a2fa75f466685bb2
tlapm ff40755
backend Isabelle Isabelle2025
backend zenon zenon version 0.8.4 [a268] 2017-11-14
backend Z3 Z3 version 4.8.9 - 64 bit
backend SMT Z3 version 4.8.9 - 64 bit
backend LS4 unknown
cvc5 /opt/cvc5/bin/cvc5 sha256 d4c534360e602f07adcbb2aafbe833e73ce1e7c6f2572cb7eee03de73d6e2e5b | cvc5 1.4.0 [git b432cd7 on branch HEAD]
ethos /opt/ethos/bin/ethos sha256 97e95d36dcb596e6439d935af68e9005a508620f667af546d92d6d3700f26538 | 0.2.4
cpc /opt/cvc5/cpc 51 files, tree 633f74115700ad32
java openjdk version "25.0.5" 2026-10-20 LTS
skill https://github.com/scottcochran/TOPAK at 6a263109521306d09b93d2ecc33e17bc338aed7e
image https://github.com/scottcochran/tla-kit at 9508c3ca69eff66825dc29e5428979dd07897ecf committed 2026-11-19T01:25:52Z
The SBOM is attached, and attested with the digest. The vulnerability scan at release time, for packages rated
HIGH or CRITICAL:
Report Summary
┌──────────────────────────────────────────────────────────────────────────────────┬────────┬─────────────────┬─────────┐
│ Target │ Type │ Vulnerabilities │ Secrets │
├──────────────────────────────────────────────────────────────────────────────────┼────────┼─────────────────┼─────────┤
│ ghcr.io/scottcochran/tla-kit@sha256:5ee10d3e9b761f91020be2c6b11a16a459966a9a4cf- │ ubuntu │ 0 │ - │
│ 5a105c964ae31a49ab59f (ubuntu 24.04) │ │ │ │
└──────────────────────────────────────────────────────────────────────────────────┴────────┴─────────────────┴─────────┘
Legend:
- '-': Not scanned
- '0': Clean (no security findings detected)
Only the latest release is supported. This release stays available, and is never deleted (ADR-0014 items 5 and 7).