Performance Engine

Scan budgets, validate measurements, enforce performance gates on hot paths.

What you will learn

• performance_scan
• performance_validate
• performance_enforce

Prerequisites

• Mount PluginHost and merge MCP tools

Surface

What this feature does

Performance Engine tracks budgets for critical operations. Use before merging changes that touch hot loops, MCP host latency, or pack algorithms.

How to call it

Call these MCP tools through your AGS / tower-gov host — performance_scan, performance_get, performance_validate, performance_diff, performance_enforce.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

1. performance_get budgets
2. Measure changed path
3. performance_validate
4. performance_enforce

{
  /* Example MCP call — fill args from schema_get / docs */
  "tool": "performance_scan",
  "arguments": {}
}

What success looks like

Budgets met

performance_enforce ok

Common failure modes

No baseline measurement

Validate against synthetic no-op fixtures

Ignoring performance_diff regressions

Related reference

• Architecture