Story: FSM consolidation into DQ
Table of Contents
This page documents a story in Sprint 13. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Move the FSM framework into the DQ layer — state machines are metadata for data-quality lifecycles, not their own concern.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 13 |
| Now | Completed 2026-02-20. |
| Waiting on | None. |
| Next | None. |
| Last touched | 2026-02-20 |
Continued from: FSM and trade support (sprint 12). FSM was originally
landed as its own stand-alone slot inside fsm_and_trade_support;
this story recognises FSM as DQ metadata and re-houses it
accordingly.
Acceptance
- SQL identifiers and file paths use the
ores_dq_fsm_*prefix anddq/location. - Notification channels + internal entity strings aligned.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Merge FSM into DQ | DONE | 2026-05-20 | 2026-02-20 | Rename ores_fsm_* SQL identifiers to ores_dq_fsm_*; relocate FSM SQL files into dq/ subdirectories; update notification channel names; rename internal entity strings ores.fsm.* → ores.dq.fsm.*. |
Decisions
- DQ is the metadata framework
- FSM, four-eyes, and similar machinery all naturally live under DQ.
Out of scope
- Re-housing four-eyes (not in this sprint).
See also
- FSM and trade support (sprint 12) — predecessor.