[irl-dan]

A calibration can be uniquely solved with zero repricing residual while its physical parameters remain sensitive to uncertain inputs. Rescaling can improve a matrix condition number without reducing that physical uncertainty. This example composes the existing calibration and sensitivity contracts to report those distinctions.

The complete case retains twenty-one scenarios, forty-two native solves and eight condition numbers from one prespecified synthetic calculation. The missing-perturbations case permits analytical uncertainty bounds while withholding seventeen native case records; deriving the bound does not establish that the missing native execution occurred. A third case adds five contradictory producer claims. A 594-word authored reference and twelve interpretation cases accompany the program.

Validation: all 35 offline source commands pass, including twenty inherited unit tests. The new fixed-record checker verifies 1,002 arithmetic correspondences, three exact packet projections, four authored table rows and twelve targeted corruptions without a native solve or provider call. All 438 other original files and all 32 component-package files are unchanged. The retained owned calculation source/plan/observations are copied unchanged, with explicit identities; no fresh public numerical reproduction is claimed.

Reporting and assessment remain agent-unqualified. These synthetic calculations do not establish financial acceptance, statistical confidence, workshop readiness or savings. No reusable definition, runtime behavior or package content changes.

Stacked on #38; draft for review. No merge or release requested.