Task: Seed an inflation curve the tenant holds

A provisioned tenant holds an inflation curve with an index a trade can name, and its fixings.

• The tenant holds at least one inflation curve config with its curve definition and the conventions it needs.
• A trade naming that index resolves it. The trade itself is the family's task; this one states the curve the trade names.
• The seed is idempotent and arrives with the ACME profile, not by hand.

State the index, then the curve, in the document the tenant already reads.

The index is the one the refdata catalogue names for the book's currency: UKRPIX for GBP, USCPIA for USD and BECPIHL for EUR. It is stated once, in the seeder's configuration generator, and the curve definitions are derived from it, so a currency whose catalogue row changes index changes in one place.

The curve travels as a ZeroInflation curve definition inside the curve configuration artefact, which is the document the tenant's publish step already reads for its discount curves. Its conventions column states <INDEX>_INFLATIONSWAP, a row the tenant's 110 inflation swap conventions already carry, so the curve resolves through a convention that exists rather than through one the seed invents.

Two things the seed states negatively, because the store refuses a guess:

• No extrapolation. The curve.flag value set arrives empty at publish time, so the guard refuses every value, and a curve that states none takes the engine's default.
• No seasonality factors and no fixings. They are the family's own market data, and the story's rule is that a class whose market data is absent still books; the family's task says what it cannot prove yet. Recorded as the capture The seeded inflation curve states its index, its conventions and no fixings.

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 tenant holds ten zero coupon inflation curves, one per entity and currency whose index the refdata catalogue carries: UKRPIX for GBP, USCPIA for USD and BECPIHL for EUR, published as curve definitions inside the same curve configuration document as the discount curves, through the artefact the tenant already reads. Each names the inflation swap convention its index holds. A curve states no extrapolation, because the curve.flag value set arrives empty and the guard refuses every value; a curve that states none takes the engine's default rather than a guessed word.

Two defects blocked the run that measures them, and both are fixed on main by their own tasks: the planner's month arithmetic invented the 31st of September and the wire wrote it as the absent date, which is A generated date is a real date; and two bond products of one term claimed one issue, which is A security is named by its product. With both, the provisioning run completes.

Measured on a fresh tenant:

The inflation family itself still books nothing: it has no planner, which is the task Populate the inflation family, and the curves are what that task needs. The curves state no fixings and no seasonality factors, so pricing an inflation swap has nothing to read yet; that is captured as The seeded inflation curve states its index, its conventions and no fixings rather than guessed at here.