elias/claw-code
1
0
Fork 0
mirror of https://github.com/ultraworkers/claw-code.git synced 2026-04-24 13:08:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

roadmap: #165 closed with evidence (cycle #81, commit 1a03359)

Browse Source 
CLAUDE.md Option A implemented. P0 doc-truthfulness family now at 3 closed +
0 open (all 3 fixed within the same dogfood session).

Taxonomy refinement added: P0 doc-truthfulness has three distinct subclasses:
- active misdocumentation (false sentence) — USAGE.md cycle #78
- copy-paste trap (broken example code) — ERROR_HANDLING.md cycle #79
- target/current boundary collapse (v2.0 as v1.0) — CLAUDE.md cycle #81

All three related to #164 (envelope divergence). Root cause consistent across
family; remedies differ per subclass.
This commit is contained in:
YeonGyu-Kim 2026-04-23 05:11:42 +09:00
parent 1a03359bb4
commit 86db2e0b03
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
ROADMAP.md
View File

@ -9117,6 +9117,25 @@ A documentation-vs-implementation divergence can cause different amounts of cons
## Pinpoint #165. CLAUDE.md documents v2.0 (aspirational) envelope as current behavior — P0 active misdocumentation
**Status: ✅ DONE (cycle #81, 2026-04-23 05:15 Seoul, commit `1a03359`). Option A implemented.**
**Fix applied:**
- CLAUDE.md SCHEMAS.md section: now labels 'target v2.0 design' and lists both current v1.0 binary shape + v2.0 target shape
- CLAUDE.md clawable-commands requirements: explicitly separates v1.0 (current) and v2.0 (post-FIX_LOCUS_164) requirements
- Added migration note pointing to FIX_LOCUS_164.md
- Preserves current truth (v1.0 as reality) while clearly labeling v2.0 target as separate future state
**Taxonomy insight (from gaebal-gajae cycle #80 review):** P0 doc-truthfulness has three distinct failure subclasses now:
- USAGE.md: **active misdocumentation** (sentence is false about consistent envelope)
- ERROR_HANDLING.md: **copy-paste trap** (example code would crash against actual binary)
- CLAUDE.md: **target/current boundary collapse** (describes target schema as if it were current reality)
All three are variants of 'doc claims X, binary does Y' but differ in consumer harm profile. Copy-paste trap is worst (immediate crash), boundary collapse is subtlest (gradual misorientation of contract expectations).
---
**Original filing follows below.**
**Status: 📋 FILED (cycle #80, 2026-04-23 05:12 Seoul).**
**Surface.** CLAUDE.md line ~31 states: