Task: Map the analytics documents that have no mapper

Simulation, sensitivity analysis, SIMM calibration and the cross asset model are the largest of the unmapped families and the ones that reach most of the schema. They come last because nothing depends on them yet.

• Each of the four documents has a domain model and a table.
• Each reads, writes back and validates.
• The share of the schema the tables cover is recorded and visible.

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