An implementation of the Edit Approval State Machine (EASM) (MCP Server)
Until 2026-09-25 this record combined several servers published from one repository. The others now have records of their own: mseep-mcp-edit-math. Checks from before that date include them.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-edit-math","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# 🛡️ Edit Math Supervisor (MCP Server) ### An implementation of the Edit Approval State Machine (EASM) ### A stateful gatekeeper for AI-driven code editing [](#donate)  ## Overview This project implements a **Model Context Protocol (MCP) server** that acts as an architectural gatekeeper between an AI coding agent and the file system. Its purpose is simple: > **An AI is not allowed to edit code unless it has demonstrated awareness of the consequences and obtained explicit human approval.** The server enforces this rule procedurally, not heuristically. --- ## Why this exists Modern AI coding assistants can generate and apply code changes faster than humans can reliably reason about their impact. This creates a dangerous asymmetry: - the AI can *act immediately* - the human can only *review after the fact* In practice, this leads to: - silent breaking changes - accidental dependency violations - refactors without understanding downstream effects This project explores a different model. **The AI must stop. Explain. Ask. And wait.** Only then is it allowed to modify code. --- ### 🧠 Philosophy: Architectural Control over AI Action This project is intentionally not focused on making AI “smarter”. Instead, it explores a different question: > What architectural constraints are required > when an AI system is allowed to act on real code? Most AI coding tools optimize for fluency and speed. This project optimizes for **procedural awareness**. The core assumption is simple: AI systems do not lack intelligence — they lack **structural incentives to pause, explain, and verify**. The Edit Approval State Machine introduces such a structure. It forces the AI to: - stop before acting - externalize its assumptions - acknowledge dependencies - wait for explicit hu…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.