The Consequence Library · How records are made and graded
In Faiz Enterprise v. State Tax Officer (R/SCA/10123/2026, 2026:GUJHC:53490-DB), decided 20 August 2026, the Gujarat High Court quashed a show cause notice, a GST registration cancellation order, the rejection of the revocation application and the appellate order, after the State Tax Officer admitted using an AI tool that produced non-existent and irrelevant judgments relied on in the order. The court incorporated the state's instructions of 18 August 2026 into its own order, so that violation amounts to contempt.
What happened
A State Tax Officer in Gujarat passed a quasi-judicial order cancelling a business's GST registration. The order relied on case law produced by an AI tool, including at least one citation to a judgment that does not exist and others irrelevant to the point. The officer admitted the use. The petitioner lost its revocation application and its appeal before reaching the High Court. On 20 August 2026 a Division Bench (Justices A. S. Supehia and Vaibhavi D. Nanavati) quashed all four orders and directed a fresh notice and a reasoned order after considering the petitioner's defence. Statewide instructions dated 18 August 2026, requiring verification against primary sources, verbatim reproduction where a tool has paraphrased, consideration of the authorities cited by the taxpayer and the officer's own application of mind, with responsibility fixed on the issuing authority, were incorporated into the court's order.
Where control failed
No departmental control identified the fabricated authorities before the order issued, or at the revocation and appellate stages. The defect was located by the petitioner's counsel and settled by the High Court.
The authority question
The order carried the state's authority. Nothing in the file distinguished the officer's own application of mind from the tool's output, which is the question the court's remedy addresses directly: verification, verbatim reproduction and the officer's independent judgment, with responsibility on the issuing authority.
What could be proven afterward
Everything material could be established afterward, because a cited judgment either exists or it does not. What the record could not show was whose judgment the order rested on. The instructions of 18 August 2026 are written to that gap.
Control state, before and after
Before the consequence
A quasi-judicial drafting process with no recorded check on the authorities relied on, and no record distinguishing the officer's reasoning from the tool's output.
After the consequence
Four orders quashed. Statewide instructions of 18 August 2026 incorporated into the court's order, with contempt as the sanction for breach. Fresh proceedings directed.
Where Regulayer sits
AI agents cannot be trusted to police themselves. Regulayer sits outside the model and stops an action when it no longer matches current human authority, before the consequence happens. It leaves an independently verifiable record of the check. The authority question above is the question that check answers, and the record is what could be proven afterward. Why the authority sits outside the AI · Live Regulayer, try to break it
Sources
- Primary: Gujarat High Court, Faiz Enterprise v. State Tax Officer, R/SCA/10123/2026, 2026:GUJHC:53490-DB, judgment 20 Aug 2026, copy bearing the neutral citation · https://www.verdictum.in/gujarat-high-court/faiz-enterprise-v-state-tax-officer-2026gujhc53490-db-gst-orders-quashed-ai-generated-judgments-1620726
- Secondary: LiveLaw, report on the judgment, Aug 2026 · https://www.livelaw.in/high-court/gujarat-high-court/gst-order-tax-officer-relied-on-ai-generated-judgments-quashed-contempt-547197
- Secondary: Bar and Bench, report on the judgment, Aug 2026 · https://www.barandbench.com/news/litigation/gujarat-high-court-flags-use-of-ai-generated-case-laws-in-tax-orders-warns-tax-officers-of-contempt
- Cross-reference: Regulayer sanctions record, Faiz Enterprise v. State Tax Officer · https://regulayer.com/sanctions/faiz-enterprise-v-state-tax-officer
Record history
Published 7 September 2026. Load-bearing facts re-verified against the cited sources on 7 September 2026. Corrections and material changes are appended here with their dates. To report an error in this record, write to hello@regulayer.com with the record slug and the source you believe is authoritative.
This record describes what sources establish about a consequence and the control state around it. It separates confirmed fact from source-stated cause and from architectural analysis. Gap codes identify a failure class, not a remedy.