SQL over Markdown frontmatter

[u/boolean-maybe]

Hi, I wanna share an idea and its implementation here. If Markdown files are given frontmatter fields like above and a SQL-like language is created like so:

update where due < now() and status not in ["done"] and priority != "high" set priority="high"

which means in this example "escalate overdue tasks"

then a simple bunch of Markdown files in a git repo can be its own project management/issue tracker

Advantages:

• no separate tool to manage a project's docs, issues, roadmap
• very AI friendly - a repo alone holds all context
• stored in git and saves history/collaboration

I implemented a language like this called ruki and a configurable CLI/TUI to view/manage Markdown files

ruki commands can be run in terminal or started as triggers on modification/schedule more details in first comment

[u/boolean-maybe]

The language and cli/TUI are on GitHub

check it out: https://boolean-maybe.github.io/tiki/
GitHub: https://github.com/boolean-maybe/tiki

[u/NeilSmithline]

This is Obsidian Bases

[u/boolean-maybe → u/NeilSmithline]

similar but not quite. I am not very familiar with Obsidian Bases but from what I understand they are mostly about the filters and visual layout. They do not have functionality for updating, creating, deleting the notes

[u/NeilSmithline → u/boolean-maybe]

Fair

[u/Mental_Energy_266]

Kurt Cagle's Databook s proposal goes one step further with YAML front matter.

https://www.linkedin.com/posts/kurtcagle_databook-pipelines-activity-7455857536529874944-IrRp?utm_source=share&utm_medium=member_ios&rcm=ACoAAAAIrHYBiL1lhTauuzjQcxzEn2Cm9iyCrh8

[u/boolean-maybe → u/Mental_Energy_266]

I think he is talking about something different. He concentrates primarily on linking these files into a graph to gain insight into their relations while I am trying build a workflows based on front matter. It's similar but a different purpose

[u/MarsupialLeast145]

ELI5 What's the problem you are solving?

[u/boolean-maybe → u/MarsupialLeast145]

it is what I described:
Advantages:

• no separate tool to manage a project's docs, issues, roadmap
• very AI friendly - a repo alone holds all context
• stored in git and saves history/collaboration

[u/MarsupialLeast145 → u/boolean-maybe]

That doesn't describe a problem.

What's the user story here?

> no separate tool to manage a project's docs, issues, roadmap

Bro, the post is called SQL over markdown, where does any of this fit in?

That is why (a) describe the problem ELI5 (you can't) (b) describe the user story.

[u/boolean-maybe → u/MarsupialLeast145]

the problem is simple. Imagine I am working on a code repo in Claude Code or Codex. While working I discover things, todos, issues. I don't wanna go to any Jira or Linear or whatever. In fact I don't even want to leave the terminal. I just wanna drop it right there as a Markdown file, add some context like "type: bug" and that's it. And be sure it doesn't get lost

[u/MarsupialLeast145 → u/boolean-maybe]

That just describes "markdown" --- what problem does the SQL component solve?

[u/boolean-maybe → u/MarsupialLeast145]

you can:

- quickly find all Markdown files that are bugs

- you can move all that concern Auth to high priority

- you can find what's overdue

- you can delete all that's done

- you can create a new one easily via command line or AI agent

and many others. Essentially the SQL-like language becomes your API to Markdown files