Sustainable operating model

Problem

The MCP server and agent evaluation framework are maintained through ad-hoc heroics rather than a defined operating model. There is no documented on-call rotation for MCP tool failures, no release cadence for tool schema or prompt updates, no triage process for incoming eval regressions, and no runbook for common operational tasks (deploying a new tool, deprecating an old one, rotating cached profiles). As the system grows beyond a single maintainer, this lack of operational structure will lead to dropped incidents, inconsistent releases, and contributor confusion about ownership.

Context

Possible Solutions

Plan

Implementation Progress

Review Feedback

• Review cleared