Persistence Engine

Scan and enforce persistence contracts so durable state stays on canonical paths.

What you will learn

• persistence_scan
• persistence_enforce
• Diff illegal stores

Prerequisites

• Mount PluginHost and merge MCP tools

Surface

What this feature does

Persistence Engine detects ad-hoc durable writes (rogue localStorage, duplicate stores) against registered persistence graphs.

How to call it

Call these MCP tools through your AGS / tower-gov host — persistence_scan, persistence_get, persistence_validate, persistence_diff, persistence_enforce.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

1. persistence_scan
2. persistence_diff
3. Move writes to canonical module
4. persistence_enforce

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

What success looks like

No illegal persistence paths

persistence_enforce ok

Common failure modes

New store bypassing canonical module

Scan clean but enforce skipped

Diff ignored after relocate

Related reference

• Architecture
• API surface