Home
AI Evidence Gap Notes
Implementation Note
Awesome GRC Workflows
Signals
About
Home
AI Evidence Gap Notes
Implementation Note
Awesome GRC Workflows
Signals
About
Subscribe
Sign in
Implementation Note
Corrected Evidence Must Not Erase the Original
Why evidence revision needs lineage, not a replacement JSON file
Oct 19
•
CodeYourCompliance
A Timestamp Field Does Not Prove When Evidence Existed
Why evidence time needs provenance, not just UTC
Sep 25
•
CodeYourCompliance
An Empty Result Does Not Prove Absence
Why collection outcome has to survive the evidence pipeline
Sep 14
•
CodeYourCompliance
1
A Changed Control Result Does Not Mean the System Changed
Why policy evaluation provenance belongs in replayable evidence
Aug 31
•
CodeYourCompliance
The Collector Is Part of the Evidence
Why collection metadata belongs in the proof chain
Aug 17
•
CodeYourCompliance
2
Invalid Evidence Is Not a Failed Control
Why Evidence Admissibility Must Gate Policy Evaluation
Aug 8
•
CodeYourCompliance
1
A Control Result Is Not Replayable Evidence
Why PASS/FAIL cannot show whether the system changed, the decision conditions changed, or the original conclusion can still be replayed.
Jul 31
•
CodeYourCompliance
1
From Evidence Principles to an Executable Control
The next stage of CodeYourCompliance is not another checklist. It is a small, replayable implementation showing how raw evidence becomes an assessment…
Jul 20
•
CodeYourCompliance
This site requires JavaScript to run correctly. Please
turn on JavaScript
or unblock scripts
