Story: Let the model state how the store keeps a column
Table of Contents
This page documents a story in Sprint 29. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
(Describe the user-visible outcome this story delivers.)
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 29 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-31 |
3. Acceptance
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Add a store transform to the mapper and state it on the convention columns | DONE | 2026-10-31 | 2026-10-31 | A generated mapper copies a domain value into the row unchanged unless the model says otherwise. The seven convention columns need the stated spelling turned into the code the store keeps. State a store transform and its header on a column, have the mapper emit the call, and move the ten hand edits onto the model. |
| Repair the generated files main left drifted | DONE | 2026-10-31 | A codegen change renders the whole estate, so the drift gate now reads two files main carries drifted: a generated eventing test hand-edited to name a catalogue feed, and a generated TypeScript view missing two columns its model declares. Both are the same defect the story names: the model is not the whole truth. |