The statutory question
Author the ratification spec for PSI attribution. The results test (s 87-18), the 80/20 unrelated-clients test (s 87-20), the employment test (s 87-25), the business-premises test (s 87-30), and the attribution mechanics under Div 86.
Why this matters
Our calculator emits a deterministic answer for any lawful input. The question the bounty answers is: does the calculator's answer match what a competent practitioner would produce from first principles reading the statute? If yes, the calculator's output is a witness. If no, the reviewer's correction becomes the fix.
Either way, the reviewer's name is bound to the version of the engine they ratified. That binding — cryptographic hash of the reviewer's verdict against the calculator's version — travels with the engine downstream.
What you are being asked to do
- Read the one-page brief and the worked example.
- Review the six (or seven) forensic questions. These are graded easy → hard; do not skip the easy ones — they anchor your reasoning trail.
- Fill out the reviewer-verdict template. It is a structured YAML-frontmatter document with three top-level verdicts — ACCEPT, REJECT, or FIX — and space for per-question citation trails.
- Return your verdict by email or as a pull request against the bounty repo. We’ll review within one business day and confirm acceptance.
What is not in scope
We are not asking you to review our source code, run our engine, audit our maths, review our software architecture, or understand our cryptographic provenance chain. Those are separate concerns, handled separately. The bounty is a statute-to-predicate ratification exercise, nothing more, nothing less.
Statutory anchors (pre-loaded)
The TaxGenii appendix (file 05 in the artefact bundle) contains the primary statutory sections and key rulings pre-cited — you do not need to hunt sources. If the appendix is thin in an area you consider critical, that is itself useful information — flag it in your verdict under the “coverage gap” section and we’ll feed the finding back to our knowledge-base team.
Attribution — how your work gets credited
Your accepted verdict is minted into the public reviewer registry with:
- Your name and credential class (CA / CTA / CPA / FIPA / TPB – registered)
- The verdict hash (SHA-256 of your submitted document)
- The calculator version you ratified
- The publication date
Default is named credit. You may opt down to initialled (“J.D.”) or anonymous when you submit. Opt-down does not reduce the prize.
Edge cases surfaced in the forensic questions
Each brief carries one deliberately load-bearing question — a scenario where a plausible-looking answer is subtly wrong — and one deliberately open-ended question that invites you to surface something we haven’t yet caught. The load-bearing question separates careful readers from skim-readers; the open-ended question is where the best verdicts extract real value beyond the prize.