Independence

Independence

Independence is the separation between the evidence claim and the system or person making that claim.

It asks whether the evidence depends only on the same party, platform, account, device, vendor, database, or internal system that benefits from the claim being accepted.

A record may be useful, but if every important part of the evidence is controlled by the claimant, the evidence may be easier to question.

The purpose of this guide is to help users understand when evidence should cross an independent trust boundary.

Independence matters because stronger evidence often needs to be checkable outside the environment that created it.

Quick Read

• Independence reduces reliance on the party, platform, vendor, account, or system making the claim.
• Stronger evidence often includes an external proof boundary, such as an independently preserved record, trusted timestamp, public proof signal, receipt, audit trail, or verifiable reference.
• Independence strengthens the evidence position, but does not decide every claim about the record.

What this means

Independence does not mean every record must be public.

It means important evidence should not depend entirely on one controlled environment.

For example, a file stored on a creator’s laptop may help show possession, but it is still self-held. A platform upload date may help show publication, but the platform controls the record. An internal business log may help show activity, but the organisation controls the system. A database export may help show a transaction, but the database owner controls the source. A screenshot may help show what was visible, but it is weak if no independent source supports it.

Independent evidence creates distance.

That distance may come from an external timestamp, third-party record, preserved export, audit trail, receipt, public anchor, authorised operator, trusted archive, or other verifiable reference.

Why it matters

Evidence is easier to challenge when the claimant controls every part of it.

A person can change files. A business can alter internal logs. A platform can remove or revise records. A vendor can lose data. A device can be reset. A cloud account can be closed. A screenshot can be edited. A database can be rewritten. A document can be backdated.

This does not mean the claim is false. It means the evidence position may be too captive.

Independence helps reduce that weakness.

It gives the record a point of reference beyond the immediate control of the claimant. That can make the evidence easier to explain, easier to verify, and harder to dismiss as purely self-serving.

What strong independence should include

A stronger independence position usually includes:

• The evidence claim — what the record is being used to support.
• The controlled environment — the person, platform, vendor, account, device, database, repository, or system where the record originated or is held.
• The dependence risk — why relying only on that environment may be weak.
• The independent reference — the external record, timestamp, anchor, receipt, audit trail, export, archive, operator, or proof signal.
• The connection — how the independent reference links to the correct record.
• The timing context — when the independent reference was created.
• The custody context — how the record and independent reference were preserved.
• The verification route — how someone else could check the independent reference later.
• The privacy position — whether independence was achieved without exposing private material unnecessarily.
• The claim boundaries — what independence supports and what it does not support.

Independence is strongest when the external reference is clearly connected to the right record and can be checked later.

Common weak points

Independence is usually weak when:

• evidence exists only on the claimant’s device
• evidence exists only inside the claimant’s internal system
• a platform upload date is treated as independent proof
• screenshots are used without source preservation
• logs are exported only after a dispute appears
• timestamps are created but not tied clearly to the source record
• receipts are stored without the file or context they relate to
• the external reference cannot be checked later
• the independent record proves existence but is claimed to prove ownership, legality, or originality
• public proof exposes private material unnecessarily
• the evidence depends on a vendor that may not preserve records long enough
• the claim overstates what the independent reference can show

Independence must be connected and bounded. A disconnected external reference does little.

How to apply this yourself

For each important record, create an independence note.

Ask:

• What claim may this evidence need to support?
• Who controls the record today?
• What platform, account, vendor, device, database, or system does the evidence depend on?
• Could that source be changed, deleted, lost, closed, or challenged?
• Is there any external reference outside that controlled environment?
• Does the external reference clearly connect to the correct record?
• When was the external reference created?
• Can someone else check it later?
• Can independence be created without exposing private material?
• What does the independent reference not prove?

Then preserve the source material, evidence note, and independent reference together or clearly cross-referenced.

Do not treat internal control as independent evidence.

What this does not prove

Independence does not automatically prove:

• ownership
• authorship
• copyright
• permission
• legality
• originality
• authenticity
• accuracy
• completeness
• absence of alteration
• absence of dispute
• that the underlying claim is true
• that EviWrite has verified or backed the record

Independence can make evidence harder to dismiss as purely self-controlled. It does not decide every issue.

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 improve independence in our evidence records.”

It must not be used to imply:

• EviWrite has independently verified the record
• EviWrite has anchored the record
• EviWrite has approved the claim
• the record is EviWrite-backed
• the record is EviWrite-certified
• the record carries the controlled ⓔ mark
• EviWrite has endorsed the organisation’s evidence process

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 Independence Checklist to check whether important records depend too heavily on one person, account, system, platform, vendor, or internal source.