Skip to content

Evidence Preservation Requirements

Purpose

Evidence preservation ensures that governance decisions remain traceable, auditable, and reproducible.

Evidence must exist before execution authorization can be considered.

Evidence Preservation Model

evidence_requirements:
  before_change:
    - baseline_hashes
    - configuration_snapshot
    - state_export
  after_change:
    - validation_results
    - updated_hashes
    - audit_logs
    - reviewer_attestation
  retention:
    - markdown_record
    - issue_json
    - evidence_summary
    - audit_report

Evidence First Rule

The following statements are always true:

evidence_first:
  review_comments:
    are_not_evidence
  proposed_fixes:
    are_not_implemented
  implemented_changes:
    are_not_verified
  verified_changes:
    require_evidence

Required Before Change

Prior to any future execution activity:

  • Capture baseline hashes
  • Capture configuration snapshot
  • Export current state
  • Preserve existing evidence records

Required After Change

Following any future execution activity:

  • Capture validation results
  • Capture updated hashes
  • Capture audit logs
  • Capture reviewer attestation

Retention Artifacts

Required retained artifacts:

  • Markdown records
  • Issue records
  • Evidence summaries
  • Audit reports

Deletion of evidence artifacts is prohibited unless explicitly authorized by governance policy.