Skip to content

docs(tools): tool removal/consolidation runbook — ratified, audited, never autonomous #3853

Description

@williamzujkowski

Part of #3850. Depends on #3852, #3840 (ladder ADR).

Context

The runbook: candidate signal → dedicated issue → human ratification via Epic D's consensus path → deprecation window (tool warns) → removal PR through the governor path (Epic B) → tier-transition/removal audit event. Consolidations additionally map old→new tool guidance for harness users.

Acceptance criteria

  • Runbook doc indexed; references the Epic D ratification gate + Epic B review path
  • The 46/47-count claims-registry entry updated as part of any removal (claims:check keeps it honest)
  • Explicit statement: no code path may remove a tool registration autonomously

Evidence required

Docs gates.

Out of scope

Performing any removal.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationp3Priority 3 - Lower impact, significant changes neededroadmap:control-planeControl Plane roadmap (M1-M4)tool-fitnessTool fitness ledger + pruning (Epic F)

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions