← ClaudeAtlas

fortax-evidence-disciplinelisted

Always-on rules for Indian CA work - every rate, threshold, due date, late fee, form, section or notification needs a source in front of you; every figure traces to a file and cell; rules checked for the right FY/AY; fail loud on out-of-scope cases; validate PAN, GSTIN, TAN, CIN; and never say done without fresh verification (recompute totals, reopen the file, list what the CA must check). Typical asks - "pakka hai?", "source kya hai", "done ho gaya?", "check karke batao", "ye figure kahan se aaya".
amit-voais/fortax-skills · ★ 1 · Code & Development · score 77
Install: claude install-skill amit-voais/fortax-skills
# Evidence discipline Needs Python 3 and internet: runs `scripts/fortax.py` (the Fortax engine on ai.fortax.in; your file is processed and not stored). ## Why this exists The CA and their clients act on what you say. A wrong due date costs a late fee. A wrong threshold costs a wrong registration. A made-up section number costs credibility the moment a CA reads it. The bar is not "sound confident", it is "be checkable". ## 1. What needs a source Any of these needs a source that is actually in front of you right now: - a due date or filing deadline - a rate, threshold, limit or slab - a penalty, late fee or interest rate - a form number, section, rule, notification or circular number - an eligibility condition - a fee payable on a portal "In front of you right now" means one of: 1. a fact from `python3 scripts/fortax.py kb "..."` with `match: strong`, its `source` URL and `captured` date (`fortax-knowledge-base`) 2. a page from the official portal or the notification itself, read in this session 3. a document in the client folder or shared in this conversation 4. a statute you can quote verbatim Your own memory of Indian tax law is not a source. It is a starting point for where to look. Anything you cannot point at is written as `[UNVERIFIED — confirm on portal]` with where to look, never as a number. ## 2. Every figure traces to its origin - Numbers come from code, not from the model. Where a Fortax engine exists (`gstr1`, `gstr2b`, `bank`), run it and read its