STATE — Kimosabe.AI

You are here. A 1-page living snapshot of the project. Updated when reality changes, not on a schedule. If this file disagrees with code, code wins and this file is wrong — fix it.

• Backward-looking: CHANGELOG.md
• Forward-looking: docs/ROADMAP.md
• Why we chose what we chose: docs/adr/
• What we're building (scope): docs/REQUIREMENTS.md
• Browsable version: https://kimosabe.ai/docs/STATE

Repository note: Code lives in Lovable's managed git storage and is mirrored to the connected GitHub repository. Two-way sync is live as of 2026-08-25 — commits made in Lovable push to GitHub automatically, and commits pushed to GitHub sync back. There is no manual push step. See CHANGELOG.md for the latest saved state.

Identity (locked)

• Name: Kimosabe.AI · Domain: kimosabe.ai
• Tagline: Curate Your Brain
• Promise: Privacy-first, end-to-end encrypted messenger for Americans. Server-blind. No phone number. No contact-graph upload.
• Brand: deep purple ground · antique gold accents · warm cream type · Inter
• Logo: Metatron's Cube — src/assets/kimosabe-logo.jpg

Phase 1 — MVP (≈ 97% complete)

Shipped & live: email+password auth · @username discovery · ECDH P-256 identity keys (in-browser) · Recovery Key (24-char, ~120-bit, double-wrapped private key) · 1:1 E2EE chat (ECDH→HKDF→AES-GCM-256) · encrypted image attachments · disappearing messages + pg_cron purge · opt-in delivery/read receipts · installable PWA + offline outbox · settings (rotate recovery, export identity, delete account) · zero-knowledge recover-with-key edge function · public /trust page.

Open before Phase 2:

Active work

• Agent SDK Preview (packages/agent-sdk-preview/) — proof-of-life Node 20+ adapter validating the AGENTS.md contract against the current 1:1 protocol. Will be rewritten when MLS lands. Not consumed by the web app.
• CI (.github/workflows/ci.yml) — typechecks the web app and the preview package on every PR so the agent contract can't silently regress.
• Documentation suite complete: STANDARDS · REQUIREMENTS · BUSINESS · PROJECT_MANAGEMENT · GAMIFICATION · ADRs 0001–0005 · per-framework agent notes (Hermes / OpenClaw / Agent Zero).

Decision waiting on a human

Use Phase 1 with real humans for 90 days before starting Phase 2. Everything below the line in ROADMAP.md (MLS, X3DH, sealed sender, voice notes, passkeys) is real engineering work. Starting it before Phase 1 has been used risks building the wrong second floor on top of the right first floor.

The recommendation here is: freeze scope, invite users, listen, then unfreeze. A counter-decision (start Phase 2 now) is fine — but it should be explicit, not drift.

What is sacred

The "Out of scope (forever)" list at the bottom of ROADMAP.md is the product. Every item on it is a feature other messengers have and we deliberately don't:

• No server-side message search
• No plaintext push notifications
• No cloud backup of message history
• No backdoor of any kind
• No phone number requirement
• No contact-graph upload

Negotiating one item off this list is the day the project becomes every other messenger. Treat any request to weaken it as an ADR-worthy event.

Phase map (one line each)

1. MVP — 1:1 E2EE PWA. (here)
2. Group + verified contacts — MLS (RFC 9420), X3DH + Double Ratchet, safety numbers, voice notes, sealed sender v1, encrypted push, optional Passkeys.
3. Metadata reduction — sealed sender v2, optional relay, encrypted profile, federated identity attestation.
4. Off-grid (native) — separate native client sharing identity keys; Bluetooth + Wi-Fi-Direct mesh; optional LoRa.
5. Super-app surfaces — encrypted feed, P2P payments, sandboxed mini-apps.
6. AI agents — frameworks plug in as first-class users with their own keypair. See AGENTS.md.

Last meaningful update: 2026-08-25 (GitHub two-way sync confirmed live; docs browsable at /docs; dates synced).