# Sthira ledger

12 entries. Nothing is deleted: superseded and rejected ones are kept.

## Settled (8)

### Database choice

- **Kind:** decision
- **Statement:** Acme Notes uses Postgres for the user store due to the need for joins across users, orgs, and notebooks.
- **Why:** We need joins across users, orgs and notebooks
- **Rejected alternatives:** MongoDB
- **Source:** Acme Notes: database choice (chatgpt, 2026-03-04, acme-db / acme-db-4)

> Ok, decided: we go with Postgres, not MongoDB. We need joins across users, orgs and notebooks.

### Acme Notes login flow choice

- **Kind:** decision
- **Statement:** Acme Notes will use magic links only, no passwords.
- **Why:** User explicitly chose magic links after noting password resets were half their support tickets at last job
- **Rejected alternatives:** email+password; OAuth
- **Source:** Acme Notes: login flow (chatgpt, 2026-03-09, acme-auth / acme-auth-2)

> Let's do magic links only, no passwords.

### Pricing strategy decision

- **Kind:** open question
- **Statement:** Pricing strategy remains undecided until beta user data is gathered
- **Why:** User explicitly stated 'I honestly can't decide yet. Let's leave pricing open until we have beta users and revisit.'
- **Source:** Acme Notes: pricing (chatgpt, 2026-03-20, acme-pricing / acme-pricing-2)

> I honestly can't decide yet. Let's leave pricing open until we have beta users and revisit.

### Acme Notes frontend stack

- **Kind:** decision
- **Statement:** Acme Notes will use SvelteKit with strict TypeScript.
- **Why:** The whole team knows Svelte already. We'll use SvelteKit, not Next.js. And always TypeScript in strict mode.
- **Rejected alternatives:** Next.js
- **Source:** Acme Notes: frontend stack (chatgpt, 2026-04-02, acme-frontend / acme-frontend-2)

> The whole team knows Svelte already. We'll use SvelteKit, not Next.js. And always TypeScript in strict mode.

### Web app first, mobile after web stability

- **Kind:** decision
- **Statement:** Acme Notes will ship the web app first and the mobile app after the web app is stable.
- **Why:** Decision: we ship the web app first and the mobile app after web is stable.
- **Source:** Acme Notes standup 2026-05-12 (transcript, 2026-05-12, 2026-05-12-standup / 2)

> Decision: we ship the web app first and the mobile app after web is stable.

### Onboarding copy draft by Friday

- **Kind:** commitment
- **Statement:** Danica will draft the onboarding copy by Friday.
- **Why:** I'll draft the onboarding copy by Friday.
- **Source:** Acme Notes standup 2026-05-12 (transcript, 2026-05-12, 2026-05-12-standup / 3)

> I'll draft the onboarding copy by Friday.

### Weekly standups move to Mondays

- **Kind:** commitment
- **Statement:** Weekly standups will move to Mondays at 10.
- **Why:** Also, weekly standups move to Mondays at 10.
- **Source:** Acme Notes standup 2026-05-12 (transcript, 2026-05-12, 2026-05-12-standup / 4)

> Also, weekly standups move to Mondays at 10.

### Acme Notes uses APNs for iOS push notifications

- **Kind:** decision
- **Statement:** Acme Notes will use APNs directly for iOS push notifications
- **Why:** User explicitly chose APNs after testing FCM and finding it flaky on iOS
- **Rejected alternatives:** Firebase Cloud Messaging (FCM)
- **Source:** Acme Notes: push notifications (chatgpt, 2026-05-20, acme-push / acme-push-2)

> Lesson learned: don't rely on FCM for iOS. Let's use APNs directly for iOS push.

## Rejected (4)

### Kitten name chosen

- **Kind:** decision
- **Statement:** User selected Miso as the perfect name for a grey kitten
- **Why:** User explicitly said 'haha Miso is perfect, thanks!' after assistant suggested Miso
- **Rejected alternatives:** Pebble; Ash
- **Source:** Cat names (chatgpt, 2026-03-06, acme-cat / acme-cat-2)

> haha Miso is perfect, thanks!

### CRDTs vs OTs

- **Kind:** decision
- **Statement:** CRDTs merge data without coordination, while OTs require central server coordination to transform operations
- **Why:** From [3]: 'OT transforms concurrent operations against each other through a central server; CRDTs merge by design without coordination.'
- **Rejected alternatives:** OTs are simpler than CRDTs; CRDTs are more scalable than OTs
- **Source:** Explain CRDTs (chatgpt, 2026-03-15, acme-crdt / acme-crdt-3)

> OT transforms concurrent operations against each other through a central server; CRDTs merge by design without coordination

### User's weekend trip planning

- **Kind:** decision
- **Statement:** User plans to visit Abbey Falls early, try a coffee estate stay, and carry a light jacket for the Coorg trip.
- **Why:** The user explicitly states they are planning a weekend trip to Coorg and the assistant provides specific tips that the user accepts with 'thanks, sounds lovely!' indicating acceptance of the advice.
- **Source:** Weekend in Coorg (chatgpt, 2026-04-11, acme-trip / acme-trip-1)

> Visit Abbey Falls early, try a coffee estate stay, and carry a light jacket.

### Poem for mom's birthday

- **Kind:** decision
- **Statement:** User will write a short poem for mom's birthday
- **Why:** User explicitly asked to write a poem for mom's birthday
- **Source:** Poem for mom (chatgpt, 2026-05-25, acme-poem / acme-poem-0)

> write a short poem for my mom's birthday
