Feature: Track who treated when logging going-out interactions

Mark commented

2026-05-28 00:07:01 +00:00

Owner

Feature Request

When logging a going-out interaction (dinner, drinks, coffee, event), optionally note who treated — you paid, they paid, or split. It's about recording the gesture, not tracking a spreadsheet.

How It Works

When logging an interaction of type "In-Person" or similar outings, optionally add:

Who paid? ○ I did ○ They did ○ We split

That's it. Simple radio button on the interaction form.

No amounts, no split calculations, no balances (unless the user wants to add those later)
No description or date — comes from the interaction itself
Shows on the interaction detail as a little note: "Alice treated" or "You treated Alice" or "Split"

Optional (future)

If both sides use the app, could sync to show "Bob treated you to dinner" on Alice's end
Amount tracking for those who want it, but purely additive — never required

Data Model

interface Interaction {
  // existing fields...
  whoPaid?: "me" | "them" | "split";
}

Simple enum on the existing Interaction. No new tables, no balance computation, no debt tracking.

Why

Kin is about nurturing relationships. Picking up the tab or being treated is part of that story. This just lets you remember who did what, the same way you remember "we went to that Italian place" — it's a memory, not an accounting entry.

## Feature Request When logging a going-out interaction (dinner, drinks, coffee, event), optionally note **who treated** — you paid, they paid, or split. It's about recording the gesture, not tracking a spreadsheet. ## How It Works When logging an interaction of type "In-Person" or similar outings, optionally add: > **Who paid?** ○ I did ○ They did ○ We split That's it. Simple radio button on the interaction form. - No amounts, no split calculations, no balances (unless the user wants to add those later) - No description or date — comes from the interaction itself - Shows on the interaction detail as a little note: "Alice treated" or "You treated Alice" or "Split" ## Optional (future) - If both sides use the app, could sync to show "Bob treated you to dinner" on Alice's end - Amount tracking for those who want it, but purely additive — never required ## Data Model ```typescript interface Interaction { // existing fields... whoPaid?: "me" | "them" | "split"; } ``` Simple enum on the existing Interaction. No new tables, no balance computation, no debt tracking. ## Why Kin is about nurturing relationships. Picking up the tab or being treated is part of that story. This just lets you remember who did what, the same way you remember "we went to that Italian place" — it's a memory, not an accounting entry.

Mark added the

blocked:needs-decision

label

2026-05-28 00:07:01 +00:00

Mark commented

2026-05-28 00:08:03 +00:00

Author

Owner

⏸ Needs Decision

Blocking factors:

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

Scope: medium Risk: low Spec: partial Type: feature
Summary: Add expense/bill splitting recording, running balance tracking, and settlement functionality between Kin contacts.
Suggestion: Follow existing architecture pattern exactly: types.ts (Expense + ExpenseSplit + Balance interfaces) → Dexie table/store (new 'expenses' table + CRUD + balance queries) → schemas.ts (Zod) → store.ts (new Zustand slice) → pages/Expenses.tsx + route in App.tsx + sidebar nav item. Start with equal split only, add custom/percentage as a follow-up. Balance tracking gated behind an opt-in flag on each expense. Accessible both from a top-level nav entry and from per-person detail page.
Rationale: Medium scope because it's a wholly new module (~8-10 files, 500-700 new lines) following the exact same additive patterns as existing features (Gifts, Interactions, DateEvents). Low risk because it touches zero existing data models or core paths — only additive changes to nav (Layout.tsx), routing (App.tsx), and import/export (db.ts). Partial spec alignment: bill splitting is relationship-adjacent (roommates, dining groups, trip sharing) but not core PRM functionality. The app is about tracking relationships, not shared finances — though it's a reasonable extension for practical relationship management.

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=low, spec=partial --- **Scope:** medium **Risk:** low **Spec:** partial **Type:** feature **Summary:** Add expense/bill splitting recording, running balance tracking, and settlement functionality between Kin contacts. **Suggestion:** Follow existing architecture pattern exactly: types.ts (Expense + ExpenseSplit + Balance interfaces) → Dexie table/store (new 'expenses' table + CRUD + balance queries) → schemas.ts (Zod) → store.ts (new Zustand slice) → pages/Expenses.tsx + route in App.tsx + sidebar nav item. Start with equal split only, add custom/percentage as a follow-up. Balance tracking gated behind an opt-in flag on each expense. Accessible both from a top-level nav entry and from per-person detail page. **Rationale:** Medium scope because it's a wholly new module (~8-10 files, 500-700 new lines) following the exact same additive patterns as existing features (Gifts, Interactions, DateEvents). Low risk because it touches zero existing data models or core paths — only additive changes to nav (Layout.tsx), routing (App.tsx), and import/export (db.ts). Partial spec alignment: bill splitting is relationship-adjacent (roommates, dining groups, trip sharing) but not core PRM functionality. The app is about tracking relationships, not shared finances — though it's a reasonable extension for practical relationship management. **Action:** Review each blocking factor above. Remove `blocked:needs-decision` label to route back to triage.

Mark changed title from ~~Feature: Bill splitting — track shared expenses and balances between people~~ to Feature: Bill splitting on going-out interactions — track who paid and optional balances

2026-05-28 00:08:30 +00:00

Mark changed title from ~~Feature: Bill splitting on going-out interactions — track who paid and optional balances~~ to Feature: Track who treated when logging going-out interactions

2026-05-28 00:09:28 +00:00

Mark referenced this issue

2026-05-28 01:40:04 +00:00

Feature: Family hub — shared events, tasks, and coordination #45

Mark added

triage-approved

quickfix

and removed

blocked:needs-decision

labels

2026-05-28 07:18:45 +00:00

Mark commented

2026-05-28 12:38:22 +00:00

Author

Owner

🤖 [quickfix-kimi_agent_kin_app_sync-27] still working — overseer retry