Skip to content

Releases

v0.6.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 21:28
v0.6.0
a53425b

v0.6.0: tlapm 9a52faf, on Ubuntu 26.04

MINOR, before 1.0 (ADR-0014 item 2): a checker pin moves, the prover,
with the runtime refresh it needs. tools/pins.py moved v0.5.0 lists
four pins:

  • checker tlapm: 1.6.0-pre at ff40755 -> 9a52faf (pull request #34).
  • runtime base: eclipse-temurin:25-jre-noble, digest 5b5a79b8…f2e5 ->
    eclipse-temurin:25-jre-resolute, digest fa681c58…c1d7 (#36).
  • runtime apt: Ubuntu's snapshot of 2026-11-15T00:00:00Z ->
    2026-11-19T00:00:00Z (#36).
  • checker Temurin JRE: listed because the base it is set by moved. Its
    value does not move: 25.0.5+8 in both bases.
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 9a52faf: tarball sha256 d9c06a04…c1f0, binary sha256 faa92f26…2cc0, kept in release tlapm-9a52faf
Java Temurin JRE 25.0.5+8, in the base
Base eclipse-temurin:25-jre-resolute, digest fa681c58…c1d7: Ubuntu 26.04.1, glibc 2.43
apt Ubuntu's snapshot of 2026-11-19T00:00:00Z: Python 3.14.4, perl 5.40.1, git 2.53.0
The skill's scripts TOPAK 6a26310

What is new:

  • The prover is upstream's rebuild of the rolling 1.6.0-pre tag at
    9a52faf. Its 13 commits since ff40755 fix the typing of quotient and
    remainder when arithmetic is off, reject expressions with ambiguous
    precedence, make % non-associative, and rename bChoice to bChoose in
    the printer, Zenon and Isabelle/TLA+.
  • 9a52faf's tlapm needs glibc 2.42, so the base moves from Ubuntu 24.04
    (2.39) to 26.04 (2.43). ADR-0003 names the new base.
  • The Dockerfile extracts the TLAPS tarball and cvc5's source with
    Python's tarfile. Ubuntu 26.04's tar opens files with openat2, which
    Docker Desktop's amd64 emulation does not implement, and a plain
    docker build . on Apple Silicon has to work (ADR-0003 item 3).
  • Every workflow step runs with bash -eo pipefail (#35). Before, a
    step that piped into tee passed when its command failed.

Evidence (ADR-0005 item 4, ADR-0013 item 3):

  • TOPAK's full proof run under 9a52faf proved 13,622 obligations in
    the modules that match their baseline, its committed count (#34,
    run 44602423185). The same count under ff40755 on the new base
    (#36, run 44598664763).
  • TOPAK's 15 pr-tier TLC modules regenerate with no differences on the
    new base (#36).
  • TOPAK's defect run under 9a52faf gives what it gave under ff40755,
    line for line, under tlapm and under the certified run; under TLC,
    every statement is violated, as before. derived/tla-kit-tlapm-
    9a52faf-defects-2026.11.19.md records it.

CI on main at a53425b (run 44613340646) passed: records, the image
built from the kept copies with its self-test, the evidence workflow's
proof and defect runs, and the commit built twice from nothing, on two
runners, gave one digest,
sha256:494881db94ade3dd0695409b4fdde58218c794658f90ce4051e3d9086bdba689.

A project that moves from v0.5.0 changes the digest its CI names, and
regenerates its proof results, since the prover moved. On TOPAK no
outcome changes: the proof counts are the same, and so is the defect
run under tlapm.
-----BEGIN SSH SIGNATURE-----
U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgl3fHFZa6qeeuu8+eDCkaq4yev9
hIkdQ/zaWgNAm0ErcAAAADZ2l0AAAAAAAAAAZzaGE1MTIAAABTAAAAC3NzaC1lZDI1NTE5
AAAAQKBofZ1N20jqQqv6E3SPZnDRDZ1CE2b5nMVuKEI2vM1eqqPM49sigjSjeRtH60usrI
YOBEUOlSsLaJws3A3X3QA=
-----END SSH SIGNATURE-----

Cite this image by its digest

ghcr.io/scottcochran/tla-kit@sha256:494881db94ade3dd0695409b4fdde58218c794658f90ce4051e3d9086bdba689

The tag v0.6.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:494881db94ade3dd0695409b4fdde58218c794658f90ce4051e3d9086bdba689 --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-9a52faf (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 faa92f2606242ce239584e665978f33c7378ba23991c6f318a74525dcb892cc0
tlapm     9a52faf
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 a53425b96ff920cd2437bf88e7ac3cee0c9a18a7 committed 2026-11-19T20:54:05Z

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:494881db94ade3dd0695409b4fdde58218c794658f9- │  ubuntu  │        0        │    -    │
│ 0ce4051e3d9086bdba689 (ubuntu 26.04)                                             │          │                 │         │
├──────────────────────────────────────────────────────────────────────────────────┼──────────┼─────────────────┼─────────┤
│ usr/bin/pebble                                                                   │ gobinary │        1        │    -    │
└──────────────────────────────────────────────────────────────────────────────────┴──────────┴─────────────────┴─────────┘
Legend:
- '-': Not scanned
- '0': Clean (no security findings detected)


For OSS Maintainers: VEX Notice
--------------------------------
If you're an OSS maintainer and Trivy has detected vulnerabilities in your project that you believe are not actually exploitable, consider issuing a VEX (Vulnerability Exploitability eXchange) statement.
VEX allows you to communicate the actual status of vulnerabilities in your project, improving security transparency and reducing false positives for your users.
Learn more and start using VEX: https://trivy.dev/docs/v0.70/guide/supply-chain/vex/repo#publishing-vex-documents

To disable this notice, set the TRIVY_DISABLE_VEX_NOTICE environment variable.


usr/bin/pebble (gobinary)
=========================
Total: 1 (HIGH: 1, CRITICAL: 0)

┌─────────┬────────────────┬──────────┬────────┬───────────────────┬─────────────────┬──────────────────────────────────────────────────────────────┐
│ Library │ Vulnerability  │ Severity │ Status │ Installed Version │  Fixed Version  │                            Title                             │
├─────────┼────────────────┼──────────┼────────┼───────────────────┼─────────────────┼──────────────────────────────────────────────────────────────┤
│ stdlib  │ CVE-2026-97054 │ HIGH     │ fixed  │ v1.27.3           │ 1.26.11, 1.27.4 │ For HTTP/1 servers, when MaxBytesReader's limit is exceeded, │
│         │                │          │        │                   │                 │ "Connecti ...                                                │
│         │                │          │        │                   │                 │ https://avd.aquasec.com/nvd/cve-2026-97054                   │
└─────────┴────────────────┴──────────┴────────┴───────────────────┴─────────────────┴──────────────────────────────────────────────────────────────┘

Only the latest release is supported. This release stays available, and is never deleted (ADR-0014 items 5 and 7).

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 01:52
9508c3c

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).

tlapm-9a52faf: the kept TLAPS tarball

Choose a tag to compare

@scottcochran scottcochran released this 19 Nov 18:43
d2da7b2

The TLAPS tarball tla-kit pins, kept so that its images can be rebuilt after upstream rebuilds the rolling
1.6.0-pre tag (ADR-0005 item 2). This release is never deleted, and its tag is never moved (ADR-0014 items 2
and 5). No image is published from it: the version releases link to it.

Asset What it is
tlapm-1.6.0-pre-x86_64-linux-gnu.tar.gz Upstream's tarball, built from tlaplus/tlapm at 9a52faf, byte for byte as served on 2026.11.19 (sha256 d9c06a04eb6b1b4192d3e22d5378143d09c9801414b9ad7ff6e918d34093c1f0)
licenses.tar.gz tla-kit's notice of the third-party software in the tarball and the image, with the licence texts the tarball leaves out (licenses/THIRD-PARTY.md)
polyml-5.9.1-src.tar.gz The source of Poly/ML 5.9.1 (LGPL-2.1), polyml/polyml at 90c0dbb2514e, tag v5.9.1, which Isabelle2025's polyml-5.9.1 component is built from
gmp-6.1.2.tar.xz, .sig The source of GMP 6.1.2 (LGPL-3.0-or-later or GPL-2.0-or-later), the release the tarball's libgmp.so.10 reports, from the GNU mirror, with its signature
libsha1-src.tar.gz The source of libsha1.so (GPL-3.0-or-later): GNU coreutils 8.4's sha1.c, as Isabelle2025's polyml-5.9.1 component builds it, with that component's README
SHA256SUMS The sha256 of every asset above

How each part's release and licence were settled: derived/tla-kit-copyleft-sources-2026.11.16.md in the repository.
That record read the tarball at ff40755. This tarball's Poly/ML, GMP and libsha1 are the same bytes.

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 18 Nov 06:43
ada119b

v0.4.0: cvc5 and ethos, for certified proofs

MINOR: new tools, and no existing pin moves (ADR-0014 item 2).
tools/pins.py moved v0.3.0 lists three new checker pins, which move
together (ADR-0017 item 4); every other pin is v0.3.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 5ade81e

What is new (Phase 6; ADR-0012 item 8, ADR-0017):

  • cvc5 at /opt/cvc5/bin/cvc5 and ethos at /opt/ethos/bin/ethos, on
    PATH, with CVC5 and ETHOS set (ADR-0004), and the CPC signature at
    /opt/cvc5/cpc. TOPAK's spec/proof-cert.sh reads them as they are.
  • The image builds them from the copies kept in release cvc5-1.4.0,
    which also holds the source of the LGPL libraries linked into them,
    at the releases their bytes show. licenses/ gains their notices.
  • tla-kit-selftest gains an smt check: ethos accepts a proof cvc5
    gives, and refuses one with a rule changed. tla-kit-info prints the
    three with their digests.
  • The weekly check compares the kept zips with upstream; the evidence
    workflow runs TOPAK's certified step when they move.

CI on main at ada119b (run 44247785902) passed:

  • records: PINS.json agrees with the Dockerfile and the README, and the
    vendored scripts match TOPAK at 5ade81e.
  • image: the build from the kept copies, every archive and binary
    checked by sha256; the self-test, smt among its checks; the MCP
    client test and the prove tool tests; spec/PinLifecycle.tla's 51 rows
    and spec/ProveRequests.tla's 78, both results files reproduced byte
    for byte.
  • reproduce: the commit built twice from nothing, on two runners, gave
    one digest.
  • evidence: TOPAK's proof-cert.sh Alone_proof, at TOPAK 0dfdfcd, in the
    candidate image: all 263 obligations proved, the 78 by SMT each with
    a proof of false that ethos accepted.

Pull request #27's run (44238524817) passed the same, and
server/compare_topak.py found the server the same as its commands on
TOPAK's Alone and Coupling.

A project that moves from v0.3.0 changes the digest its CI names and
regenerates nothing: TLC, the prover and the runtime are the same
bytes, so no verdict changes. Certified results (proof-cert.sh) can
now be generated in the image.

Cite this image by its digest

ghcr.io/scottcochran/tla-kit@sha256:6c27b7a007d723b55c126eedd4a6f295ecefdfb98a1c27c34580eaab862b8f2f

The tag v0.4.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:6c27b7a007d723b55c126eedd4a6f295ecefdfb98a1c27c34580eaab862b8f2f --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 5ade81efcc50bd9dd4de555b208dc890d5746606
image     https://github.com/scottcochran/tla-kit at ada119b7db96089bc7b2bc6a3b774b92fab28fe1 committed 2026-11-18T05:57:06Z

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:6c27b7a007d723b55c126eedd4a6f295ecefdfb98a1- │ ubuntu │        0        │    -    │
│ c27c34580eaab862b8f2f (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).

cvc5-1.4.0: the kept cvc5 and ethos

Choose a tag to compare

@scottcochran scottcochran released this 18 Nov 04:20
6f73402

cvc5's and ethos's Linux x86_64 builds, which tla-kit's image installs, kept so that its images can be rebuilt
after upstream stops serving them (ADR-0017). The two binaries are static, and link LGPL libraries. This release
also holds those libraries' source, at the releases their bytes show. This release is never deleted, and its tag
is never moved (ADR-0014 items 2 and 5). No image is published from it: the version releases link to it.

Asset What it is
cvc5-Linux-x86_64-static.zip Upstream's cvc5 1.4.0 (b432cd7), its static build without GPL libraries, byte for byte as served on 2026.11.17
ethos-linux-x86_64.zip Upstream's ethos 0.2.4 (8dc85c4), the commit cvc5 1.4.0 names, byte for byte as served on 2026.11.17
cvc5-1.4.0-src.tar.gz cvc5's source at tag cvc5-1.4.0 (BSD-3-Clause), which holds the CPC signature at proofs/eo/cpc/
ethos-0.2.4-src.tar.gz ethos's source at tag ethos-0.2.4 (BSD-3-Clause)
gmp-6.3.0.tar.bz2, .sig The source of GMP 6.3.0 (LGPL-3.0-or-later or GPL-2.0-or-later), linked into cvc5, from the GNU mirror, with its signature
mpfr-4.2.2.tar.xz, .sig The source of MPFR 4.2.2 (LGPL-3.0-or-later), linked into cvc5, from the GNU mirror, with its signature
libpoly-0.2.1.tar.gz The source of LibPoly 0.2.1 (LGPL-3.0), linked into cvc5, SRI-CSL/libpoly at tag v0.2.1
glibc_2.35-0ubuntu3.14.*, glibc_2.35.orig.tar.xz, .asc Ubuntu 22.04's source package of glibc 2.35-0ubuntu3.14 (LGPL-2.1-or-later), linked into both
gmp_6.2.1+dfsg-3ubuntu1.*, gmp_6.2.1+dfsg.orig.tar.xz Ubuntu 22.04's source package of GMP 2:6.2.1+dfsg-3ubuntu1, linked into ethos
licenses.tar.gz tla-kit's notice of the third-party software in the image, with the licence texts the zips leave out (licenses/THIRD-PARTY.md)
SHA256SUMS The sha256 of every asset above

How each library's release and licence were settled: derived/tla-kit-licence-check-cvc5-ethos-2026.11.17.md and
derived/tla-kit-static-libraries-2026.11.17.md in the repository.

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 17 Nov 07:03
4aee1f5

v0.3.0: the MCP server's proof tools

MINOR: new server tools, and no pin moves (ADR-0014 item 2).
tools/pins.py moved v0.2.0 lists nothing, so every pin is v0.2.0's:

Pin Value
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…e2f5
apt Ubuntu's snapshot of 2026-11-15T00:00:00Z
The skill's scripts TOPAK 5ade81e

PINS.json changed by one served-state entry only: upstream no longer
serves the pinned tlapm tarball (2026.11.16). The image builds from the
kept copy, as before.

What is new is tla-kit's own code:

  • Five proof tools in tla-kit mcp (Phase 4; ADR-0009, ADR-0016):
    prove, proof_check, proof_results, flip_test and proof_sync. prove
    runs tlapm per request, in a process group of its own killed whole on
    a timeout or a cancel, with a cache the server owns, one run per
    module at a time, and every child reaped before it answers. A failed
    obligation comes back with its text, the backends tried and why each
    failed. proof_results is the only one that writes into the project:
    the skill's dated proof results file.
  • The server handles requests concurrently, and a cancelled request
    gets no response (MCP 2025-06-18).
  • parse and symbols read proof modules: they give SANY the prover's
    library.

The image gains no package.

CI on main at 4aee1f5 (run 44033259889) passed:

  • records: PINS.json agrees with the Dockerfile and the README, and the
    vendored scripts match TOPAK at 5ade81e.
  • image: the build from the kept prover tarball; the self-test; the MCP
    client test, every tool over stdio against the skill's fixture.
  • reproduce: the commit built twice from nothing, on two runners, gave
    one digest.

On pull requests #21 and #22, in images built from them:

  • server/test_prove.py tried to break each property of
    spec/ProveRequests.tla (ADR-0016 item 7): runs of one module take
    turns, a cancelled request gets no response, a cancel after the
    response changes nothing, a timeout kills the whole group, and no
    backend is left alive or unreaped. All passed. proof_results through
    the server wrote the file that the script, run directly, reproduced
    byte for byte.
  • server/compare_topak.py: the nine model-checking tools against their
    commands on TOPAK's Alone and Coupling, at 5ade81e, 84 comparisons,
    all the same.

spec/ProveRequests.tla, the design the tools follow, has 78 rows, all
as expected; they reproduced byte for byte in v0.2.0 and are
regenerated in CI.

No project pins tla-kit yet. A project that moves from v0.2.0 changes
the digest its CI names, and regenerates nothing: the checker, the
prover and the runtime are the same bytes, so no verdict changes
(ADR-0014 item 2, MINOR).

Cite this image by its digest

ghcr.io/scottcochran/tla-kit@sha256:948e6d1f275d64e4114950f03c2b5d1236068d1f3fe60885de7625789fc8257f

The tag v0.3.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:948e6d1f275d64e4114950f03c2b5d1236068d1f3fe60885de7625789fc8257f --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).

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
java      openjdk version "25.0.5" 2026-10-20 LTS
skill     https://github.com/scottcochran/TOPAK at 5ade81efcc50bd9dd4de555b208dc890d5746606
image     https://github.com/scottcochran/tla-kit at 4aee1f56e0477a2aba60227bead4a82a5a5f5248 committed 2026-11-17T06:42: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:948e6d1f275d64e4114950f03c2b5d1236068d1f3fe- │ ubuntu │        0        │    -    │
│ 60885de7625789fc8257f (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).

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 16 Nov 23:06
2bea23e

v0.2.0: the MCP server for model checking

MINOR: a new server tool, and no pin moves (ADR-0014 item 2).
tools/pins.py moved v0.1.0 lists nothing, so every pin is v0.1.0's:

Pin Value
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…e2f5
apt Ubuntu's snapshot of 2026-11-15T00:00:00Z
The skill's scripts TOPAK 5ade81e

What is new is tla-kit's own code:

  • tla-kit mcp: an MCP server over stdio, standard library only (ADR-0008),
    with nine tools: info, parse, symbols, evaluate, tlc_run, simulate,
    coverage, state_graph and tlc_rows. Only tlc_rows writes into the project,
    and only the skill's generator's results file (ADR-0006).
  • tla-kit: one command for mcp, info and selftest.
  • tla-kit-selftest gains an mcp check.

The image gains no package. Its digest differs from v0.1.0's because these
files are in it.

CI on main at 2bea23e (run 43973837070) passed:

  • records: PINS.json agrees with the Dockerfile and the README, and the
    vendored scripts match TOPAK at 5ade81e.
  • image: the build from the kept prover tarball; the self-test, mcp among its
    checks; the MCP client test, which drives every tool over stdio against the
    skill's fixture.
  • reproduce: the commit built twice from nothing, on two runners, gave one
    digest.

Phase 3's "Done when" was met in CI on pull request #11 (run 43921629481), in
the image built from it: server/compare_topak.py compared each of the nine
tools with the command it stands for on TOPAK's Alone and Coupling, at
5ade81e. All 84 comparisons were the same: every row of both modules through
tlc_run and the skill's tlc_run.py, and each module's results file, byte for
byte, from tlc_rows and tlc_rows.py.

No project pins tla-kit yet. A project that moves from v0.1.0 changes the
digest its CI names, and regenerates nothing: the checker, the prover and
the runtime are the same bytes, so no verdict changes (ADR-0014 item 2,
MINOR).

Cite this image by its digest

ghcr.io/scottcochran/tla-kit@sha256:5554015f9927001f933a4ec9e440fc0e1d37dc5676ce3acd47190b2d6dfc1e5d

The tag v0.2.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:5554015f9927001f933a4ec9e440fc0e1d37dc5676ce3acd47190b2d6dfc1e5d --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).

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
java      openjdk version "25.0.5" 2026-10-20 LTS
skill     https://github.com/scottcochran/TOPAK at 5ade81efcc50bd9dd4de555b208dc890d5746606
image     https://github.com/scottcochran/tla-kit at 2bea23e99f182dee9306b402e625fe019afa758a committed 2026-11-16T22:50:21Z

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:5554015f9927001f933a4ec9e440fc0e1d37dc5676c- │ ubuntu │        0        │    -    │
│ e3acd47190b2d6dfc1e5d (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).

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 16 Nov 08:54
bfeecc8

v0.1.0: the first release

Kind of move

The first release. There is no earlier release to move from, so no pin moves.
Releases stay at 0.x until Phase 2 is done (ADR-0014 item 2).

Pin Value
TLC, SANY, PlusCal tla2tools.jar v1.7.4, sha256 936a2620…0e88
TLAPS tlapm 1.6.0-pre at ff40755: binary sha256 6182df63…5bb2, and the tarball sha256 99db29f1…6bcc, kept in release tlapm-ff40755
Java Temurin JRE 25.0.5+8, in the base
Base eclipse-temurin:25-jre-noble, digest 5b5a79b8…e2f5, resolved 2026.11.15
apt Ubuntu's snapshot of 2026-11-15T00:00:00Z
The skill's scripts TOPAK 5ade81e

PINS.json, attached, lists every pin with its values and sources.

Evidence

CI on main at bfeecc8 (run 43824194995) passed:

  • records: PINS.json agrees with the Dockerfile and the README, and the vendored
    scripts match TOPAK at 5ade81e.
  • image: the build from the kept prover tarball, and the self-test (the pins,
    all 48 installed files against PINS.json, the environment, the notices, sany,
    pcal, tlc, and the skill's setup check with proofs). Also the PinLifecycle
    rows: all 50 as expected, with spec/PinLifecycle-results-2026.11.16.txt
    reproduced byte for byte.
  • reproduce: the commit built twice from nothing, on two runners, gave one
    digest.

The spike's checks against TOPAK (the README's spike table) were run in an
image built from the spike, not from this commit. They are repeated from this
release's published digest as Phase 1c's last check.

What a project must regenerate if it adopts this release

No project pins tla-kit yet. A project that adopts this release:

  • names its digest, not this tag, in its CI and its results files
    (ADR-0002, ADR-0010 item 4);
  • keeps its TLC results, if they were made with tla2tools.jar v1.7.4
    (936a2620…0e88): the checker is the same jar;
  • regenerates its proof results files if they name another tlapm build. This
    image holds ff40755. Moving to it is the project's decision (ADR-0005 item 5):
    TOPAK's D1, and the same question in gov-tla.

Cite this image by its digest

ghcr.io/scottcochran/tla-kit@sha256:454328cd7464efcf8a27a063c51c10086e09571c462c73d085b4a249e44950c6

The tag v0.1.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:454328cd7464efcf8a27a063c51c10086e09571c462c73d085b4a249e44950c6 --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).

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
java      openjdk version "25.0.5" 2026-10-20 LTS
skill     https://github.com/scottcochran/TOPAK at 5ade81efcc50bd9dd4de555b208dc890d5746606
image     https://github.com/scottcochran/tla-kit at bfeecc8f0bf9ea9446488a03ebd92ccb574c421a committed 2026-11-16T07:29:10Z

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:454328cd7464efcf8a27a063c51c10086e09571c462- │ ubuntu │        0        │    -    │
│ c73d085b4a249e44950c6 (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).

tlapm-ff40755: the kept TLAPS tarball

Choose a tag to compare

@scottcochran scottcochran released this 16 Nov 05:49
5ca9f97

The TLAPS tarball tla-kit pins, kept so that its images can be rebuilt after upstream rebuilds the rolling
1.6.0-pre tag (ADR-0005 item 2). This release is never deleted, and its tag is never moved (ADR-0014 items 2
and 5). No image is published from it: the version releases link to it.

Asset What it is
tlapm-1.6.0-pre-x86_64-linux-gnu.tar.gz Upstream's tarball, built from tlaplus/tlapm at ff40755, byte for byte as served on 2026.11.15 (sha256 99db29f119cb6f43ffed653b212ba2d005e5bf8e242c53468876cb0d08da6bcc)
licenses.tar.gz tla-kit's notice of the third-party software in the tarball and the image, with the licence texts the tarball leaves out (licenses/THIRD-PARTY.md)
polyml-5.9.1-src.tar.gz The source of Poly/ML 5.9.1 (LGPL-2.1), polyml/polyml at 90c0dbb2514e, tag v5.9.1, which Isabelle2025's polyml-5.9.1 component is built from
gmp-6.1.2.tar.xz, .sig The source of GMP 6.1.2 (LGPL-3.0-or-later or GPL-2.0-or-later), the release the tarball's libgmp.so.10 reports, from the GNU mirror, with its signature
libsha1-src.tar.gz The source of libsha1.so (GPL-3.0-or-later): GNU coreutils 8.4's sha1.c, as Isabelle2025's polyml-5.9.1 component builds it, with that component's README
SHA256SUMS The sha256 of every asset above

How each part's release and licence were settled: derived/tla-kit-copyleft-sources-2026.11.16.md in the repository.