Planned, in progress, and shipped

How something moves from planned to shipped

A provider adapter is not finished when it parses one export on one machine. It is finished when there are sanitized fixtures covering the formats it claims to support, when it passes the shared contract suite that every adapter runs against, when the privacy review confirms nothing beyond normalized statistics leaves the browser, and when unknown shapes produce a warning instead of a plausible-looking number.

That gate is why the planned list is longer than the supported list and why it moves slowly. Enabling an importer that half-works is worse than leaving it disabled: the resulting charts are wrong in ways nobody can see, and the person using them has no reason to suspect it.

Why planned providers have pages at all

Every planned adapter has a page describing its status. Those pages accept no files, enable no importer, and are excluded from search indexing, because a page about software that does not exist yet should not compete in search results with documentation for software that does.

They exist for one reason: so that someone searching for whether their tool is supported gets a clear no with a date-free explanation, rather than an ambiguous silence that reads like a yes. If a source matters to your workflow, saying so through the contact page is the strongest signal available for ordering the queue.

What the next items actually require

The near-term list is short because each item has a real prerequisite rather than a schedule.

• Automated email verification. Account recovery is manual today, which is workable at the current scale and will not stay workable. This is the item that most limits everything else.
• Fixture coverage for the remaining supported providers, so the contract suite proves what the documentation claims.
• Richer visual analytics and project suggestions, which depend on having enough correctly-labelled metrics to be worth visualising.
• More recap formats, once the underlying aggregates are stable across every provider rather than only the well-instrumented ones.

What is not planned, and why

Background folder watching and silent collection are permanently out of scope. An analytics product that reads your machine without asking is a surveillance product with a dashboard attached, and no amount of local-first architecture changes that. Imports begin with an explicit selection, every time.

Full raw-chat cloud backup is also out. Storing complete transcripts would make every other privacy commitment on this site conditional on our infrastructure never being breached. Native mobile applications and a billing system are not planned either: the installable web app covers the former, and there is nothing to bill for.