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

Axiom-engine pilot model version for Nigeria (rulespec-ng)

Open
#461 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
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend

Research direction

Compare the Ghana pilot issue and Belgium-pilot pattern in #447/#448, then read the AxiomNigeriaPilot and rulespec-ng#3 references. Confirm how the merged Nigeria Tax Act 2025 modules compose through the axiom-programs spec, and check the lane's oracle index and cited validation anchors. Done means a runnable first-year-2026 Nigeria pilot model using the composed gross-to-tax program.

Written by the indexing model from the issue text.

Description

Companion to the Ghana pilot issue, same Belgium-pilot pattern (#447/#448): AxiomNigeriaPilot wrapping the rulespec-ng encodings (Nigeria Tax Act 2025 Fourth Schedule rate schedule + s.30 chargeable income and rent relief — merged; validated against the gazette print, GRA-style external anchors and the PwC Worldwide Tax Summaries sample computation; no household oracle exists for Nigeria, which is documented in the lane's oracle index).

Prerequisite: the composed gross-to-tax program (rulespec-ng#3 — s.30 into Fourth Schedule via an axiom-programs spec). Nigeria's modules already chain conceptually (chargeable income feeds the schedule), so this is the thinner of the two adapters.

Motivation: runnable examples of the current Nigerian law (first year of assessment 2026) for the TaxDev/IFS conversation; the 2023-era policyengine-ng package models the repealed PITA regime and is superseded by this path.

🤖 Generated with Claude Code

Dominant language
Python
Stars
7
Forks
9
Avg merge
16h 16m
Merged PRs (30d)
8

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.