Concepts
Evidence-first investigations
Why Mike Trace keeps evidence separate from claims and conclusions.
Debugging often goes wrong when a confident statement is mistaken for proof. Mike Trace is built to prevent that.
Keeping things apart
Mike Trace keeps a clear distinction between:
- What someone said: a bug report, a hunch, an agent’s suggestion.
- What was observed: a screenshot, a measurement, a reproduced failure.
- What was concluded: the explanation the evidence supports.
A claim doesn’t quietly become a fact just because it was repeated or because it came from someone senior. Conclusions need evidence behind them before an investigation can be closed.
Human reports are preserved
When a person describes a problem, their words are kept as written. Agents can add their own interpretation alongside, but they never overwrite the original.
Verification is evidence
“It’s fixed” isn’t enough on its own. A fix is considered verified when there is fresh evidence, gathered after the change, showing that the problem is gone.
Ruled-out explanations matter
The explanations you rejected, and why, are part of the record. They stop the next person, or the next agent, from walking the same dead end.