Tracking Engine

Track work items / ledger alignment with tracking_enforce.

What you will learn

• tracking_scan
• tracking_enforce
• Keep ledger honest

Prerequisites

• Mount PluginHost and merge MCP tools

Surface

What this feature does

Tracking Engine aligns agent work status with tracked records — prevents “implementing” forever or false user_approved.

How to call it

Call these MCP tools through your AGS / tower-gov host — tracking_scan, tracking_get, tracking_validate, tracking_diff, tracking_enforce.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

1. tracking_scan
2. Update ledger
3. tracking_validate
4. tracking_enforce

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

What success looks like

Ledger status matches commits

tracking_enforce ok

Common failure modes

Status done/complete language

user_approved without user

Orphan tracking ids

Related reference

• Architecture