science(workforce-validation): require resolvable authority for every material final-weight adjustment #423

Finding

Fresh review of canonical Workforce Validation owner PR #235 at predecessor 89b1334c1a036437ae1f0e37a7058fca8f7aeb82 found a remaining reproducibility gap: FinalWeightAdjustmentCoordinate admitted an unrecognized material transform with only a digest even though no released deterministic owner-record resolver existed. A digest is integrity evidence, not an owner locator.

RED → causal repair

• d7aa67c6d2550a0b3ff8d790e845667009d02438: source-first hostile regression requiring an ungoverned custom transform to fail closed.
• 17b80f9e360dc82bf93c6831c2c6d3504af50a90: minimal production guard rejecting adjustment_code values absent from the governed specialized evidence map.
• 9625f95dc3b90ba119c462a7587accf2c4f068e1: aligns the stale predecessor generic-transform test.
• e4945f0bcea20aff5cc5dee3f86a9964ddbb3107: records the rule in CHANGELOG.
• 57214b4968c5968a4009cad56ea9d23a186ee9d9: predecessor provenance reseal for the science(workforce-validation): require resolvable authority for every material final-weight adjustment #423-only CHANGELOG state.

#424 is additive: because every admitted material adjustment is now governed, component-binding owner records must also carry a contiguous one-based receipt sequence rather than preserving holes for hypothetical generic steps. That later repair does not weaken or supersede #423.

A future adjustment family may be admitted only together with a released/versioned owner receipt namespace, exact reference/version/digest identity, deterministic purpose-bound owner resolution, canonical reconstruction, binding/corroboration semantics and release/currentness verification.

Current evidence boundary

Canonical #235 is now exact 03bf5040e7eb307c4df55ebd01453dcbd1ae0cef, open · Ready · mechanically mergeable. 03bf5040... is a documentation-only successor that repaired stale README language left behind by #423/#424: the README now states that every admitted governed adjustment requires an exact binding and that binding sequences are contiguous and one-based. The README is not a manifest.json inventory member, so no unrelated manifest churn was introduced.

Independent exact-tree verification was last acquired at predecessor 731b5e9605f0d4d8f27e45920c68b73da2d44be0: 1,441/1,441 service and built-wheel tests, 5,186/5,186 statements and 1,116/1,116 branches (100%), Foundation 23/23, repository/manifest validation, warnings-as-errors compileall and diff check. Those exact-head counts are not transferred to 03bf5040.... Current-head Foundation/Security/SAST/CodeQL runs were created and remain queued; PostgreSQL owner-schema evidence and a qualifying independent current-head approval remain outstanding.

Ready is review admission only. No merge, immutable release or release-ready claim is made.

Completion boundary

Keep open through current exact-head functional/coverage/docstring/wheel/PostgreSQL/provenance/hosted-check/independent-review GREEN, normal protected #235 integration and durable #248 adoption or a verified successor. Do not close merely because the source admission gap is repaired.