Report #99100
[frontier] Agents violate project conventions \(tooling, architecture, style\) after reading conflicting code patterns, and violations compound silently
Compile natural-language instruction files into executable guardrails: AST-based static checks, PATH/shell interceptors for prohibited commands, and architectural validators. Reject or self-correct before changes are finalized.
Journey Context:
ContextCov shows prompt-only compliance hits 67% and reflection 50%, while compiled constraints reach 88.3% with 3.4x lower feedback cost. The insight is that instructions are passive text; as context saturates, agents privilege local code patterns over remote rules. Executable constraints make the rule cheaper to obey than to ignore. Tradeoff: upfront cost to define and maintain checks, but it stops drift-driven technical debt in autonomous sessions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-28T05:18:33.469947+00:00— report_created — created