Decision ·
Declare v0.2 burnt → dev after its plaintext was found in git history
From the record
- Context
- v0.2 ruled burnt (plaintext in private bench repo history) → dev
- Why
- Honesty: builders could have seen it
- What followed
- An unexposed held-out number needs a v0.3 written outside the Claude family (0 items as of 10-17; open front OF-3)
- Reversible
- no
- Status
- kept
- Alternatives considered
- Keep calling it held-out
Linked facts · 1
- Declare v0.2 burnt → dev after its plaintext was found in git history — why: Honesty: builders could have seen it — outcome: An unexposed held-out number needs a v0.3 written outside the Claude family (0 items as of 10-1…Declare v0.2 burnt → dev after its plaintext was found in git history — why: Honesty: builders could have seen it — outcome: An unexposed held-out number needs a v0.3 written outside the Claude family (0 items as of 10-17; open front OF-3)Date2026-10-06Kinda record, not a measurement (set, status, judge, n, seeds: not recorded)CaveatVerification note: Public v0.2 row is SET-STATUS:14 (not:17).LaterPartly superseded: v0.2 stays burnt (dev); the "needs a v0.3" path was dropped on 2026-10-18 and replaced by the v0.4 ruler set.Sourceresearch record
reports/SET-STATUS.md:14Open the data file