PolicyEngine / PolicyEngine/microcosm

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

Open
#671 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
0
Forks
4
Avg merge
1d 3h
Merged PRs (30d)
94

Description

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/.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the adult-care section of _buildo-runtime/reviews/sol_r14_diag.log and the checkpoints under _buildo-runtime/out/dev-f010-r7/. Trace the two-target family’s donor and comparator surfaces, then align them to the same declared clone leg without changing tolerances or gates. Document the coupled flag-to-expense chain in the operator-ordering doc and evaluate the is_incapable_of_self_care and pre_subsidy_care_expenses battery legs on the 4% + 10% pair.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.