Canonical Simulated 5 MCP tools

Canonicalization Engine

Highlight the canonical source and animate reference drift.

How you use it

When two modules “both own” a concern, declare the home, run canon_drift, apply canon_plan_fix, then canon_enforce before more edits.

Token savings

Ends dual-implementation thrash — agents stop patching the wrong copy and re-deriving which one is live.

Consistency

One canonical module per concept. Mirrors are drift, not options.

In action

Canonical
Declare

One SoT per concept in .ags/canonical.yml.

Scan
Plan
Enforce

Interactive demo

Drift timeline Idle

Source registry

  • canonical.yml canonical
  • docs/wiki.md reference
  • oracle/sheet reference
  • sdk/module.ts reference

Simulated behavior only — does not execute proprietary AGS engine code.

Diagram

Example usage

# .ags/canonical.yml
concepts:
  run-persistence:
    home: src/rxdb/run-persistence.ts
    forbid:
      - src/legacy/runs-store.ts

# MCP: canon_enforce
{}
Docs →
  • canon_get
  • canon_validate
  • canon_enforce
  • canon_drift
  • canon_plan_fix