Skip to content

Adult-care transfer: align QRF donor clone with the battery comparator (diagnosis option 4) #671

Description

@MaxGhenis

Chartered from the #660 battery diagnosis (Max ratified 8/13). Scoped, 2–4 day fix; independent of the calibration epic.

Mechanism (fully receipted in the diagnosis): the adult-care two-target chain trains its QRF on owner_projection_of_asec_origin_clone_1 while the by-origin battery compares clone 0 — and the two ASEC clones genuinely differ (10%: clone-1 donor has 30 carriers with q50 $15,000; clone-0 comparator has 37 carriers with q50 $3,000). Raw ACS output versus its actual clone-1 donor passes (envelope 0.143); versus the clone-0 comparator it fails (1.836). Statutory reconciliation then prunes 1,731 → 421 carriers deterministically (818 false-flag, 491 role-structure, 1 ranking). The rung-to-rung "flip" (0.55× → 1.31×) is the coupled flag draw + donor/comparator mismatch + pruning — not spontaneous amount drift.

Fix shape: train the adult-care family from the same clone owner the battery compares (or define one common post-reconciliation donor/comparator surface for the family). Blast radius: the two-target adult-care family and downstream CDCC variables only. No tolerance or gate changes.

Definition of done: the family's donor and comparator surfaces are the same declared clone leg; the coupled flag→expense chain documented in the operator-ordering doc; battery legs for is_incapable_of_self_care and pre_subsidy_care_expenses evaluated on a 4% + 10% pair with the receipts posted here.

Reference: _buildo-runtime/reviews/sol_r14_diag.log (adult-care section), checkpoints under _buildo-runtime/out/dev-f010-r7/.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions