docs: brand identity, copy guide, release checklists, store assets, README

README.md

@@ -2,6 +2,8 @@
 
 > *Private daily questions for couples who want honest answers before shared conversations.*
 
+**Product goal:** private, mutual-reveal relationship questions with real encryption and calmer UX.
+
 Closer is a **couples relationship app** built for partners who want a steadier way to talk, reflect, and make time for each other. It turns relationship check-ins into small, intentional rituals — one daily question, curated conversation packs, private answers, partner reveal flows, gentle reminders, and shared date planning.
 
 The app is **not** a social network, **not** a therapy replacement, and **not** a productivity tracker. There are no public feeds, no likes, no followers, and no infinite scroll. The core loop is simple: **answer honestly, choose what to reveal, and keep a record of the conversations that mattered.**
@@ -50,7 +52,8 @@ Subscription apps for couples have a trust problem — confusing trial wording,
 
 ## What Closer Does
 
-Closer gives couples a private, shared space for guided connection:
+Closer gives couples a private, shared space for guided connection. Every feature should support
+the product goal: **private, mutual-reveal relationship questions with real encryption and calmer UX**.
 
 - **Daily question** — one prompt a day, with written, scale, multiple-choice, and this-or-that answer modes.
 - **Private-first answers** — each partner answers independently before deciding whether to reveal or discuss.

docs/brand/visual-identity.md

@@ -3,6 +3,9 @@
 Closer should feel private, warm, and made for an equal partnership—not clinical, gamified, or like
 a public dating profile.
 
+Product goal: **private, mutual-reveal relationship questions with real encryption and calmer UX**.
+Visual decisions should reinforce that promise before decoration, novelty, or growth mechanics.
+
 ## Brand mark
 
 The mark is one heart formed by two equal halves. Pink and lavender represent two people meeting at

docs/copy-guide.md

@@ -1,5 +1,7 @@
 # Copy Guide
 
+Product goal: **private, mutual-reveal relationship questions with real encryption and calmer UX**.
+
 ## Voice
 - Warm, calm, and direct.
 - Speak to the couple, not to the implementation.
@@ -8,6 +10,7 @@
 
 ## Do
 - Say "private answer", "saved reflection", "question pack", and "reveal".
+- Use "mutual reveal" when explaining that both partners answer before seeing each other's response.
 - Use verbs for buttons: "Answer", "Reveal", "Open", "Remove".
 - Let empty states offer a gentle next step.
 - Name emotional intent when it helps: care, honesty, repair, closeness.
@@ -16,6 +19,7 @@
 - Internal terms such as "local", "preview", "placeholder", "seeded", "database", and "later batch".
 - Roadmap copy inside the app.
 - Overexplaining technical state.
+- Claims about encryption that are stronger than the implemented reveal model.
 - Destructive language as a primary action unless the screen is explicitly confirming deletion.
 
 ## Examples

docs/qa/private-mvp-checklist.md

@@ -3,6 +3,8 @@
 > Manual testing checklist for the internal MVP build. Covers every top-level flow in the app and notes known gaps discovered during the 2025-06 QA pass.
 > Last updated: 2026-06-21 — reflects pairing security hardening, notification preferences, appearance screen, email invite removal, real PartnerHomeScreen, real SubscriptionScreen, ProGuard log stripping, strings.xml, and support URL fix. All 17 release blocker items resolved or pending deploy.
 
+Product goal under test: **private, mutual-reveal relationship questions with real encryption and calmer UX**.
+
 ---
 
 ## Environment & Setup

docs/release/internal-testing-checklist.md

@@ -2,6 +2,8 @@
 
 > Steps to prepare, sign, and distribute an internal testing build for the private MVP. Assumes Android Gradle Plugin 8.7.3, Kotlin 2.0.21, minSdk 26, targetSdk/compileSdk 35, and `app.closer` applicationId.
 
+Internal testing should verify the product goal: **private, mutual-reveal relationship questions with real encryption and calmer UX**.
+
 ---
 
 ## 1. Pre-build Checklist

docs/release/store-assets.md

@@ -2,6 +2,8 @@
 
 > Checklist of assets, metadata, and compliance items needed for a Google Play Store submission. Targeting the private MVP / internal launch phase.
 
+Store assets should express the product goal: **private, mutual-reveal relationship questions with real encryption and calmer UX**.
+
 ---
 
 ## 1. Store Listing Metadata