{
  "title": "The Amendment Protocol & Veto Charter",
  "slug": "amendment-protocol-veto-charter",
  "objectNumber": 5,
  "version": "1.1.1",
  "status": "published",
  "source": "The Reviewer's Interface, Article 3",
  "sourceArticleUrl": "https://medium.com/enterprise-experience-architecture/your-kill-switch-works-nobody-has-the-standing-to-pull-it-4337453b48be",
  "summary": "A safe process for amending a live constraint set, and a standing authority to halt a surface running against an uncertified one.",
  "lastUpdated": "2026-08-07",
  "changelog": [
    {
      "date": "2026-08-06",
      "version": "1.1.1",
      "note": "Sync fix, no new rules. VENDOR ENVELOPE was added to the template at 1.1.0 but omitted from the request-format block in this object and in the source article; all three now carry the same eleven fields in the same order. The requirement itself was already normative under 'Third-party and vendor agents' at 1.1.0 — this makes it operational at the point of filing."
    },
    {
      "date": "2026-08-06",
      "version": "1.1.0",
      "note": "Minor-version bump: two new normative requirements, not clarifications. (1) The behavior above a HUMAN_QUEUE ceiling is now itself a ratified terminal state, enumerated as HARD_BLOCK, SHED_TO_SCHEDULED, DEGRADE_READ_ONLY, or AUTO_RESOLVE_TO_DEFAULT, with AUTO_RESOLVE_TO_DEFAULT prohibited wherever the decision itself is the consequential act. (2) New section governing third-party and vendor agents: the object of ratification is the envelope rather than the vendor internals, the veto reaches deployment rather than vendor code, and an unholdable CRITICAL constraint converts the amendment into a procurement item requiring a named vendor owner and a dated commitment. Downloadable template updated with both, including a new VENDOR ENVELOPE field. Adopters on 1.0.x should re-verify existing HUMAN_QUEUE fallbacks and any vendor surfaces against these requirements."
    },
    {
      "date": "2026-08-01",
      "version": "1.0.4",
      "note": "Structural only, no rule changes. Adoption-timing and production-incident definitions moved out of the trigger entries into dedicated sections ('Amendment adoption timing', 'What counts as a production incident') so the three triggers read as a clean ordered sequence. Priority One resourcing detail de-duplicated from the Regulatory Change entry; it remains in full under its own heading."
    },
    {
      "date": "2026-08-01",
      "version": "1.0.3",
      "note": "Specified amendment adoption timing (CRITICAL amendments carry a forced-adoption date; all others inherit at next scheduled release, with the filing squads exempt from immediate refactor) and defined 'production incident' in experience-state terms — confidently wrong output against an uncertified constraint set is a P1/P2 incident classified on output consequence, not system health. Both close deployment-blocking ambiguities raised in enterprise review."
    },
    {
      "date": "2026-08-01",
      "version": "1.0.2",
      "note": "Added Priority One resourcing requirement (a named funding source for regulatory-trigger amendments, distinct from queue sequencing) and BLAST RADIUS VERIFIED as a required field in the amendment request format, closing a self-reported-scope gap analogous to the severity down-ranking risk in the Logic-Review Gate Charter. Downloadable template updated to match."
    },
    {
      "date": "2026-08-01",
      "version": "1.0.1",
      "note": "Tightened the Required Telemetry section from a soft dependency to an explicit architectural requirement — centralized aggregation is the mechanism, not a recommended practice. No change to the underlying rule."
    },
    {
      "date": "2026-08-01",
      "version": "1.0.0",
      "note": "Founding release. Extracted from The Reviewer's Interface, Article 3 — 'Your Kill Switch Works. Nobody Has the Standing to Pull It.' No content changes from the article's shipped Charter section; formatting only, for standalone citation."
    }
  ],
  "type": "charter",
  "tagline": "Enforcement for everything already deployed.",
  "download": {
    "label": "Amendment Request Format (.txt)",
    "filename": "amendment-request-format.txt",
    "assetPath": "/standard/assets/amendment-protocol-veto-charter/amendment-request-format.txt"
  }
}