Qollqa Register · machine-citation findings

Downloads

The data, its manifest, its proof, and the open instruments.

The register

Revision 19, prepared 2026-09-21. Every file below is served from this site.

FileWhat it is
amc-registry-federal-v1.csvEvery entry, one row each
amc-registry-respondents-v1.csvOne row per respondent, for every order read at source. An order that sanctions four people and two firms separately cannot be held in one amount field; this is where the breakdown lives
amc-registry-federal-v1.jsonThe same data, nested
summary.jsonThe computed counts, as the generator emitted them
MANIFEST.jsonSHA-256 of each file in the revision
MANIFEST.sha256The same hashes, in the format sha256sum reads
MANIFEST.json.otsOpenTimestamps proof of the manifest
corrections.jsonEvery correction the register has made to something it published, machine-readable. Not part of the anchored release: it spans revisions and grows after one is sealed, so it is served beside the manifest rather than inside it
The OpenTimestamps proof is confirmed. The manifest is committed by Bitcoin block 968,034. The proof served here is the upgraded one, which carries the block path, so ots verify completes without contacting a calendar server. The earlier pending proof required one.

Open instruments

Published for comment, openly licensed, unowned. The register claims no patent over any of them and any party may implement them.

FileWhat it is
qollqa-contribution-v0.1.schema.json Contribution schema, JSON Schema 2020-12. 11 of 11 conformance cases pass
qollqa-system-registry-v0.1.json 29 normalized system identifiers, 85 aliases
Not yet published: qollqa-claim-c14n-v1. The contribution schema names this canonicalization as the condition under which two contributors hashing the same proposition produce the same digest. It is specified in the schema's prose and has not been written as a standalone document. Until it is, a contribution carrying that canonicalization identifier is asserting conformance to something this register has not published, and it is named here as an omission rather than left for a reader to discover.
The file names are the ones the anchored manifest states, not tidier ones. MANIFEST.json is what the timestamp proof covers and it names these files; republishing them under a different name would break sha256sum -c for anyone following the instruction below. The chain outranks the cosmetics.

Verifying a download

Hash the files and compare against the manifest, then verify the manifest against its own proof. The point of publishing the proof is that this does not require trusting the register.

sha256sum -c MANIFEST.sha256
ots verify MANIFEST.json.ots

Licensing

The register data is available for licensing, including for uses that redistribute it. Write to [email protected]. The open instruments above are not licensed separately and carry no fee.