Stax Digital Garden

BPT-1008 - Decoupling Capture from Categorization

3 min read

Living Document Notice
Published 2026-09-21. The evolving architecture, revisions, and connected notes for this dispatch live in the Stax Digital Garden.

Decoupling Capture from Categorization

Decoupling Capture from Categorization: 1980s CRT data visualization of raw spool intake and asynchronous knowledge grid promotion

The Cognitive Friction of Premature Filing

Every note-taking system eventually confronts the capture bottleneck: you are in the middle of diagnosing a broken build, reading an upstream RFC, or pairing on an incident, and an idea or critical terminal command demands recording.

In conventional personal knowledge management workflows, recording that single observation requires paying an immediate tax:

  1. Launch or switch into a heavy graphical interface.
  2. Select a destination folder or namespace.
  3. Apply appropriate taxonomical tags or frontmatter properties.
  4. Establish bidirectional wikilinks to relevant topic hubs.

Faced with this overhead, engineers either postpone capture entirely—losing the context—or save links into browser tab groups and read-it-later queues that slowly decay into unreviewed information graveyards. The act of capturing requires low cognitive resistance; the act of filing requires deliberate reflection. Forcing both operations to occur simultaneously damages both.

Append-Only Raw Intake

The remedy is strictly separating capture into an append-only, zero-friction operation. Recording an observation should never require launching an editor, selecting a parent folder, or deciding on metadata schema.

A shell utility or background keystroke should accept raw text from standard input and immediately commit it to an intake log without further prompts:

# Append an unformatted observation directly to the daily intake spool
echo "nginx 1.25 renegotiation bug requires ssl_session_tickets off" | bpt-intake
 
# Direct command output capture during an active debugging session
gdb -batch -ex "bt full" -p 4182 | bpt-intake --context "incident-db01"

Under the hood, these entries are written with a microsecond timestamp into a single flat journal file. No indexing is performed, no schemas are validated, and the active terminal focus is never interrupted. Capture finishes in under ten milliseconds.

Scheduled Promotion vs. Automatic Expiration

Once thoughts are securely on physical disk, categorization shifts from an interruptive chore to an asynchronous batch task.

During an end-of-week review, a lightweight CLI sweeps the intake buffer:

  • High-value technical patterns are promoted into permanent concept notes with proper YAML frontmatter and backlinks.
  • Project-specific action items are dispatched to issue trackers or sprint scratchpads.
  • Context-less fragments and stale links that no longer matter are purged without guilt.

If an entry in the intake buffer is neither promoted nor referenced within fourteen days, the system does not nag the user with notifications. It quietly moves the entry into cold chronological archive logs. A personal knowledge base should retain high-signal decisions, not maintain a monument to every fleeting thought.

  • Directus Target: blog
  • Garden Source Reference: MOC - Bosun PKM Tools, MOC - Ingestion & Capture, MOC - The Plain-Text Longevity Standard, [BSN-1013 - Plain Text as a Durable Substrate](BSN-1013 - Plain Text as a Durable Substrate)

Graph View