Task: Design the trade shape and document the trade domain it rests on

Settle the target trade shape with the owner, decision by decision, and leave the knowledge base telling one consistent story about it.

• The investigation records sections 1 to 16 with each decision and the alternatives it set aside.
• The knowledge notes the design needed exist and agree with each other: sets, groups and links; netting sets; compression, merge and allocation; book moves; the sandbox.
• The implementation stories are scaffolded.

(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.)

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.

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.

The trade shape is settled and recorded in Investigation: the trade shape, sixteen sections, each with the decision and the alternatives it set aside. The trade becomes an immutable anchor with components per access pattern; sets, groups and links are told apart; activities, authorisation decisions, the agreement and structures are entities; every instrument family follows the rule the bonds arrived at; workspaces leave the trade model and sandboxes replace them.

The knowledge base needed to tell one story first, so the design produced seven notes — Trade sets, groups and links; Netting sets; Trade compression; Trade merge; Trade allocation; Book moves; Sandbox — and brought the link catalogue, Trade Links, Trade Versioning, Trade Activity, Trade Structures, the book cluster and the funding and sweep notes into line. The book move and sandbox notes were checked against Basel RBC25 and MAR12, IFRS 9, EMIR Article 9, MiFIR Article 25 and MiFID II Article 16(6).

Seven implementation stories are in sprint 26 and seven instrument family stories in the backlog. The deal id to trade id rename is a task of its own on the story.