Add Belgium target and population-input boundary - #824
Draft
MaxGhenis wants to merge 16 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
takes_up_*from entering Axiom or the Microcosm input contractChronicle owns publisher facts and provenance. Microcosm constructs/calibrates the population and populates measured or latent nullable flags. PolicyEngine consumes those flags and owns later non-legal take-up and labor-response mechanics. Axiom may receive only concepts specifically grounded in public policy documents.
Unknown is
null, neverfalse. Activating a mapped target requires all typed readiness fields plus a bound frame receipt provingn_unknown == 0; changing a readiness string alone is insufficient. No activation path is added here.Target boundary
The calibration-candidate count surface contains Statbel population, Statbel fiscal-income returns, and ONEM complete-unemployment recipients; each is still blocked on its named bridge or input. The separate monetary profile contains SPF Finances PIT receipts as a blocked calibration candidate, with ONSS worker contributions and NBB household disposable income retained for historical validation only.
GRAPA, pension, and all nine regional child-benefit rows are validation-only. The child rows nevertheless define the typed Microcosm inputs needed for future receipt/participation validation. They do not construct eligibility denominators, take-up rates, or behavior. No wealth target is declared because an official pinned HFCS package and exact interview-period/support bridge are still absent.
Chronicle #212/#213 reconciliation
Chronicle #212 declares the relevant record identities and administrative scopes. The newer source-faithfulness audit in Chronicle #213 establishes that the Opgroeien dashboard capture, Iriscare material, and Ostbelgien manual transcription are not activation-grade publisher artifacts.
Accordingly, five mappings carry
publisher_source_readiness="native_publisher_artifact_required_missing": one Opgroeien, two Iriscare, and two Ostbelgien rows. GRAPA and the four Walloon child rows have pinned official source material, but remain independently blocked on Microcosm population/input/period/completeness gates. Publisher household rows remain excluded until their unit is proved equivalent to a Microcosm household.Source follow-ups are tracked in Chronicle #215 (HFCS), #216 (Iriscare), #217 (Opgroeien), and #218 (Ostbelgien).
Reviewed coordinates
main@d1e3e397bdc4b7e6b9e05dc73cf6345e7111e6db654cb6c2cba558ee8aec32144d22f8d04495866c0f75a2bb5fae8a197e4e1f6541a5af34708fc206fe3fd81670f106c5509847312ba61dd4c4742626510e3e6c9c2cd7f61854c56f6edd2acb14bc1cd8Validation
verification=okgit diff --checkpassThe two deselected US parity-regeneration cases fail identically on
main@d1e3e397: the local feed exposes a CBOsource_projectionwhile the committed US reference remainsobserved_only. This branch does not touch that data or assertion path.Independent exact-head review
Served
claude-fable-5adjudicated the exactd1e3e397…654cb6c2range and returnedVERDICT: APPROVEwith no actionable correctness, source-faithfulness, architecture, or coverage finding. Attested Subfleet run:20260831-090042-microcosm-824-exact-head-fable-v4, session1b93f442-ea78-4ae2-af0a-c6f76622853e(requested: claude-fable-5,served: claude-fable-5).Because the Claude read-only wrapper currently rejects
--safe-mode, the review ran with workspace permission only in a disposable detached copy. The reviewer added three local-only commits ending at7bf22f8d; the complete delta from the PR head is exactly two adjudication Markdown files (ADJUDICATION_824_PROGRESS.mdandADJUDICATION_824_REPORT.md) and zero product files. Nothing from that copy was pushed. The adjudication report explicitly binds approval to PR head654cb6c2, not the local journal commits.The reviewer independently passed 508 focused tests and found the full no-engine
microcosm-buildshard clean except four pre-existingpolicyengine_usimport failures in an unchanged US test file. GitHub's engine-equipped US matrix is green at this head.This PR remains draft and must not be merged here. The publisher artifacts, Microcosm population/input/period/completeness work, dependency review, and merge-time journal historicization remain follow-up gates even after exact-head approval and CI.