Task: Publish the conventions as a configuration document

The conventions are published reference data, but the report type requires a conventions configuration. Decide what a conventions configuration is for a party, publish it, and make it depend on the convention datasets.

• Each party holds a conventions configuration that a definition can bind to, published after its conventions.
• The dataset declares its dependency on the convention datasets.

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

Retired on 2026-10-11. The task "Store the report configuration documents in DQ and populate ACME's" covers this work in one deliverable: phase A adds the DQ side of the four required kinds, and the ACME datasets follow in its second part.