Story: Party database groundwork
Table of Contents
This page documents a story in Sprint 09. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Lay the first SQL table for party so subsequent sprints can build
the domain layer + UI on top. Postponed within sprint 09.
Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent sprint | Sprint 09 |
| Now | Postponed in sprint 09; carried forward. |
| Waiting on | A sprint with the slot to land the table + domain layer together. |
| Next | Return alongside the party domain layer work. |
| Last touched | 2026-01-20 |
Continued in: Party schemes and FPML reference data (sprint 10) — lands the 13 reference-data types needed before party can be implemented.
Acceptance
party_tblcolumn list documented and reviewed.- FK targets identified (tenant, party_type scheme, business_center).
- Task ready to pick up in a later sprint.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Party table structure | BACKLOG | 2026-05-19 | First-cut SQL table for party (LEI, tenant_id, party_type_id, business_center_id, status, etc.). Foundation for later domain layer + UI. |
Decisions
- Postpone rather than half-do
- only 20 minutes of v0 work landed; better to roll the table-creation into the sprint that also tackles the domain layer.
Out of scope
- Party domain layer (C++).
- Party UI.
See also
None.