Guard: trigger on spoon_all_designs (live catalog source), not all_designs curator table — avoids needless prod deploys on curator churn

8ccea8a1d29291d432584ef595e10a4e2a9f91cc · 2026-05-30 21:12:14 -0700 · Steve Abrams

Files touched

M scripts/settlement-guard-sweep.sh

Diff

commit 8ccea8a1d29291d432584ef595e10a4e2a9f91cc
Author: Steve Abrams <steve@designerwallcoverings.com>
Date:   Sat May 30 21:12:14 2026 -0700

    Guard: trigger on spoon_all_designs (live catalog source), not all_designs curator table — avoids needless prod deploys on curator churn
---
 scripts/settlement-guard-sweep.sh | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/scripts/settlement-guard-sweep.sh b/scripts/settlement-guard-sweep.sh
index 5670e61..e39bfc9 100755
--- a/scripts/settlement-guard-sweep.sh
+++ b/scripts/settlement-guard-sweep.sh
@@ -26,7 +26,11 @@ ts() { date '+%Y-%m-%d %H:%M:%S'; }
 # Predicate for a genuine settlement LEGAL block (NOT the BLEED_GHOST quality family).
 PRED="is_published=TRUE AND (settlement_verdict='BLOCK' OR settlement_verdict LIKE 'REVIEW-VISION-ERROR%')"
 
-N=$(psql dw_unified -At -c "SELECT count(*) FROM all_designs WHERE $PRED;" 2>>"$LOG")
+# Trigger on spoon_all_designs — the CATALOG SOURCE the live grid reads (via designs.json).
+# all_designs is the curator table and is NOT customer-facing, so its churn must NOT drive
+# prod deploys. We still mirror-clean all_designs below for curator consistency, but the
+# spoon count is what decides whether a leak is actually live.
+N=$(psql dw_unified -At -c "SELECT count(*) FROM spoon_all_designs WHERE $PRED;" 2>>"$LOG")
 
 if [ "${N:-0}" -eq 0 ]; then
   echo "$(ts) clean — 0 settlement-legal-block designs published" >> "$LOG"

← 0b0f327 publish drunk-animals 5/28-5/30 batch2 (+44 via curator forc · back to Wallco Ai · publish next-5 settlement-clean drunk-animals batch3 (Steve 25e21a7 →