Task: Prove the full pipeline against live data

Run a definition whose configuration executes every phase, from live trades and market data through to results recorded in the database, and show that the two chains differ only in the phases between them.

• The input artifact is generated from live data and the engine accepts it.
• The engine's results are queryable in the result store after the run.
• The four phases the substituted chain also runs behave identically in both runs.

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