Skip to main content

​
Summary

A systematic audit of Grace’s 8 OpenClaw agent files against the live STRATT codebase revealed 49 issues — accumulated in roughly 3 days of active development. 11 were CRITICAL phantom concepts (referencing entities that no longer exist in the codebase).

​
What caused the drift

Three STRATT refactors happened in quick succession without corresponding agent file updates:
  1. URI scheme rename (strat:// → stratt://) — touched every file referencing the URI format. 6 agent files still used the old scheme.
  2. Council expansion (3 → 7 councils, 16 → 35 agents) — 4 new councils (Bastion, Compass, Herald, Terra) added to councils/ but invisible to Grace.
  3. Unit type rename (fragment → supply) — a single git commit renamed the type, but 5 agent files still referenced “fragment”.

​
Business impact

  • Grace was routing to 3 councils when 7 existed — 57% of governance was invisible
  • Every strat:// reference in Grace output was a phantom concept — immediately undermining credibility
  • The 22-org ecosystem (vs 7 tracked) meant Grace was blind to 15 orgs, 23 GH Projects, and ~300 repos

​
Operational takeaway

Agent context files need a post-refactor alignment check built into the development workflow. Not a monthly review — a check triggered by schema-level changes (URI renames, type changes, entity additions). Added to HEARTBEAT.md as a weekly audit item.