BACK TO THE WORKSHOP

Lucid.

For the things you saved somewhere.

IntelligenceMemoryHuman experience
Status
In development
My work
Software architecture, data modelling & interface design

A thought in a note. A useful link in a tab. A plan in a message. Lucid is my exploration of personal software that brings those pieces into context, while keeping their sources and your control in view.

The pieces already exist

The difficulty is often remembering where to look. Lucid starts with the context scattered across everyday tools: what you read, save, plan, and return to. The aim is to make those connections useful without turning personal organisation into another full-time task.

Starting with the browser

One working piece is LucidTab, a browser extension that captures visits and readable page content. A visit can point to a reusable document record, so the same article does not need to be captured again every time another part of the system needs it.

A memory with a source

I’m building a shared data model that separates observations from the conclusions drawn from them. Visiting a page is an observation; deciding what that visit means is an interpretation. Keeping them separate makes room for corrections, changing context, and a useful answer to “where did that come from?”

Where it stands

The capture tools and shared data contracts are in development. The wider connected experience is the direction of the project, rather than a finished product. The design question I keep returning to is how much a system should remember—and how easily you should be able to change its mind.

What if the things you saved could find each other?
ONE WORKING PIECE

A useful page.
A little more context.

  1. 01 · A VISIT

    Something you read.

    A browser visit records where a piece of information came from.

  2. 02 · A DOCUMENT

    Something worth keeping.

    Readable content becomes a reusable document, with its source attached.

  3. 03 · A CONNECTION

    Something you can find again.

    The visit links to the document. Other parts of Lucid can reuse that record.

A schematic of LucidTab’s capture flow. Observations and interpretations remain separate in the shared data model.