agent-verification-discipline

To verify code state and file contents before completion reporting, inspect source files, run tests, and check command results to gather explicit evidence. This verification discipline requires deterministic proof of diffs and machine state before any assertion is made.

Evidence-based debugging prevents false assumptions by requiring source inspection and minimal deterministic verification of logs and machine state before asserting facts. This method forces explicit handling of uncertainty rather than relying on stale assumptions during bug investigation.

Performing a reliable code review with repository inspection requires checking file contents, diffs, and versions against the actual live machine facts. This verification process ensures that security validation and factual answers are backed by inspected source evidence.

Yes, you can use verification checks for security validation and repo inspection. The process applies evidence-first checking to confirm file contents, tests, and machine state, ensuring security claims are validated through deterministic source inspection before action.

The best way to handle uncertainty when verifying live machine facts is to enforce explicit uncertainty handling alongside minimal deterministic verification. This approach requires gathering concrete proof from command results and inspected diffs before closing a task or reporting findings.

You need source inspection for factual answers in software engineering whenever you must verify claims, code state, or versions before taking action. This discipline applies to debugging, code review, and completion reporting to prevent false claims and incorrect changes.