October 1, 2026 marks the first duty wave of Connecticut’s AI Responsibility and Transparency Act—the CART Act, Public Act 26-15, signed May 27, 2026 as Substitute Senate Bill 5. It is not a single switch: the statute carries at least six distinct effective dates through 2028.
What does begin October 1, per enrolled-text readings and compliance reports, includes frontier-developer safety and whistleblower duties, provenance requirements for large generative image, audio, or video systems referencing C2PA-style standards, amended subscription disclosures, and a requirement that WARN notices state whether a layoff relates to AI or another technological change.
The automated employment decision technology framework (AEDT, sections 7–12) also “takes effect” October 1, 2026, but operative information-sharing (developer) and disclosure (deployer) duties largely attach to technologies deployed in the state on or after October 1, 2027. Summarizing the CART Act as “a 2027 employment law” or as “everything applies in 2026” is, either way, imprecise.
Neural Pulse urges that caution because secondary coverage has diverged on bill numbers, dates, and sections. Public Act 26-100, signed June 2, 2026, even repealed original CART Act sections before they created duties, replacing subscription-disclosure rules.
October 1 generative provenance covers image, audio, or video systems with more than one million monthly users accessible to consumers—not text generation as the core category. Covered providers must include provenance data to the extent commercially and technically reasonable and make tampering or removal difficult.
Enforcement is essentially by the Attorney General under CUTPA and specific civil mechanisms—with reported caps on the order of $1,000 per violation for frontier duties, plus injunctions—and several sections expressly bar private rights of action. Anyone selling “immediate citizen suits” as an October 1 effect is, on those readings, overstating.
January 1, 2027 brings AI-companion duties (disclosure and self-harm protocols) and anonymous internal reporting channels for large frontier developers. October 1, 2027 triggers AEDT deployment duties. In 2028, social-media protections for minors.
In September’s climate—Ferguson at the FTC, Schatz-Warner in the Senate, Menin in NYC—Connecticut matters because it is state law with a real calendar, not just a hearing. Firms operating agents or multimodal generators toward Connecticut consumers must map which product hits which date.
Frontier labs with users in the state will face, in the first wave, expectations of reporting channels and documentable safety controls, plus provenance on covered synthetic media. Who counts as a “large frontier developer” will demand close statutory reading.
Employers preparing WARN notices must get used to declaring whether AI explains the layoff. That line connects the CART Act to the national labor debate without waiting for 2027.
Neural Pulse offers no legal advice: it offers a journalistic synthesis anchored in public dates. Compliance teams must verify the current enrolled text and later amendments before turning a headline into an internal control.
Compared with NYC proposals (municipal kill switch) or the federal 45-day bill, Connecticut is a mosaic: provenance and WARN now; automated employment with a 2027 trigger; companions in January.
For the archive, September 26’s value is the countdown: days remain until the first wave. Generic “responsible AI” statements no longer suffice against a state AG with dates on the calendar.
Close: on October 1, 2026 the CART Act stops being a May promise and becomes a checklist—with the explicit caveat that not every checklist item lights up the same day.
