Skip to content

Add Ambika Yemul's Tax Technical Memorandum Builder - #119

Open
yemulambika wants to merge 1 commit into
superdocsapp:mainfrom
yemulambika:ambika-yemul-tax-memorandum-builder
Open

Add Ambika Yemul's Tax Technical Memorandum Builder#119
yemulambika wants to merge 1 commit into
superdocsapp:mainfrom
yemulambika:ambika-yemul-tax-memorandum-builder

Conversation

@yemulambika

Copy link
Copy Markdown

Candidate

Name: Ambika Yemul
Assigned build: Tax Technical Memorandum Builder

This evidence-first workflow serves accounting managers and in-house tax reviewers who need to validate authority quotations, monetary figures, and AI-proposed memorandum edits before export.

Architecture and SuperDocs usage

The React browser UI calls only a same-origin Node BFF. The BFF owns the server-side credential and Bearer header; real mode never falls back silently to the offline adapter.

The workflow uses four logical SuperDocs operation groups:

  1. upload four synthetic source documents;
  2. start asynchronous chat and poll to awaiting_approval;
  3. submit independent per-change approval/rejection decisions and reviewer notes;
  4. export client-ready and file-ready HTML from the same reviewed session state.

Exact quotation matching blocks an unattached/fabricated authority. String-preserved numeric rows and deterministic calculations block unmatched figures. Stable proposal IDs keep duplicate Analysis headings independently actionable, and an application fingerprint suppresses duplicate approval submissions.

Offline verification

  • Unit tests: 18 passed / 18 across 2 files
  • Offline Playwright: 4 passed / 4, retries disabled
  • TypeScript: passed
  • ESLint: passed
  • Prettier: passed
  • Production build: passed
  • Dependency audit: 0 vulnerabilities
  • Bundle and source scans: 0 real secrets, 0 personal email addresses, 0 browser API-key/direct-host/auth strings

Observed live workflow

The supervised visible workflow uploaded four documents and reached awaiting_approval. It displayed three quotation checks and monetary traceability, approved one proposal, rejected one proposal, reached zero mandatory pending decisions, submitted reviewed content once, and downloaded client-ready and file-ready HTML. Both outputs rendered in Chromium; approved material and citations remained, while rejected and fabricated material was absent.

The observed live exports had an orphan duplicate Analysis heading after rejection. The renderer was corrected afterward, and offline regressions prove the approved block remains while the rejected block and empty heading are absent. No corrected second live API run was made. DOCX and PDF export are not claimed.

Limitations

This is a fictional, single-scenario, in-memory demonstration—not tax advice and not production-ready. Public evidence is deliberately limited to one sanitized offline screenshot and a compact verification summary. Authentication, persistence, multi-tenant isolation, deployment hardening, and production observability are out of scope.

Screenshot

Tax Technical Memorandum Builder review workflow

Submission checklist

  • Changed files are confined to use-cases/yemulambika/tax-technical-memorandum-builder/.
  • No secret, personal email, .env, dependency/build output, raw Playwright result, trace, recording, browser profile, or temporary download is included.
  • The browser never receives the credential or an Authorization header.
  • Only HTML export is claimed.
  • No additional live SuperDocs quota was consumed during PR preparation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant