bi-14 step 03 — The record, including rejections
Goal
Convert code review into durable learning — the part almost everyone skips.
Tasks
For every attempt, landed or not, record:
| Field | Note |
|---|---|
| bug | as the project sees it |
| reproduction | the first thing you lose if unwritten |
| spec | what should happen, implementation-independent |
| suspected subsystem | your prediction — score it |
| source path + call path | so the navigation transfers |
| test | what would have caught this |
| proposed fix | including alternatives you rejected |
| reviewer feedback | the highest-value field |
| architectural lesson | what you now believe that you did not |
- Complete the record for each rung attempted.
- Write the architectural lesson even for rejected CLs. A rejected CL with a clear lesson is a successful lab.
- Score your subsystem predictions across all attempts. Compare with your
bi-01drill accuracy — has navigation calibration improved?
Done when
- A record exists per attempt, rejections included
-
Prediction accuracy compared against
bi-01 -
PROGRESS.mdcontribution ladder updated honestly