Task: Close the equity model phase
Table of Contents
This page documents a task in the Rework the equity instruments to the instrument table rule story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
The design states the model phase is complete and names exactly what blocks the rest.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Rework the equity instruments to the instrument table rule |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-18 |
3. Acceptance
4. Plan
(Implementation strategy. Written when work starts; key decisions
are distilled into the parent story's * Decisions at close, but the
plan itself stays — it is the historical record of what we did.)
5. Measurements
Every number this task claims about a tree, with the command that produced it
and the commit it was measured at. A number without both is not a measurement,
because a clean-up record describes a tree and trunk moves under a branch: a
consumer count, a gate's component count and a suite's size all change with no
code changing, and the reader of a bare number cannot tell which tree it came
from. Where the raw output matters, put it in an evidence/ file beside the
task and name that file in the Command column.
| What | Value | Command | Commit |
|---|---|---|---|
6. Notes
7. Test Scenarios
Manual QA scenarios (scaffolded via compass add test_scenario)
that verify this task. Link
new ones here as they're created; the scenario doc itself links back
via its "Verifies task" field.
| Scenario | State | Notes |
|---|---|---|
8. PRs
| PR | Title |
|---|---|
| #3503 | [agile] Close the equity model phase |
9. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
10. Result
The design states that the model phase is complete. Fifteen equity entity models, twelve fact tables, the header and the basket child, and every additively-modelled product has its own table.
It also names what blocks the rest, with the evidence that made the difference between a claim and a finding. The three remaining splits and the routing re-point are mapper-coupled, and this was tested rather than assumed: the mapper writes the digital path's barrier columns at lines 578 to 580 and 668 to 669, writes basket_json at line 840 and reads it at 1229, and the routing enum it would have to follow is consumed by the trade component queries and the export service.
Verification is the documentation check: all 39 components pass.