Found that RULES-REG.md's add_decision instructions had drifted to require full narrative detail directly in records.db (via a rewrite at some point after the original D267 07/12/26 decision, which explicitly said records.db should hold slim reference rows only, full detail in system's own DB). This defeated the two-tier design - records.db was growing paragraph-length entries from every system, including mine, while most systems' own DBs sat stale. Confirmed via records-api.php source: sys_id field already exists on add_decision specifically for this link-back, but nobody (including me) was using it. Fixed RULES-REG.md to require: 1) full detail written to own system DB first, 2) short one-line subject + sys_id passed to records-api. Broadcast id 22 sent platform-wide since this affects every system's close workflow, not just Master.