Long-running repositories collect Markdown files that disagree about what is current. Once Codex,...
Long-running repositories collect Markdown files that disagree about what is current. Once Codex, Claude, and humans work across many sessions, an old architecture note can quietly become "the plan" again.
Markdown Gatekeeper keeps one current revision per topic. Competing docs stay proposals; superseded sources remain recoverable.
Local-first. Plain Markdown and Git. No account or cloud service.
npm install -g github:nanlogic/markdown-gatekeeper
mdg setup codex
mdg init .
Read the original article and join the discussion on Dev.to
Read on Dev.to
How we built a 483 KB zero-WebKit macOS Universal Binary and a single-file Ubuntu HUD with...
These are two separate runs of my agent. The two questions and two answers are copied word for word....
Main instruction files that tell the agent who it is score lower than the rest, at every file...
Overview Hey everyone 👋 For a long time my OpenCode workflow was one agent, one giant...
Consider a web API that needs to call a second API, and the second API needs to know whose data it i...
What building MOSAIC taught me about trustworthy AI experiments, replay, and knowing what your...