Story: Variability service
Table of Contents
This page documents a story in Sprint 06. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
Stand up ores.variability as a proper service: feature-flag domain
model + repository + messaging surface. Closes the feature-flags
thread that started as POSTPONED in sprint 03.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 06 |
| Now | Completed 2025-12-08. |
| Waiting on | None. |
| Next | None. |
| Last touched | 2025-12-08 |
3. Acceptance
- Variability domain type defined.
- Repository persists via sqlgen.
- Messaging surface exposes list / toggle / read operations.
- REPL and Qt UI can read and toggle flags.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Create a variability service for feature flags | DONE | 2025-12-08 | 2025-12-08 | Stand up ores.variability service: feature-flag domain model + repository + messaging. |
| Add messaging to variability | DONE | 2025-12-08 | 2025-12-08 | Wire the variability service onto the comms layer so clients can list / toggle feature flags. |
5. Decisions
- Variability as its own service
- keeps it independent of accounts (which is where feature flags lived by accident).
6. See also
- Split feature flags out of accounts (sprint 05) — the work that made this story possible.
- ores.variability — the component this story stood up.