News Weekly
0% read
Your progress · 0/5 chapters
About 39 min total
Policy, Regulation & GovernanceISSUE #4 · STORY 20 OF 40Oct 1, 2026CONFIRMED

California's robo-boss ban works by inverting the burden of proof

SB 947, signed on 30 September, bars employers from relying solely on an automated decision system when disciplining or firing, and requires human corroboration when a system is the primary basis. The provision doing the real work is procedural: show that a system was used and the employer must prove it did not primarily rely on it, or face $500 per violation plus punitive damages.

A machine-printed slip lies in a steel cradle on a clerk's counter beside a tray of differently shaped hand-stamped tags, with a release lever that will not move unless one of those tags is laid next to the slip.

Read it your way

CHAPTER 1Picked for Explorer

The 60-second version

Governor Newsom signed SB 947 on 30 September, chaptered as Chapter 859, adding Labor Code sections 1520 through 1526.7. It becomes operative on 1 July 2027 and is deliberately narrow: discipline and termination only, and no notice before the decision is made.

Sole reliance is a flat barAn employer may not rely solely on an automated decision system for a disciplinary or termination decision, at any level of confidence.
Primary reliance needs a humanWhere the system is the primary basis, a human must corroborate it using the data behind it or other supporting information.
The burden flipsOnce automated use is demonstrated, the employer must show it did not primarily rely on the system or that it complied.
Gig workers are excludedThe 2026 version dropped contractor coverage after ride-hailing companies objected, leaving the least protected workers with nothing.
Finish this chapter for +15 XP
A staircase descends to a bare landing where one person holds a single folded paper, while behind them the stair stops at a blank wall with the exposed steel ends of the removed flight left unpainted.
Flip the switch

Employment AI law, from outcomes to process

QuestionHow was the decision producedThe statute makes sole or primary machine reliance unlawful in its own right, whatever the outcome was.
RemedyThe employer proves the negativeOnce automated use is shown, the employer must show it did not primarily rely, or that it complied.
StatusA dated statutory dutyCorroboration, a prescribed notice and a data right all attach from 1 July 2027, with penalties.
Your next move · Explorer

Read the statute, not the coverage

1Read the definition and operative sections directly, because the entire part is short and the definitions do all the gating.
2Apply the exclusion list to your own tools, which carves out firewalls, antivirus, identity and access management, calculators and databases.
3Check the two-tier structure against any summary you have read, since coverage repeatedly merges sole and primary reliance.

Switch your reading mode at the top to see a different next move.

Tap to open

Things to keep an eye on

Pop quiz · unlock the Burden shift badge

Did it stick?

0/3
At what level of reliance do the corroboration, notice and data-access duties attach?+20 XP
What must an employer prove once a system was used in a termination decision?+20 XP
Which of these does the statute not require?+20 XP
Your call · +5 XP

You run HR systems used for discipline in California. What is the first build task?

Research dossierThe full research, labeled and sourcedCONFIRMED9 sources · 39 min read · 20 sections
Story identity
FieldValue

Date reconciliation (important)

The story's event date is recorded as 2026-10-01, which is the date the chaptered text was published by Legislative Counsel and the date the law drew wide press coverage. The operative signature date is 2026-09-30. Both dates fall inside the configured window, so the story is eligible on either reading. The signature date, the announcement date and the effective date are three different dates: 2026-09-30 / 2026-10-01 / 2027-07-01.

Evidence status

ClaimLabelBasis

✓

What happened?

🎓 For Explorer

On 30 September 2026, in the closing days of the legislative session and on what local reporting describes as his last day to sign or veto before leaving office in January, Governor Gavin Newsom signed SB 947, chaptered as Chapter 859, adding Part 5.5.5 to Division 2 of the California Labor Code.

The law is new Labor Code sections 1520 through 1526.7. It governs the use of "automated decision systems" (ADS) — defined in § 1520(c) as "any computational process derived from machine learning, statistical modeling, data analytics, or artificial intelligence that issues simplified output, including a score, classification, or recommendation, that is used to assist or replace human discretionary decisionmaking and materially impacts natural persons."

Three duties and three prohibitions do the real work:

  • § 1522(b)(1) — an employer "shall not rely solely on an ADS when making a disciplinary or termination decision."
  • § 1522(b)(2) — where an employer "primarily relies upon an ADS output" for such a decision, it "shall direct a human to corroborate the decision using data that was collected or used to produce the ADS output or other relevant corroborating or supporting information."
  • § 1522(c) — if the employer cannot corroborate, or the human reviewer concludes the output is "inaccurate, incomplete, or misleading," the employer "shall not use the ADS output to make a disciplinary or termination decision."
  • § 1522(d) — the employee may request, and the employer must provide, "a meaningful, objective description of the employee's own data used by the ADS."
  • § 1524 — the employer "primarily relied upon" an ADS must give the affected employee a written post-use notice at the moment it tells the employee of the decision, containing four mandated elements.
  • § 1522(a) — three categorical prohibitions with no human-review escape hatch: no ADS use to prevent compliance with or violate labour, occupational-safety, employment or civil-rights law; no ADS inference of an employee's protected status under Government Code § 12940 (FEHA); no ADS use to predict and take adverse action against a worker for exercising legal rights.

Separately, in the same session Newsom signed SB 951 (Cal-WARN notice when AI causes a mass layoff, relocation or termination), AB 1331 (no workplace surveillance tools in workplace bathrooms), AB 1883 (restrictions on AI workplace surveillance, including emotion inference and neural data), and AB 1979 (AI advisory only in nursing, no replacement of clinical judgment). He vetoed AB 2656 and AB 2575 the same day.

The sequel, not the debut

SB 947 is a narrowed re-run of SB 7 (2025), which Newsom vetoed on 13 October 2025. His veto message called the earlier bill's "unfocused notification requirements on any business using even the most innocuous tools" and its "overly broad restrictions." He also pointed to duplicative existing regulation — the California Privacy Protection Agency's newly finalised ADMT regulations. McNerney then re-introduced the bill in February 2026 and removed the pre-use notification requirement, dropped gig-worker coverage that had drawn heavy criticism from Uber and Lyft, and tightened the ADS definition. The 2026 version is what the Governor signed.


Δ

What changed?

The headline change is that "a robot fired me" stopped being a grievance and became a statutory cause of action — with a defined burden-shifting rule attached.

Five specific deltas matter:

  1. A flat prohibition on sole reliance. § 1522(b)(1) is unconditional: no employer may rely solely on an ADS output for a disciplinary or termination decision. This is not conditioned on any finding about how central the ADS was.
  2. A separate, affirmative corroboration duty at the "primary basis" threshold. § 1522(b)(2) is triggered by primary reliance. This is a materially different and lower standard than sole reliance, and the statute keeps the two tiers apart. Any secondary reporting that collapses them into one "human-in-the-loop" phrase loses the operative distinction.
  3. A mandatory, statutorily prescribed notice with four fixed elements. § 1524(b) requires the notice to affirmatively state that the employer primarily relied on an ADS, that "a human reviewed the decision and corroborated the ADS output," a human contact, and the anti-retaliation statement. This is a prescribed certification, not a free-form memo.
  4. A new employee data right. § 1522(d) creates a request-and-response right to "a meaningful, objective description of the employee's own data used by the ADS."
  5. An evidentiary reversal in litigation. § 1526.1(c): in any civil action or administrative proceeding for a violation of § 1522(b) or (c), "once it has been demonstrated that an ADS was used to make a disciplinary or termination decision, the employer must demonstrate that the employer did not primarily rely upon an ADS or that the employer complied with Sections 1522 and 1524." The burden of proof shifts to the employer once ADS use is shown. Sanctions are $500 per violation, with preliminary injunctive relief, punitive damages and attorney's fees available (§ 1526.1(d)–(e)).

The four precision points that matter most

(a) "Sole basis" vs "primary basis" are not interchangeable. framing ("Where an ADS is the primary basis for such a decision, the employer must have human corroboration, provide written notice, and give the employee access to the data used") is directionally right but incomplete. Per the chaptered text, corroboration, notice and data access attach at primary reliance; a flat bar attaches at sole reliance; and both duties attach only to disciplinary and termination decisions. The corollary matters commercially: a workflow in which an ADS is one of several inputs but is not primarily relied upon is still lawful — but only if the employer can prove that under a burden-shifting rule.

(b) The bill does not cover other adverse actions. The corroboration, notice and data-access duties reach discipline and termination only. They do not reach hiring, promotion, compensation, scheduling, or deactivation of gig workers. Those remain governed by other instruments (CCPA ADMT regulations, FEHA, the Civil Rights Council's ADS rules, and the new Cal-WARN expansion in SB 951). The "AI-driven firing and discipline" framing in the story title is therefore accurate, and importantly narrower than a general "AI hiring law" reading.

(c) The employer definition is far wider than private tech. Under § 1520(d), "employer" includes "all branches of state government, including all cities, counties, charter counties, municipalities, charter municipalities, cities and counties, special districts, transit districts, the University of California upon agreement by the regents, the California State University, community college districts, school districts, or any other governmental entity" — plus labour contractors, farm labour contractors (§ 1682) and foreign labour contractors (§ 9998.1 of the Business and Professions Code). This reaches public-sector HR and the staffing supply chain, not just Silicon Valley vendors.

(d) The nickname is not a statutory short title. The chaptered text carries no short title: it reads "An act to add Part 5.5.5 (commencing with Section 1520) to Division 2 of the Labor Code." "No Robo Bosses Act of 2026" is the name used by the sponsor's press release and by press coverage. Treat it as a nickname that has become the de facto handle.

--

A staircase descends to a bare landing where one person holds a single folded paper, while behind them the stair stops at a blank wall with the exposed steel ends of the removed flight left unpainted.
↔

Before → Change → After

🎓 For Explorer
Before (status quo at signature, 2026-09-30)
**No state statute** barred sole reliance on an automated system for a firing or disciplinary decision.
**Chicago/Illinois Public Act 103-0804** (effective January 2026) required employers to **notify** workers when AI is used for specified employment purposes. Per CNBC's independent read: it "stops short of an outright prohibition on deploying agentic digital systems for employment decisions." Notice, no corroboration duty.
**NYC Local Law 144** (bias audits for automated hiring tools) was the most aggressive US rule on employment AI, but it is a **municipal** requirement and per the California Gazette's comparative read "does not extend to termination or discipline."
**The CPPA's ADMT regulations** (adopted September 2025) already imposed notice, access and opt-out duties on automated decisionmaking for CCPA-covered businesses. Newsom's 2025 veto message leaned on this existing regime. SB 947 explicitly **carves them back in** at § 1526.4.
**Existing tort and statutory law** — FEHA, the state's wrongful-termination and discrimination regimes — already covered *discriminatory outcomes* from algorithms, but required the worker to prove discrimination. There was no rule about the *process*.
Practically: "bossware" — more than 550 such products per the sponsor's estimate — could terminate, deactivate or discipline with no statutory human-in-the-loop requirement.
→
After (what the operating environment looks like from 2027-07-01)
Every California adverse-action decision pipeline, at every public employer, staffing firm and private employer, has a statutory audit point: *was this sole reliance? was it primary? who corroborated, with what, and can we prove it?*
"Human-in-the-loop" stops being an ethics aspiration and becomes an evidentiary record-keeping obligation with a penalty attached.
Multistate employers get a partial harmonisation gift: § 1526.3 says an employer compliant with **this** part's notice requirements "is not required to comply with any substantially similar notice provisions related to automated decision systems used for employment-related decisions required under any other state law" — an unusually explicit interstate compliance safe harbour.
Local ordinances survive: § 1526.2 declines to preempt any city, county or city-and-county ordinance providing equal or greater protection.
CPPA ADMT duties **survive for CCPA businesses** (§ 1526.4) — this is not a displacement statute.
⚙

How it works

Definitions that do the gating (Lab. Code § 1520)

TermStatutory definition (paraphrased from chaptered text)Why it matters
ADS (§1520(c))Computational process derived from ML, statistical modelling, data analytics or AI that issues simplified output — a score, classification or recommendation — used to assist or replace human discretionary decisionmaking and materially impacts natural personsBroad on inputs, narrow on output form. "Simplified output" is the operative qualifier.
ADS exclusionsSpam email filter, firewall, antivirus software, identity and access management tools, calculator, database, dataset, other compilation of dataSecurity tooling, BI and data-warehouse tools are out. IAM explicitly out.
ADS output (§1520(a))Any information, data, assumptions, predictions, scoring, recommendations, decisions or conclusions generated by an ADSNotably includes assumptions — so a model's reasoning inputs, not just its verdict.
Employee data (§1520(d)(4))Any information that identifies, relates to, or describes an employee, regardless of how collected, inferred or obtainedInference counts.
Employee (§1520(d)(2))"Any person employed by an employer"No gig-worker coverage — Prop 22 contractors excluded (confirmed by KQED and CNBC).
Employer (§1520(d))Private person exercising control over wages/hours/conditions; plus all branches of state government and local government entities; plus labour contractors, farm labour contractors, foreign labour contractorsPublic sector and staffing are inside the perimeter.

The decision gate, in the order the statute orders it

Adverse action contemplated (disciplinary or termination only)
        │
        ├── §1522(a) screen ────────────────────────────────  FLAT PROHIBITIONS
        │   • would it prevent compliance with / violate labour,
        │     occupational-safety, employment or civil-rights law?
        │   • does it infer protected status under Gov. Code §12940?
        │   • does it predict & take adverse action against a worker
        │     for exercising legal rights?
        │        → any YES = prohibited outright. No review cures it.
        │
        ├── §1522(b)(1) ─────────────────────────────────────  SOLE-RELIANCE BAR
        │   Is the ADS the ONLY basis for the decision?
        │        → YES = prohibited. Flat. No materiality threshold.
        │
        ├── §1522(b)(2) ─────────────────────────────────────  CORROBORATION
        │   Does the employer PRIMARILY rely on the ADS output?
        │        → YES: direct a human to corroborate, using data
        │          collected or used to produce the ADS output, or
        │          other relevant corroborating/supporting info:
        │          (A) supervisory or managerial evaluations
        │          (B) personnel files
        │          (C) work product of employees
        │          (D) peer reviews
        │          (E) witness interviews (may include relevant
        │              online customer reviews)
        │
        ├── §1522(c) ────────────────────────────────────────  STOP RULE
        │   Could not corroborate? OR human reviewer found the
        │   output inaccurate / incomplete / misleading?
        │        → YES: the ADS output may NOT be used for the
        │          decision at all.
        │
        ├── §1524 ───────────────────────────────────────────  POST-USE NOTICE
        │   At the moment the employer informs the employee of the
        │   decision, issue a separate, stand-alone written notice:
        │     (1) plain language
        │     (2) in the language used for routine employee comms
        │     (3) simple easy-to-use delivery (email, hyperlink,
        │         other written format)
        │   Content, all four required:
        │     (1) that the employer PRIMARILY relied on an ADS
        │     (2) that a human reviewed the decision and CORROBORATED
        │         the ADS output
        │     (3) a human contact for more information, including
        │         the employee's data-description right
        │     (4) that retaliation is prohibited
        │
        └── §1522(d) ─────────────────────────────────────────  DATA RIGHT (on request)
            Employee requests a "meaningful, objective description"
            of their own data used by the ADS → employer must provide.
            §1522(e): the description must anonymise other individuals'
            personal information.

Enforcement architecture (§§ 1526–1526.7)

MechanismProvision
Anti-retaliation (no discharge, threat, demotion, suspension, discrimination)§ 1526
Labor Commissioner enforcement — investigation, temporary relief / status quo pending hearing under Labor Code §§ 98.3, 98.7, 98.74, 1197.1, citations, civil action§ 1526.1(a)
Public prosecutor enforcement§ 1526.1(b)
Burden shift on ADS use§ 1526.1(c)
Preliminary injunctive relief, punitive damages, attorney's fees§ 1526.1(d)
$500 civil penalty per violation§ 1526.1(e)
Local ordinances not preempted where equal or greater protection§ 1526.2
Interstate notice preemption / CPPA carve-out§§ 1526.3, 1526.4
CBA waiver§ 1526.5
Federal-necessity carve-out§ 1526.6
Operative date§ 1526.7 — 1 July 2027
Statewide concern, binds all cities including charter citiesAct § 2
SeverabilityAct § 3

The exemptions, precisely

CBA waiver (§ 1526.5). The part does not apply to parties covered by a collective bargaining agreement only if the agreement all three: (1) explicitly waives the part "in clear and unambiguous terms"; (2) expressly provides for the wages or earning, working conditions, and other terms and conditions of work; and (3) provides protection from algorithmic management. This is a three-part conjunctive test, not a general union opt-out — a materially underexamined detail in most coverage.

Federal necessity (§ 1526.6). No application to the extent ADS use is required by, or reasonably necessary to comply with, a federal statute, federal regulation or binding federal contract relating to (1) development of aircraft for use in the national airspace, or (2) development of products or services for national security, military, space or defense purposes. Subsection (b) narrows this further: the carve-out applies only to the operations covered by the listed federal instruments.

CPPA carve-back (§ 1526.4). A business subject to the CCPA remains subject to any privacy-related ADMT regulation duly adopted by the California Privacy Protection Agency under Civil Code § 1798.185 and § 1798.199.40(b). Confirmed as live regulation: CPPA lists a completed September 2025 package, "CCPA Updates, Insurance, Cybersecurity Audits, Risk Assessments, and Automated Decisionmaking Technology (ADMT) Regulations."

Interstate notice safe harbour (§ 1526.3). Compliance with this part's notice requirements displaces "substantially similar notice provisions related to automated decision systems used for employment-related decisions" under other state law — but expressly not for "quotas, as defined in Section 2100," or any other automated standards applied to working conditions.


!

Why it matters

🎓 For Explorer

INTERPRETATION, grounded in confirmed statutory text.

  1. It regulates the process, not the outcome. FEHA and anti-discrimination law already made discriminatory algorithmic outcomes unlawful. SB 947 makes it unlawful for the outcome to be produced by a specific process — one where the machine was the sole or primary basis. That is a categorically different compliance object: it cannot be discharged by an outcome-testing regime (bias audits, disparate-impact analysis) alone.
  2. The burden shift makes it enforceable in practice. A worker cannot easily prove what the employer "primarily relied on" — that fact lives in the employer's systems. § 1526.1(c) resolves the information asymmetry by requiring the employer to demonstrate the negative once ADS use is shown. This is the single most consequential procedural provision in the bill.
  3. It reaches a compliance surface nobody had instrumented. The corroboration list in § 1522(b)(2) — supervisory evaluations, personnel files, work product, peer reviews, witness interviews — is an inventory of exactly the artefacts HR systems rarely retain per-decision in a reviewable form. Employers will have to prove, per decision, that corroborating material existed and was considered.
  4. It converts "human in the loop" from a marketing claim to an auditable control. A vendor that advertises "human-in-the-loop review" is now asserting something with statutory consequences. The law does not require independence, authority or expertise — but it does require the employer to say in writing that a human reviewed and corroborated, under penalty of per-violation penalties and punitive damages.
  5. It is deliberately the first. Combined with the same-day package (SB 951 mass-layoff notice, AB 1883 emotion/neural-data surveillance restrictions, AB 1331 bathroom surveillance, AB 1979 clinical judgment), California has assembled a complete employment-AI legislative stack roughly one year before its federal counterparts exist. Per CNBC, federal legislation carrying the same name (Sen. Ed Markey and Sen. Brian Schatz, June 2026) was "effectively dead on arrival," and New York, Louisiana and New Jersey had proposals but had not acted.
  6. The political economy matters. The Governor signed this on his way out of office, in a session where he signed an EO requiring state agencies to keep saying "artificial intelligence" rather than "Super Intelligence." The bill became law in an environment of high public distrust of workplace AI (CNBC cites a July Gallup poll: 39% of Americans say AI does more harm than good, up 8 points from 31%; and a Pew study released that August: 71% think AI will take people's jobs). PREDICTION, low confidence: this signing is more likely to be read as a positioning statement about 2028 than as a technical compliance milestone.

✦

What became possible?

🎓 For Explorer

What genuinely became possible on 2026-09-30:

  • A statutory cause of action with a workable evidentiary path. A terminated worker who can show any ADS was used in the decision gets the burden shifted. Combined with $500/violation penalties and punitive damages, this makes class-adjacent exposure real.
  • A discoverable compliance surface for adversarial use. Antitrust, employment and consumer plaintiffs now have a statutory hook — "the employer primarily relied on an ADS" — that does not require proving discrimination.
  • A compliance product category. Per-decision corroboration records, ADS-output lineage, "primarily relied on" classification, prescribed notice generation, and data-description response workflows become sellable enterprise software. This is the clearest new business surface the story creates.
  • A bargaining chip. § 1526.5's CBA carve-out (waiver plus explicit working-terms coverage plus algorithmic-management protection) gives unions a concrete template: "we will waive the statute only if our CBA bans algorithmic management." Unions can now price the statute's protections.
  • A template other states can copy. A narrowed, veto-proof, union-sponsored, 29–10 / 53–14 bill with an explicit interstate-notice safe harbour (§ 1526.3) is a genuinely portable artifact. California solved the multistate-conflict problem that stalled other states.
  • A defensible "we don't rely on robots" claim. Employer marketing in California now has a statutory backing.

What did NOT become possible:

  • Employers cannot lawfully automate discipline or termination. The gate is a stop, not a speed-up.
  • There is no right to pre-decision notice, no pre-decision data access, no appeal or independent-review mechanism, no right to an explanation of the reasoning, and no audit requirement. All of those remain absent.
  • Nothing changed for hiring, promotion, compensation or scheduling under this statute.
  • Nothing changed for gig contractors classified as independent contractors under Proposition 22. KQED's reporting is explicit that rideshare drivers were "notably left out of the SB 947 party," and CNBC confirms McNerney "stripped language that would have extended the Act's protections to gig workers."

◎

Implications

Technical

INTERPRETATION of statutory text in engineering terms.

  • "Materially impacts natural persons" and "simplified output" define the detection problem. § 1520(c) reaches computational processes emitting a score, classification or recommendation that materially impacts people, and excludes firewalls, antivirus, IAM, calculators, databases and datasets. Engineering consequence: an enterprise needs a runtime classifier that decides whether any given component emits a materially-impacting simplified output. That is a hard, contestable call, and the statute gives no threshold, no list, and no safe harbour.
  • "ADS output" includes "assumptions" (§ 1520(a)). This is broader than most people expect. The compliance record must capture the model's inputs and reasoning-relevant parameters, not just the score. Feature-level lineage is required, not optional.
  • "Employee data" includes inferred information (§ 1520(d)(4)). Any model feature derived by inference — inferred emotion, inferred productivity, inferred protected-class proxies — is employee data. The § 1522(a)(2) prohibition on inferring protected status under Gov. Code § 12940 therefore reaches feature engineering, not just decisioning. This is the highest-consequence line in the bill for ML teams.
  • A corroboration service must be built. § 1522(b)(2) requires the corroborating material to be available to and used by the human reviewer. Engineering minimum: a decision-time system that (a) surfaces the ADS output alongside its source data, (b) captures the supervisor's evaluation / personnel file / work product / peer review / witness statements considered, (c) records the corroboration verdict, and (d) timestamps the reviewer. The CA Gazette's claim that the reviewer must have "authority, competence, and practical ability to override" is not in the statute — do not build a compliance control on it as a legal requirement (see §13).
  • The § 1522(c) stop rule needs a hard kill path. If corroboration fails or the reviewer concludes the output is inaccurate/incomplete/misleading, the ADS output "shall not" be used for the decision. That means the decision must be unwindable and re-decisionable on non-ADS grounds.
  • The notice must be generated, not written. § 1524 prescribes four content elements, plain language, a separate stand-alone communication, in the employee's routine communication language, delivered at the moment the decision is communicated. Engineering requirement: notice templating that is (a) language-aware, (b) segregated from the termination letter, (c) versioned for audit, and (d) triggered by the ADS-primary classification.
  • The data-description response needs redaction. § 1522(e) requires the description to anonymise other individuals' personal information — so a per-employee data-subject response pipeline with cross-entity redaction is mandatory. The statute's own drafting here is sloppy ("the customer's, other employee's, or individual's personal information," a phrase that reads as carryover from a consumer-facing draft), so expect to over-comply here rather than under-comply.
  • Interim preemption (§ 1526.3) is an architectural instruction. Multi-state employers can build one notice path for ADS-related employment decisions where another state's law is "substantially similar" — but not for quota rules (§ 2100) or other automated working-conditions standards. Quota compliance must stay on a separate track.
  • Nothing in the architecture enforces the § 1522(a) prohibitions technically. Using an ADS to infer protected status is a prohibition, not a control. There is no compliant implementation of that feature; the work is to remove the capability, not to gate it.

Developer

For developers of HR technology, workforce analytics, staffing platforms, scheduling and adjacent SaaS:

  • Your product's "human-in-the-loop" marketing becomes a statutory representation. If a customer relies on your score as the primary basis for a disciplinary or termination decision, the customer — not you — must satisfy §§ 1522 and 1524. Your product must therefore enable the compliance: expose ADS-output lineage, expose corroborating artefacts, classify reliance level, emit the prescribed notice, and answer data-description requests. A vendor that supplies a score with no lineage is effectively supplying an unusable product for discipline/termination decisions in California.
  • There is no safe harbour for "assist." § 1520(c) covers processes used "to assist or replace" human discretionary decisionmaking. Positioning a tool as a decision assistant does not move it outside the definition.
  • Feature-level protected-status inference is a stop-ship. § 1522(a)(2) prohibits using an ADS "to infer an employee's protected status under Section 12940." Age, disability, family status, pregnancy, race proxies, and any aggregate signal derived from them are in scope. Audit your feature store for proxy inference, not just for explicit protected attributes.
  • Public-sector and staffing customers are in scope. § 1520(d) puts cities, counties, school districts, transit districts, UC, CSU, labour contractors, farm labour contractors and foreign labour contractors inside "employer." If your roadmap assumed "HR tech = private tech," your addressable-compliance surface just changed.
  • Rigour on the exclusion list is cheap insurance. § 1520(c) excludes firewalls, antivirus, IAM tools, calculators, databases and datasets. Document why each component you ship is or is not an ADS — § 1526.1(c) puts the evidentiary burden on the employer, but the employer will look to the vendor for the taxonomy.
  • Build the reliance-level classifier as a first-class API. Given § 1522(b)(1) (sole reliance, flat bar) and § 1522(b)(2) (primary reliance, corroboration + notice), the single highest-value new endpoint in your product is a deterministic, auditable "was this decision sole, primary, secondary, or uninvolved ADS reliance?" call made at decision time.
  • No gig-worker features from this statute. Do not sell California coverage to platforms on the basis that Prop 22 contractors are covered. They are not.

Enterprise

For California-exposed employers, ranked by urgency:

  1. Inventory and classify (§1520(c)). Build a register of every system emitting a materially-impacting score, classification or recommendation that reaches a disciplinary or termination decision — including spreadsheets, vendor tools, and "informal" manager-facing dashboards. Record the exclusion analysis too.
  2. Kill sole-reliance paths (§1522(b)(1)). Any pipeline where the ADS output is the decision is prohibited today as a matter of engineering, from 2027-07-01. This is a build task, not a policy task.
  3. Instrument corroboration (§1522(b)(2)). The corroboration list is your data model. Supervisory evaluations, personnel files, work product, peer reviews, witness interviews must be captureable at decision time and retrievable later, per decision.
  4. Implement the stop rule (§1522(c)). Unwinding a decision is harder than making one. Design the re-decision path.
  5. Template the notice (§1524). Four content elements, plain language, stand-alone, correct language, simple delivery, issued at the moment of the decision communication. Build it into the termination workflow; do not let it be a manual step at a moment when HR is under pressure.
  6. Stand up a data-description responder (§1522(d)–(e)). "Meaningful, objective description of the employee's own data used by the ADS," anonymised for others. This is a per-employee, ad-hoc, human-reviewed response.
  7. Fix the protected-status problem (§1522(a)(2)). This is a capability-removal project, not a policy project. It affects feature engineering, vendor features and even legitimate-seeming productivity models.
  8. Map the enforcement surface. Labor Commissioner (with authority to order interim status-quo relief), public prosecutor, and private action. Retention of decision records should be planned for adversarial production, not for routine HR housekeeping.
  9. Check the CBA interaction. If any part of your workforce is under a collective bargaining agreement, § 1526.5's three-part test governs whether the statute applies at all. This is a legal question to answer per agreement, not a blanket assumption either way.
  10. Reconcile with the CPPA ADMT regime. § 1526.4 keeps CPPA duties alive for CCPA businesses. § 1526.3's preemption covers other state ADS-notice laws but not the CPPA and not quota rules. You are likely running two overlapping programmes; plan for one evidence base feeding both.
  11. Public-sector readiness. Cities, counties, districts, UC and CSU are "employers" under § 1520(d). Public-entity HR tech contracts signed before 2026 will need amendment to carry corroboration, notice and data-response obligations, and procurement should require it prospectively.

Strategic

  • PREDICTION (moderate confidence): Other states will copy the architecture faster than they copy the substance. § 1526.3's interstate notice preemption is the exportable novelty — it gives multistate employers a reason to prefer California-style rules. A second state adopting the same clause would materially increase the value of that clause and accelerate a federal baseline. Candidate movers per CNBC and Fisher Phillips: New York, New Jersey, Louisiana, Massachusetts.
  • PREDICTION (moderate confidence): Litigation, not regulation, will produce the first real doctrine. The undefined term "primarily relies" is the battleground — the Chamber of Progress's Robert Singleton objected to precisely this in a letter urging veto, and the objection survived into the enacted law. Expect definitional fights in the first § 1526.1(c) burden-shift motions.
  • INTERPRETATION: the statute's own circularity is a predictable litigation seam. § 1522(b)(2) directs the human to corroborate "using data that was collected or used to produce the ADS output or other relevant corroborating or supporting information," then lists corroborating information. The primary instruction points back at the very data that generated the output. Jackson Lewis reads the clause as "using the information that produced the output or other relevant material," i.e. either satisfies. A plaintiff will read it as insufficient. This ambiguity will not be resolved until 2028.
  • INTERPRETATION: the vendor relationship inverts. Today HR buys a score and remains the decision-maker of record. After this, the employer must produce per-decision evidence of review and issue a statutory certification. That makes evidence-capable vendors structurally advantaged and black-box vendors structurally exposed — the buyer is no longer buying a ranking, they are buying an evidentiary record.
  • INTERPRETATION: the California pattern (union-sponsored, narrowed to survive a veto, explicit carve-outs for collective bargaining, gig workers, national security and CPPA duplication) is a reusable playbook for other states. Notably, § 1526.5 does not merely exempt CBAs — it conditions the exemption on algorithmic-management protection. That is a policy design other legislatures can lift directly.
  • PREDICTION (low-moderate confidence): the § 1522(a)(2) protected-status inference prohibition will produce the most litigation risk per unit of compliance effort, because it is a capability ban that most employers do not yet know exists in statutory form. Several organisations will discover an inference they believed was lawful.

⚠

Risks & limitations

Risks

Risks to employers

  1. Sole-reliance exposure in legacy pipelines. Any system that auto-terminates, auto-suspend or auto-deactivates without a human decision is a flat violation from 2027-07-01, regardless of how accurate it is.
  2. "Primarily relied on" is undefined. Under § 1526.1(c) the employer must prove it did not primarily rely. Ambiguity in the standard is litigated against the party holding the records.
  3. Rubber-stamp review. § 1524(b)(2) requires the employer to certify in writing that "a human reviewed the decision and corroborated the ADS output." Review that is a formality is a certification the employer cannot honestly make.
  4. Protected-status inference (§1522(a)(2)) — a flat prohibition on a capability that many employers ship today without a legal review.
  5. Notice as a fresh evidentiary exhibit. The § 1524 notice is a contemporaneous, employer-authored, per-decision statement about the basis of a termination. In any dispute it is a document the employer's counsel did not write for the litigation.
  6. $500 per violation is unremarkable per item but multiplicative across a workforce and a lookback period.
  7. Retaliation exposure (§1526) attaches to employees "using or attempting to use their rights under this part," including filing a Labor Commissioner complaint — so internal investigation volume rises.
  8. Punitive damages and attorney's fees (§1526.1(d)) raise the ceiling well above the per-violation penalty.
  9. Interim status-quo relief lets the Labor Commissioner order that a termination or suspension be undone pending investigation.
  10. Public employers and labour contractors cannot contract out of the statute's substance, and public-entity procurement cycles are slow.

Risks to the law itself

  1. Definition risk. "Materially impacts natural persons," "simplified output," "primarily relies," "disciplinary" and "deactivation" are all undefined. § 1526.1(c) even uses "disciplinary or deactivation decision" where § 1522(b) says "disciplinary or termination decision" — a drafting inconsistency in the burden-shifting provision, in the very provision that will decide cases.
  2. Enforcement-capacity risk. A new Labor Code part with no dedicated guidance, no forms, no approved notice template and no published interpretive rules 21 months before it bites.
  3. Preemption risk. § 1526.2 preserves local ordinances with "equal or greater protection," inviting divergent local overlay. § 1526.3's "substantially similar" test is undefined and will be litigated across state lines.
  4. Policy-reversal risk. The bill is a direct product of one Governor's late-session decision. Its own sponsor's characterisation of the successor bill's negotiation ("McNerney removed the pre-notification requirement and stripped language") shows the statute's content is a function of a single veto negotiation.

Limitations

Limitations of the research

  • This analysis rests on the chaptered bill text (Chapter 859, version dated 09/30/26) as published by California Legislative Counsel. The legislative history, committee reports, bill analyses, fiscal estimates and Newsom's signing statement were not retrieved. No court has yet construed any section.
  • Earlier versions were not compared. The chaptered text was read; the 10 prior versions in the leginfo version list (02/02/26 introduced through 09/04/26 enrolled) were not diffed. Statements here describe the enacted law only.
  • No comparative statutory survey was performed. The "first in the nation" assessment rests on press and law-firm comparative analysis (CNBC, California Gazette, Jackson Lewis, Fisher Phillips) identifying Illinois PA 103-0804, NYC Local Law 144, the Colorado AI Act and the EU AI Act as the nearest comparators. A dedicated 50-state survey was not run.
  • The "No Robo Bosses Act of 2026" name is not a short title in the chaptered text. Whether it appeared in an earlier version was not determined.
  • Federal bills (Markey/Schatz, June 2026) and the pending New York, New Jersey and Louisiana proposals were identified via press reporting, not by reading the bills.

Limitations of the law itself

  • Narrow by design. Discipline and termination only. No hiring, promotion, pay, scheduling or performance-review coverage.
  • No employees' remedies in the operative duties section beyond the general scheme. No pre-decision notice. No appeal. No independent reviewer. No audit mandate. No record-retention mandate. No licensing or vendor-certification regime.
  • "Corroborate" is circular on its face (§ 1522(b)(2): corroborate using "data that was collected or used to produce the ADS output").
  • The corroboration duty prescribes inputs, not a standard. Listing permissible evidence is not a test for what makes it sufficient.
  • The anti-retaliation clause does not create a private right of action on its face; remedies run through the § 1526.1 channels. Whether a standalone § 1526 claim exists is untested.
  • $500 per violation is a low per-event figure relative to the cost of the compliance programme, which is presumably the point.
  • No gig workers. Proposition 22 contractors remain exposed to algorithmic management with none of these protections.
  • Section 1526.4 keeps CPPA ADMT duties alive, so the "one statute fixes it" reading is wrong for CCPA businesses.
  • Section 1526.5's CBA carve-out is a bargaining instrument, not just an exemption.

?

Open questions

  1. Will the Labor Commissioner issue regulations, model notices or interpretive guidance before 1 July 2027? Nothing in the Act requires it.
  2. What does "primarily relies upon" mean as a matter of evidentiary burden when the record will be produced by the employer? This is the whole case.
  3. Is a corroborating human reviewer who is the author of the original performance documentation — the manager whose write-up seeded the data — a meaningful corroborator under § 1522(b)(2)?
  4. Do § 1522(a)'s categorical prohibitions trigger on feature presence (an unused but deployed protected-status inference model) or on use?
  5. Does the § 1522(d) "meaningful, objective description" reach model weights, prompts and feature importances, or only data points? The statute says "data," and § 1520(d)(4) says "any information that identifies, relates to, or describes an employee," which points toward the broader reading.
  6. Does § 1522(e) anonymisation permit partial redaction that preserves the explanation, and who decides?
  7. Does § 1526.1(c)'s burden shift apply in arbitration, or only in "civil action[s] or administrative proceeding[s]"? It names only those two forums — a gap for California employers with mandatory arbitration clauses.
  8. Is "disciplinary" narrower than "discipline" in § 1524(a)? The statute uses "disciplinary" without definition, and a manager's write-up might be either a "discipline" (covered) or performance management (not covered).
  9. Do school districts and UC (§ 1520(d)(2)(B)) face special constraints from other law — e.g. constitutional due process or statutory tenure protections — that conflict with § 1526.1(a)'s interim relief?
  10. Will § 1526.3's "substantially similar" preemption be asserted against New York, New Jersey or Massachusetts laws, and who arbitrates that?
  11. Are CBA waivers under § 1526.5 already being negotiated into 2027 contracts, and what does "protection from algorithmic management" have to say to be sufficient?
  12. Will § 1526.6's federal-necessity carve-out be read expansively by defence contractors using it as a general shield?
  13. Will anyone test whether a federal No Robo Bosses bill revives, and would a federal statute preempt § 1526.3's interstate scheme?

↗

What happens next?

🎓 For Explorer

CONFIRMED / scheduled

  • 1 July 2027 — § 1526.7: the Part becomes operative. All duties and prohibitions apply.
  • The Labor Commissioner gains authority under § 1526.1(a) to investigate, order interim relief and issue citations "through the procedures set forth in Section 98.3, 98.7, 98.74, or 1197.1." Nothing in the Act schedules guidance, model notices or interpretive rules.

PREDICTION — near-term watch items (labelled as prediction, not fact)

  1. No Labor Commissioner guidance before 2027 is plausible, and its absence would be the single biggest enforcement variable. Expect employer-side law firms and consultancies to produce the first interpretive artefacts instead.
  2. First test of "primarily relies" will arrive as a summary-judgment motion on a § 1526.1(c) burden shift, likely in Los Angeles or San Francisco, within 12–24 months of the operative date. PREDICTION, moderate confidence on timing; low confidence on outcome.
  3. Interim status-quo relief is the sharpest near-term exposure. A Labor Commissioner ordering a termination or suspension to be reversed pending investigation is a far larger cost than $500 per violation.
  4. Vendor product cycles will be visibly reorganised around California by mid-2027: reliance classification, corroboration records, notice generation, data-description response. PREDICTION, moderate-high confidence.
  5. At least one state will introduce a copy during the 2027 sessions, and the interesting contest will be over whether to adopt § 1526.3's interstate notice preemption. PREDICTION, moderate confidence.
  6. Proposition 22 gig-worker exclusion will be litigated or legislated, because it is the most visible gap in an otherwise labour-movement-sponsored bill. PREDICTION, moderate confidence.
  7. A challenge on § 1522(a)(2)'s breadth is likely, on the theory that it bans a capability rather than regulating conduct. The statute's own words — "shall not use an ADS to infer an employee's protected status" — read as capability-neutral but are capable of capability-level reading. PREDICTION, low-moderate confidence.
  8. Enforcement will run through the Labor Commissioner and public prosecutors long before private employment litigation. § 1526.1(c)'s burden shift is most useful to a plaintiff's counsel with records access; the Commissioner route needs no private bar. PREDICTION, moderate confidence.

★

Editorial takeaway

🎓 For Explorer

The headline was right and the operative text is narrower and stranger than the headline.

Three things are worth taking away in order.

First, the actual new thing is a burden shift, not a "human in the loop." Every headline in this story's coverage — mine included — describes a human-in-the-loop requirement. The statute's most consequential provision is § 1526.1(c): once it is demonstrated that an ADS was used to make a disciplinary or termination decision, the employer must prove it did not primarily rely on the ADS, or that it complied. That reverses the ordinary logic of employment litigation, where the worker must prove the employer did something wrong and the employer holds the records. It is why a $500-per-violation penalty is not a small number: it is a multiplier applied to a burden the employer cannot easily discharge.

Second, "first US law" is defensible but only if you say what you mean. California is the first state statute to bar sole reliance on an automated decision system and require human corroboration for firing and discipline. Illinois has required notice since January 2026; New York City has required bias audits for automated hiring tools since 2021; Colorado's AI Act does not reach employment discipline; the EU AI Act reaches this ground ex ante rather than through a corroboration duty. The press release saying "first such law in the nation" is a stakeholder claim; the version that survives scrutiny is "first state statute of its kind." Note also that KQED, reporting from California, chose the softer "some of the strongest in the country." That editorial restraint is informative.

Third, the most consequential line in the bill is not about robo bosses. It is § 1522(a)(2): an employer "shall not use an ADS to infer an employee's protected status under Section 12940." That is a capability prohibition aimed at feature engineering, not at decision review. It is the provision most likely to generate surprise, because almost nobody outside the bargaining room described it as the point of the bill. A statute announced as being about robot firing contains its sharpest rule about what data you may model at all.

And the quiet cost. Proposition 22 contractors were removed from the bill after Uber and Lyft objected (CNBC). So the workers KQED quotes as most exposed to algorithmic management — rideshare drivers whose work, pay and deactivation are algorithmically determined — receive none of this protection. The statute reaches employees, public-sector staff and labour contractors, and stops at the platform boundary. Whether the line falls there for a principled reason or a lobbying reason is the question worth carrying into every other state's copy of this law.

Research sources

Primary Sources (4)
Primary
California Privacy Protection Agency — Laws & Regulations - **URL:** https://cppa.ca.gov/regulations/ - **Organisation:** California Privacy Protection Agency (CalPrivacy)** That the CPPA has **already adopted** the "CCPA Updates, Insurance, Cybersecurity Audits, Risk Assessments, and Automated Decisionmaking Technology (ADMT) Regulations (September 2025)" — confirming that § 1526.4 of SB 947 (preserving CPPA ADMT duties for CCPA businesses) is a live obligation, not a future one. Also confirms CPPA rulemaking status as of retrieval. — ** **CONFIRMED** — primary regulator record, used for the § 1526.4 interaction. ---
URL unavailable
Primary
"Newsom Signs McNerney's No Robo Bosses Act of 2026 Requiring Human Oversight of AI in the Workplace" - **URL:** https://sd05.senate.ca.gov/news/newsom-signs-mcnerneys-no-robo-bosses-act-2026-requiring-human-oversight-ai-workplace - **Organisation:** Office of California State Senator Jerry McNerney, 5th Senate District (sponsor's own office)** Sponsor-side account of the signing; the bill's popular name ("No Robo Bosses Act of 2026"); that the bill is sponsored by the California Federation of Labor Unions, AFL-CIO with Lorena Gonzalez as lead sponsor; McNerney's direct quotes ("No worker should ever be fired or disciplined by a robo boss"); the sponsor's own "first such law in the nation" assertion; enforcement routed through the Labor Commissioner, Attorney General or local prosecutors; and the sponsor's cited estimates (550+ "bossware" products; AI assistants misrepresenting news content 45% of the time). — ** **STAKEHOLDER ACCOUNT / COMPANY CLAIM.** The "first in the nation" line and the product/misinformation statistics originate here and are not independently verified in this research. Quotes are accurate to the sponsor; the factual claims about statutory content are independently confirmed against source 1.Date: 2026-09-30
URL unavailable
Primary
California SB 947 — Official bill votes record - **URL:** https://leginfo.legislature.ca.gov/faces/billVotesClient.xhtml?bill_id=202520260SB947 - **Organisation:** California Legislature (official legislative information system)** Final floor votes — **Senate 29 ayes, 10 noes, 1 not voting** (McNerney concurrence motion, 2026-08-31) and **Assembly 53 ayes, 14 noes, 12 not voting** (third reading by Bryan, 2026-08-30). Independently corrects California Gazette's "Senate 28-10". Also confirms the version lineage (introduced 2026-02-02 → enrolled 2026-09-04 → chaptered 2026-09-30) and a near party-line vote pattern on both floors. — ** **CONFIRMED** — primary legislative record.
URL unavailable
Primary
California SB 947 — Chaptered bill text (Chapter 859), Labor Code Part 5.5.5 §§ 1520–1526.7 - **URL:** https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260SB947 - **Organisation:** California Legislative Counsel / California Legislature (official legislative information system)The authoritative operative text. Confirms: bill number, session (2025–2026), author (McNerney), Chapter 859, signature date 2026-09-30, operative date 2027-07-01 (§ 1526.7); the two-tier standard — flat sole-reliance bar (§ 1522(b)(1)) versus human corroboration at primary reliance (§ 1522(b)(2)); the § 1522(c) stop rule; the employee data-description right (§ 1522(d)) and anonymisation constraint (§ 1522(e)); the four mandatory elements of the § 1524 post-use notice; the three flat prohibitions in § 1522(a); the breadth of "employer" (§ 1520(d), including public entities, labour contractors, farm and foreign labour contractors); the ADS definition and its exclusions (§ 1520(c)); enforcement, burden shift and $500 per-violation penalty (§§ 1526, 1526.1); CBA waiver (§ 1526.5); federal-necessity carve-out (§ 1526.6); interstate notice preemption (§ 1526.3); CPPA carve-back (§ 1526.4); local non-preemption (§ 1526.2); statewide-concern and severability clauses. — CONFIRMED — controlling source. Used to overturn several press claims . — The chaptered text carries no short title — it reads only "An act to add Part 5.5.5 (commencing with Section 1520) to Division 2 of the Labor Code." "No Robo Bosses Act of 2026" is a sponsor/press nickname.
URL unavailable
Independent Sources (4)
Independent
"California Governor Vetoes 'No Robo Bosses Act' – What Employers Need to Know About Latest AI Workplace News" — Benjamin M. Ebbink, Usama Kahf - **URL:** https://www.fisherphillips.com/en/insights/insights/california-governor-vetoes-no-robo-bosses-act - **Organisation:** Fisher & Phillips LLP** Independent verification of the predecessor **SB 7 (2025) — "No Robo Bosses Act" — vetoed by Newsom on 13 October 2025**; the veto letter's grounds ("unfocused notification requirements" on businesses "using even the most innocuous tools"; duplication with the newly finalised CPPA ADMT regulations; cost to small employers); that SB 7 would have reached discipline, termination **and scheduling**; that the California Civil Rights Department's ADS regulations took effect 1 October; that Massachusetts and other states were already considering similar measures; and that after the veto employers should not treat the CPPA ADMT rules as absent. — ** **INDEPENDENTLY VERIFIED** — establishes the veto-history baseline that makes SB 947 a narrowed successor rather than a first-of-kind statute in California. ---
URL unavailable
Independent
"California Gov. Newsom bans AI 'robo bosses' in landmark state law, reversing his earlier veto" — Paxton Honerkamp - **URL:** https://www.cnbc.com/2026/09/30/california-gavin-newsom-ai-ban.html - **Organisation:** CNBC (Versant Media)** Independent business-press reporting confirming the signing and the core duties; the distinction between the sole-reliance prohibition and the "primarily" corroboration duty; that SB 947 requires "a description of the employee data used by the system, and a human point of contact"; the **comparative legal status** evidence underpinning the "first" assessment — **Illinois Public Act 103-0804** (in effect January 2026) requires notice for specified AI employment uses but "stops short of an outright prohibition"; federal legislation carrying the same name introduced June 2026 by **Sen. Ed Markey and Sen. Brian Schatz** was "effectively dead on arrival"; **New York, Louisiana and New Jersey** had similar bills proposed but not enacted; **Robert Singleton of the Chamber of Progress** urging veto on the grounds that **"primarily relies" is never defined** and employers have "no objective standard"; McNerney's pre-veto SB 7 language ("unfocused notification requirements on any business using even the most innocuous tools") and the removal of pre-notification and gig-worker coverage; McNerney's CNBC interview quotes; polling context (July Gallup: 39% say AI does more harm than good, up from 31%; August Pew: 71% think AI will take jobs); the July 2026 Meta lawsuit alleging AI-assisted ranking for layoffs; and an Electronic Frontier Foundation statement. — ** **INDEPENDENTLY VERIFIED** — the strongest independent support for the "first US state statute of its kind" assessment and for the "primarily relies" ambiguity risk.Date: Published 2026-09-30 19:29 ET; updated 2026-10-01 09:21 ET
URL unavailable
Independent
"California Passes No Robo Bosses Act" — Eric J. Felsberg, Scott P. Jang (Jackson Lewis P.C.), via National Law Review - **URL:** https://natlawreview.com/article/california-passes-no-robo-bosses-act - **Organisation:** Jackson Lewis P.C. California Workplace Law Blog, published by National Law Review** Independent **statutory analysis** confirming: the effective date of 1 July 2027; the ADS definition and its exclusions; that an employer "may not solely rely on an ADS" and that when it "primarily relies on ADS output" a human must "review and corroborate the decision using the information that produced the output or other relevant material"; that if the output cannot be corroborated or is found inaccurate/incomplete/misleading it may not be used; the separate stand-alone written notice with human contact and data-description right and anti-retaliation statement; the § 1522(a) prohibitions on inferring FEHA protected status and on evading labour/employment/safety/civil-rights law; Labor Commissioner and public-prosecutor enforcement; the conditional collective bargaining waiver; and practical pre-July-2027 employer guidance. — ** **INDEPENDENTLY VERIFIED** — practice-side legal reading of the statute; agrees with the chaptered text. Its phrasing "using the information that produced the output **or** other relevant material" is the basis for noting the circularity in § 1522(b)(2).
URL unavailable
Independent
"Newsom Signs Slate of AI Workplace Laws, Barring 'Robo Bosses' and Surveillance" — Rachael Myrow - **URL:** https://www.kqed.org/news/12102337/newsom-signs-slate-of-ai-workplace-laws-barring-robo-bosses-and-surveillance - **Organisation:** KQED (public media, San Francisco Bay Area)** Independent reporting that the laws were **signed Wednesday 30 September 2026**; that the signing fell on the Governor's last day to act before leaving office in January; that **a previous version of the "robo bosses" legislation was vetoed the prior year**; the companion slate signed the same day (**SB 951** mass-layoff notice when AI causes layoff/relocation/termination with a 60-day notice trigger at 25% displacement per the Transparency Coalition; **AB 1331** bathroom surveillance; **AB 1883** emotion-inference and neural-data surveillance; **AB 1979** nursing clinical judgment), signed-earlier laws (SB 1050, SB 928, AB 2148, AB 1609) and same-day vetoes (**AB 2656**, **AB 2575**); Newsom's quoted statement ("AI should expand opportunity — not come at the expense of workers and families"); Lorena Gonzalez's quoted statement; McNerney's quoted statement; that **rideshare drivers under Proposition 22 are excluded** (quoting Nicole Moore, Rideshare Drivers United). Notably describes the package as "some of the strongest in the country" rather than asserting national firsts. — ** **INDEPENDENTLY VERIFIED** — corroborates signature date, veto history, companion legislation, gig-worker exclusion; editorial language on the "first" question is used as a counterpoint to the sponsor's superlative.Date: Published and updated 2026-10-01
URL unavailable
Secondary Sources (1)
Secondary
"California's No Robo Bosses Act Reaches Governor Newsom's Desk After Bipartisan Legislative Approval" — California Gazette Staff - **URL:** https://cagazette.com/californias-no-robo-bosses-act-reaches-governor-newsoms-desk-after-bipartisan-legislative-approval/ - **Organisation:** California Gazette- **What it supports (used with heavy caveats):** Pre-signature legislative history — that McNerney introduced SB 947 on 2026-02-02, that it cleared both chambers with a 2026-09-30 signing deadline, and that SB 947 is a revised version of vetoed SB 7. Also a comparative framing of the "first in the nation" claim, citing **NYC Local Law 144** (bias audits for automated hiring tools, not extending to termination or discipline), the **Colorado AI Transparency Act** (insurance and consumer contexts) and the **EU AI Act** (high-risk classification, timelines through 2027). Also reports the Chamber of Commerce and CTIA cost warnings and employer-group opposition to SB 947. — ** **SECONDARY — partially contradicted by primary text. Several claims in this article do not appear in the chaptered statute and are flagged, not adopted:** (a) "Senate 28-10" is wrong — the official record is 29 ayes / 10 noes / 1 NVR; (b) a **12-month cadence** for the data-description right does not exist in § 1522(d); (c) the requirement that the human reviewer have "authority, competence, and practical ability to override" does not appear in § 1522(b)(2); (d) the claim that the bill "restricts automated systems in compensation decisions" does not appear in § 1522; (e) the claim that the bill bans systems predicting "future behavior" misreads § 1522(a)(3), which prohibits predicting and taking adverse action **for exercising legal rights**; (f) the claim that the § 1524 notice must "describe the data inputs the system relied on" is not one of the four prescribed elements in § 1524(b). Used in this research **only** for legislative-timeline facts and comparative framing, both of which are independently corroborated by primary sources 1, 2 and 7. ---Date: 2026-09-09
URL unavailable