physical-evidence-and-verification

What problem does it solve?

This discipline enforces that every state-changing action is backed by physical evidence to prevent hallucinations, memory drift, and unfounded success claims.

Core Features & Use Cases

• Anti-hallucination and anti-storytelling gates ensure conclusions follow from verifiable data.
• Pre-execution baseline and post-action verification: read the filesystem and git state before changes; verify results after actions to confirm what happened.
• Recovery workflows and structured root-cause analysis to identify failure points, undo unintended changes, and improve trust in outcomes.

Quick Start

Establish a baseline and read state before changes, then perform actions and immediately verify with read_file and git status to capture verifiable evidence.