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

Intentional relational cadence — apply habit formation dynamics toward another person #82

New issue
Closed
opened 2026-06-09 02:35:41 +00:00 by Mark · 1 comment
Mark commented 2026-06-09 02:35:41 +00:00
Owner
Copy link

Summary

Use the spaced repetition / lock-in mechanics from #81 as a tool of intentional relational investment — applying a deliberate cadence toward another person to build trust, deepen connection, and gradually establish a mutual rhythm. Not manipulation, but acting with purpose: knowing that consistent, well-timed presence matters, and using the app to help you deliver that.

Romantic relationships and intimacy levels are first-class concerns throughout. The same mechanism that works for "call grandma every 2 weeks" applies differently to "deepen this romantic connection" — shorter windows, intimacy-aware timing, privacy constraints.

P1: Relational cadence mode (core UX)

A new mode in Kin where you select a person and say "I want to intentionally invest in this relationship." The app then manages a spaced-repetition cadence for them, not just for you.

  • Add "Invest in this relationship" toggle on PersonDetail — activates a cadence target for the selected person
  • Cadence type selection: frequency (every X days), deepening (expanding intervals = trust-building), milestone (events/dates), romantic (intimacy-aware timing)
  • Romantic cadence mode: shorter base intervals, different expanding factor (gentler curve), integrates with intimacy logging toggle, suggests moments that align with romantic context (anniversaries, milestones, quality-time patterns)
  • The engine from #81 drives the nudge: expanding intervals, lock-in scoring, decay curves — but framed as "recommended touchpoint" not "you're overdue"
  • Dashboard shows active investments: "You're investing in 4 relationships — Alex is nearing a cadence milestone"
  • After each interaction, shows next window: "Next check-in with Sarah: ~5 days. Consistent touchpoints here build toward a deeper connection."
  • Relationship warm-up mode: for reconnection efforts, start with tighter intervals (every 2-3 days) that gradually expand as trust rebuilds

P2: Reciprocity & mutual awareness

Not scorekeeping, but awareness of the two-way dynamic so you can calibrate.

  • Initiation ratio per person over trailing 4/8/12 weeks: "You initiated 7/10 recent interactions with Sarah" — shown as a quiet indicator, not a judgment
  • Responsiveness profile: detect typical reply cadence per person (same-day, within 2 days, etc.) so you don't misread silence
  • "Both-sides cooling" flag: if interaction volume drops >50% on both sides for 4+ weeks, flag the relationship as atrophying regardless of who dropped the ball
  • Trending arrows on PersonDetail: "Activity is up this quarter" / "Conversation depth has increased" / "This connection is cooling"
  • Shared activity detection: if you both log interactions around the same topics, surface it (feeds Emergent Observations)
  • These metrics are private, local-only, and can be hidden entirely if the user prefers

P3: Mutual cadence discovery

Instead of imposing a cadence, discover what naturally works between two people.

  • Analyze interaction timestamps to detect the natural interval: "You and Alex connect every 10-14 days — 83% match rate over 6 weeks"
  • Surface the natural cadence as a suggestion: "This rhythm is working. Want to reinforce it?"
  • If the natural cadence diverges from a stated goal, flag it gently: "You set a goal of weekly, but your natural rhythm is every 10 days — consider adjusting?"
  • Mutual lock-in: if both parties initiate reliably over the natural cadence period, mark the relationship as "mutual" — the investment is sustainable

P4: Sensitivity & privacy layer

These features touch the most sensitive relationship data in the app. Must be handled with care.

  • Every relational cadence feature is opt-in — nothing tracks or monitors anyone without explicit user activation
  • All reciprocity/awareness metrics stored only on-device, never exported or included in share/backup by default
  • Romantic cadence mode should have a biometric/PIN gate (ties into vault #26's authentication)
  • Option to pause all relational investment tracking (emergency stop, doesn't delete data)
  • Clear UI labeling: "Private awareness — never shared, never synced"
  • Ability to reset metrics for a specific relationship ("start fresh")

P5: Goal integration with #80

Connect this feature to the Relationship Goals model.

  • Goal types get a new strategy: "Intentional cadence" — the goal defines the outcome ("deepen friendship with Sarah"), the cadence engine drives the how
  • Romantic goal templates: "Nurture romantic connection", "Rebuild intimacy", "Deepen partnership", "Navigate a transition together"
  • Goals show cadence health: "On track — 4 weeks of consistent investment" / "Slipping — 2 weeks since last touchpoint"
  • Milestone celebration: when lock-in score crosses thresholds, celebrate it as a goal milestone within the existing Milestone system

Tech notes

  • Reuses #81's cadence engine directly — same interval calculator, lock-in scoring, decay curves
  • Adds a relationalCadence field to the Person type (or a separate settings object per person)
  • Reciprocity is pure computation over existing interaction timestamps — no new data collection
  • Responsiveness detection requires timestamps but no new permissions (already have interaction data)
  • All P4 privacy controls need to exist before any P1/P2/P3 feature ships
  • Romantic cadence mode differs from platonic only in default parameters (interval floor, expansion factor) — the math is the same
## Summary Use the spaced repetition / lock-in mechanics from #81 as a tool of **intentional relational investment** — applying a deliberate cadence toward another person to build trust, deepen connection, and gradually establish a mutual rhythm. Not manipulation, but acting with purpose: knowing that consistent, well-timed presence matters, and using the app to help you deliver that. Romantic relationships and intimacy levels are first-class concerns throughout. The same mechanism that works for "call grandma every 2 weeks" applies differently to "deepen this romantic connection" — shorter windows, intimacy-aware timing, privacy constraints. --- ### P1: Relational cadence mode (core UX) A new mode in Kin where you select a person and say "I want to intentionally invest in this relationship." The app then manages a spaced-repetition cadence *for them*, not just for you. - [ ] Add "Invest in this relationship" toggle on PersonDetail — activates a cadence target for the selected person - [ ] Cadence type selection: frequency (every X days), deepening (expanding intervals = trust-building), milestone (events/dates), romantic (intimacy-aware timing) - [ ] Romantic cadence mode: shorter base intervals, different expanding factor (gentler curve), integrates with intimacy logging toggle, suggests moments that align with romantic context (anniversaries, milestones, quality-time patterns) - [ ] The engine from #81 drives the nudge: expanding intervals, lock-in scoring, decay curves — but framed as "recommended touchpoint" not "you're overdue" - [ ] Dashboard shows active investments: "You're investing in 4 relationships — Alex is nearing a cadence milestone" - [ ] After each interaction, shows next window: "Next check-in with Sarah: ~5 days. Consistent touchpoints here build toward a deeper connection." - [ ] Relationship warm-up mode: for reconnection efforts, start with tighter intervals (every 2-3 days) that gradually expand as trust rebuilds ### P2: Reciprocity & mutual awareness Not scorekeeping, but awareness of the two-way dynamic so you can calibrate. - [ ] Initiation ratio per person over trailing 4/8/12 weeks: "You initiated 7/10 recent interactions with Sarah" — shown as a quiet indicator, not a judgment - [ ] Responsiveness profile: detect typical reply cadence per person (same-day, within 2 days, etc.) so you don't misread silence - [ ] "Both-sides cooling" flag: if interaction volume drops >50% on both sides for 4+ weeks, flag the relationship as atrophying regardless of who dropped the ball - [ ] Trending arrows on PersonDetail: "Activity is up this quarter" / "Conversation depth has increased" / "This connection is cooling" - [ ] Shared activity detection: if you both log interactions around the same topics, surface it (feeds Emergent Observations) - [ ] These metrics are private, local-only, and can be hidden entirely if the user prefers ### P3: Mutual cadence discovery Instead of imposing a cadence, discover what naturally works between two people. - [ ] Analyze interaction timestamps to detect the natural interval: "You and Alex connect every 10-14 days — 83% match rate over 6 weeks" - [ ] Surface the natural cadence as a suggestion: "This rhythm is working. Want to reinforce it?" - [ ] If the natural cadence diverges from a stated goal, flag it gently: "You set a goal of weekly, but your natural rhythm is every 10 days — consider adjusting?" - [ ] Mutual lock-in: if both parties initiate reliably over the natural cadence period, mark the relationship as "mutual" — the investment is sustainable ### P4: Sensitivity & privacy layer These features touch the most sensitive relationship data in the app. Must be handled with care. - [ ] Every relational cadence feature is opt-in — nothing tracks or monitors anyone without explicit user activation - [ ] All reciprocity/awareness metrics stored only on-device, never exported or included in share/backup by default - [ ] Romantic cadence mode should have a biometric/PIN gate (ties into vault #26's authentication) - [ ] Option to pause all relational investment tracking (emergency stop, doesn't delete data) - [ ] Clear UI labeling: "Private awareness — never shared, never synced" - [ ] Ability to reset metrics for a specific relationship ("start fresh") ### P5: Goal integration with #80 Connect this feature to the Relationship Goals model. - [ ] Goal types get a new strategy: "Intentional cadence" — the goal defines the outcome ("deepen friendship with Sarah"), the cadence engine drives the how - [ ] Romantic goal templates: "Nurture romantic connection", "Rebuild intimacy", "Deepen partnership", "Navigate a transition together" - [ ] Goals show cadence health: "On track — 4 weeks of consistent investment" / "Slipping — 2 weeks since last touchpoint" - [ ] Milestone celebration: when lock-in score crosses thresholds, celebrate it as a goal milestone within the existing Milestone system ## Tech notes - Reuses #81's cadence engine directly — same interval calculator, lock-in scoring, decay curves - Adds a `relationalCadence` field to the Person type (or a separate settings object per person) - Reciprocity is pure computation over existing interaction timestamps — no new data collection - Responsiveness detection requires timestamps but no new permissions (already have interaction data) - All P4 privacy controls need to exist before any P1/P2/P3 feature ships - Romantic cadence mode differs from platonic only in default parameters (interval floor, expansion factor) — the math is the same
Mark commented 2026-06-09 03:50:27 +00:00
Author
Owner
Copy link

This issue has been decomposed into the following sub-issues:

# Title Phase Scope
#89 Intentional relational cadence — apply habit formation dynam A new mode in Kin where you select a person and say "I want to intentionally inv
#90 Intentional relational cadence — apply habit formation dynam Not scorekeeping, but awareness of the two-way dynamic so you can calibrate. -
#91 Intentional relational cadence — apply habit formation dynam Instead of imposing a cadence, discover what naturally works between two people.
#92 Intentional relational cadence — apply habit formation dynam These features touch the most sensitive relationship data in the app. Must be ha
#93 Intentional relational cadence — apply habit formation dynam Connect this feature to the Relationship Goals model. - [ ] Goal types get a ne

Each sub-issue has been labeled with needs-triage and will be evaluated by the triage pipeline before queue routing.

This issue has been decomposed into the following sub-issues: | # | Title | Phase Scope | |---|-------|-------------| | #89 | Intentional relational cadence — apply habit formation dynam | A new mode in Kin where you select a person and say "I want to intentionally inv | | #90 | Intentional relational cadence — apply habit formation dynam | Not scorekeeping, but awareness of the two-way dynamic so you can calibrate. - | | #91 | Intentional relational cadence — apply habit formation dynam | Instead of imposing a cadence, discover what naturally works between two people. | | #92 | Intentional relational cadence — apply habit formation dynam | These features touch the most sensitive relationship data in the app. Must be ha | | #93 | Intentional relational cadence — apply habit formation dynam | Connect this feature to the Relationship Goals model. - [ ] Goal types get a ne | Each sub-issue has been labeled with `needs-triage` and will be evaluated by the triage pipeline before queue routing.
Mark closed this issue 2026-06-09 03:50:27 +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#82
No description provided.