every published artifact of IQA — mirrored here, sealed by our own organ
This is the archive of record for every released artifact of the
IQA packages: one row per release and registry, each file byte-identical to what the registries
serve (the SHA-256 column is the proof) and carrying a live Ed25519 seal from our organ. For
package-manager installs use the registries directly; use this archive when you want the bytes from
the scheme's own domain, or when a registry is unreachable. The seal bundle lives at
/attestations/release-attestations.json —
every row below is a record in it.
Version
Registry
File
SHA-256 (first 16)
Seal
loading the ledger live…
Not archived, on the record: release 1.2.7 was a
springboard — byte-identical to 1.2.8 with only the version changed — and was yanked after
1.2.8 shipped; it is not archived here. The 0.1.x and 1.2.1–1.2.5-alpha
releases predate the first three-language implementation and are likewise out of this archive's
scope. This archive is append-only: new releases are added, nothing is removed. The iqa-mcp placeholder releases (npm 0.0.0-stage, npm and crates 0.0.1) predate the sealed 1.0.x line and are likewise not archived here.
Internet-Draft archive
the sealed version history of the draft family (combined ISE draft + two early split drafts) — the authoritative text always lives at ietf.org
Version
Registry
File
SHA-256 (first 16)
Seal
loading the ledger live…
The tarball contains the three official IETF renderings (txt · html · xml), byte-identical to what ietf.org serves. This section is append-only.
Conformance experiment code
sealed interop artifacts of the lra / aae / icam runner families — runner + frozen inputs + recorded outputs, byte-replayable offline — plus every seal of our own vector-family pages (grant-ref · lease-boundary · ae128-fail-closed · pulse-header · uri-grammar · route-shard)
Version
Registry
File
SHA-256 (first 16)
Seal
loading the ledger live…
Each tarball is the sealed artifact of record for its run — the report pages
(revision 3 ·
revision 2) carry the replay commands and the full
18-section run record. The vector-family entries below the runner artifacts are the page seals of
our own families, first-published at iqa.org/conformance/. This section is append-only.
Lab records & candidates (Agent-Authority-Conformance)
every site-freeze seal of the estate — report pages, station pages, the brief, the whitepaper, the URI reference — rendered live from the ledger, newest first
Record
Registry
File
SHA-256 (first 16)
Seal
loading the ledger live…
Every row is a record in the ledger (append-only). The vector-family page seals are not listed here — they live in the conformance section above, next to the runner artifacts they belong with.
Blog seals
every sealed version of every blog.aicent.com article — rendered live from the blog seal ledger, newest first
Version
Article
Registry
SHA-256 (first 16)
Seal
loading the blog seal ledger live…
The blog is sealed with the same organ and the same dual-address discipline as every artifact above — but its ledger is separate: /attestations/blog-seals.json, also mirrored at blog.aicent.com/attestations/. One row per sealed version: corrected articles re-seal as a new version (v2, v3), both generations stay on the record, and the full table with resolvable dual addresses lives on the attestations page. This section is append-only.
Sibling archive: the RTTP package archive (formerly rttp.com/downloads/) now redirects here — this page is the single archive of record, and the RTTP mirror files remain served at rttp.com/downloads/files/. · Organ AID:
ba92fadd46a51caf25633e0f315c4ad10103b879d7397397362f89dc33817153 · verify offline with
pip install "iqa-org[ed25519]==1.3.2".