-
Notifications
You must be signed in to change notification settings - Fork 3
Evidence‑and‑Claims
Pheonetic Coder edited this page Aug 25, 2025
·
1 revision
Maintaining a clear record of evidence and claims is essential for traceability and trust in the Genesis Code Protocol. During a run, capture all data, notes, calculations and code outputs relevant to your Spark. Store each item in the Evidence directory and record its metadata in Evidence_Index.jsonl. Use ClaimGraph.json to map hypotheses to supporting or refuting evidence and Source_Reliability.csv to rate the credibility of sources.
- Capture evidence immediately. Record evidence as soon as it is produced, including timestamps, phase numbers and descriptive notes.
- Assign unique identifiers. Give each piece of evidence a unique ID and reference it in the claim graph.
- Assess source reliability. Evaluate the credibility of your data sources and document any limitations, uncertainties or biases.
- Separate raw and processed data. Keep raw data separate from processed results to facilitate reanalysis and reproducibility.
- Link evidence to reproduction protocols. Connect each evidence entry to the corresponding reproduction steps and results.
Consistent evidence management improves reproducibility and supports the construction of a defensible Invention Package.