evidence-based-reporting

To prevent unverified claims in diagnostic reports, enforce evidence-first discipline requiring concrete command-line output for every factual statement before documentation. This blocks inference-as-fact by mandating specific citations.

To stop inference-as-fact errors during debugging documentation, mandate that every factual claim passes command-line verification first. You must collect and record the verifiable output before writing the statement.

You need evidence-based reporting for technical documentation when generating plans or diagnostic documents that require strict trust. It ensures every factual statement is backed by collected evidence, preventing incomplete verification.

The best way to verify a process is not running is to execute `ps aux` and record the output. You can only state the claim after capturing this verifiable evidence, even if the output is empty.

Yes, evidence-based reporting works without external dependencies. It enforces its verification discipline natively by mandating specific command-line verifications and citation formats directly within your reports.