Mark/kimi_agent_kin_app_sync
1
0
Fork 0
Code Issues 3 Pull requests Projects Releases 2 Packages Wiki Activity Actions

Feature: Romantic relationship tracking — intimacy logging, date night planning, black book integration #46

New issue
Closed
opened 2026-05-28 02:51:41 +00:00 by Mark · 3 comments
Mark commented 2026-05-28 02:51:41 +00:00
Owner
Copy link

Feature Request

Dedicated romantic relationship features, with the Little Black Book (#26) as the privacy layer for keeping those relationships discreet.

Romantic-Specific Tracking

Date Night Planning & Logging

  • Track date nights separately from general going-out interactions
  • Recurring: weekly date night, monthly weekend away
  • Who planned it, who treated, quality rating (1-5)
  • Suggestions: "You haven't had a date night in 3 weeks"

Intimacy Logging

  • Optional, granular per user comfort level
  • Mood/energy tags per interaction (loving, connected, distant, tired, stressed)
  • Pattern detection: correlate mood/energy with time of month, stress periods, work travel
  • Purely on-device, never synced, completely opt-in

Relationship Milestones

  • Anniversary tracking (in Dates already, but expand)
  • First date, first trip, moving in together, engagement, wedding
  • Custom milestones the user defines
  • Countdowns and reminders

Conflict & Repair Tracking

  • Log tough conversations separately (optional tag on Interaction)
  • Track repair attempts and effectiveness
  • Pattern: do you reconnect faster after certain types of conflict?
  • Only visible inside the black book if the relationship is vaulted

Black Book Integration (#26)

Romantic features and black book are intertwined:

  • All romantic tracking can optionally live inside the locked vault
  • Move a romantic partner to the black book = their entire history (dates, intimacy, milestones, gifts) goes with them
  • When vault is locked, no trace of romantic partners anywhere in the main app
  • Discreet mode: the black book icon doesn't show until a hidden gesture triggers it

Data Model Additions

interface Person {
  // existing fields...
  relationshipType: "friend" | "family" | "colleague" | "romantic" | "partner" | "spouse" | "other";
  romanceFields?: {
    anniversary?: string;
    milestones: Array<{ type: string; date: string; label: string }>;
    loveLanguageObserved?: string;  // inferred from data, not self-reported
  };
}

interface Interaction {
  // existing fields...
  mood?: string;              // loving, connected, distant, etc.
  intimacyLevel?: number;     // 1-5, if user opts in
  isRomantic?: boolean;        // tags for romantic interactions
  isConflict?: boolean;        // tags for hard conversations
  repairAttempt?: boolean;     // logged after a conflict
}

Privacy Layer

  • Black book vault required for sensitive romantic data (optional)
  • Intimacy logging is off by default with explicit opt-in
  • No romantic data in the weekly digest
  • Biometric gate before viewing romantic partner details

Acceptance Criteria

  • Date night logging with quality rating and planner attribution
  • Optional mood/energy tagging on interactions
  • Relationship milestones with countdowns
  • Conflict/repair tracking with correlation observations
  • Black book holds romantic partner data when vaulted
  • Intimacy logging opt-in, off by default
  • Date night suggestions from cadence data
  • All romantic data optional, granulated, privacy-first
## Feature Request Dedicated romantic relationship features, with the Little Black Book (#26) as the privacy layer for keeping those relationships discreet. ## Romantic-Specific Tracking ### Date Night Planning & Logging - Track date nights separately from general going-out interactions - Recurring: weekly date night, monthly weekend away - Who planned it, who treated, quality rating (1-5) - Suggestions: "You haven't had a date night in 3 weeks" ### Intimacy Logging - Optional, granular per user comfort level - Mood/energy tags per interaction (loving, connected, distant, tired, stressed) - Pattern detection: correlate mood/energy with time of month, stress periods, work travel - Purely on-device, never synced, completely opt-in ### Relationship Milestones - Anniversary tracking (in Dates already, but expand) - First date, first trip, moving in together, engagement, wedding - Custom milestones the user defines - Countdowns and reminders ### Conflict & Repair Tracking - Log tough conversations separately (optional tag on Interaction) - Track repair attempts and effectiveness - Pattern: do you reconnect faster after certain types of conflict? - Only visible inside the black book if the relationship is vaulted ## Black Book Integration (#26) Romantic features and black book are intertwined: - All romantic tracking can optionally live inside the locked vault - Move a romantic partner to the black book = their entire history (dates, intimacy, milestones, gifts) goes with them - When vault is locked, no trace of romantic partners anywhere in the main app - Discreet mode: the black book icon doesn't show until a hidden gesture triggers it ## Data Model Additions ```typescript interface Person { // existing fields... relationshipType: "friend" | "family" | "colleague" | "romantic" | "partner" | "spouse" | "other"; romanceFields?: { anniversary?: string; milestones: Array<{ type: string; date: string; label: string }>; loveLanguageObserved?: string; // inferred from data, not self-reported }; } interface Interaction { // existing fields... mood?: string; // loving, connected, distant, etc. intimacyLevel?: number; // 1-5, if user opts in isRomantic?: boolean; // tags for romantic interactions isConflict?: boolean; // tags for hard conversations repairAttempt?: boolean; // logged after a conflict } ``` ## Privacy Layer - Black book vault required for sensitive romantic data (optional) - Intimacy logging is off by default with explicit opt-in - No romantic data in the weekly digest - Biometric gate before viewing romantic partner details ## Acceptance Criteria - [ ] Date night logging with quality rating and planner attribution - [ ] Optional mood/energy tagging on interactions - [ ] Relationship milestones with countdowns - [ ] Conflict/repair tracking with correlation observations - [ ] Black book holds romantic partner data when vaulted - [ ] Intimacy logging opt-in, off by default - [ ] Date night suggestions from cadence data - [ ] All romantic data optional, granulated, privacy-first
Mark commented 2026-05-28 02:54:10 +00:00
Author
Owner
Copy link

⏸ Needs Decision

Blocking factors:

  • Didn't meet auto-approve criteria — scope=medium, risk=medium, spec=partial

Scope: medium Risk: medium Spec: partial Type: feature
Summary: Feature: Romantic relationship tracking — intimacy logging, date night planning, black book integration
Suggestion: needs investigation
Rationale:

Action: Review each blocking factor above. Remove blocked:needs-decision label to route back to triage.

## ⏸ Needs Decision **Blocking factors:** - **Didn't meet auto-approve criteria** — scope=medium, risk=medium, spec=partial --- **Scope:** medium **Risk:** medium **Spec:** partial **Type:** feature **Summary:** Feature: Romantic relationship tracking — intimacy logging, date night planning, black book integration **Suggestion:** needs investigation **Rationale:** **Action:** Review each blocking factor above. Remove `blocked:needs-decision` label to route back to triage.
Mark commented 2026-05-30 05:43:06 +00:00
Author
Owner
Copy link

GSD VERIFY phase found no changes after implementation.
Worker output: ]11;?\API call failed after 3 retries: HTTP 429: Rate limit exceeded. Please try again later.

GSD VERIFY phase found no changes after implementation. Worker output: ]11;?\API call failed after 3 retries: HTTP 429: Rate limit exceeded. Please try again later.
Mark commented 2026-05-30 14:16:07 +00:00
Author
Owner
Copy link

Decomposed into 7 slices:

  • #47 — Romantic relationship type + romanceFields data model (foundation, no deps)
  • #48 — Date night planning & logging with quality ratings (deps: #47)
  • #49 — Relationship milestones + countdowns (deps: #47)
  • #50 — Conflict & repair tracking (deps: #47)
  • #51 — Intimacy logging, opt-in off by default (deps: #47)
  • #52 — Romantic mood/energy tags + pattern detection (deps: #47)
  • #53 — Date night suggestions from cadence data (deps: #47, #48)

Black Book integration (#26) is intentionally excluded — it's a separate epic. Closing this parent as decomposed.

Decomposed into 7 slices: - #47 — Romantic relationship type + romanceFields data model (foundation, no deps) - #48 — Date night planning & logging with quality ratings (deps: #47) - #49 — Relationship milestones + countdowns (deps: #47) - #50 — Conflict & repair tracking (deps: #47) - #51 — Intimacy logging, opt-in off by default (deps: #47) - #52 — Romantic mood/energy tags + pattern detection (deps: #47) - #53 — Date night suggestions from cadence data (deps: #47, #48) Black Book integration (#26) is intentionally excluded — it's a separate epic. Closing this parent as decomposed.
Mark closed this issue 2026-05-30 14:16:17 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v1.1.0
v1.0.0
Labels
Clear labels   
blocked:depends-p1

Depends on #139 (P1) landing first. Picker should not auto-dispatch.

  
blocked:gate-research

   
blocked:lint-failed

   
blocked:needs-decision

   
blocked:needs-human

   
blocked:verify-failed

   
bug

   
data-loss

Data integrity or data loss risk

  
documentation

   
enhancement

   
feature-request

   
in-progress

   
needs-decompose

Issue needs decompose processing

  
needs-triage

   
pwa

Progressive Web App functionality

  
quickfix

   
security

Security vulnerability or hardening

  
security/high

High severity security issue

  
security/medium

Medium severity security issue

  
test

   
test-coverage

Test coverage review / gap report

  
triage-approved

Approved for automated fix pipeline

  
vault

Requires vault/LBB authentication (#26) — discretion-sensitive feature

No labels
blocked:depends-p1
blocked:gate-research
blocked:lint-failed
blocked:needs-decision
blocked:needs-human
blocked:verify-failed
bug
data-loss
documentation
enhancement
feature-request
in-progress
needs-decompose
needs-triage
pwa
quickfix
security
security/high
security/medium
test
test-coverage
triage-approved
vault
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/kimi_agent_kin_app_sync#46
No description provided.