Relay
A Markdown-and-Git coordination layer that sits between captured information, AI agents and the systems that actually run the work.
CREATED SEP 21, 2026 · UPDATED SEP 22, 2026
PROBLEM
Actions arrive from everywhere: recordings, meeting notes, chat with an agent, a thought on a walk. The systems that run the work are good at running it and bad at intake, so the gap between hearing a thing and it existing somewhere reliable is where it gets lost.
HYPOTHESIS
A Markdown file in a Git repository is enough of a queue. If capture, triage and routing are agent skills against two files, any agent can feed it, history is the commit log, and nothing needs a database or a server.
ARCHITECTURE
Two Markdown files are the whole state: an inbox and a sorted board, with a validator that runs after every change. Three agent skills do the work: capture from source material, route an item to its execution system with the real external identifier, and report the queue read-only. Work and personal never mix; anything ambiguous stays in Relay rather than being guessed into the wrong system. A small Kanban UI reads the same files.