[META] Define QWED-Tax scope: a deterministic verification layer, NOT a GST/tax platform (non-goals)

[rahuldass19]

Purpose

This is a pinned scope/decision issue, not a feature. Recent inbound interest (enterprise/IBM-partner) revealed a recurring assumption:

"QWED-Tax = a GST/tax compliance platform."

The code says otherwise. Before we add more GST features (#29, #30, #32, #33), we should explicitly decide how far this project goes — so every future feature/PR can be judged against an agreed boundary instead of drifting into "tax software" territory.

---

What the Audit Revealed

People expect more than the code does. That's useful requirements-discovery, but acting on all of it would silently turn a verification project into a tax platform with a very different (and much heavier) maintenance burden.

---

The Three Paths

Path A — Stay narrow

• Position purely as a "Deterministic Tax Verification Layer."
• Only add checks that are deterministic, objective, small, testable.
• Lowest maintenance, clearest identity.

Path B — Expand selectively (Recommended starting point)

• Add high-value, deterministic GST checks: GSTIN checksum (GSTIN validation is regex-only: implement real 15th-digit checksum (docstring falsely claims "checksum validation") #29), CGST/SGST/IGST split (Add CGST/SGST/IGST split verification (intra-state vs inter-state place-of-supply) #30), better RCM (Expand GST Reverse Charge (RCM) coverage beyond the 3 "demo" services #32), audit trace (Add structured statutory audit-trace to guard outputs (section/rule reference per decision) #33).
• Stop and reassess after these land.
• Keeps QWED identity while closing real, code-confirmed gaps.

Path C — Become a GST platform

• GSTN integration, GSTR-1/2B, e-invoicing/IRN, notifications/circulars tracking, per-state change management, HSN/SAC classification maintenance.
• This converts QWED from a verification company into a tax-software company.
• Proposed: explicitly NOT this project.

---

Proposed Decision

• Adopt Path B, with a hard boundary at the edge of deterministic verification.
• Treat anything requiring live data sync, classification-corpus maintenance, or filing workflows as out of scope by default.

---

Proposed Non-Goals (Out of scope unless explicitly revisited)

• GSTN portal integration / live GSTIN status lookup
• GSTR-1 / GSTR-2B reconciliation
• e-invoicing / IRN generation
• HSN/SAC classification system (corpus maintenance trap)
• Tracking notifications / circulars / per-state rate changes as a service
• Tax calculation engine (QWED verifies claims; it does not originate filings)

---

How This Guides Other Issues

Issue	Path B fit?
#29 GSTIN checksum	✅ deterministic, small
#30 CGST/SGST/IGST split	✅ deterministic
#32 RCM expansion	✅ (as a bounded rule table, not full Sec 9(4) matrix)
#33 Audit trace	✅ verification-supporting
HSN/SAC classification	❌ Path C — declined by default
GSTN/GSTR/IRN	❌ Path C — declined by default

---

Decision Checklist

• Maintainers agree on Path B as the operating boundary.
• Non-goals list ratified and linked from README (Docs honesty: README claims India GST is "Production Ready" — reposition as a verification layer, not a compliance product #31).
• Future GST feature requests are triaged against this issue.

[rahuldass19]

README positioning audit — aligns with Path B decision

Ran a full positioning + architecture review of the repo. This comment maps the findings against the Path B decision proposed in this issue, and provides the README rewrite direction.

Current README state

The README is 70% correct but has positioning gaps that could cause exactly the confusion this issue exists to prevent:

Section	Current	Problem
Title (line 1)	"Deterministic Verification for Payroll, Tax, and Compliance"	Sounds like a calculator — "for Payroll, Tax" implies it computes payroll taxes
Line 78	"Unlike calculators (Avalara) or executors (Gusto), QWED is a Verifier"	✅ Correct — but buried at line 78
Line 101	"What QWED Tax Verification System"	Grammatically broken heading
Line 104	"Enterprise-Grade Tax Code Verification Engine"	"Tax Code" is ambiguous — source code? Tax law? HSN/SAC codes?
Line 111	"Status: ✅ Production Ready" (India GST)	Overclaims — this is what the Ranga email honestly said is NOT production GST assurance
Missing	No "AI-agent-era" framing	The core question QWED-Tax answers — "should this AI-generated tax decision be allowed to execute?" — is not the first thing a reader sees

The positioning sentence that should be front and center

From the review (echoing the email to STAR Systems):

Tax software answers: "What is the correct calculation?"
QWED-Tax answers: "Should this AI-generated tax decision be allowed to execute?"

This single sentence:

• Separates QWED-Tax from every tax calculator/filing platform in the market
• Centers the AI-agent-era framing (why this exists NOW, not 10 years ago)
• Makes the "verification layer" identity unmistakable
• Directly supports the Path B boundary — we verify, we don't calculate/file

Recommended README rewrite (Path B aligned)

New opening (replace lines 1-10):

QWED-Tax — The Verification Gate for AI-Generated Tax Decisions

Tax software answers: "What is the correct calculation?"
QWED-Tax answers: "Should this AI-generated tax decision be allowed to execute?"

QWED-Tax sits between AI agents and execution systems (Gusto, Avalara, Stripe) —
verifying that tax decisions are legally sound before they execute.
Not a calculator. Not a filing platform. A deterministic verification layer
powered by Z3 and Decimal math.

Status table update (line 107-112):

• Change "✅ Production Ready" to "⚠️ Verification Layer — Not a Compliance Product"
• Add a note: "Guards verify specific deterministic rules. Full GST compliance (GSTR filing, GSTN integration, HSN/SAC classification) is explicitly out of scope. See scope definition."

Move the comparison table (currently line 78-84) to the top — it's the strongest positioning element.

Move "Procedural Accuracy" (line 94) higher — the procedure-before-calculation concept is a key differentiator.

Alignment with #31

This issue mentions #31 (README claims India GST is "Production Ready"). The README rewrite should address both:

• [META] Define QWED-Tax scope: a deterministic verification layer, NOT a GST/tax platform (non-goals) #34: scope/positioning (verifier, not platform)
• Docs honesty: README claims India GST is "Production Ready" — reposition as a verification layer, not a compliance product #31: honesty (don't claim production ready for partial coverage)

What the rewrite does NOT do

• Does not remove any guard documentation — all guards are accurately described
• Does not change the architecture diagram — the "Swiss Cheese" defense is correct
• Does not remove the "Real World Failures" section — that's the strongest proof point
• Does not promise features outside Path B boundary

Recommended action

1. Ratify Path B in this issue (if not already done)
2. Rewrite README per above direction — can be a separate PR
3. Update status table — remove "Production Ready" claims
4. Link Docs honesty: README claims India GST is "Production Ready" — reposition as a verification layer, not a compliance product #31 as closed by the README rewrite

[rahuldass19]

Resolution

Path B is now ratified and implemented via #46 (merged).

What landed

• README repositioned from "Deterministic Verification for Payroll, Tax, and Compliance" → "The Verification Gate for AI-Generated Tax Decisions"
• Core positioning sentence added: "Tax software answers: What is the correct calculation? QWED-Tax answers: Should this AI-generated tax decision be allowed to execute?"
• Comparison table (Filter / Shield / Proof) promoted to top of README
• "✅ Production Ready" status claims replaced with "🟢 Verification Layer" for both US and India
• Explicit Non-Goals section added: GSTN integration, GSTR reconciliation, e-Invoicing/IRN, HSN/SAC classification, tax filing, regulatory change tracking, payroll execution, tax calculation engine
• "Accounts Payable Automation" → "Accounts Payable Verification"
• Roadmap reframed: "ERP Integrations" → "ERP Verification Connectors"; "massive vision" language removed
• Section reordered: identity → comparison → problem → architecture → procedural accuracy → coverage → non-goals → guards → privacy → install → SDK → examples → roadmap

Related

• Docs honesty: README claims India GST is "Production Ready" — reposition as a verification layer, not a compliance product #31 (README "Production Ready" overclaim) — already closed via docs(tax): GSTIN checksum, CGST/SGST/IGST split, expanded RCM, audit-trace docs#216, and further reinforced by docs: reposition README as verification layer (refs #34, #31) #46
• Structured Verification Diagnostics — 3-Layer TaxDiagnosticResult Model #39 (TaxDiagnosticResult tri-state model) — merged, provides the structured diagnostics foundation that supports the verification-layer identity

Non-goals ratified

The following are explicitly out of scope unless revisited:

• GSTN portal integration / live GSTIN status lookup
• GSTR-1 / GSTR-2B / GSTR-3B reconciliation
• e-Invoicing / IRN generation
• HSN/SAC classification system
• Tax filing or return preparation
• Regulatory change tracking as a service
• Payroll processing or execution
• Tax calculation as a standalone engine

Future feature requests will be triaged against this boundary.