yolo tick 12: couples-closets debate verdict (HOLD - pilot with safeguards)

543e924f77841164e4000e0bc3bdc9e6b0008f40 · 2026-05-12 00:56:41 -0700 · SteveStudio2

Files touched

A docs/DEBATE-couples-2026-05-12.md

Diff

commit 543e924f77841164e4000e0bc3bdc9e6b0008f40
Author: SteveStudio2 <stevestudio2@SteveStacStudio.lan>
Date:   Tue May 12 00:56:41 2026 -0700

    yolo tick 12: couples-closets debate verdict (HOLD - pilot with safeguards)
---
 docs/DEBATE-couples-2026-05-12.md | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/docs/DEBATE-couples-2026-05-12.md b/docs/DEBATE-couples-2026-05-12.md
new file mode 100644
index 0000000..38e7643
--- /dev/null
+++ b/docs/DEBATE-couples-2026-05-12.md
@@ -0,0 +1,34 @@
+# Dream-team Debate — Couples / Shared Closets (2026-05-12, tick 12)
+
+**Topic:** Should WhatsMyStyle support couples / shared closets?
+
+**Spec under consideration**
+- One Dopple twin per partner
+- Outfit-builder draws from both closets
+- Gifts mode: partner A picks clothes for partner B (B approves render)
+- Privacy: per-garment opt-in (private items)
+- UX: partner-switcher pill in Studio
+- Cost: doubles render budget per couple
+- Risk: divorce/breakup — exit flow must purge cross-twin training data
+
+**Panel:** qwen3:14b (DEFENDER) · hermes3:8b (PROSECUTOR) · gemma3:12b (PRAGMATIST)
+
+**Verdict:** **HOLD** — Pilot the couples feature with strict data tracking, user feedback, and mandatory relationship health checks to mitigate risks before full rollout.
+
+## Agreed actions (synthesized)
+
+1. **Pilot with safeguards.** Launch a limited couples feature with contextual privacy controls, breakup data reset options, and a "report" function for gift mode misuse, alongside rigorous user feedback collection.
+
+2. **Mandatory relationship health checks.** Integrate third-party audits for cross-twin data exits and require users to confirm mutual consent for shared closet participation.
+
+3. **Scalability and cultural testing.** Validate ROI and cultural acceptance through targeted user research before scaling, ensuring technical debt and privacy risks are addressed proactively.
+
+## Next-tick action items (engineering)
+
+- [ ] Design `couples` table (couple_id, partner_a_user_id, partner_b_user_id, opt_in_at, exit_at)
+- [ ] Per-garment `closet.privacy` enum: `shared` | `private`
+- [ ] Gift-mode consent UI: B-approves render slot before A can confirm
+- [ ] Breakup flow: `POST /api/couple/exit` purges cross-twin embeddings, gift-mode try-ons, and analytics joins
+- [ ] Pilot gate: feature flag `couples_pilot`, require both partners to be paying users
+
+Persisted to SQLite `debates` table id 8.

← b9b14db yolo tick 12: +40 sustainability brands, +6 takeback program · back to Whatsmystyle · yolo tick 13: couples + embedding_drifts schema; closet.priv 477ba99 →