Tax Paperwork

Verification

How we check public-preview draft PDFs

Tax Paperwork runs automated checks before a public-preview workflow stays on the site. The checks are meant to catch broken official PDF mappings, missing required fields, stale source files, unsupported data paths, layout drift, and unsafe public-preview promises.

Important boundary These checks increase software confidence. They do not prove that a tax position is correct, that a user should file, that the IRS will accept a filing, or that Tax Paperwork is IRS-approved, a preparer, a law firm, a CPA firm, or a filing service.
9 public-preview workflows

Every implemented workflow stays browser-local and produces watermarked draft PDFs only.

11 official source PDF baselines

IRS source files are tracked with source metadata and drift checks.

4,844 official fields accounted for

4,844 official fields are mapped or intentionally ignored with reasons.

676 / 676 required fill fields exercised

Valid synthetic scenarios must touch every required mapped field.

119 synthetic data-path scenarios

188 / 188 required coverage tags are covered.

40 draft packet PDFs generated

Deterministic fixture packets are built from synthetic facts only and summarized with packet-contract evidence.

40 / 40 packet artifacts hash-anchored

Each committed generated packet PDF has a SHA-256 recorded in its non-sensitive summary.

79 invalid packet scenarios blocked

Synthetic unsupported or invalid scenarios must stay blocked before packet artifact generation.

224 rendered PDF page snapshots

144 official-form pages and 80 support pages are rendered.

9 browser-smoke routes covered

Mobile browser tests cover public routes and generic draft filenames.

What the automation checks

  • Current public-preview forms have catalog entries, public routes, source modules, source PDFs, fixture packets, and browser-smoke coverage.
  • Official PDF fields are inventoried, and supported fields are mapped by name and type.
  • Valid synthetic fixtures exercise required mapped fields and generate draft packet artifacts with recorded SHA-256 hashes.
  • Unsupported or invalid scenarios stay blocked before packet artifact generation.
  • The CI packet-artifact verifier separately checks committed packet hashes, rebuilt validation/report metadata, fallback absence, support-page presence, and invalid-scenario blocking.
  • Rendered PDF snapshots keep official pages and support pages from going blank or disappearing.
  • Public pages keep the preview boundary: no payment, no submission, no mailing, no professional review, and no final filing packet downloads.

What the automation cannot decide

  • Whether a person should make an election, file a gift-tax return, request a certificate, or send a notice.
  • Whether a legal or tax position is right for a specific user.
  • Whether an unsupported fact belongs in a professional review path instead of software.
  • Whether the IRS has processed, accepted, or agreed with a mailed or faxed item.

Workflow evidence

Workflow Source PDFs Required fields exercised Data paths Draft packets Rendered pages Status
Form 709 3 440 / 440 24 5 generated / 19 blocked 60 Passing
Form 8892 1 19 / 19 12 4 generated / 8 blocked 12 Passing
Form 8822 1 8 / 8 14 5 generated / 9 blocked 20 Passing
Form 8822-B 1 13 / 13 17 6 generated / 11 blocked 24 Passing
Form 2553 1 51 / 51 11 3 generated / 8 blocked 18 Passing
Form 8832 1 20 / 20 11 3 generated / 8 blocked 30 Passing
Form 8802 1 33 / 33 9 4 generated / 5 blocked 20 Passing
Form SS-4 1 53 / 53 12 6 generated / 6 blocked 24 Passing
Form 56 1 39 / 39 9 4 generated / 5 blocked 16 Passing

Last dashboard update: May 6, 2026. Counts come from a committed non-sensitive dashboard artifact generated by the local verification tools.