Task: Carry the credit digits

Every credit money value is stored and exported as the digits the document wrote, and every credit numeric column has the type its kind needs: money is an exact decimal, a continuous quantity is a binary float, and the column and the domain type agree.

• UpfrontFee and Strike keep the document's digits, through the reapply script.
• A continuous quantity (FixedRecoveryRate, AttachmentPoint, DetachmentPoint, ParticipationRate) stays a binary float.
• The tranche columns are double precision, so each column agrees with its domain type; recovery_rate stays double precision.
• A mapper test holds the digits of the money member the mapper stores, and the goldens that change are numeric text only.
• The ORE suite passes.

1. Classify. Sort every credit numeric column and binding member into money or continuous, with the exact-money check of the data-oriented design page. Money is an exact decimal. A continuous quantity stays a binary float. The column and the domain type must agree.
2. The binding. Add a table of credit money members to the reapply script: the two UpfrontFee members and the index option's Strike. The script patches the struct, the getter, the element info and the serializer of each, and it refuses an anchor that is missing or not unique.
3. The mapper. The forward mapping already reads a lexical leaf through exact_decimal. The reverse mapping writes the strike with set_exact, which moves to the boundary header so both mappers share it.
4. The tranche columns. The tranche points are continuous quantities. Their columns become double precision, so they agree with their double domain type.
5. Tests and goldens. A mapper test holds the strike's digits, a binding test holds the strike and the upfront fee, and the goldens that change are regenerated.

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.

• The first version of this unit made the recovery rate, the tranche points and the participation rate lexical leaves and the recovery rate an exact decimal. That was wrong. The data-oriented design page lists the recovery rate and the tranche fraction as continuous quantities, which stay binary floats, and the review criteria the data-model skill walks showed the contradiction. The unit was corrected before it was raised: those members are not leaves, the recovery rate keeps its type, and the tranche columns follow their domain type. The participation rate is treated as continuous like a weight; the page does not name it, so the operator can overrule that.
• The design, the ER diagram, the memory and the runbook carried the same mistake and are corrected in this unit.

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 credit money members keep the document's digits. The upfront fee and the option strike are lexical leaves in the ORE binding, patched in by the reapply script, and the strike is read and written through them. The continuous quantities, the recovery rate, the tranche points and the participation rate, stay binary floats, as the data-oriented design rule says, and the tranche columns are double precision so each agrees with its domain type.

Three golden files changed, one numeric line each. The ORE suite, the trading suite after a database recreate, the codegen tests and the SQL hygiene check pass.

Acceptance met: the money members keep their digits through the script, the continuous quantities stay floats, the tranche columns agree with their domain type, a mapper test and a binding test hold the digits, and the ORE suite passes.