Source and Context Hygiene
Source hygiene rules cover turning mined lessons into public guidance, preferring stable sources, keeping binary artifacts out of history, and keeping local or private context out...
Shared-history boundaries, source material, and reusable public guidance.
4 rules
Generalize Project-Specific RulesSOURCE-GENERALIZE-PROJECT-SPECIFIC-RULESExtract the portable failure mode before promoting local lessons into shared guidance. Provider, repo, or tool details should stay local unless they clarify the durable rule.Keep Binaries Out of Source ControlSOURCE-KEEP-BINARIES-OUT-OF-SOURCE-CONTROLStore large or opaque artifacts in systems designed for assets, releases, CI evidence, or external data. Keeping source history textual and reviewable avoids clone cost and painful history rewrites.Make Shared Artifacts StandaloneSOURCE-MAKE-SHARED-ARTIFACTS-STANDALONERestate the problem, rationale, evidence, and tradeoffs in shared docs, templates, generated packs, or reusable guidance. Future readers should not need private notes or transcripts to trust the artifact.Prefer Primary Stable SourcesSOURCE-PREFER-PRIMARY-STABLE-SOURCESAnchor durable guidance in sources readers can inspect, compare, and challenge. Use links to clarify judgment, not to decorate rules or depend on private memory.