the_pour_manifesto

The Pour Manifesto: Why We Build

The Problem: The Tragedy of the Uncaptured Thought

Obsidian is a beautiful, sprawling garden for our minds. It is the perfect place to wander, connect ideas, and synthesize knowledge.

But opening the gates takes too long.

When you are deep in a flow state, dialing in the perfect espresso shot, or standing in the crowd at a festival, your brain operates in seconds, not minutes. If the process of logging a thought takes longer than the thought itself, the thought dies.

Opening a GUI, waiting for the Electron client to render, finding the right folder, opening the daily note, and formatting the YAML frontmatter—that isn't just friction. It is a barrier to entry. It makes the act of remembering feel like administrative work. And because of that friction, we stop writing. We lose the nuances of our days.

The Vision: Writing More About What Matters

We don't log data just to have data.

We log coffee (pour coffee) because we are chasing the perfect extraction, and we want to remember how that Ethiopian light roast tasted at a 1:15 ratio.

We log music (pour music) because the energy of a live set and the people we shared it with are memories worth keeping.

We log ourselves (pour me) because our passing thoughts, midnight epiphanies, and daily anxieties deserve a place to rest outside our own heads.

We want to write more about the things that bring us joy. To do that, the tool must get out of the way entirely.

The Ethos of Pour

Pour is not a workspace. It is a reflex.

It is a terminal-native capture tool designed to be as fluid and instantaneous as the command itself.

  • Velocity is a Feature: The time between having a thought and executing the capture must be near zero. pour lives where we already live: the terminal. No context switching, no mouse clicks.
  • Capture First, Synthesize Later: pour separates the act of recording from the act of organizing. You pour the raw data into the vault flawlessly formatted. You can open Obsidian on Sunday to make sense of it all.
  • Plaintext is Forever: We reject proprietary databases. A memory should not be locked behind a subscription or a specific app version. Everything pour generates is strict, portable Markdown and YAML. It belongs to you.
  • Fluidity: The name is the instruction. You don't "execute a script" or "insert a database row." You pour a V60. You pour your thoughts. It is a continuous, natural motion.

The User Story

As a developer and enthusiast, I want a frictionless, instant-booting terminal interface to log highly structured data (like coffee recipes and concert memories) directly into my Obsidian vault, so that I can capture the details of the things I love without breaking my workflow or wrestling with a GUI.