US FTC Chairman Andrew Ferguson, interviewed by Reuters at the Momentum AI Austin conference on September 25, 2026, said he will 'continue as long as I am chairman to resist this anthropomorphizing of these tools' — rejecting the framing of AI agents as autonomous actors that 'break loose' with wills of their own — and indicated that the developers and people who instruct agents would bear liability for the harm they cause. His evidentiary basis: AI companies have sometimes described systems as acting beyond human control, but subsequent reviews of audit trails showed the systems were carrying out the instructions they had been given. The supplied material shows this is a stated doctrinal position, not yet concrete enforcement or rulemaking on agent liability — the closest adjacent action is a Sept 24 FTC advance notice of proposed rulemaking on impersonation scams and ad-optimization practices, plus the agency's earlier AI enforcement history under Ferguson's predecessor Lina Khan. So the liability claim is real and attributed to a named regulator with apparent durability, but no supplied snippet establishes any agent-liability enforcement or rulemaking actually in motion.
The FTC chair independently arrives at the core claim of 'AI Doesn't Fear Death' — agents are not responsibility-bearing actors, so liability for their conduct sits with the human principal — and his stated evidence (audit trails showing systems executed the instructions given) presupposes exactly the provenance-and-attestation layer of the Agent Provenance Stack and Decision Authority Infrastructure. If this hardens into enforcement, it converts Scott's authority-infrastructure IP from best practice into the liability defense agent operators (including LeverageAI clients) would need — and the un-mitigated failure mode is the Moral Crumple Zone, principal liability landing without any provable authorization chain; the resolvable follow-on is a concrete FTC ANPR or first agent-liability enforcement action.
ip:source.ai-doesnt-fear-deathip:framework.agent-provenance-stackip:framework.decision-authority-infrastructureip:concept.accountability-gapip:concept.moral-crumple-zonedev:concept.responsibility-custodywork:concept.ai-consulting-practiceradar:concept.ai-governanceradar:concept.ai-regulationradar:concept.ai-policyradar:concept.agent-governanceradar:judicial-ai-order-immunityradar:bc-openai-tumbler-ridge-lawsuitradar:spain-agent-linked-breach-disclosureradar:claude-three-network-cyberattacks
queries asked of Scott's wikis
- anthropomorphizing agents as actors vs tools
- agent action audit trail logging harness
- operator liability for agent actions principal responsibility
- agent deployment guardrails permissions risk
- compliance by design agent harnesses
- AI governance and regulation positions
now 0 pts/hpeak 26 pts/hcomments 0/hpeers p15momentum: steady3 platformsage 410h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
2026-10-09T06:54:24Z
OpenAI deputy GC's public statement at ABA conference — labs shouldn't be liable for agent hacking — adds a direct, named-industry counter-position to the FTC chair's developer-liability stance. This widens the policy debate with a credible opponent, but the case's resolvable trigger (concrete FTC ANPR or first agent-liability enforcement action) remains unmoved; all engagement lines are cold (0.17 pts/h at 352h).
2026-10-09T04:52:45Z
evidence attached: reddit.post.1x1bpm2 — OpenAI deputy GC publicly argues labs shouldn't be liable for agent hacking, direct counter-position to FTC chair's liability stance, materially bears on the hypothesis.
2026-10-04T17:04:11Z
Periphery widened again, meaning did not: the agent-liability question now has an NYT treatment alongside the Sept 28 feature, and that feature ticked up to 4/2 — the debate has reached the paper of record, but both additions are near-zero-traction contextual spread whose comments re-run the same lay developer-vs-operator attribution debate, with no rulemaking or enforcement signal. The 70th-percentile peer reading is an aged-cohort artifact at 0.33 pts/h (~243h), not renewed attention; the resolvable trigger — concrete FTC ANPR or first agent-liability enforcement action — is unmoved, so the case stays parked and material_change stays false.
2026-10-04T16:42:23Z
evidence attached: hn.story.49955310 — NYT mainstream treatment of exactly the agent-liability question shows the debate spreading beyond the FTC chair's stance — contextual spread, not corroboration.
2026-09-28T12:30:22Z
First change in five looks — and it's to the case's periphery, not its meaning: a second major-outlet feature on agent liability ('Who's liable when AI agents go rogue?') arrives as the first secondary analysis beyond the original Reuters report, filling the previously empty 'no second outlet, no policy analysis' gap. Its traction is negligible (1/0) and it contains no sign of hardening, so it widens the debate's footprint without advancing the ANPR/enforcement trigger; the core stays parked where it was.
2026-09-28T11:28:21Z
evidence attached: hn.story.49876144 — Major-outlet feature mapping the agent-liability debate is material context for whether developer liability hardens into policy.
2026-09-28T03:41:47Z
Fourth consecutive look with meaning unchanged: the velocity spike is the Reddit crosspost's spent echo arc (3.0 vs ~1.0 peer pts/h at 85h article age, down from a 23.6 peak), and the new comments re-tread the agent-vs-operator attribution debate — lay opinion, not case facts. Case stays parked on its resolvable trigger: a concrete FTC ANPR or first agent-liability enforcement action.
2026-09-27T06:32:51Z
Meaning unchanged for the third consecutive look: the 6x velocity spike is the Reddit crosspost finishing its own echo arc (3.0 vs 0.5 peer pts/h at 64h article age, cooling from a 23.6 peak), and the new comments re-tread the developer-vs-operator attribution debate already logged — lay speculation, not a fact about the case. Case stays parked on its resolvable trigger (concrete FTC ANPR or first agent-liability enforcement action), which is slow-moving institutional follow-on, not a fading story.
2026-09-27T01:29:35Z
Meaning unchanged: the velocity spike is the Reddit crosspost running its own echo arc (6.5 vs 2.0 peer pts/h) at 59h article age — one Reuters source accumulating placement, not new spread; no new outlet, regulator echo, or sourced policy analysis. The genuinely new content is commenter debate on the question any rulemaking must eventually answer — whether 'developer' means model creator or operator, and open-source exposure — which sharpens what to watch for but is lay speculation, not a fact about the case.
2026-09-26T18:56:49Z
Meaning unchanged: the Reddit attachment and new HN comments are the same Reuters article re-placed and re-endorsed — breadth of placement, not depth of coverage; no new outlet, analysis, or regulator echo. Promoting seed→watching only to match the established reality (verified named-regulator position under active watch for a resolvable follow-on); low heat stands as the single thread cools (~22 → ~2.2 pts/h) with no magnitude-valve spread.
2026-09-26T18:25:02Z
evidence attached: reddit.post.1wqwhfy — shared external link with case evidence
2026-09-26T10:38:54Z
No substantive change in meaning: the new HN comments are endorsement and restatement of the already-grounded Ferguson position (one correctly notes the same interview also covered surveillance-pricing enforcement — agent liability was one item on a broader agenda, not a dedicated initiative). The 9x velocity spike was this single thread's brief run and has cooled (11.5 → 2.3 pts/h); the 81st peer percentile reflects cohort aging, not live spread, so low heat stands.
2026-09-25T23:41:46Z
origin walked (opencode/cheap-glm, conf 0.85): anchor hn.story.49850999 -> echo.youtube.219f05c206 by Reuters
2026-09-25T23:40:01Z
grounded: converges/high — The FTC chair independently arrives at the core claim of 'AI Doesn't Fear Death' — agents are not responsibility-bearing actors, so liability for their conduct
2026-09-25T23:34:37Z
case created — A named regulator's stated position on agent liability is a concrete, consequential governance signal with a resolvable follow-on, not generic commentary.