doomemacs-config

A house to write, think, and return to. Agents open the same Org files and leave traces of their work beside the human’s plans. The editor is not replaced by an agent: it becomes the meeting point between their work.

An agent writing for me is not the same as making writing comfortable

Connecting notes, reading books, writing Korean, entering equations: even when an agent can produce a document, the comfort of following a thought with your own hands is a separate concern. A human editor remains at the centre of this configuration.

Built on Doom Emacs, it brings Org-mode and Denote together with Korean input, Evil keybindings, search, citations, and terminals. GUI and TTY are both daily working surfaces, without pretending that remote clipboard transport or image support is identical everywhere. This is a public example of interfaces repaired through long use, not a turnkey distribution to copy unchanged.

For GLG, this house is the command centre used all day long. A message for the stewards of several projects is first written here as one journal heading, then copied and pasted to each of them. A key could send that heading directly, but copy and paste is enough for now, so no such key exists. More automation is not the goal in itself. What this house protects is that what is written by hand is read under the same rules by humans and agents alike.

Human and agent work on one timeline

lisp/workflow-shared.el is the data contract shared by the user’s Emacs, the agent RPC daemon, and the export daemons. Tags, TODO states, agenda files, and attachment paths must not work correctly only in the GUI. Themes and keybindings may differ; the rules for reading and writing the same records must agree.

The working surfaces are separated: user is the GUI editor, pi is full Doom shared by multiple TTY clients, and server is the agent RPC daemon. Here, pi is an Emacs socket name, not a Pi agent identity. Separate daemons isolate execution; they do not automatically coordinate concurrent edits to the same Org file.

From files to a garden, and back to thought

Org · Denote → ox-hugo Markdown export → Quartz digital garden
      ↑                                         ↓
 Next human and agent work ← retrieval followed by source reading

This house also owns the note-export pipeline. Emacs daemons convert Org to Markdown; link, figure, and content checks support publication to the digital garden. ox-hugo owns conversion; Quartz in the separate garden repository owns publication. Published tags pass through the vocabulary defined by meta notes, rather than an arbitrary allowlist.

geworfen brings the same agenda into the browser as a public timeline. The website and the retrieval engine live in their own repositories.

What agents cannot read cannot be revisited together

Beside Org and Denote, EKG by Andrew Hyatt has come back. It was tried from 2023 before Denote became the centre of writing. This time it is not a garden migration but a separate workbench for questions. Tags stay as separate clues such as 과학 (science) and 무엇 (what), and notes carrying both are found by intersection. GLG says there is still no answer to how knowledge can be built up in layers. EKG is one Emacs-like interpretation of that question; this house keeps it as today’s address, not a finished system.

If agents cannot read what a person wrote, the two cannot revisit that record together. EKG is an SQLite database, so agents cannot open it the way they open an Org file. The agent RPC daemon therefore offers three read doors: a listing by combined tags, one note’s raw text, and how many notes carry each tag. They read through EKG’s own library rather than a private parser, and no door edits notes or changes tags. The first reader is a care bot that is always on. The aim was for it to read these notes as it reads the journal and to talk in the context of life and learning. In the reply GLG shared, the bot reported querying two tags together and answering from the notes’ text. These doors are not a fence around the whole daemon, and they do not mean agents are always reading the notes. The read contract and its boundaries are in the README and #12.

What the neighbours own

• agent-config keeps shared skills and working principles across harnesses. This house provides the Emacs functions those skills can call.
• Entwurf opens independent sibling sessions and delivers messages by garden id. The ghostel/tmux surface here can hold those sessions without taking ownership of their authentication, transcripts, or delivery.
• andenken retrieves earlier decisions from conversations and public garden writing. This house owns the Org sources and garden export; a retrieval index does not become the owner of memory.

Inside Emacs, gptel-agent, pilish (a Pi RPC client), and agent-shell (an ACP client) offer additional working surfaces. Not every sibling has to move inside an Emacs buffer. Attaching to tmux through ghostel lets the human return to terminal sessions running independently of Emacs.

Boundaries that make a long-lived house maintainable

config.el stays a loader; concerns live in separate lisp/ modules. Pure logic is tested without Doom under emacs -Q where possible. Keybindings layer individual keys onto Doom’s existing prefix maps instead of replacing entire groups. When upstream changes, this configuration adapts first. The rule is executable: test-keybinding-lint.el rejects named-prefix forms that would replace an existing map.

Current Neomacs validation and workarounds belong to neomacs-config. This repository retains a minimal comparison profile and reproducible probes that run under both Neomacs and GNU Emacs.

This page is the front door. The README owns installation, commands, and current implementation; the steward’s note keeps dated judgments and boundaries in Korean. Rather than copying operational logs onto the homepage, each surface links to the place where its record lives.