In KiwiFS, every page is a plain markdown file with optional YAML frontmatter. There is no database, no proprietary format, no schema migration. The filesystem is the database.Documentation Index
Fetch the complete documentation index at: https://docs.kiwifs.com/llms.txt
Use this file to discover all available pages before exploring further.
Why files?
- Universal — every language, tool, and agent can read and write files.
- Durable — files outlast databases, SaaS tools, and proprietary formats.
- Diffable — git gives you full history, blame, and merge for free.
- Inspectable —
cat,grep,find,treework out of the box. - Portable — copy the directory to move your knowledge anywhere.
Frontmatter as structured data
Each file can include YAML frontmatter for structured metadata:The .kiwi/ directory
KiwiFS stores its configuration and internal data in a .kiwi/ directory at the root of your knowledge base:
knowledge
.kiwi
config.toml
comments
playbook.md
SCHEMA.md
schemas
templates
index.md
pages
getting-started.md
episodes
Git versioning
Whenversioning = "git" (the default), every write — via REST, MCP, NFS, or filesystem — creates a git commit. The commit author is set from the X-Actor header or MCP actor parameter.
- Full history for every page
- Blame to trace which agent wrote which line
- Diff between any two versions
- Rollback to any previous state
Implications
Because files are the source of truth:- Backup is
git pushorrsync. - Import adds files; export reads them.
- Migration is copying a directory.
- Multiple tools can operate on the same knowledge base (KiwiFS, git, editors, scripts).
- No vendor lock-in — if you stop using KiwiFS, your markdown files remain.