Storehouse and Timeline

Storehouse & Timeline

Routes: /storehouse · /timeline · Sidebar: Your Data → Storehouse · Home → Timeline

The Storehouse is Compass's founding promise: one local place that holds all of your data — owned by you, never lost if a service shuts down, and exportable at will. It pairs a set of owned domains (Contacts, Subscriptions, Assets) with a universal Drop Zone → Timeline that turns any data export into one searchable, append-only life log. Design: docs/storehouse-roadmap.md.

Related but distinct: the /overview home page. Compass also has a newer Overview page (/overview, Home section, and the app's actual default landing route — / redirects there) that bills itself with a near-identical pitch: "Everything you've brought into Compass, in one place." It's a global search-everything box over the Timeline plus quick links into People, Contacts, Merchants & Places, Subscriptions, and Household & Assets, built on top of the newer cross-reference/derived-entities engine (see below) rather than this page's direct per-domain aggregation. Storehouse.tsx at /storehouse is unchanged and still the place for the read-only domain tiles described below — the two pages currently coexist as different "one place for everything" views, Overview being the more general entry point and Storehouse the domain-focused summary.

Storehouse overview (/storehouse)

A read-only home base with summary tiles — Contacts count, Subscriptions (annual total + active), Assets (total value, by type) — plus upcoming renewals (subscriptions + assets, next 60 days), each deep-linking to its domain page, the Export Center, and the Vault. It grows as more domains land (documents, medical, finance net worth).

The owned domains:

• Contacts — a vCard-structured address book; import from CSV / vCard / macOS / LinkedIn / Facebook / Google Voice; export as vCard.
• Subscriptions — first-class subscriptions (cost, cadence, status, next renewal), distinct from the detected recurring charges in Finance. Manual entries cover what Compass can't see (cash / annual / another card).
• Assets — household inventory by type (insurance / vehicle / property / membership / warranty / pet / other) with renewal highlighting.

The Drop Zone → Timeline (/timeline)

Drag any data export — CSV, JSON, XML, mbox, zip, or a SQLite file — into the Drop Zone. A registry of ~44 recognizers (electron/lib/recognizers.ts) sniffs each file by name / header / shape and normalizes it into the unified records store. Coverage today:

• Activity & media — Netflix, Spotify, YouTube, Goodreads, Amazon.
• Social — LinkedIn (12 record types), Facebook (posts/friends/comments/messages/…), Google Takeout (activity/Chrome/Play/Pay/Calendar/Fit/Voice).
• Money — PayPal, Venmo (CSV).
• Streaming-scale files — Apple Health export.xml, email archives (.mbox).
• Local databases — browser history (Chrome / Safari / Firefox), iMessage chat.db.
• PDFs — credit report, tax documents, Social Security statement, generic letters (a content-light index — the sensitive source text is never stored).

Every record carries source + type + occurredAt + payload and a content-addressed hash, so re-importing the same export is idempotent (no double-counting).

Searching the Timeline

• Full-text — a records_fts (FTS5) index over title/body/payload, bm25-ranked.
• By meaning — an opt-in local semantic index (records-embeddings.json, via Ollama) with a transparent FTS fallback when there's no index. Toggle it on the Timeline.
• Curate — high-volume/low-signal sources (browser history) are tagged a firehose and collapsed by default ("Show browsing (N hidden)"). Nothing is deleted — tag & filter, keep everything.
• On this day — a Dashboard card surfaces records from prior years sharing today's date.

Privacy: the Timeline is the one deliberate, user-opted-in relaxation of the aggregates-only assistant boundary — compass_search_timeline / search_records can return matching records (capped, char-budgeted, payload never returned). The vault and raw finance stay aggregates-only. See Security & Privacy.

The cross-reference engine: from records to People & Places

Dropping files into the Timeline is only half of Compass's founding promise — the other half is turning that raw, siloed pile of records into entities you actually recognize: the people you talk to, the merchants you pay, the places you go. electron/lib/entities.ts projects the records store into typed candidates (kind: person / merchant / place / subscription-candidate), cached in a derived_entities table so the projection doesn't have to be recomputed from scratch on every page load. Every domain page now reads through this shared projection instead of doing its own ad-hoc extraction:

• People (/people) — the directory of people the projection finds across messages, contacts-like records, and more.
• Merchants & Places (/places, sidebar: People & Places) — src/pages/Places.tsx surfaces the merchant and place kinds the same engine derives from your spending and location-bearing records.

Both pages share the same one-click promote flow: entities:promote takes a derived candidate and materializes it into an owned row — a contacts entry, a subscriptions entry, or a places entry (the places table, distinct from the derived_entities cache, is the permanent home for a promoted merchant/place). Nothing is promoted automatically; derived entities are suggestions until you act on them, exactly like the Timeline's "nothing is deleted, only tagged" philosophy above.

Related

• People — the cross-source people directory built on the cross-reference engine above.
• Data Rights & Acquisition — how to get the exports you drop here.
• Backup & Restore — the Universal Export Center.