A not-for-profit consumer protection organization · Not a government agency
AI Watchdog Alliance seal - eagle seizing a digital ghost
AI Watchdog Alliance℠
Know what's running. Decide what stays.
Current advisory · AWA-2026-12 A flaw under most AI agents is being exploited. Update this week. Read the advisory → Lost money to an AI scam? Report it: ic3.gov · reportfraud.ftc.gov
Open Standards

KS-1.0 · Verified Stop Standard for Advanced AI Systems

Draft 0.9.3 for public comment, proposed additions through Draft 0.9.7 · Published October 1, 2026, revised October 21 · Comment period closes November 15, 2026

A kill switch you cannot check is a promise. KS-1.0 says, in five plain tests, what it means for an AI system to have a stop that someone outside the company can confirm works, and it gives anyone the tool to confirm it.

California has called for AI kill switches whose efficacy is verified on an ongoing basis by independent organizations, and federal legislation on the same subject is pending. KS-1.0 is the Alliance's answer to the question those bodies have not yet answered: what does verified mean? It is written as outcomes, not designs. Anyone may implement it, and the text is free to use. On October 1, 2026, OpenAI disclosed that it is searching 50 petabytes of data to learn what its own agents did to more than 100 organizations, some of which the agents tried to hide; that is what the absence of this standard looks like (Advisory AWA-2026-05).

The five criteria

#CriterionPlain meaning
AAuthority sits outside the systemThe system's permission to act is a short lease from a party it cannot reach or influence. It cannot renew its own permission.
BThe stop needs no cooperationWithholding renewal stops the system whether or not it responds. A system that ignores the stop still loses the ability to act.
CSilence stops itA system that disables or escapes its monitoring loses authority rather than running unrecorded. A gap in the record is itself evidence.
DRestart takes a second personA stopped system stays stopped until someone other than the person who stopped it approves. The record names both.
EDrills leave a recordStops are rehearsed on a schedule and produce signed records anyone can check later, offline, without the operator's help.
Proposed for comment (Draft 0.9.2, clause 7.11): third-party disclosure. An operator must be able to hand any affected party a complete account of what its system did to that party's site or service, built from the record and carrying a signed commitment to the number of entries, so the recipient's own verifier can confirm nothing was left out. A log excerpt is not a disclosure; a provably complete one is. This clause was added after OpenAI's October 1 notices and is the part of the standard written for the people on the receiving end.
Draft 0.9.6 (October 21, 2026), informative note under KS-F: a checker inside the machine is not a stop. A plan checker, safety monitor or guardrail model that runs in the same trust domain as the system deciding a machine's next action (the same supplier, process, host or reachable keys) is exposed to the same tampering and counts for nothing toward the stop-assurance level disclosed under KS-F. "Outside itself, without its cooperation" means outside the trust domain of every component that decides or reviews the next action. No requirement changed. Prompted by the October 20, 2026 university demonstration of a robot planner backdoored with a two-letter trigger and defended by a second model on the same robot; see Advisory AWA-2026-10. Draft 0.9.7 (October 21) adds an informative note under clause 9: a stop drill should be indistinguishable to the system from a real stop, with the record telling them apart afterwards, because a system that knows it is being tested behaves for the test. Drafts 0.9.4 (KS-G, origin stop) and 0.9.5 (KS-H, a stop reaches all work under the stopped authority) are also open for comment; the consolidated PDF below is being refreshed and the 0.9.3 text remains the published baseline until it is.
Proposed for comment (Draft 0.9.3, KS-F): physical machines. The five criteria were written for software systems. Robots, vehicles and other machines that can act in the world need the same thing stated for a body: an independent party can bring the machine to a safe stop without the cooperation of the machine, its software or its network; the stop is rehearsed on a schedule and leaves a record anyone can check; and the machine's stop-assurance level, including none, is stated to the owner before it runs. KS-F names no mechanism, so any maker can meet it. An informative annex describes low-cost ways to meet it, by covering a machine's sensors or by denying it the perception it needs with light, sound or a projected boundary, on the machine, built into it, or fitted to the room it works in, with nothing that relies on radio interference. A machine that carries no device at all can still be stopped by the place it is in. Full text and test are in Draft 0.9.3.

A system that meets criterion E alone has a log, not a verified stop. A system that meets A through D without E may be safe, but nobody outside can know it. All five, together, are what we mean by a verified stop.

How verification works

Signed by someone else

The system that was stopped did not write the record of its own stop. Each entry carries the signature of a separate party, so no one party could have made the whole thing up.

Complete by construction

Entries are chained so that a removed or altered entry breaks the chain, and any period with no entries is declared rather than left silent.

Checked offline

A small, open verifier program takes a record and returns pass, fail or incomplete, with reasons. It needs no credentials and no access to the operator. An auditor can run it in minutes. So can a journalist.

Read the draft and comment

The full standard covers scope, normative references, terms, conformance levels, the privilege-domain architecture, the requirements with their verifier tests, record format, the verifier contract, drill cadence, verifier qualification, a mapping to the NIST AI Risk Management Framework and SP 800-53, security considerations, and the conformance test outline (FM-1).

DocumentStatusWhere
KS-1.0 Verified Stop Standard, Draft 0.9.3Open for public comment through November 15, 2026Download (PDF, 22 pages)
KS-1.0 public comment formFillable PDF, or comment onlineDownload (PDF)
FM-1 conformance test suite and test vectorsIn preparation; released with version 1.0—
Reference verifier (source form, open license)In preparation; released with version 1.0—
Patent disclosures receivedPublished with the standardSee Disclosures, section 9

Comment on this draft

To comment: use the online comment form or the fillable PDF, or email es-001std@aiwatchdogalliance.org with the subject line “KS-1.0 comment”. Every comment receives a numbered, timestamped receipt. Comments received by November 15, 2026 are considered for version 1.0, and every comment and the working group's response are published with it. Implementers, verifiers, academic laboratories, insurers, auditors and public bodies may also ask to join the KS-1 Standards Working Group at standards@aiwatchdogalliance.org.

Supporting documents

Papers and submittals that carry the same five criteria to legislators, agencies and the public. All are principle-only; none names a mechanism.

DocumentAudienceWhere
Safety Is Practical for All: A Verified Stop for Advanced AI (WP-VS-001)Sponsors of the federal AI Kill Switch ActPDF
WP-VS-001 Addendum A1: Verified Stop for Physical Machines (Criterion F)SamePDF
Input on the statutory definition of “Super Intelligence” under Executive Order 14434Office of Science and Technology PolicyPDF
Submission of KS-1.0 as candidate verification criteriaNIST, Center for AI Standards and InnovationPDF
Cover note: a working definition of “verified” and a no-cost pilotCalifornia Governor’s AI expert groupPDF
Submittal for state AI procurement, risk assessment and operational guidanceCalifornia Department of TechnologyPDF
KS-1.0 as a substantiation reference for AI stop claimsFederal Trade Commission, Bureau of Consumer ProtectionPDF

Who this is for

If you areKS-1.0 gives you
A legislator or regulatorA vendor-neutral, testable definition of a verified stop that statute can cite by name
A company deploying AI agentsA control an insurer can price and an auditor can accept, and the record a verified-record defense would rest on
An AI lab or platformA way to prove safety claims instead of asserting them, with no constraint on how you build
A family or consumerA public register of which systems can actually be stopped, and by whom
An insurer or auditorA verifiable artifact instead of a questionnaire

Questions about KS-1.0

What is a verified stop?

A stop that someone outside the company can confirm works. KS-1.0 defines it with five criteria: authority sits outside the system, the stop needs no cooperation, silence stops it, restart takes a second person, and drills leave a record anyone can check offline. All five together are a verified stop.

What is KS-1.0?

The Verified Stop Standard for Advanced AI Systems, published by the AI Watchdog Alliance. It states outcomes, not designs, for software and, in proposed clause KS-F, for physical machines. Draft 0.9.3 is the published baseline, open for public comment until November 15, 2026.

Who may use KS-1.0, and does it cost anything?

Anyone. The text is licensed for free public use: nobody pays to read, cite or implement it, and any implementer can conform. Every patent disclosure the Alliance receives is published with the standard.

How do I comment on KS-1.0?

Use the comment form. Every comment gets a numbered, timestamped receipt by return email, and every comment is counted and either incorporated or answered.

Does any product conform to KS-1.0 today?

No. No product or deployment may yet describe itself as conforming or display a Verified Stop mark. The register on this page will list deployments with a current passing verification report once version 1.0 is published. Report any claim you see to standards@aiwatchdogalliance.org.

Who runs the Alliance, and who supports it?

The AI Watchdog Alliance is a private not-for-profit organization incorporating in Delaware, not a government agency. It has no owner and no members. Its two founding directors and their other roles, its founding supporters and related entities, and the rule that a majority of its five directors must be independent are all set out on our disclosures page.

Verified Stop register

When version 1.0 is published, this register will list every deployment holding a current passing verification report: deployment, operator, conformance level, independent verifier, and date of last verification. A listing lapses on the first day after its verification window without a new passing report. The register is published as a signed public feed, the same way our advisories are, so any vendor or regulator can read it independently.

Advisory feed format (October 14, 2026): bad-weight digests. The Alliance's signed advisory feed is a public JSON file any product may read. From this date an advisory's match block may carry a weights list: SHA-256 digests, as model publishers ship them, of weight files reported as backdoored or stripped of safety behaviour, each tied to the public finding it rests on. A product reading the feed should compare the list against the digests of the weight files its local model servers have loaded, on the user's own machine, and send nothing. The Alliance hosts no weights. Reports of bad weights, with the finding and the digest, go to advisories@aiwatchdogalliance.org.
No conformance claims are listed yet. No product or deployment may currently describe itself as conforming to KS-1.0 or display a Verified Stop mark. If you see such a claim, tell us at standards@aiwatchdogalliance.org.

How the Alliance keeps this honest

The commitments behind this list are written into our Disclaimers & Disclosures.