Task: Decide the publish declaration unit

Choose and record the unit a publish_from_dq declaration is written in, so the facet can express the real relation between the 122 models that opt into an artefact table and the 57 functions that publish them.

• The two candidate declaration units are stated: one declaration per publish function, and a document model that groups the artefact tables one publication writes.
• One is chosen and recorded in the story's Decisions, with the reason and the evidence that decided it.
• curve_configuration (31 artefact tables) and analytics' today's market (5) are checked against the chosen unit and both are expressible.

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