Semantic Engine

Enforce meaning constraints — e.g. done requires user_approved — via semantic_enforce.

What you will learn

• Load semantic graph
• Detect contradictions
• Pass semantic_enforce

Prerequisites

• Mount PluginHost and merge MCP tools
• Agent commit message schema

Surface

What this feature does

Semantic domains encode constraints across CAP, staging, sentinel, versioning, deployment, efficiency, and impact. Contradictions (status done + User-approved: no) hold the path.

How to call it

Call these MCP tools through your AGS / tower-gov host — semantic_scan, semantic_get, semantic_validate, semantic_diff, semantic_enforce.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

1. semantic_get for domains you touch
2. Align commit trailers / ledger status
3. semantic_enforce

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

What success looks like

No contradiction issues

semantic_enforce ok

Common failure modes

Claiming finished without approval

Conflicting domain assertions in one change

Skipping semantic_diff after graph edits

Related reference

• Semantic domains
• Architecture