Repository navigation
chore(irs): register TY2026 2026v3.0/v4.0 MeF schemas and rules in manifest (FIL-4) - #168
Merged
Merged
Conversation
…les in manifest Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
filedyoda
commented
Oct 23, 2026
filedyoda
left a comment
Contributor
Author
There was a problem hiding this comment.
Taxo review for FIL-4 step 1: approve. GitHub won't record a formal approval, because the agent connector shares the author's account. I'll merge once unit-and-preflight is green.
Verified:
- I recomputed SHA-256 for all 8 declared files (3 XSDs each for 2026v3.0/v4.0, plus both rules
.xlsm) from the installedirs/copies. All match the manifest. - The manifest shape fits
scripts/testing/irs.ts.rulespackages are keyed by filename, so later code that referencesirs/rules/1040_Business_Rules_2026v{3,4}.0.xlsmwill count as declared. - Metadata only: no code, tax values, cases or baselines changed. No tax-accuracy sign-off is needed.
Non-blocking nits for a later PR:
- README says "ATS-valid from 2026-08-13" for v3.0. 08-13 is the IRS release date; please confirm it against the ATS publication schedule, or reword it to "released 2026-08-13".
- The existing README source paths end with the extracted dir (
› 2026v1.0/); the new rows don't. The.pdfrules are listed in the README but not hashed in the manifest. Hash them, or drop "(+.pdf)", if the PDFs aren't meant to be tracked.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Step 1 of FIL-4. Adds
manifest.jsonentries (SHA-256) formef/2026v3.0,mef/2026v4.0, and the 2026v3.0/v4.0 business rules (.xlsm, since the IRS no longer ships CSV), plus matching rows inirs/README.md. Metadata only: no code, no tax values, no baselines changed.Verified: the hashes were computed from the files installed in
irs/.check:irs(run asbun scripts/testing/irs.ts) reports the new packages present and unaltered. It lists 11 of 12 packages present; the gap is the unrelated publicty2026-corpussnapshot.Not verified:
check:mef,check:ats,check:ty2026, structure and unit gates were not run, because the change does not touch code they read. CI skipsirs/content, which is gitignored. Nothing was tested against a live ATS run, which needs Filed's IRS credentials.Next PRs: v3.0/v4.0 rules conversion, the diff against 2026v1.0, and the builder update.
🤖 Generated with Claude Code