Feed Integrity & Verification

Cryptographic Provenance

Cryptographic provenance adds an independent verification layer to machine-readable public records. For Aigistry’s National AI Feed, verified Authority Record publications may receive cryptographic proof fields after provider authentication, authority validation, registry processing, and feed normalization.

Authority Records Record Hashing Ed25519 Signatures Public-Key Verification Tamper Detection

Why Cryptographic Provenance Matters

Provenance identifies where information came from. Cryptographic provenance strengthens that relationship by allowing a published record to be checked after publication. When a record includes a cryptographic hash and registry signature, the record can be tested against a public key to determine whether the signed content still matches the record that was processed by the registry.

Authority

Aigistry begins with verified Authority Records. Provider-submitted publications are associated with a specific government authority before they move into the National AI Feed processing pipeline.

Integrity

Once a record is normalized, Aigistry generates a cryptographic hash of the record. The hash functions as a tamper-evident fingerprint for the finalized machine-readable publication.

Verification

Aigistry signs the record hash using an Ed25519 registry signing key. The corresponding public key allows the signature to be independently checked without exposing the private signing key.

How the Signing Process Works

A participating GovTech provider submits a publication through the Provider API.

Aigistry validates the provider API key, provider token, and active Authority Record.

The record is processed into the National AI Feed pipeline with normalized attribution, jurisdiction, timestamp, and source fields.

Aigistry generates a SHA-256 record hash from the finalized machine-readable record.

Aigistry signs the record hash using Ed25519 and adds proof fields to the published feed record.

Proof Fields

Signed National AI Feed records may include the following cryptographic proof fields:

{ “record_hash”: “sha256:…”, “signature”: “…”, “signature_algorithm”: “Ed25519”, “signed_at”: “2026-06-02T17:45:01+00:00”, “public_key_id”: “aigistry-registry-key-1” }

These fields do not replace the issuing authority, the GovTech provider, or the original public source. They provide an additional integrity signal showing that the finalized registry record was signed after validation and processing.

What the Signature Does — and Does Not — Prove

A registry signature confirms that a specific record hash was signed by Aigistry after registry processing. It supports tamper detection and independent verification of feed integrity. It does not certify the policy content of a government statement, replace official agency publication, or convert illustrative educational records into verified Authority Record publications.

Signed Records

Signed records indicate that a publication passed through the Provider API, active Authority Record validation, queue processing, and registry signing workflow.

Cryptographic Proof

Each signed record includes cryptographic proof fields tied to its finalized machine-readable state. These fields support integrity verification and help detect whether a published record has been altered after signing.

Public Verification

Public-key verification allows external systems to test whether a signed record still matches the hash that Aigistry signed. This supports downstream auditability and machine-readable integrity review.

Public Verification Resources

Signed National AI Feed records may be independently verified using Aigistry’s published verification key.

View Public Verification Key

Cryptographic Provenance Is an Integrity Layer

Aigistry’s core registry function remains authority attribution, provenance, jurisdiction clarity, timestamping, and machine-readable publication. Cryptographic signing extends that function by adding a verifiable integrity layer to processed National AI Feed records.