Charles Jones#Evidence
6pages on this subject — across the log, the case studies and the documentation.
Entry 002 — A control was fabricated, then read as evidence
Four artifacts sat in the evidence base as controls. Their bytes never came from the run they claimed to describe, and nothing about the set announced itself as wrong.
How to read your recording
If we sent you a recording of what an assistant saw on your site, this explains what you are looking at.
Every figure is a pointer
A number inherited from a previous session, a state file, or a tool is re-measured before it is acted on.
A gate that never ran is never clean
Silence from a check and success from a check are indistinguishable unless you make them different.
Nothing filed is rewritten
Corrections sit beside what they correct, dated. The record is append-only.
A control is captured, never authored
Evidence has to come from the run it claims to describe. A well-formed file passes every check that asks whether it is well-formed.