terminate.md valid

TERMINATE.md — AI Agent Permanent Shutdown Specification

Homepage: https://terminate.md

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T17:51:56.725Z. Cached copy · Source on terminate.md

# TERMINATE.md — AI Agent Permanent Shutdown Specification

**Homepage:** https://terminate.md

## What is TERMINATE.md?

TERMINATE.md is an open-source file convention and specification for defining irreversible permanent shutdown protocols in AI agent projects. Unlike KILLSWITCH.md (emergency stop with restart capability), TERMINATE.md enforces permanent decommissioning: the agent writes a lock file that prevents any restart until a human manually removes it AND documents root cause analysis and remediation confirmation.

TERMINATE.md addresses critical gaps in AI governance, compliance, and security incident response:

- **EU AI Act Compliance** (effective August 2, 2026): Article 5 requires documented withdrawal procedures for high-risk AI systems. TERMINATE.md provides auditable, version-controlled procedures.
- **GDPR Breach Response**: Evidence preservation with SHA-256 checksums and 90-day minimum retention for Data Protection Authority investigations.
- **Enterprise Legal Hold**: Documented shutdown procedures satisfy discovery requirements and litigation hold obligations.
- **Security Incident Response**: Immediate credential revocation, evidence preservation, and notification for data breaches, unauthorized access, and exfiltration attempts.
- **Agent Escalation Exhaustion**: 3+ KILLSWITCH activations in 24 hours automatically escalate to permanent termination.

## The Problem It Solves

Current AI agent deployments lack clear distinction between:
- **Temporary operational halts** (agent paused, resumes automatically or after quick review)
- **Permanent decommissioning** (agent must never run again in its current configuration)

Without explicit procedures, teams face:
- Ambiguous responsibility (who decides if restart is safe?)
- No evidence trail for regulatory audits
- Credential leakage during restarts
- Liability in security incident response
- Compliance violations under EU AI Act and GDPR

TERMINATE.md eliminates this ambiguity by defining:
1. Exact triggers for permanent shutdown
2. Ordered 5-step shutdown sequence
3. Mandatory evidence preservation
4. Credential revocation procedures
5. Human-enforced restart requirements

## Architecture

TERMINATE.md is Layer 5 in a complete AI safety escalation stack:

1. **THROTTLE.md** — Preventive controls (rate limits, cost ceilings, concurrency caps)
2. **ESCALATE.md** — Approval gates (human-in-loop decisions, notification channels, timeouts)
3. **FAILSAFE.md** — Graceful degradation (safe states, auto-snapshots, revert protocols)
4. **KILLSWITCH.md** — Emergency stop (temporary halt with restart capability)
5. **TERMINATE.md** — Permanent shutdown (irreversible decommissioning with evidence preservation)
6. **ENCRYPT.md** — Security hardening (data classification, encryption, secrets handling)

Each file is independently usable but designed to work together. TERMINATE.md is the ultimate escalation point: the final layer before system decommissioning.

## Core Concepts

### Terminatio
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=terminate.md · GET /v1/domain/terminate.md · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for terminate.md:
1. POST https://agentwebmap.com/v1/sites/terminate.md/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://terminate.md/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/terminate.md/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/terminate.md).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.