consume, curate, create
a lot of systems are good at capture and weak at digestion. this one starts earlier. everything taken in is part of a diet, and the real decision sits in the middle: what gets kept, what gets omitted, and what earns a new form.
the hinge is curation
the framework is simple on purpose:
- consume what enters the field through reading, watching, listening, bookmarking, scrolling, or ambient repetition.
- curate what relation to keep with it: connect it, hold it provisionally, cluster it, extract from it, or let it go.
- create when the material has enough pressure to become a note, argument, cluster, thread, playlist, image set, or other artifact.
where it departs from productivity systems
this sits near para and zettelkasten, but it is doing different work. para sorts material by operational context. zettelkasten turns reading into linked thought. consume, curate, create asks what should happen after exposure and before accumulation becomes identity.
that is why the diet metaphor matters. the question is not just what was captured. the question is what entered the system often enough to shape taste, attention, or future thought.
three valid endings
- internal curation: the intake remains useful without becoming public.
- dismissal or omission: the system records that something was considered and not kept.
- creation: the intake crosses a threshold and becomes something new.
the point is not to turn every input into output. the point is to stop pretending passive accumulation is neutral.
why it matters here
this framework now anchors the vault itself: twitter scraping, apple-notes mirroring, visual intake, and daily periodicals all flow through the same question. what came in today, what mattered, what deserves a durable home, and what only deserved to be noticed once?