No source laundering. A complete route, serial number or portal page does not become exact law unless the official source and amendment chain are closed.
| Tier | Robots | Release | Requirements |
|---|---|---|---|
| A - Certified exact/current | index,follow | May deploy after normal QA | Official source, exact text, amendment chain, effective date, conditions and reviewer approval |
| B - Direct current operational | index,follow where substantive | May deploy with legal hierarchy banner | Official portal/advisory plus statutory anchor and supersession check |
| C - Controlled reconstructed | noindex,follow | Research use; do not represent as exact | Source locator and explicit closure task |
| D - Historical | noindex,follow unless a substantive history page | Period-specific research only | Historical date, supersession and current link |
| E - Unresolved | noindex,follow | Do not rely or deploy as law | P0/P1 source closure |
Required official fields
- Authority, number, date and Gazette reference
- Enabling provision and commencement
- Principal entry, amendments and corrigenda
- Conditions, explanations and annexures
- CGST/IGST/UTGST/SGST counterpart
- Judicial and administrative later treatment
Finin2min Q&A
Does “complete package” mean every notification row is certified verbatim?
No. It means the entire required scope, workflow, route and source-closure control are included. Exact certification remains visible at row level.
Which page should be deployed where multiple phases share a canonical?
Use the publication-precedence register. It selects the latest safe phase and suppresses archived predecessors.
Can noindex pages be used professionally?
They are research and source-control pages. Verify the official source and complete the stated review gate before reliance or public indexation.
How is the repository kept current?
Daily official-source monitoring, weekly judicial and State review, monthly redlines, quarterly source-quality review and annual republication.