{"what_this_is":"What our records are made of, which algorithms sign them, how they will be carried across the federal post-quantum deadlines, and where AI is and is not used. Facts with their check URLs; no certification is claimed.","hashing":{"algorithm":"SHA-256 over canonical JSON (RFC 8785 / JCS)","note":"Quantum computers do not break SHA-256 as a record of integrity (Grover halves the margin to 128 bits, which remains out of reach). Every receipt hash issued today stays verifiable without change.","check":"https://alphacovenantholdings.com/api/receipts/verify/{sha256}"},"signatures":[{"algorithm":"Ed25519 (FIPS 186-5 EdDSA)","key":"did:web key-1","role":"signature of record on every receipt, audit-log entry, correction and certification","status":"classical; FIPS 186-5 approved; scheduled for replacement as signature of record (see plan)"},{"algorithm":"ML-DSA-65 (FIPS 204, lattice)","key":"did:web key-pq-1","role":"post-quantum signature in the HYBRID set on every new receipt at registration, and the parallel proof on every Verifiable Credential export","status":"in use since 2026; on every new receipt since 2026-10-25; verifies offline against the key in the DID document; reference implementation, not FIPS-validated"},{"algorithm":"SLH-DSA-SHA2-192s (FIPS 205, hash-based)","key":"did:web key-slh-1","role":"archive-grade post-quantum signature on registry tree-head checkpoints and the daily archive digest","status":"in use since 2026; different mathematics from ML-DSA so a break in one does not take the other"},{"algorithm":"OpenTimestamps (SHA-256 Merkle proof anchored in Bitcoin)","key":"none — public calendars","role":"independent timestamp on each daily digest","status":"hash-based; not affected by the signature transition"}],"did_document":"https://alphacovenantholdings.com/api/vc/did.json","federal_dates_for_context":{"source":"Executive Order 14412 (June 2026) and OMB M-26-15 (24 June 2026), implementing NIST IR 8547","key_establishment":"agencies' high-value and high-impact systems move to post-quantum key establishment (FIPS 203) by 2030-12-31","digital_signatures":"agencies' high-value and high-impact systems move to post-quantum digital signatures by 2031-12-31","who_it_binds":"Federal agencies' covered systems; the FAR Council is directed to carry the obligations into contract terms by the end of 2030. It does not bind this platform directly. It will bind what our customers can accept as evidence, which is why the plan below exists."},"signature_set_state_for_new_receipts":"HYBRID (since 2026-10-25): every new receipt's registry row carries receipt-signature-set/v1 — ML-DSA-65 and Ed25519, each over the ASCII bytes of the receipt SHA-256; the set verifies only if both verify. GET /api/receipts/{rid}/signatures.","plan":[{"by":"done 2026-10","what":"Phase 0–3: signing-path inventory published; algorithm/standard/key id named on every signature; HYBRID set (ML-DSA-65 + Ed25519) on every new receipt at registration; SLH-DSA on archive checkpoints; OpenTimestamps on the daily digest."},{"by":"2027-06-30","what":"Audit-log entries and decision-record countersignatures move from Ed25519-only to the HYBRID set. An external party verifies at least 1,000 hybrid sets from the public keys alone; we publish the first such report."},{"by":"2030-12-31","what":"Phase 4: ML-DSA-65 becomes the signature of record; Ed25519 retained as a compatibility proof; a FIPS-validated implementation replaces the reference one if available. Key ids change; the DID document keeps every historical key so nothing issued earlier stops verifying."},{"by":"2031-12-31","what":"Phase 5: Ed25519 no longer issued (state PQC_ONLY) — earlier if a break is published. Historical receipts remain verifiable by their SHA-256, their OpenTimestamps anchor, their SLH-DSA archive signature and the retired Ed25519 key published in the DID document."}],"cryptography_statement":"https://alphacovenantholdings.com/api/public/cryptography.html","plan_rule":"Nothing already issued is re-signed, re-hashed or edited. Durability comes from keeping every key and every proof public, not from changing the record.","ai_use":{"receipts":"No language model reads a source, builds a receipt, chooses what prints, computes a hash or signs anything. A receipt is a deterministic read of named official files.","where_ai_is_used":["Plain-English explanation of a record already fetched (/api/explain) and the record reader / Q&A (/api/ai): the model sees only numbered lines lifted from the record, is instructed not to add facts, and its output is labeled explanation — it is not part of the receipt or its hash.","Forms Desk drafts (/api/forms-desk) and the free help guide on /free (/api/free-guide): same construction, same label, logged with the model name.","Operator-only tools that never face a customer: the daily self-check summary written FROM computed results, Federal Register scout memos, the internal advisory desk, and caption drafts for our own posts — a person reviews before anything is published."],"logging":"Every model call passes through one ledger function (aillog.record) that records surface, provider, model and time, and refuses while a receipt is being built; the ledger is public in aggregate at /api/public/ai-calls and per receipt at /api/public/ai-calls?receipt_id=. Every receipt body carries ai_statement.model_calls_during_build = 0 inside its hashed, signed body.","statement":"We make no claim that this satisfies OMB M-25-21 or any agency's AI governance plan; those bind agencies. Any account can switch AI off entirely (AI-off mode) and take the product as plain software. The regulatory position — EU AI Act, Colorado, Texas, California, Utah, OMB, GDPR Art. 22, NIST AI RMF — with what each turns on and what we do not claim is published at /api/public/ai-position.html."},"record_format":{"receipt":"Plain JSON, canonicalised; SHA-256; detached signatures; public registry row with id, time and hash; optional W3C Verifiable Credential export; HTML rendering is a view, not the record.","export":"Any receipt, cover or daily digest can be copied into a records system as JSON with its proofs; no proprietary reader is needed to verify it.","not_a_screenshot":"The record is what the source printed, read by a program at a stated time, with the request URL; a screenshot shows what a screen displayed to a person."},"how_to_check":"https://alphacovenantholdings.com/api/public-record/verify-guide.html"}