Claim Boundaries
Claim boundaries define what can safely be said about a record.
They are the line between what the evidence supports and what someone wants the evidence to support.
A record may be useful, but the claim made from it may still be too broad. A timestamp may show that a file existed at a point in time. It does not automatically prove authorship, ownership, permission, legality, originality, or truth. A screenshot may show what appeared on a screen. It does not automatically prove source, sequence, authenticity, or completeness. A framework-aligned process may show that public guidance was followed. It does not mean EviWrite has verified or backed the record.
The purpose of this guide is to help users avoid overclaiming.
Quick Read
- Claim boundaries keep evidence wording accurate.
- A record should only be used to support claims that the preserved evidence can actually justify.
- Poor claim wording can damage otherwise useful evidence by creating false confidence or misleading trust signals.
What this means
Claim boundaries are the control layer around evidence statements.
They apply to internal records, public statements, website badges, reports, receipts, audit summaries, legal positions, customer claims, platform notices, research statements, AI training declarations, synthetic media labels, and any other situation where evidence is used to support a claim.
The key question is simple:
What does the evidence actually support?
A person or organisation should avoid turning a narrow evidence point into a broad conclusion. Evidence that supports existence should not be described as proof of ownership. Evidence that supports publication should not be described as proof of creation. Evidence that supports framework alignment should not be described as EviWrite verification.
Claim boundaries make evidence more credible because they prevent it from being oversold.
Why it matters
Evidence can fail because of the wording attached to it.
A record may be strong for one purpose and weak for another. If the claim is too broad, the evidence becomes vulnerable.
For example, saying “this file existed on this date” is narrower and safer than saying “this proves we own this work.” Saying “we follow the EviWrite Framework” is different from saying “EviWrite verified our evidence.” Saying “this record can be checked against a receipt” is different from saying “this record is legally proven.”
Overstatement creates risk. It can mislead users, customers, counterparties, reviewers, regulators, courts, partners, or the public. It can also weaken trust in the evidence system itself.
Clear claim boundaries prevent that.
What strong claim boundaries should include
A stronger claim-boundary position usually includes:
- The evidence item — the file, record, dataset, receipt, timestamp, screenshot, message, decision, publication, approval, or proof signal being relied on.
- The proposed claim — the wording someone wants to use.
- The supported claim — the narrower statement the evidence can actually support.
- The unsupported claim — what the evidence does not prove.
- The evidence basis — which records support the claim.
- The verification status — whether the evidence has been checked, can be checked, or has not been checked.
- The independence position — whether the evidence depends on the claimant or has an external proof boundary.
- The privacy position — whether the evidence can be checked without unnecessary disclosure.
- The authority position — who is allowed to make the claim.
- The trust-signal position — whether any badge, mark, certificate, receipt, or verification wording is permitted.
- The correction route — how inaccurate claims will be corrected.
Claim boundaries should be set before evidence is used publicly.
Common weak points
Claim boundaries are usually weak when:
- a timestamp is treated as proof of ownership
- an upload date is treated as proof of authorship
- a screenshot is treated as complete proof
- possession of a file is treated as proof of rights
- platform publication is treated as proof of creation
- metadata is treated as proof without source preservation
- “verified” is used without saying what was checked
- “certified” is used without a certification process
- “approved” is used without authority
- “EviWrite-backed” is used for records not created through EviWrite or an authorised evidencing channel
- the controlled ⓔ mark is implied without permission
- framework alignment is presented as EviWrite verification
- legal, ownership, originality, permission, or authenticity claims are inferred without enough evidence
These are not wording details. They are evidence risks.
How to apply this yourself
For each important evidence claim, create a claim-boundary note.
Ask:
- What exact claim do we want to make?
- What evidence supports that claim?
- What is the narrowest accurate version of the claim?
- What does the evidence not prove?
- Has the evidence been independently checked, or can it only be checked later?
- Does the claim imply ownership, authorship, permission, legality, originality, authenticity, approval, certification, or verification?
- Are those implications supported?
- Are we using any badge, mark, receipt, public proof signal, or framework wording?
- Are we allowed to use that wording?
- What correction is needed if the claim is too broad?
Then rewrite the claim until it matches the evidence.
Do not make evidence sound stronger than it is.
What this does not prove
Claim boundaries do not automatically prove:
- ownership
- authorship
- copyright
- permission
- legality
- originality
- authenticity
- accuracy
- completeness
- absence of dispute
- that the evidence has been independently verified
- that EviWrite has approved, certified, or backed the record
Claim boundaries control wording. They do not decide the underlying truth.
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 define claim boundaries for important evidence records.”
It must not be used to imply:
- EviWrite has verified the evidence
- EviWrite has approved the claim
- EviWrite has certified the record
- the record is EviWrite-backed
- the record is EviWrite-sealed
- the record carries the controlled ⓔ mark
- EviWrite has endorsed the organisation’s public statements
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 Claim Boundaries Checklist to check whether evidence wording is accurate, limited, supportable, and free from misleading verification, certification, approval, or EviWrite-backed claims.