Record why an approach was rejected—and when to revisit it

Automated excerpt

A shared invalidation design is now available for review. Keep “needs review,” “reopened,” and “accepted” distinct. For the next code review, try one small check: identify an earlier rejected approach, find its reason, and explain whether that reason still applies.

Selected automatically from source text; not independently written or fact-checked. Read the original for full context.