Origin Evidence

Origin Evidence

Origin evidence is evidence of where a record came from.

It helps connect a file, work, dataset, message, decision, claim, output, or event to its source.

A record may exist, but existence alone is not enough. If the origin is unclear, the record may be difficult to explain, verify, trust, or rely on later.

The purpose of this guide is to help users preserve the source information that gives a digital record meaning.

Origin evidence is especially important for authorship, business records, research, AI-assisted work, training data, synthetic media, incident records, and any situation where a person or organisation may later need to show where something came from.

Quick Read

• Origin evidence shows where a record came from.
• It should preserve the source material, creator or supplier context, system context, and surrounding facts.
• Origin evidence does not automatically prove ownership, permission, legality, originality, or truth.

What this means

Origin evidence is the part of an evidence record that explains the source.

For a creative work, this may include drafts, project files, exports, notes, timestamps, version history, and publication context.

For a business record, it may include the system that generated the record, the person or team responsible, approvals, related communications, and the workflow that produced it.

For a dataset, it may include collection source, supplier details, licence or permission context, lineage, processing history, and documentation.

For AI-assisted work, it may include human inputs, prompts, outputs, edits, source materials, and contribution context.

Origin evidence answers the question: where did this record come from, and why should that source be understood as connected to the claim?

Why it matters

Many evidence claims fail because the record is detached from its source.

A screenshot may show something, but not reliably show where it came from. A file may exist, but not show who created it. A timestamp may show that a file existed at a point in time, but not explain its origin. A platform record may show publication, but not creation. A dataset reference may show use, but not provenance or permission.

Origin evidence reduces that weakness.

It helps prevent a record from becoming a loose object with no reliable context.

If origin is not preserved early, it may be difficult or impossible to reconstruct later. People leave. Accounts close. platforms change. Files are renamed. Metadata is stripped. Source systems are migrated. Drafts are deleted.

What strong origin evidence should include

A stronger origin evidence position usually includes:

• The source material — the original file, draft, record, dataset, message, capture, export, or working material.
• The origin claim — what is being claimed about where the record came from.
• Creator or supplier context — who created, supplied, captured, generated, received, or controlled the record.
• System context — the device, application, platform, workflow, repository, account, or process involved.
• Version context — earlier drafts, later versions, edits, exports, or transformations.
• Supporting communications — messages, approvals, instructions, contracts, notes, or logs that explain the source.
• Authority context — whether the person or organisation had the right to create, hold, evidence, or rely on the record.
• Preservation context — where the source material is kept and how it can be recovered.
• Verification context — how the source connection could be checked later.
• Claim boundaries — what the origin evidence does and does not show.

The required level depends on the risk. A casual internal record may need less. A disputed authorship claim, regulated decision, AI training data claim, or public trust statement may need much more.

Common weak points

Origin evidence is usually weak when:

• only the final file is preserved
• drafts or source files are missing
• screenshots are kept without the underlying source
• the record is separated from the account, device, system, or workflow that produced it
• the creator, supplier, or responsible person is unclear
• messages or approvals explaining the source are missing
• metadata is relied on without preserving the file properly
• an upload date is treated as proof of creation
• a platform record is treated as proof of origin
• a dataset is used without preserving provenance or licence context
• AI-assisted output is kept without prompts, inputs, edits, or contribution context
• the origin claim says more than the record can support

These weaknesses make later explanation harder.

How to apply this yourself

For each important record, create a clear origin note.

Ask:

• What is the record?
• Where did it come from?
• Who created, supplied, captured, generated, received, or controlled it?
• What system, platform, device, application, process, or workflow produced it?
• What earlier drafts, versions, inputs, or source materials exist?
• What supporting messages, approvals, contracts, notes, or logs explain the source?
• What claim are we making about origin?
• What part of that claim is directly supported by the evidence?
• What part is only inferred?
• How can the source connection be checked later?

Then preserve the source material and the surrounding context together.

Do not rely on the final file alone if the origin may matter.

What this does not prove

Origin evidence does not automatically prove:

• ownership
• copyright
• permission
• legality
• originality
• authorship
• authenticity
• accuracy
• exclusive control
• absence of dispute
• that the record has not been copied, altered, or challenged
• that EviWrite has verified the origin

Origin evidence helps show where a record came from. It does not decide every claim about that record.

Framework-aligned claim boundary

A person or organisation may use this guide as part of EviWrite Framework alignment if they apply the guidance honestly and avoid implying EviWrite involvement.

Acceptable wording may include:

“We use the EviWrite Framework to preserve origin evidence for important records.”

It must not be used to imply:

• EviWrite has verified the origin
• EviWrite has confirmed authorship
• EviWrite has confirmed ownership
• EviWrite has approved the claim
• the record is EviWrite-backed
• the record is EviWrite-certified
• the record carries the controlled ⓔ mark

Framework-aligned means public guidance was followed.

EviWrite-backed means the record was created through EviWrite or an authorised evidencing channel.

Related checklist

Use the Origin Evidence Checklist to check whether the source material, creator or supplier context, system context, supporting records, and origin claim have been preserved.