RUL-012 — Done means wired and deployed, not just built and tested

Ruling

"include wiring and deployment in your definition of done permanently" and "do not claim completion until you can verify every single word in your completion report." (verbatim, session 242, 2026-07-18). A capability that exists but is not wired into the production caller/registry/config and deployed/installed where it runs is NOT done.

Evidence

• Global memory feedback-done-means-wired-and-deployed: multiple deliverables were built but left unwired/undeployed (janus patch built but initially not the default transport; installer existed but didn't install from GitLab; ontology draft sat on disk unreported).
• AGENTS.md Hard Rule 8: "Built is not done — WIRED is done" — the 2026-07-12 spec-gap audit found the entire U:Vfy verification subsystem (63 tested modules), the plugin SDK, and a 769-line NotificationCenter gadget all built-but-unreachable.

Enforcement

• gate scripts/health_check.py check_orphan_modules

Verification

scripts/health_check.py's check_orphan_modules runs the orphan-module ratchet (serialize_codebase_ast.py orphans --check against the committed plans/orphan-modules-baseline.txt): it fails when a NEW src module becomes production-unreachable — nothing outside tests imports it, transitively, from any production entrypoint. Growth of the unwired-debt ledger fails the check; shrinking it is advisory.