Unfiled

Unfiled is a notes app in development. It separates quick capture from organization: users can save the original text, then review, change, or undo how it is organized.

I’m designing and building the web and mobile applications, shared data model, background processing, and encryption migration.

Original captures are stored separately from organized notes. Typed mutations and inverse operations record what changed and how to undo it. Receipts, revisions, and source history are part of the data model.

Organization uses deterministic rules before a model call. Ambiguous results go to review, generated text stays distinct, and stale AI work cannot overwrite a newer manual edit. Search, routing, correction, and undo use the same capture history.

Milestones A and B and the credential-free third gate of Milestone C are complete. The repository includes a mobile-first application shell, a web surface, a background worker, the Supabase schema, and shared contracts for domain logic, synchronization, search, and AI routing.

Private and AI-assisted content are separate data classes. Private captures are blocked at the model boundary rather than sent through a fallback application key.

Current work includes managed KMS root-key custody, envelope encryption, typed encrypted records, compare-and-swap operations, and resumable backfills with verification. Manual private captures can use the encrypted path.

The application is not fully encrypted at rest, and no mode is end-to-end encrypted. New AI-assisted captures are blocked until the organizer has an atomic encrypted writer. The production repository layer has not fully switched to the new adapters, and plaintext storage and search contracts still need to be removed.

The next work completes the organizer write path, migration and cutover checks, and account-specific infrastructure and Apple delivery validation. Later milestones cover deeper routing, review, search, interactive notes, operations, and public-launch readiness.