Notes need friction in the right place

Capture should be almost frictionless. Review should not be.

A note that takes fifteen seconds to open loses ideas. A capture flow that demands tags, folders, links, and a perfect title asks the writer to predict the future.

The minimum useful record is small:

timestamp
text
optional source
optional context

Review is where the note becomes trash, reference, task, or writing material. That decision is easier after the idea has cooled. A review queue admits that capture is messy without making the mess permanent.

Ask:

• is this still true?
• where did it come from?
• is there an action?
• would I search for it later?
• does it connect to current work?
• is it a sentence worth expanding?

Retrieval needs boring handles. Titles, project names, subsystem names, failure modes, tools, related specs, and likely future search terms help more than a perfect folder tree. Embeddings can find neighborhoods; they do not replace useful titles.

Tasks should leave the note system. A captured reminder can become an issue, checklist, calendar item, or be deleted. Otherwise notes become a guilt-based task manager.

Writing notes need a smaller next move: attach the sentence to a draft, add the example, split the idea, keep it, or delete it because it only sounded good for ten minutes.

The right friction depends on the failure. Lost ideas mean capture is too hard. Unused notes mean review is too soft. Unfindable notes need better handles. Hidden tasks need a clearer boundary.

Make capture fast, review unavoidable, retrieval concrete, and deletion cheap.