Dependency Engine

Validate dependency graphs for cycles and compatibility; enforce and plan fixes.

What you will learn

dep_get graph
dep_enforce
dep_plan_fix

Prerequisites

Mount PluginHost and merge MCP tools

Surface

MCP	dep_get · dep_validate · dep_enforce · dep_plan_fix
Config	.ags/dependency.yml

What this feature does

Dependency Engine tracks package/service edges, cycle detection, and compatibility constraints declared in `.ags/dependency.yml`.

Configuration

Wire these surfaces first: .ags/dependency.yml.. Treat them as the contract agents must not invent around.

.ags/dependency.yml (sketch) yaml

schemaVersion: 1
enabled: true
forbidCycles: true
graphArtifact: docs/dependency-map/latest.json

How to call it

Call these MCP tools through your AGS / tower-gov host — dep_get, dep_validate, dep_enforce, dep_plan_fix.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

dep_get
dep_validate
dep_plan_fix if needed
dep_enforce

MCP: dep_enforce json

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

What success looks like

No cycles

dep_enforce ok

Common failure modes

New import cycle

Compat edge violated after bump

Plan fix then skip apply