`data/legal-review-tag-20260530.md`

35 lines
# drunk-animals — legal-review tagging (2026-05-30)

## Action
Tagged all held (unpublished, not user-removed) `drunk-animals` designs with the
`legal-review` tag in `dw_unified.all_designs`.

- **895** rows tagged `legal-review`
- **0** held rows left untagged after the run

## Why
These designs are blocked by the settlement DB trigger
(`settlement_publish_check()`): each prompt satisfies **Part A** (directional
palms + open space + multi-color) **AND Part B** (banana) — the exact
prohibited combination from the settlement. The publish trigger RAISEs on every
one of them.

Steve's explicit standing decision (2026-05-30): **never override the settlement
gate** for this set. They stay unpublished permanently. The `legal-review` tag
makes them filterable/identifiable in the curator so they aren't mistaken for
ordinary unpublished work or re-attempted.

## SQL applied (Mac2 dw_unified)
```sql
UPDATE all_designs
SET tags = array_append(COALESCE(tags, '{}'::text[]), 'legal-review')
WHERE category='drunk-animals'
  AND is_published IS NOT TRUE
  AND COALESCE(user_removed,FALSE)=FALSE
  AND NOT ('legal-review' = ANY(COALESCE(tags, '{}'::text[])));
-- UPDATE 895
```

Note: `tags` is a Postgres `text[]` array (not CSV). Plain tag UPDATE does not
flip `is_published`, so the settlement trigger does not fire.