Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

NZ source-only Axiom transport and entitlement smoke

Open
#507 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@MaxGhenis is already working on this.

Since Aug 30, 2026.

  • #508 by @MaxGhenis — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
api, data, testing

Research direction

Start with #506 and the shared Simulation API entry point; trace the NZ adapter boundary, Microcosm entity-table HDF5 inputs, Frame weight resolution, and the Axiom official-budget module for 2026–27. Use the requested focused boundary tests, opt-in real-runtime tests, and executable example as completion checks, including rejection of missing or unsupported inputs and recording source, input, and runtime hashes.

Written by the indexing model from the issue text.

Description

Implement the source-only integration slice of #506: a Pydantic NZ dataset/model adapter through the shared Simulation API; read Microcosm entity-table HDF5 with exact decimal and nullable-boolean decoding; resolve person/family weights through Frame from the sole household weight vector; execute the actual Axiom official-budget module for explicit tax year 2026–27; reject missing inputs and unsupported controls; preserve source files and record input/runtime hashes; provide focused boundary and opt-in real-runtime tests plus an executable example.

This issue does not include a calibrated population, certified country release, fiscal/payment/debt bridges, or completed national Scorecard replications. Those remain tracked in #506 and the NZ country-expansion dependencies.

Dominant language
Python
Stars
8
Forks
9
Avg merge
15h 28m
Merged PRs (30d)
13

Getting set up

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.

More from PolicyEngine/policyengine.py

All issues in PolicyEngine/policyengine.py

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.