What is directly present?
Record the original artifact, event, timestamp, source path, and custody before adding interpretation.
Evidence Packet Workbench
Build a caseboard that
preserves uncertainty.
Create evidence nodes, connect support and contradiction, record provenance and custody, and export the packet locally. The visual board is paired with a complete structured-list representation.
Direct answer
How should this evidence packet express attribution?
Start with one bounded proposition and connect only the support or contradiction actually represented by each node. The public evidence-attribution method treats claim status, analytic confidence, source reliability, coordination, actor identity, sponsorship, intent, reach, and effect as separate fields. Repeated reporting from one origin is not independent corroboration, and provenance metadata is not a truth verdict.
- Correction
- Preserve earlier nodes and supersede visibly
Before adding a node
Name the evidence layer.
The numeric confidence field is retained for backward compatibility with the existing evidence-packet schema. It does not replace a written claim status, source-reliability assessment, assumptions, counterevidence, or the highest supported attribution rung.
What is being inferred?
State assumptions, alternatives, confidence, source quality, and what evidence would change the judgment.
Which rung is supported?
Do not let content, coordination, identity, sponsor, intent, reach, or effect collapse into one label.
Local packet
Untitled evidence packet
No nodesVisual caseboard
Relationships among claims and evidence
ObservationSource reportHypothesisContradiction
Accessible representation
