-
Notifications
You must be signed in to change notification settings - Fork 3
Artifacts‑and‑Ledgers
Every Genesis Code Protocol run produces a set of artifacts organised into categories. These artifacts document evidence, reproducibility protocols, provenance data and index files. Ledgers record decisions and processes throughout the run.
Includes the Evidence_Index.jsonl (list of evidence files), ClaimGraph.json (graph linking hypotheses to supporting or refuting evidence) and Source_Reliability.csv (ratings of evidence sources).
Contains the REPRO_PROTOCOL.md (step‑by‑step reproduction instructions), REPRO_RESULTS.csv (original experiment results) and ENV_LOCKFILE.yml (software and hardware environment details).
Holds software and AI bills of materials (SBOM/AI‑BOM), signature bundles and attestations for verifying authenticity and provenance.
The Gate_Signals.json file records the status of each gate (allow, deny or needs‑human) across all phases.
Index files such as INDEX.md and MANIFEST.json summarise all artifacts and their locations within the run directory.
The Exit Wizard packages the final deliverables into an export (ZIP or PDF‑A) for archiving, submission or publication.
Two ledgers track process and decisions:
- DECISION_LEDGER – logs all gate decisions, model recommendations and user overrides.
- PROCESS_LEDGER – records major actions, tool calls, file writes and timing/cost metrics throughout the run.
These ledgers provide an auditable history of the run and should be updated at each phase. Keep them current to support reproducibility, compliance and provenance.