Wheel reinvention audit

A wheel-reinvention audit asks whether custom code is carrying a solved capability that a project or ecosystem owner should carry.

Procedure

1. State the desired outcome in one plain sentence. Separate it from the proposed implementation, dependency, or first example.

   Completion criterion: OUTCOME describes observable behavior without naming how to build it.

2. Pin the audit surface. Use the proposed design when code does not exist, the changed files and their diff when a change exists, or the named files when auditing existing code. Record the paths and comparison point.

   Completion criterion: every conclusion can be traced to a named file, diff, or proposal section.