[MaxGhenis]

This updates docs/parity-ledger.md for what merged after its last check at f8ffc7d9 (#569). It re-verifies five rows and step 1 of the critical path at 9967dfd6 (master after #577), and step 2's successor entry at 9a344a1a (master after #561). It changes no code, gate, run or progress data, so docs/progress.md and the scorecard are untouched.

Verified at 9967dfd6

• Covered earnings. CE v2's design note, CE0, merged in #568 (docs/design/covered_earnings_v2.md, which says nothing in it has run). That replaces the clause calling the retired correction design a draft. CE1's coverage-rule registry is in review (#583).
• Births. OP0.1's source, exposure, access and power audit merged (#567). OP1's harness is still in review (#566).
• Alignment. The open-population design's revision 14 (#576), §§3 and 6.4: OP6 will align births and emigration and leave death draws to the mortality adapter the mortality lane chooses, the baseline's or SM once admitted. SM is designed to preserve the baseline's expected deaths within each age, sex and year cell, up to a logged clipping residual (mortality design §6).
• Poverty (U2). #577 committed the pre-registration evidence record the specification pins (docs/design/u2_preregistration_evidence.json). Step 7's fresh forecast was frozen and independently checked in the lane's evidence folder, outside the repository, so it can't be checked here yet. The next step is the Candidate 2 design: latent-permanent conditioned chained QRF (research memo) #42 registration, which is Max's, and then the one-shot.
• National costs. F0, Registration 18's build, is in review as #585. F1, the income tax on benefits, is in review as #586, after #578 corrected F1's signed-split invariants in the mortality design (§6).
• Critical path, step 1. The held-out data registry merged in #560. B0.2's plan is now #584, which replaced Track B B0.2: source, exposure, access and power records for B3 through J #554.
• P2 (at 9a344a1a). P2, the successor's reserve, merged in #561. The forward-earnings row and critical-path step 2 say so; neither S1 nor P2 has registered.
• Header. It records the third verification.

Seven link definitions are added (#576, #577, #578, #583, #584, #585, #586). Every reference resolves, and no definition is unused.

Not covered here

Merges after 9a344a1a (for example D1a, SSI0 and SM1, once they land) get their own ledger update. The branch merges master 9a344a1a.

Review

Review r1 (20261025-023327-ledger-587-review-r1) asked for two medium fixes, both applied in a7564e4a: the poverty row now says where step 7's record lives, and the alignment row names the death adapter and the cell-level conservation. Review r2 (20261025-041855-ledger-587-review-r2) found round 1's alignment fix good and asked for two more medium fixes, applied in the next commit: the poverty row no longer describes the unposted registration's content, and the forward-earnings row no longer calls P2 a draft. A delta review at the new head follows.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
social-security-model	Ready	Preview	Oct 25, 2026 8:38am UTC

[MaxGhenis]

Merged at 6f8946630d0f4685dfbe9e532f5ada19be3c8cd3 with --merge --match-head-commit.

• Checks: gh pr checks exited 0 on the latest run for this head (Tests run 40177370894: four pytest shards, pytest (3.14), graph-integration 3.13 and 3.14; lint and build; Vercel; deploy skipped).
• State: MERGEABLE and CLEAN, not a draft, no CHANGES_REQUESTED review.
• Independent reviews (GPT-6.1 Sol, read-only):
  • round 1 at 4dcc0992: two medium wording fixes, applied in a7564e4a;
  • round 2 at a7564e4a: approved the master merge cd0dbe46 (tree equal to git merge-tree --write-tree) and the round-1 fixes, and asked for two medium fixes, applied in 6f894663;
  • round 3 at 6f894663: APPROVE. Both round-2 findings fixed, nothing else changed, all 232 reference uses resolve to 82 definitions. Its one minor finding was a stale sentence in this PR's body, now corrected.
• Scope: docs/parity-ledger.md only, plus the merge of master 9a344a1a. No tier change.

Merges after 9a344a1a get their own ledger update.