Artifact evidence is not the same as success

Separate observed creation, command execution, visible output, and verified completion; preserve failures and the exact next check.

Separate observed creation, command execution, visible output, and verified completion; preserve failures and the exact next check.

Evidence levels

A file appearing does not prove that its contents work. A command running does not prove that it finished successfully. A successful structural check does not prove behavior in the application. Keep each event separate, attach the relevant artifact or exact signal, and state what remains unverified.

Useful receipts answer: what was attempted; what changed; what was actually observed; which check ran; what passed or failed; what remains uncertain; and what the next session should reproduce. Failed demonstrations are evidence, not editorial blemishes to erase.

The environment examples demonstrate stderr guidance, quarantine behavior, blocked destructive commands, and rewritten issue flags under a test harness. Their own caveats distinguish those results from a live agent’s tendency to comply. The MDFlow example demonstrates inspection and proposal mechanics while retaining an unverified eval roster and a wrapper exercise that did not cleanly succeed. The Markers example is a deliberately planted bug and a bounded redacted trail, not a measured success rate on organic bugs.

Source references