01 · PROBLEM
Answer "why is the code this way and what alternatives were rejected" for any line.
02 · HYPOTHESIS
Every landing records chosen candidate, rejected candidates (links to read-only forks), conflict resolutions, reviewer decision, as Agent-Trace-compatible notes; `why <file:line>` walks blame -> ledger.
03 · EVIDENCE SO FAR
LATESTNot tested. The agents gathered reports of the pain behind this idea and scored it on paper only; no experiment has been run on it. Cited pain: E-C161; Agent Trace leaves rebase/storage open (E-C335); "why" in announcement (E-C005); workflows gap 5 (provenance that survives integration).website/projects.json
04 · NEXT FALSIFICATION TEST
Not yet scheduled. Smallest demo on record: after a tournament (A05) or conflict, `why` shows the losing alternative and reason.
StatusNot selected; parked without a test
We would drop or park it ifIf in a blind archaeology task the ledger does not change the engineer's answer vs plain blame+PR text, kill.