index

Pour Documentation

For LLMs: Start here. Navigate to a directory index for scoped exploration, or jump directly to a core document below.

For Humans: See above… but use the graph to guide your exploration!

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.

Directory Indexes (00 index/)

Directory Index Contents
02 references/ REFERENCES Library API references and external docs
04 architecture/ ARCHITECTURE Design spec, ADRs
05 notes/ NOTES Active development notes
07 stories/ STORIES Vision and manifesto
08 specs/ SPECS Feature and component specifications

Core Documents

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.

Quick Reference

Common Commands

cargo build              # compile
cargo run                # run dashboard
cargo run -- coffee      # run a specific module
cargo test               # run all tests
cargo clippy             # lint
cargo fmt                # format

Key File Locations

Area File
Entry point src/main.rs
Config schema ~/.config/pour/config.toml
Cache ~/.cache/pour/state.json

Architecture Overview

Pour writes to Obsidian via a hybrid transport layer:

  1. API — HTTP via reqwest to Obsidian Local REST API (http://127.0.0.1:27124)
  2. File System — Direct std::fs fallback if API unavailable

Dynamic Data Fetching (3-tier fallback)

API query -> disk scan -> ~/.cache/pour/state.json cache -> freetext input

Last Updated: 2026-03-31
Documentation Version: v0.1.0