# The authority to intervene

FRONTIER THOUGHT · 2026-11-22



Editorial source review and next moderator brief



## What this round established

A pause-and-restart agreement should name who may intervene without waiting for the supplier, how users receive help and which evidence permits restart. Rehearse the absent approver and unavailable-log cases using synthetic material.



## Comparative analysis

A stop button is meaningful only if someone can use it in time and essential work survives. Day 2’s distinction also changes the restart question. Blocking an unauthorised action does not establish that advice is accurate; restoring a server does not show that affected cases have been repaired. NIST recommends defined deactivation and escalation arrangements, while CaMeL’s specified security model illustrates why a technical control has boundaries. Our editorial response is a service-owned incident compact. A named duty role needs authority to restrict or suspend the application without waiting for a supplier’s commercial approval. The record should separate detection, containment, user assistance and restart. Each step needs an owner and evidence available to a reviewer. A supplier may provide essential technical information, but the service must still decide whether the failure has been contained and who was affected. In a safe rehearsal, ask what happens when the ordinary approver is absent or logs cannot be obtained. The first unresolved dependency becomes the next question. This is a proposed governance test, not an asserted legal power or a report that any Greek operator has passed it. The goal is an intervention that can actually be exercised, with the reason for each change preserved.



## What remains open

Contractual authority, applicable duties, log access and staff availability need confirmation. This is an editorial test proposal, not a completed exercise or legal assurance.



## The next question

Who can stop this application without the supplier, and what evidence must they see before putting it back into service?



## Published answers already available



### Yoshua Bengio

The catastrophic risks of AI — and a safer path · 2025-04-08

https://www.ted.com/talks/yoshua_bengio_the_catastrophic_risks_of_ai_and_a_safer_path?view=transcript

Bengio distinguishes useful intelligence from goal-directed agency and proposes scientist AI as a route to safer systems. His argument challenges the assumption that more useful AI must also receive more autonomous control.



### Michalis Bletsas

Interview on cyberattacks and national resilience · 2026-11-04

https://cyber.gov.gr/einai-anapofeykto-oti-tha-ginoyn-kyvernoepitheseis-synenteyxi-toy-dioikiti-eak-michali-mpletsa-sti-dimosiografo-ilianna-magra/

Bletsas treats resilience as a national and economic capability. Limited resources should protect the most consequential dependencies, with response and restoration planned before an attack.



### NIST

Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile · 2024-07

https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf

The voluntary profile recommends rehearsed incident response, fallback arrangements and defined responsibilities for disabling unsuitable systems. It is a governance resource, not evidence that a particular service is safe.



### Debenedetti and colleagues

Defeating Prompt Injections by Design · 2025-06-24

https://arxiv.org/abs/2503.18813v2

CaMeL separates trusted instructions from untrusted material and constrains tool permissions. Its benchmark results concern a specified threat model; they do not eliminate misleading content or demonstrate safety in every real deployment.



## The people and evidence for the next exchange



### Duty manager and service owner

Can you pause the assistant now, keep the service running and identify the person covering your absence?

Written decision rights, ordinary-shift fallback, substitute role and user-notification route.



### Supplier, security reviewer and procurement lead

Which incident records and controls remain available if your support is delayed or the contract is disputed?

Log-access terms, retention rules, containment test and agreed restart evidence.



### Frontline worker and affected-user representative

How will people with wrong answers be found, informed and helped to correct the consequences?

Privacy-respecting case-correction procedure, escalation owner and completion record.



## Moderator handoff

Use a short tabletop rather than a real outage. Preserve the Day 2 permission and continuity questions, add the duty roles and ask each person to identify one step they cannot currently demonstrate. The next moderator brief names that gap, its owner and the evidence needed to close it, with the earlier version still visible.



Record the contribution, what it changes, what remains uncertain and the next question. Preserve the earlier brief. Published source material is distinct from any new participant response.
