What NOT to Save

Before saving, ask whether persistence and this audience are authorized, whether a maintained source already exists, and what a future session would otherwise get wrong.

Do not copy credentials, unnecessary personal data, raw private transcripts or private model reasoning. Do not duplicate dependency versions, code structure, full task histories or deployment status. Link to the source and keep only the non-obvious lesson or reason.

The correct authority depends on the claim: code shows implementation; approved business intent defines expected meaning; runtime evidence shows deployed behavior. A mined legacy rule is an observation until validated. Keep private exploration private; global promotion needs separate applicability and sharing authority.