Who pays when an AI system causes harm
Liability is still split between the vendor, the deployer and the operator. No single statute assigns it.
City Council
Under review
Reading order
What this desk follows, and why it stays open
Policy moves slower than the technology it tries to govern, so this page is built as a running ledger rather than a single verdict. Each entry tracks a proposal, a hearing or a rule already in force — and states plainly whether it is still being argued, under review, or past its comment window. Where a question is unresolved, we say so instead of guessing at an outcome.
If you are trying to follow one thread — AI liability in particular — the three questions below are the ones that keep coming back at hearings, in council chambers and in the filings that land on this desk.
Skip to the questions- The proposal Who filed it, which body votes
- The obligation What it asks a company to do
- The recourse Who can complain, and where
On the table now
Policy desk list
Six threads this desk is actively following. Each row names the instrument being debated, the body with jurisdiction, and the stage it has reached — so you can tell a proposal from a rule that already applies.
Pricing algorithms and franchise antitrust exposure
Software that recommends prices across independent operators raises a coordination question courts are still untangling.
Federal court
In litigation
Data centers and who gets a say in siting them
Power, water and noise are pushed onto host neighborhoods while the tax revenue lands elsewhere.
Municipal
Contested
Monitoring infrastructure, and the limits of automated enforcement
Camera-based systems that issue findings rather than suggestions invite an appeal question.
State agency
Comment period
Automation in small-business operations
When scheduling and service decisions move to agents, labor rules written for managers need a second look.
Labor board
Open question
Public oversight and the disclosure question
Notice rules vary by agency, so two residents can face the same automated decision with different rights to see it.
Multi-agency
Early stage
Rows stay on this list while a decision is genuinely open. When a rule is finalized, repealed or struck down we move the thread into the archive at the news archive with the date the change took effect.
How a measure moves
A policy story is rarely one event. It is a chain of small procedural steps, and a piece that skips them reads as opinion. These are the stages we track and report on, in the order they usually arrive.
If a stage is missing from a filing — no fiscal note, no comment window, no named enforcement office — that gap is itself the story, and we report it as one.
-
Drafting
The text appears
A sponsor files language, often with a memo explaining intent. The scope line — who is covered, who is exempt — decides most of what follows.
-
Hearing
Both sides get a record
Testimony is where the abstract argument meets a concrete case. We read the submitted statements and the questions asked afterward, not just the opening remarks.
-
Comment
The window opens and closes
A written comment period is the cheapest way for a resident or a small firm to enter the file. Deadlines matter, and they are easy to miss.
-
Adoption
A vote, then a date
Passage is not the same as effect. Rules usually carry a compliance date, and that date is what changes behavior.
-
Challenge
Enforcement or reversal
The rule either gets used or gets tested. Both outcomes are worth reporting, and neither is final on the day it happens.
From the desk
Reporting & oversight
City Council · Liability
Liability questions dominate the council hearing on AI safety
Members pressed on a question the current code does not answer: when an automated system produces a wrong decision, which party in the chain is accountable for it? Witnesses described vendors, deployers and operators passing the same obligation between them, and asked the council to name a responsible party in statute rather than in guidance. The hearing produced no vote, but it put the drafting question on the record.
What to watch next: whether the committee publishes draft language before the next session, and whether any enforcement office is named with funding attached. A mandate without a funded enforcement path tends to stall at the first disputed case.
Read the hearing reportMunicipal
A council meeting derailed over data centers
Residents wanted power and water commitments in writing before any approval moved forward. The meeting broke up without a resolution, and the siting question stayed open.
Public opinion
Concern grows over the pace of AI development
Survey work and public comment both point the same direction: people want a slower rollout and clearer notice, not a pause. That gap shapes how hearings are framed.
Beyond New York
Europe's model race and its rulebook
European releases arrive under a disclosure regime with its own deadlines. What gets filed there often previews the compliance arguments that reach U.S. agencies later.
What this desk actually does
No scoreboard, just the working method behind every policy entry on this page. It is the same process whether the subject is AI liability, a franchise pricing tool or a council vote on data centers.
- Primary text first
- Filings, transcripts, votes — not press summaries
- Stage named
- Draft, hearing, comment, adoption or challenge
- Who is affected
- Residents, small firms, agencies — by name
- Corrections open
- Errors are amended on the page, with the date
Where to go next
Policy reporting sits alongside the technology and business desks, because the rules being written here land on the companies and products those desks cover. If you are following one subject, these are the shortest routes through the paper.
Newsroom
Elisha Yong Journal354 E 31st St, Brooklyn, NY 11226, USA
Monday to Friday, 9:00 AM – 6:00 PM
Phone +1 833 292 3148
Email TheodoreMeyer@elishayong.com
Questions readers keep asking
Short answers to the things people actually write in about, when the subject is AI liability and local regulation. If your question is not here, the newsroom inbox is open during working hours.
Is there a single federal law on AI liability yet?
No. The obligations in force today are a patchwork — sector rules from federal agencies, state statutes, and city-level requirements that apply only inside their own jurisdiction. That means the answer to "who is liable" can change depending on where a system is used and which regulator has authority over the operator.
How can a resident or a small business comment on a rule?
Almost always in writing, during a defined window. Agencies publish a notice, a comment period and a closing date; city bodies often accept testimony at a hearing as well. A short comment that names your specific situation and cites the clause that worries you carries more weight than a general objection, and it becomes part of the public file either way.
Why does this desk report on European rules at all?
Because companies rarely build two versions of the same system. A disclosure or testing requirement adopted in one large market tends to shape the product everywhere, and the compliance arguments made in one place get reused in another. Following them early often explains a U.S. filing months before it arrives.
Does this page take a position on the proposals?
No. The policy desk reports what a measure says, who it covers, what stage it has reached and what opponents and supporters argue. Advocacy belongs on the opinion page, where it is labeled as such and signed. Our standards for sourcing, corrections and labeling are published in full.
I think something on this page is wrong. What now?
Write to the newsroom with the specific passage and, if you have one, the document that contradicts it. Corrections are amended on the page with the date noted, so the record shows what changed and when. We would rather fix a line than defend it.