QueueCutter

Public fork · bounded contributionPublic fork · Apr-May 2026

A guided paperwork copilot for seven US, Indian and UK forms that produces a filled PDF, checklist, submission guide and risk warnings.

Problem

Government forms can be difficult to identify and complete, but a helper must not imply that a generated draft was filed, accepted or legally correct.

Implementation record

How I solved it

  1. 01

    Kept the scope to seven fixed forms, pairing the React and Express flow with pdf-lib output, a checklist and submission guidance rather than claiming live government filing.

  2. 02

    Added the public follow-on discovery and country-specific escalation paths, then documented the hand-off clearly: the user receives a draft and submits it manually.

  3. 03

    Added environment, smoke and browser-verification scaffolding around the fork's follow-on change while preserving the upstream ownership boundary.

My role / what I owned

Maintainer and contributor to a public fork

  • Added the fork's public follow-on feature and bug-fix commit, including AI form discovery and country-specific escalation paths.
  • Added the current README, environment template and smoke and browser-verification scaffolding.
  • Kept the delivery boundary explicit: the application generates a PDF and guidance for the user to submit manually.

How it was built

Team
GitHub identifies Nivish-21/QueueCutter as a fork of Nivinv2000/QueueCutter. The public history shows one Nivish-21 follow-on commit; it does not establish ownership of the upstream build or a collaborator split.
Tools
  • TypeScript
  • React
  • Express
  • PostgreSQL
  • Drizzle ORM
  • OpenAPI
  • Orval
  • pdf-lib
  • OpenAI
Use of AI
The current README documents AI-assisted form discovery, explanations, answer interpretation, question simplification and inconsistency checks through custom endpoints.

Source and current state

  • The public repository exposes the seven fixed form definitions, React and Express application, PDF generation and smoke-test command.
  • GitHub marks the repository as a public fork that is one Nivish-21 commit ahead of its upstream source.
  • That follow-on commit adds the current README plus form-discovery, escalation, responsive and verification changes.
Status
Active public fork that generates ready-to-submit PDFs for manual submission.
What it shows
The inspectable source demonstrates the guided seven-form flow and PDF output. It does not establish users, adoption or successful filings.
Source repositoryOpens in a new tab