---
digest: >
  v0.29.0 is the Ariad Refinement Workbench release. It makes Refinement a
  first-class Builder Mode work field beside Delivery: Builder Home shows
  Workbench state, Refinement Stories and Change Requests persist durably,
  Navigators can compose and pull RSs, traverse CR cycles, and close RS arcs
  with validation evidence preserved while roadmap Delivery remains untouched.
---

# v0.29.0 — Ariad Refinement Workbench

**Date:** 2026-06-17

## Highlights

- Adds Builder Home work fields for Delivery and Refinement, with Workbench state visible during activation.
- Persists Refinement Stories, Change Requests, and active Refinement cursor state in durable SQLite tables.
- Adds conversational and CLI support for creating RSs, capturing CRs, attaching CRs, showing RS overviews, and pulling an RS into active Refinement Work.
- Adds CR lifecycle transitions: select, confirm, plan, mark implemented, validate, and done note.
- Adds RS lifecycle transitions: review, coherence, and close.
- Guards RS closure so unfinished CRs cannot be closed silently; CRs must be done, parked, rejected, or promoted.
- Extends sandbox reset so Workbench stories, change requests, and cursors clear between dogfooding runs.

## Where We Started

`v0.28.0` made Delivery Story flow a first-class Ariad Builder path, but every adjustment still had to live either in roadmap Delivery or in conversational memory. Dogfooding exposed a different kind of work: small or emergent care for existing capability. These requests were real enough to need confirmation, validation, and closure, but too local to deserve roadmap weight.

Ariad already had the conceptual pressure for a third work area. Builder needed the runtime shape: an orientation surface, durable Workbench storage, a way to compose and pull Refinement Stories, a CR cycle for mutations, and RS-level review/coherence/close for the whole refinement arc.

## What Changed

Builder activation now renders a Workbench-aware home surface. The Navigator can see the Delivery field and Refinement field before choosing work. Activation remains orientation only: it does not pull Delivery Work, pull Refinement Work, select CRs, or execute lifecycle work automatically.

The Workbench is durable. Refinement Stories and Change Requests are stored outside roadmap files, with ordering, status, provenance, outcome notes, and active cursor state. Sandbox reset clears this state so dogfooding can start from a clean Workbench.

Refinement composition is now explicit. The Navigator can create an RS, capture CRs, attach existing CRs, inspect an RS overview, and pull an RS into active Refinement Work. Pulling an RS sets the active Refinement Story but deliberately leaves the active Change Request empty.

The CR cycle is now stateful. A CR moves through select, confirm, plan, implementation evidence, validation evidence, and done note. Surfaces show current phase, active cursor state, next conversational move, and the boundary that non-implementation transitions do not mutate files or touch Delivery Work.

The RS can now close coherently. Review and coherence are RS-level checkpoints that do not mutate files. Close requires coherence first and refuses unfinished CRs. When the RS closes, active Refinement state clears while CR outcomes and done notes remain stored.

## Conscious Exclusions

- No release, push, tag, or stable promotion policy was added. That remains the next Builder governance layer.
- No full debt ledger or pay-now Refactor loop was added. Follow-up CRs remain in the Workbench until the debt-ledger story provides durable debt workflow.
- No automatic CR clustering or AI-suggested RS composition was added.
- No web UI for the Workbench was added.
- No quick-refinement shortcut was added as a single atomic command; the composed path is available through RS create, CR capture, and RS pull.
- Refinement does not promote CRs to Delivery automatically. Promotion remains an explicit Navigator decision.

## What We Learned

Refinement is not lighter because it is less disciplined. It is lighter because the unit of commitment is smaller and the roadmap stays clean. The Workbench gives Builder a place to hold care without inflating every friction into Delivery.

The key boundary is the active field. Roadmap items enter Delivery Work. Workbench items enter Refinement Work. Builder Home became the place where that distinction is visible before execution begins.

The dogfood cycle also confirmed that surfaces need to carry state, not just report commands. The Navigator needs to see which CR phase or RS phase is active, what evidence was recorded, what the next move is, and whether files or Delivery state changed.

## Next Horizon

The next release boundary is release and push governance. Builder now has Delivery and Refinement lifecycle closure, but ordinary Done must remain separate from commit, push, tag, stable promotion, and release authorization. CV20.DS7 should make those policies explicit and inspectable.
