Status: Accepted, 2026-10-10. Consolidated on 2026-10-12 from 0007 and 0015.
Context#
The first plan gave each version up to 0.5 one theme, which kept users waiting months for work
ready in days and made a version number promise a whole theme. The plan that followed
(docs/dev/plan-zeca.md) grew: Zeca’s memory and work, a companion that speaks when it should, an
Android phone, and leftovers. Holding 0.2.0 until all of it is done would keep the Operations
milestone waiting for work it does not need.
Decision#
- The first release is 0.1.0.
- Releases stay small and frequent: a 0.1.x goes out whenever one or two steps are merged and the R3 smoke check passes; urgent fixes are the next one too. A patch number does not mean “fixes only”, and may pass 9.
- 0.2.0 is tagged at the gate of
plan-zeca.md’s wave 4: the Nest, policies (0004), tasks, starting agents from the app and their review. It ships with the Living Flock layout (0021); the gate is the R3 smoke on that layout, once after U1 and again after U13, and the tag comes after the second. - After it, waves 5 to 7 (the companion, the phone, the leftovers) ship as 0.2.x releases under the same rule.
- Linux first through 0.2.x, with Android as the one exception (0004). Windows and macOS betas may land late in 0.2.x (plan-zeca X7); their full support comes after.
- 1.0 means “done for Linux”.
Consequences#
- Users get each feature when it is ready; the changelog is per release.
- Steps once promised by 0.2.0 that the plan puts later (the command palette, open-mic voice, the side panel, the desktop bird, Vercel, the voice dictionary) arrive in 0.2.x.
plan-zeca.md, Waves, points at this record.
History#
- 0007, 2026-10-04: the first release is 0.1.0; one theme per version up to 0.5 (dropped by 0015).
- 0015, 2026-10-04: small 0.1.x releases, with everything planned by 0.2.0 (narrowed here to the wave 4 gate).