You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
E4---R["Provenance first; custody transitions recorded; production attributable; release separately verified"]
48
+
```
49
+
50
+
## Evidence record identity
51
+
52
+
A stage record SHOULD identify, where applicable:
53
+
54
+
- `evidence_id` — unique evidence record identifier.
55
+
- `parent_id` — identifier of the preceding or source record.
56
+
- `stage` — `origin`, `custody`, `production`, or `release`.
57
+
- `subject` — thing, work, transaction, program, or event being described.
58
+
- `actor` — person, organization, process, or system performing an action.
59
+
- `custodian` — party or system responsible for custody/control.
60
+
- `jurisdiction` — relevant jurisdiction or governing context.
61
+
- `timestamp` — event time or document time.
62
+
- `location` — relevant physical or logical location.
63
+
- `action` — event performed.
64
+
- `input` — material or state entering the event.
65
+
- `output` — material or state resulting from the event.
66
+
- `source` — source record or evidence reference.
67
+
- `authority` — authority relied upon for an action or release.
68
+
- `hash` — integrity digest when available.
69
+
- `signature` — signing or attestation information when available.
70
+
- `verification` — verification state and method.
71
+
- `notes` — additional factual context.
72
+
73
+
Material unknown values SHOULD be explicitly represented as `unknown`, `not-applicable`, or `not-recorded` rather than silently converted into facts.
74
+
75
+
## 1 — Origin
76
+
77
+
Origin establishes where the chain begins. It may identify an originating record, source artifact, initiating request, transaction, observation, or other event.
78
+
79
+
Origin does not by itself establish the truth of every proposition contained in a source. It establishes provenance for the chain and gives later records a reference point.
80
+
81
+
## 2 — Custody
82
+
83
+
Custody records changes in possession, control, stewardship, or responsible system. Each material transition SHOULD identify the prior and subsequent custodian and the event connecting them.
84
+
85
+
The custody record should preserve the distinction between physical possession, logical access, ownership, authority, and documentary responsibility where those concepts differ.
86
+
87
+
## 3 — Production
88
+
89
+
Production records what was actually done with the subject or input: execution, transformation, compilation, manufacture, processing, program operation, or another attributable production event.
90
+
91
+
Production SHOULD identify the actor/process, relevant inputs and outputs, execution time, environment where material, and verification evidence.
92
+
93
+
## 4 — Release
94
+
95
+
Release records the authorized disposition or outward transition of the produced result: publication, delivery, deployment, transfer, or other release.
96
+
97
+
Release SHOULD be separately verified from production. Producing something does not, by itself, establish authorization to release it.
98
+
99
+
## FACT / Economy
100
+
101
+
**FACT / Economy** identifies the documentary layer for observable or sourced facts concerning resources, transactions, inputs, outputs, ownership, custody, costs, or economic activity.
102
+
103
+
Economic claims SHOULD remain traceable to their source records and should not be treated as verified merely because they appear in this graph.
104
+
105
+
## Morals / Program Governance
106
+
107
+
**Morals / Program Governance** identifies declared principles, constraints, duties, policies, standards, or governance rules used to guide a program.
108
+
109
+
This category records governance material; it does not automatically make a moral, legal, or policy proposition universally authoritative.
110
+
111
+
## Programs / Release
112
+
113
+
**Programs / Release** identifies operational program activity and the state in which an output is authorized or intended to be released.
114
+
115
+
Program execution and release authorization SHOULD remain separately identifiable so that the chain distinguishes what a program did from what a responsible authority permitted to leave the controlled process.
116
+
117
+
## Chain-of-evidence rule
118
+
119
+
A reviewer SHOULD be able to move backward from a release to its production record, from production to its custody/input records, and from custody to the originating record, preserving:
The evidence graph is a provenance structure. It does **not** turn an unsupported assertion into a fact merely because the assertion is represented as a node or edge.
124
+
125
+
## Integrity and revision
126
+
127
+
When practical, evidence documents SHOULD retain:
128
+
129
+
- document content hash;
130
+
- parent-document hash or identifier;
131
+
- author or actor identity;
132
+
- creation and modification timestamps;
133
+
- repository commit or transaction identifier;
134
+
- verification result.
135
+
136
+
Substantive changes SHOULD produce a new revision or otherwise preserve the historical record rather than silently changing the meaning of an earlier evidence state.
137
+
138
+
## Evidence principle
139
+
140
+
> Provenance first; custody transitions are recorded; production is attributable; release is separately verified.
141
+
142
+
## Technical scope and non-claims
143
+
144
+
This `.mmd` convention is a technical documentation and provenance format. It does not by itself determine legal custody, governmental ownership, citizenship, moral correctness, economic value, or admissibility of evidence. Those determinations remain dependent upon applicable source records, authorities, laws, policies, and independent review.
145
+
146
+
The document can be rendered as Mermaid-compatible material while remaining ordinary UTF-8 text. A renderer may use the front matter as metadata or ignore it and render the Mermaid body.
15
147
16
-
S["File convention: US-EVIDENCE-<stage>.mmd"]
17
-
E4---S
148
+
## Relationship to the descriptor
18
149
19
-
R["Evidence principle: provenance first; custody transitions are recorded; production is attributable; release is separately verified."]
20
-
E4---R
150
+
The companion `US-EVIDENCE-DOCUMENT-TYPE.mmd` defines the broader document-type specification. This file is the canonical 1, 2, 3, 4 evidence-chain document and incorporates the operational rules necessary to use that specification directly.
0 commit comments