lra-runner

lease-revocation-axes · revision 2 (candidate) · independent run

The first independent, non-author-produced run of the APS suite family lease-revocation-axes: a from-scratch Python verifier written against the family contract, replaying the frozen revision-2 vectors under all four profile combinations. Result: independent_run_matched — 48 baseline runs, 176 calls, 528 axis comparisons, 176 composite comparisons, zero failures; 12/12 mutants fail on exactly their pinned case sets; 20 diagnostic runs and 12 oracle checkpoints clean; all five reporting-semantics checks pass. Vectors digest-gated: the runner refuses to score any vector file whose SHA-256 is not pinned in its manifest.

Artifact	SHA-256 (first 16)	Seal
lra-runner-20261023b.tar.gz (complete artifact · 27,608 B · current)	`71c4e2a875cfdda1…`	sealed
lra-runner-20261023.tar.gz (superseded by rev b · kept as sealed history)	`70e812f78fd02fde…`	sealed

Manifest: lra_runner.py (the runner) · vendor/vectors.json + vendor/oracle-checkpoints.json + vendor/SHA256SUMS.txt (frozen inputs, digest-gated) · RUN-REPORT-2026-10-23.md · PROVENANCE.md · run-output.json (the recorded run) · README.md. Raw files are also served unarchived under /conformance/lra-runner/.

Replay, offline, two commands (Python 3 standard library only — no packages, no network):

tar xzf lra-runner-20261023.tar.gz
python3 lra-runner/lra_runner.py

Expected output ends with RESULT: independent_run_matched; the digest gate prints OK against the pinned manifest. The frozen vectors digest is a0a07ea58bcacfd0….

Provenance: independently authored from the family contract (PR #180); the canonical development copy is github.com/Aicent-Stack/conformance/lra-runner — the tarball above is sealed from the same bytes. A companion author-produced production-code mapping (no vectors scored) lives at PRODUCTION-CODE-MAPPING.md.

One artifact, two addresses

Both addresses are derived from the artifact's own SHA-256 digest — nothing is invented, nothing is registered: the sister schemes split one referent across the question and the answer. Paste either into the respective scheme's resolver to see it resolve locally, without any network call beyond fetching this page.

rttp:// · the question (WHERE + WHEN) · intent side rttp://71c4e2a8.conformance.iqa

intent = first 8 hex of the current artifact digest (the intent field is 8 lowercase hex by grammar); pillar and root are operator-chosen labels. Authority: 71c4e2a8.conformance.iqa.

iqa:// · the answer (WHETHER) · attestation side iqa://71c4e2a875cfdda1c0f31a1cc8b44bb1.forge.iqa

subject = first 32 hex of the same digest; organ forge (closed set) — this is the exact subject the organ seal above attests, and the organ answers live at /organ-api/v1/production?subject=71c4e2a875cfdda1c0f31a1cc8b44bb1. Each sealed cut carries its own address pair; the superseded rev-a pair remains verifiable in the seal bundle.

Verify offline with pip install "iqa-org[ed25519]==1.3.1" and the seal bundle at /attestations/release-attestations.json · Organ AID: ba92fadd46a51caf25633e0f315c4ad10103b879d7397397362f89dc33817153.