Provenance is the point
Why a post should know which commit produced it
tobi · · 1 min read
The problem with blogging about code
By the time you write the post, the context is gone. You remember the conclusion but not the diff, and the reader gets prose with no way to check it.
What Rill does instead
The MCP server reads the git state of the project you are working in and attaches the commit, branch and touched files to the post. Not typed in afterwards — captured at the moment the note was written.
That gives search a second axis. Not only "what is this post about" but "what code did it come from".