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

Axiom-engine pilot model version for Ghana (rulespec-gh)

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend

Research direction

Read the Belgium pilot pattern in issue #447 and draft PR #448, then check the rulespec-gh#5 prerequisite and its composed gross-to-tax program. Trace how household inputs reach the engine bindings and Simulation(...).run(). Done means a runnable AxiomGhanaPilot with exact per-case parity for modeled rules, plus documentation of GHAMOD's missing 35% top band.

Written by the indexing model from the issue text.

Description

Following the Belgium pilot pattern (#447, draft PR #448: AxiomBelgiumPilot as a raw TaxBenefitModelVersion outside certified-release machinery): add an AxiomGhanaPilot wrapping the rulespec-gh encodings (Act 1111 individual rate schedule + Act 896 Fifth Schedule personal reliefs, both merged and GHAMOD-validated — per-case parity exact to the cedi on everything both systems model; GHAMOD's own missing 35% top band documented and reported upstream to UNU-WIDER).

Prerequisite: the composed gross-to-tax program (rulespec-gh#5 — s.2 chargeable-income chain + axiom-programs spec). Once that lands, this adapter is thin: household inputs → composed program via the engine bindings → Simulation(...).run().

Motivation: runnable pip install policyengine examples for Ghana strengthen the TaxDev/IFS conversation about African tax-benefit tooling (inbound from ODI, July 2026).

🤖 Generated with Claude Code

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.