A result should have a basis.
Project evidence can include a source reference, a versioned artifact, a test result or a receipt from an external action. Its job is to support a specific claim.
A screenshot may demonstrate appearance. A build result may demonstrate compilation. Neither proves that a production deployment succeeded. Evidence should match the thing being asserted.
Distinguish observation from inference.
Record what the system observed, what it inferred, and what remains uncertain. Preserve the identifiers and versions needed to recover the underlying record.
Sensitive details should remain in an appropriately controlled location. A public summary can point to the existence of evidence without disclosing private data.
Use lessons to change the next action.
A useful lesson describes the failure, the intervention, the observed outcome and the environment where it applies. Record its application in a later project so learning has a visible effect.