Tier 2 · Content pipelines and provenance
Keep a project pitfall file
Record symptoms, evidence, rules and verification with their source.
Record the failure before generalizing
Keep a project-local pitfall file. For each entry record the symptom, affected versions and configuration, minimal reproduction, expected and observed behavior, evidence location, cause when established, corrective rule, and verification result. Mark an unconfirmed cause as unconfirmed; do not turn it into a universal rule.
Keep the evidence with the rule
Retain the source and incident footnote when moving a rule to its owning topic. Use a reason footnote only for an actual incident. Separate project defaults from observed engine behavior. Before promoting an entry, check whether an existing rule already covers it and link that rule instead of duplicating it.
Verify and maintain
Repeat the reproduction after the fix and record the tested versions. Revisit version-dependent advice when packages change. Preserve the earlier evidence when revising an entry. Specialized pitfalls are listed beside their owning workflows in the topic navigation.