This website uses cookies

Read our Privacy policy and Terms of use for more information.

New York Staffs Its AI Regulator: Register in November, Comply in January

On 21 September Governor Hochul set two hard dates for New York's RAISE Act: large frontier AI developers will be directed to register with the state from November 2026 and comply in full from 1 January 2027, overseen by a newly staffed regulator inside the Department of Financial Services.

Why It Matters

The administering body is not a future agency but a staffed one: the Office of Digital Innovation, Governance, Integrity and Trust (DIGIT), housed inside the New York State Department of Financial Services, a regulator with an existing examination culture. It now has a named Deputy Director — Marc Gilman, its first full-time hire — with DFS Acting Superintendent Kaitlin Asrow leading implementation. An office with a filing cadence and a public complaint channel is a different proposition from a statute with a future date on it.

The duties are concrete. Developers must publish a safety and transparency framework on their own website, report critical safety incidents to DIGIT within 72 hours, file quarterly assessments of catastrophic risks, and register with a disclosure statement at least every other year from 2027. A 72-hour clock that depends on a weekday triage queue is not a 72-hour clock — the operational build needs a named owner and an out-of-hours path.

New York's move lands against a fragmented backdrop. The same week, California signed a data-centre disclosure package while eleven of its AI bills sat unsigned, and Canada's AI-transparency consultation closes today. Regulators are moving at very different speeds and in different directions — which makes a New York nexus, once triggered, the most concrete near-term obligation on the board.

Action Items

  1. Determine RAISE threshold coverage — by early November, decide whether any model in development crosses the large-frontier-developer threshold for a New York nexus; the registration step lands in November, with no exact date yet published.

  2. Stand up a 72-hour incident clock — assign a named owner and an out-of-hours escalation path before November; a duty measured in hours cannot depend on a weekday queue.

  3. Comment to Canada's ISED consultation today — file even a brief submission before it closes tonight (23 September), prioritising the AI-agent-tracking and serious-incident questions.

Get the full analysis. Pro subscribers receive the complete deep dive, all 5 action items, source documents, and jurisdiction-specific compliance checklists.

logo

Subscribe to Pro to read the rest.

Become a paying subscriber of Pro to get access to this post and other subscriber-only content.

Upgrade

A subscription gets you:

  • Deep dives of each updated regulation
  • Source verification documents
  • Extended jurisdiction-specific analysis
  • Compliance deadline tracker
  • Regulation crosswalk