Schema Engine

Scan, get, validate, diff, and enforce the Schema graph before adding MCP tools or DiffRules.

What you will learn

schema_get family
schema_enforce pass
Register new schemas correctly

Prerequisites

Surface

Imports	@tmrxjd/agent-governance-system
MCP	schema_scan · schema_get · schema_validate · schema_diff · schema_enforce

What this feature does

Schema Engine owns Zod/JSON shapes for staging categories, enforcement sessions, confidence reports, version policy, deployment policy, arrays, canonical registry, and more. Call schema_get before inventing fields; schema_enforce before commit when schemas change.

How to call it

Call these MCP tools through your AGS / tower-gov host — schema_scan, schema_get, schema_validate, schema_diff, schema_enforce.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

schema_scan / schema_get
Edit registered schema module
schema_validate
schema_enforce

MCP: schema_enforce json

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

Get a family

Fetch a schema id before extending it.

MCP: schema_get json

{ "id": "schema:staging-category" }

What success looks like

schema_enforce ok

schema_diff clean or explained

Common failure modes

New MCP tool without schema node

Hand-edited graph artifact drift

Skipping schema_get then failing confidence checklist