Project intake
Thirteen mandatory fields. Schema IUP-INFRA-TAX-001 version 0.3, section 15.1. The capital expenditure split and prior incentive availed are mandatory because without them no figure can be computed — only appear to be.
Upload a PDF and the fields below can be filled from it. Nothing is transmitted anywhere — the file is read in this browser. Every proposed value is shown with the sentence it came from, and nothing is applied until you confirm it.
No assessment generated yet. Complete the intake and press Generate preliminary position.
Assessment register
Every assessment saved here is numbered, dated and stamped with the register version and hash used to produce it. Schema section 19. Attachments are stored with the record.
Source documents — Family A
Investor incentive instruments. Each confers entitlements on an investor. Identity is taken from the title page, never the filename.
Source documents — Family B
Infrastructure delivery and concession instruments. These govern how an asset is structured, procured, awarded and operated. This is the Division's own core work.
Reference material
Data sheets and presentations. Not instruments; no clause is carded from these.
Instruments not held — acquisition list
What the Division does not hold, why it is required, and the evidence of the gap. Source Document Register IUP-INFRA-TAX-002 version 1.0, section 8.
The carded rules
Generated from IUP-INFRA-TAX-004 Stage 0 Extraction Workbook version 1.1 and never edited here. To correct a rule, correct the workbook, have a second officer verify it, and re-export — Schema section 18.2.
Open questions
Every interpretive doubt recorded at the moment it arose. These are not defects in the system; they are findings about the instruments, and they are among the most durable outputs of the exercise.
Document library
The controlled documents governing this work. Each carries a document number, a version, a date and a change log.
How this works
1. What the tool is
The policy rulebook has been typed into a computer, one rule at a time. Each rule carries the exact words, the instrument and page it came from, who it applies to, what switches it on, what it grants or requires, who approves it, which other rules cap or block it, and which officer verified it.
2. The processing sequence
| Step | Action | Performed by |
|---|---|---|
| 1 | Project profile captured against the intake schema | Officer, or read from an uploaded document and confirmed |
| 2 | Profile normalised; units converted; region derived from district | System — deterministic |
| 3 | Every clause trigger evaluated against the profile | System. No language model |
| 4 | Matched set assembled; ambiguous clauses set aside for review | System — deterministic |
| 5 | Relations traversed; preconditions and ceilings drawn in | System — deterministic |
| 6 | Governing definition selected for each term, by narrowest scope | System — deterministic |
| 7 | Bands evaluated; the winning band computed against the resolved base | System — deterministic |
| 8 | Constraints applied across the whole set — exclusivity, ceilings | System — deterministic |
| 9 | Approval chain and contingent liabilities compiled | System — deterministic |
| 10 | Report rendered with verbatim text and a full citation on every line | System — deterministic |
| 11 | Officer reviews, confirms, varies or overrides; the ground is recorded | The officer |
Step 8 is the one that prevents the most serious failure. Without it the system computes individually correct benefits and returns a collectively unlawful total — with a perfect citation beside every line.
3. Citation convention
Every reference is written in full: the clause number exactly as printed, the full official title of the instrument, its Source Document Register number, and both the printed page and the PDF page. Symbols are never used in place of a reference.
Clause 9.1.2(B)(1) of the Uttar Pradesh Warehousing and Logistics Policy 2022 (SRC-001), printed page 23, PDF page 24.
4. Reading an uploaded document
An uploaded PDF is read in this browser and used to propose intake values. Every proposal is shown with the sentence it came from and nothing is applied until you confirm it. Where a document has no text layer, or a legacy font that decodes to unreadable characters, the tool says so rather than passing on nonsense — the second case is the more dangerous, because such a file appears searchable and is not.
5. Correcting a wrong output
| Situation | What happens |
|---|---|
| The register is right, this project is exceptional | Record an override on the report. The ground is mandatory. Both values are shown side by side and the assessment version increments. |
| The register itself is wrong | Correct the workbook, log the change with its ground, have a second officer verify it, and re-export. The superseded row is kept, never overwritten, so earlier assessments remain reproducible. |
Scope and limits
This system does not adjudicate eligibility, does not issue determinations, and does not replace departmental sanction. It produces a cited, verifiable preliminary position which a competent officer then confirms, varies or rejects.
Schema IUP-INFRA-TAX-001 version 0.3, section 1.3. This limit is a design requirement and not a form of words.
Where the language model sits, and where it does not
| Task | Performed by |
|---|---|
| Reading policy documents and carding rules | A person, assisted. Nothing unverified enters the register |
| Deciding which rules apply | Ordinary program code. No language model |
| Calculating amounts | Ordinary program code. No language model |
| Applying ceilings and exclusivity | Ordinary program code. No language model |
| Reading an uploaded PDF | Ordinary program code in this browser. No language model, no upload |
| Deciding anything at all | The officer, always |
No language model executes anywhere in this page. Nothing you type or upload is transmitted anywhere — every calculation happens in this browser.
Reproducibility
Identical inputs against an identical register version produce an identical report. Every report carries the register version and its hash, so a position taken today can be reproduced exactly at any later date, and the register as it stood on that date can be shown.
What this tool deliberately does not compute
Where a figure is determined by a financial model, by competitive bidding, or by a Central Government scheme rather than by the text of a State instrument, the tool returns the eligibility gate, the stated ceiling, the approval chain and the caveat — never a figure. Viability Gap Funding is the principal instance. Schema section 21.
A rate with no base is not a figure
A percentage exemption from stamp duty, electricity duty or a certification cost has a base this profile does not carry. The tool states the rate and declines to state a rupee amount. It will not compute such an exemption against eligible capital investment, which would produce a confident figure bearing no relation to the actual liability.