Builder Engine

Scan builder graphs and create/enforce build plans with builder_* tools.

What you will learn

• builder_scan
• builder_create
• builder_enforce

Prerequisites

• Mount PluginHost and merge MCP tools

Surface

What this feature does

Builder Engine manages generative/build plans tied to governance graphs — use builder_create for new nodes, builder_enforce before accepting generated output.

How to call it

Call these MCP tools through your AGS / tower-gov host — builder_scan, builder_get, builder_validate, builder_diff, builder_enforce, builder_create.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

1. builder_scan
2. builder_create
3. builder_validate
4. builder_enforce

{ "kind": "module", "name": "auth-refresh" }

What success looks like

builder_enforce ok

Diff explained

Common failure modes

Create without enforce

Orphan builder nodes

Diff drift ignored

Related reference

• Architecture
• API surface