A file can be perfectly unchanged and completely false.
If someone fabricates a document today, calculates a checksum and preserves it flawlessly for fifty years, future fixity checks can prove the forged bitstream remained unchanged. They cannot prove the document was genuine when it entered custody.
Digital record authenticity is a larger claim. It concerns whether a record is what it purports to be and whether its identity and integrity can be supported across creation, use, transfer, preservation and reproduction.
This article sits beneath How Archives Work, How Digital Fixity Works and How Preservation Metadata Works. Fixity asks whether bits changed. Authenticity asks whether the preserved record still deserves to be treated as the record it claims to be.
1. Authenticity Begins With Identity
Before asking whether a record changed, we need to know which record we are talking about.
Identity can include creator, date, addressee, subject, version, record type, system of origin and relationships to a transaction or case.
If two files are visually identical but one is a draft and one is the formally issued record, they do not have the same archival identity.
2. Integrity Means More Than Bit Equality
Bit-level fixity is powerful evidence of technical continuity. Record integrity also concerns whether the record remains complete enough and unaltered in the aspects required for its evidential role.
A migration can change every byte while preserving the record’s essential content, structure and context. Conversely, an unchanged file can lose integrity as a record if it becomes detached from the metadata that establishes who created it and why.
3. Provenance Connects the Record to Its Origin
Who created the record? In which system? As part of what activity? Under what authority?
Provenance connects the digital object to the process that produced it. Without provenance, a future user may have a document but no defensible basis for placing it inside an institutional history.
4. Context Makes a Record a Record
A record acquires meaning through relationships.
An email belongs to a conversation. An invoice belongs to a transaction. A court order belongs to a case. A research result belongs to a study. Remove those relationships and the isolated file can remain readable while its evidential meaning weakens.
5. Chain of Custody Makes Handoffs Visible
Digital records can pass through creators, systems, departments, vendors, archives and migration platforms.
Each handoff creates a possibility of substitution, unauthorised alteration or context loss. A documented chain of custody records who controlled the record, when control changed and which checks confirmed the transfer.
The general handoff owner remains How Cross-System Handoffs Work.
6. Authenticity Is Supported by Procedures
The InterPARES research programme has long emphasised that trustworthy digital records depend on recordkeeping and preservation procedures, not on one magical technical property. Its work develops requirements and methods for assessing and maintaining authentic electronic records. See InterPARES.
That is an important civilisational principle: authenticity is produced by a system of controls whose evidence accumulates over time.
7. Signatures Can Support Authenticity Without Solving It Alone
A digital signature can provide evidence that a particular key signed a particular bitstream and that the signed bytes have not changed since signing.
It does not by itself prove that the signer was authorised, that the document’s contents were true, that the key was not compromised or that the institutional context has been preserved.
Cryptographic evidence is one layer inside a wider authenticity argument.
8. Migration Changes Bits Without Necessarily Destroying Authenticity
A digital record may need to be migrated to remain usable.
The new copy has a different checksum. Authenticity is maintained through controlled transformation: preserve the source, document the migration, identify the significant properties, validate the result and record the derivation relationship.
Authenticity therefore depends on continuity of evidence rather than identity of bytes across every preservation action.
9. Authentic Copies Matter in Digital Preservation
Long-term preservation frequently works by creating copies: storage replicas, migrated versions, normalised versions, emulated representations and access derivatives.
The archive needs procedures that let it assert which copies are authentic representations of the record and which are merely convenient derivatives.
InterPARES distinguishes requirements supporting the presumption of authenticity and requirements supporting production of authentic copies under preservation custody. See its project products on authenticity and preservation.
10. Authenticity Is Not Accuracy
An authentic record can contain an error.
If an official clerk entered the wrong date in a genuine record, the archive may preserve an authentic record of an inaccurate assertion.
Authenticity asks whether the record is genuinely the record produced by the stated process. Accuracy asks whether its assertions correctly describe reality. Those claims should remain separate.
11. Authenticity Is Not Truth
A genuine propaganda poster is authentic as an artefact and not therefore true in its claims.
A preserved scientific paper is authentic as the published article and may later be shown to contain a flawed conclusion.
Archives preserve evidence about what people and institutions produced, not a guarantee that every preserved statement is factually correct.
12. Dynamic Records Complicate Authenticity
Traditional documents often have a relatively stable final form. Databases, dashboards and interactive systems can change continuously.
The archive may need to define which states constitute records: snapshots, transactions, event logs, exported reports or preserved runtime environments.
Authenticity starts with a clear declaration of what unit of record is being preserved.
13. Worked Example: Email Record
An email file contains sender, recipients, timestamp, subject, body and headers.
To preserve it as an organisational record, the archive may also need mailbox context, thread relationships, attachments, transfer history and evidence that the message came from the recordkeeping system rather than an arbitrary exported copy.
14. Worked Example: Signed Contract
A signed PDF is transferred to an archive. The archive verifies the transfer checksum, records signature-related information, acquisition source and custody, and preserves the original file.
If a future migration is needed, the archive keeps the source and records the migrated representation as a derivative rather than silently replacing the signed bitstream.
15. Worked Example: Database Record
A database contains a transaction that changes several tables.
Preserving only one row can lose the context that proves which transaction created it. Audit logs, schema, timestamps and related records may be necessary to preserve the evidential structure.
16. Worked Example: eduKate Published Article
An eduKate article can be updated, corrected or re-editioned. Authenticity requires distinguishing the edition actually published at a given time from later modifications.
Wintour House’s edition discipline — publication date, source state, correction history and canonical identity — provides the editorial layer that an archival preservation system can later carry forward.
17. Failure Mode: Hash Equals Authentic
A repository verifies a checksum and labels the record authentic.
That proves only that the current file matches the recorded baseline. If the baseline came from an unverified source, the authenticity claim remains unsupported.
18. Failure Mode: Context Stripped During Export
A records system exports thousands of PDFs but leaves behind identifiers, workflow history and relationships.
The documents remain readable and lose part of the evidence that established their record identity.
19. A Digital-Authenticity Checklist
- Define the record identity clearly.
- Preserve creator, date, transaction and system-of-origin context.
- Establish fixity at a defensible custody point.
- Document every significant handoff.
- Protect provenance and preservation metadata.
- Use signatures or cryptographic evidence where appropriate without treating them as complete proof.
- Record migrations and derivative relationships.
- Distinguish authenticity from factual accuracy and truth.
- Define how authentic copies are produced and verified.
- Preserve correction and version history rather than silently overwriting it.
20. Read the Mechanism Forward, Backward and Sideways
Forward: creation in context → record identity → controlled use → custody handoffs → preservation actions → authentic copy or representation → future use. Backward: start from a disputed record and reconstruct origin, context, custody and transformations. Sideways: compare creator, records manager, archivist, security specialist and historian. Each contributes evidence to the same authenticity claim.
21. The Civilisation Lesson
Digital civilisation depends on records that can survive the death of the systems that created them without becoming anonymous files.
Authenticity is not a property a file possesses alone. It is a supported continuity claim built from identity, integrity, provenance, custody and documented preservation.
Continue through How Digital Fixity Works, How Preservation Metadata Works and the How X Works hub. Next: preservation planning — how archives watch technology, collections and users closely enough to act before today’s readable objects become tomorrow’s emergencies.