A growing number of founders and teams run their entire company on folders of markdown files, versioned in git. One folder for product specs. One for marketing. One for legal. One for feedback. Every document in one place, readable by any tool, owned by you forever.
marketing/positioning/competitor-brief.md
The brief is one file in a workspace of marketing docs.
They added a review step in their June release, but it only covers wiki pages, not shared docs.
A teammate's comment, anchored to the claim it questions.
Your company's knowledge already lives in documents. Strategy decks, product specs, marketing briefs, legal agreements, meeting notes, feedback logs. Most of it is scattered across Notion, Google Docs, Confluence, and Slack threads. Finding the right document means remembering which tool it is in.
The Company OS pattern replaces all of that with plain markdown files in folders. One folder per function. Git tracks every change. You stop paying for seats in six different tools and start working from one place you actually control.
The idea is not new. But agents made it urgent. When an agent can read and write your company's documents, the format matters. Markdown in a git repo is the one format every agent already understands.
Every meeting, scorecard, and goal is a markdown file with YAML front matter. The whole business runs through Claude Code.
sethlevine.com"How much cognitive overhead disappears when you stop context-switching between eight different applications."
blog.fortrabbit.comMigrated their whole company from Notion to markdown. "Owning the files matters more than we expected."
news.aakashg.comBuilt a Company OS where a team of 9 ships what used to take 90. Three layers: ontology, skill files, delivery.
stephango.comThe philosophical case from the Obsidian CEO. "The files you create are more important than the tools you use to create them."
gardenresearch.euA guide to building a markdown-based operating layer for a 20-person company. "The wiki is not a wiki. It is a substrate."
Every Company OS today requires a terminal. Brad Feld's version runs through Claude Code. Garden Research's version runs through git. If you are comfortable with a command line, the pattern works. If anyone on your team is not, they are locked out of the company's own documents.
The other problem is trust. When agents can write across every folder in your company, marketing and legal and product and planning, you need to know what changed. A git diff is not a review. Most people skip it, and the documents drift without anyone noticing.
Open each folder as a Stet workspace. Product specs in one workspace. Marketing docs in another. Legal in a third. You see all of them in a sidebar, and every change in every workspace flows through the same review step.
Your team does not need a terminal. They open a folder and start writing. When an agent edits a document, the change shows up as a proposal they can read, accept, or reject. When they want to direct an agent, they leave an AI note in the document itself.
Because every workspace keeps its own document history, you can see how any file got to its current state. Who changed what, when, and whether a human approved it. Across the whole company, not just one folder.
A typical setup has a workspace for each function. You choose the review mode per folder: manual for documents that need sign-off, auto for documents where changes can land but stay marked.
Specs, roadmap, backlog, research notes. The source of truth for what you are building and why.
Positioning, copy, experiments, competitive intel. One place to find every brief.
Terms, privacy policy, agreements. Documents where every word matters and every change needs a review.
Meeting notes, hiring docs, processes, feedback logs. The working memory of the company.
The foundational essay. He has carried his text files since 1990.
joshtronic.comA developer migrates everything to ~/Notes. Tired of wondering which EULA lets his data train a model.
extency.com"Boring is exactly what business memory needs." Why markdown folders beat every knowledge-base product.
getstet.appOur own short read on why the format wins and what Stet adds on top of it.
Start with one folder. Pick the function you touch most, marketing, product, whatever has the most documents you keep reaching for. Open it in Stet. Add more workspaces as you go.