ACI-032: The Highlander Rule

Thesis

When agents write the code, a second implementation of one concern arrives before anyone notices, and the guards attach to only one copy. Keep the rule, there can be only one, and enforce it with a lookup that reports its own freshness and a check that goes red on a second copy at every landing, keeping the audit for recovery. A module registry is worth keeping only when it is generated and guarded, or deleted and documented, never when hand-maintained and trusted.