Bounded answer
Record conflicting evidence as separate, versioned propositions with their scopes and uncertainty; do not average disagreement into a confident sentence or choose a preferred source silently. For DOI version relationships, preserve the DOI, publisher record, preprint or manuscript, version of record, correction, and access copy.
Input contract
What must be fixed first
Claim and scope
Each conflicting source and locator
Version and publication relationship
Declared uncertainty or unresolved question
Procedure
Work the decision in order
- 1
Normalize the propositions without erasing scope.
- 2
Inspect each cited passage independently.
- 3
Classify direct contradiction, scope difference, or version change.
- 4
Preserve uncertainty and missing evidence.
- 5
State what evidence could resolve the conflict.
Expected outputs
- Typed conflict record
- Scope comparison
- Unresolved-evidence requirement
Refuse when
- One side has not been inspected.
- Different populations or definitions are called contradictions.
- A later source silently overwrites historical evidence.
- A DOI identifies a work or version according to its registration; it does not prove that every hosted copy is textually identical.
Questions this guide answers
How should conflict and uncertainty be recorded for DOI version relationship?
Record conflicting evidence as separate, versioned propositions with their scopes and uncertainty; do not average disagreement into a confident sentence or choose a preferred source silently. Preserve the DOI, publisher record, preprint or manuscript, version of record, correction, and access copy.
What must be preserved for DOI version relationships?
The DOI, publisher record, preprint or manuscript, version of record, correction, and access copy.
When must the protocol refuse?
It must refuse when one side has not been inspected. or when the identified source cannot be inspected at the required depth.
Does a successful preflight verify the claim?
No. It shows that the evidence request is sufficiently structured to begin inspection; factual verification remains a separate stage.
What does this protocol not establish about DOI version relationships?
A DOI identifies a work or version according to its registration; it does not prove that every hosted copy is textually identical.
Limits
- A DOI identifies a work or version according to its registration; it does not prove that every hosted copy is textually identical.
- This protocol produces a preflight or evidence-structure finding, not a verified Evidence Dossier.
- No source is treated as inspected merely because its metadata or identifier resolves.