PolicyEngine / PolicyEngine/microcosm
Add the NZ transport contract and real-Axiom Frame bridge
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 4
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 94
Description
Part of #343. Add a spec-only NZ transport package and a verified Frame-to-Axiom boundary before attempting a population calibration.
Acceptance:
- Pin the public US donor artifact by immutable revision, filename, SHA-256, and byte size; retain donor/support provenance.
- Pin the reviewed NZ RuleSpec input/output contract and cell identities for Chronicle WFF/IWTC administrative counts. Keep official Budget scores and entitlement dollars held out from calibration.
- Add a closed person/household/family export contract: eleven substantive inputs are mandatory, ten unrelated eager inputs may be explicit padding zeros, and only household weights are stored.
- Extend the generic Axiom adapter for canonical RuleSpec roots, explicit tax-year bounds, exact-bounded Decimal input conversion, and exact HDF persistence.
- Exercise actual Axiom native software on a tiny nonuniform household/family fixture, including missing-input, membership, weight, and formula-owned export refusals.
- Document the reusable three-parallel-lane country expansion playbook and the explicit gates before a calibrated release/dashboard publication/official-score replication.
This issue does not authorize a fabricated or uncalibrated NZ release. Donor-to-NZD/family/period bridges, reviewed fact bindings, shared build operators, calibration thresholds, Treasury source activation, and an official operating-cost accounting bridge remain on the parent epic before publication.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the generic Axiom adapter, the RuleSpec input/output contract, and the tiny nonuniform household/family fixture described in the acceptance criteria. Trace the required donor provenance, closed export contract, exact Decimal/HDF handling, native Axiom refusal checks, and country-expansion documentation. Done means all listed contracts and gates are verified without publishing an uncalibrated NZ release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data, documentation, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100