2 Commits

Author SHA1 Message Date
claude 5cae33a517 Split honesty into three milestones, defer five capabilities (V-719)
Owner's call. M1 is the turn path, M2 is memory he cannot correct, M3 is
step-up. They were one milestone and are three jobs: M1 and M2 touch
different code and owe different docs, and step-up is configuration, not
honesty. Nine milestones now.

Speaker recognition, smart home, bluetooth, model swap and self-update
move past v1. Bluetooth was on the v1 list and comes off it: no bluez on
the box. Their spec entries keep their DoD.

--no-verify: committing on master by the owner's call this session.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-15 18:40:45 +04:00
claude 78a9c61acb Write the capability spec with a DoD for each (V-719)
51 capabilities: the 39 rows from the 2026-08-13 audit plus 12 v1 items
that had no audit row. Each entry carries a state reference to the living
doc that owns it, a plain DoD list observable on the running box, and the
scenario file that scopes it.

Applying "state is a reference" found 17 capabilities with no living doc.
Only 5 of 51 entries cite a scenario that exists.

--no-verify: committing on master by the owner's call this session.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-15 18:21:36 +04:00