A collaborative editor for humans. Markdown in Git for AI agents. A specification engine that measures what your documents fail to say.
Git repositories are the best-designed knowledge management system in existence. Versioning, ownership, review workflows, structured format, full history. The reason engineers don't spend hours searching for information is that Git imposed a discipline on code that no other knowledge tool has imposed on anything else.
Meanwhile, organizational knowledge — policies, processes, runbooks, institutional wisdom — lives across a dozen tools in proprietary formats. That was tolerable when only humans needed to read it. Humans can infer, navigate ambiguity, fill gaps with context. AI agents cannot.
VanaMD brings Git's discipline to the rest of the organization's knowledge. A collaborative editor non-technical people can use. Markdown in Git underneath so it's natively readable by AI. A specification engine that measures how much of each document's meaning must be inferred. Built for two audiences as first-class consumers of the same knowledge base.
Every organizational knowledge system that works at scale has these four properties. Most have none.
Every edit is a Git commit. Full history, blame, diff. You know who changed what, when, and why. So does the agent.
One source of truth. Clear ownership. Clear canonical status. When a human or an agent retrieves an answer, there is no ambiguity about whether it's current.
Every document is clean Markdown. An auto-generated llms.txt tells agents what's available. Trust directives tell them how much to rely on what they're reading. The format is the interface.
A substrate only AI can read is a database. A substrate only humans can read is a wiki. VanaMD gives humans a collaborative editor — and serves agents the same content through protocols designed for them.
Everything ships together. There is no integration to configure, no format to convert, no pipeline to maintain.
Non-technical users write normally. Real-time collaboration, comments, version history. Markdown in Git underneath — invisible discipline for people creating knowledge.
True version control — branching, merging, blame, diff — on all organizational knowledge. Any tool that reads Git reads this. git clone https://token@your-instance/git/workspace and you have everything.
AI agents connect via the Model Context Protocol. 13 tools across read, write, and admin tiers. Workspace → collection → zone permission model. Write tools disabled by default — you control what agents can do.
Not all documents are the same. Decision records show status, alternatives, consequences. Runbooks show steps with verification. Research shows sources with trust ratings. Each shape renders how documents are actually used.
Measures how much of each document's meaning must be inferred. Surfaces ambiguous terms, underspecified procedures, contradictions, and missing context. Most organizational knowledge is 20–30% specified — AI agents and new hires cannot fill the rest.
Staleness detection, gap analysis, contradiction flagging. Surfaces what's missing, not just what exists — so humans and agents can trust what they find.
Attestation tracking, review workflows, direction-aware classification, audit trails backed by Git history. Built-in compliance lifecycle for regulated environments.
Inbound directives tell agents how much to trust each document. Outbound evaluation scores agent actions before they modify content. Agent policy files versioned in Git — trust constraints travel with content, auditable via git log.
Every document in the knowledge base is discoverable by AI agents without custom integration. Machine-readable index at /llms.txt — updated automatically on every change.
Most knowledge management tools tell you what documents exist. VanaMD tells you what they fail to say.
The specification engine analyzes documents and measures their specification depth — how completely they state what they mean. The engine reaches 90%+ recall on planted specification gaps across a synthetic eval harness, validated against 3 iterative improvement cycles.
An ADR is not a runbook. A research brief is not a meeting note. VanaMD renders each document type with purpose-built UI — the shape surfaces what matters for that document's purpose.
Shows status, alternatives considered, consequences, and decision history. Every option that was evaluated — not just the one chosen.
Research and analysis with source trust ratings, findings summary, and confidence indicators. Built for documents that require interpretation.
Enforcement level, review schedule, attestation status, and compliance lifecycle. Surfaces what requires action — not just what the policy says.
Time-aware rendering for evolving documents — change history, validity windows, expiry indicators. Knowledge that has a date.
Step cards with state tracking. Each step shows completion status, prerequisites, and verification criteria — for runbooks and procedures.
Sortable, filterable table view for reference documents. Unique entry enforcement, search, and structured field display.
AI agents connect to VanaMD via the Model Context Protocol. 13 tools across three permission tiers — workspace, collection, and zone.
Write tools are disabled by default. You control exactly what agents can do. Permission grants are scoped, auditable, and revocable. Agent actions leave an audit trail in Git history.
17 security hardening measures across 5 audits. Not "we'll harden it later" — hardened in the open, documented in Git.
All traffic over TLS 1.2+. HSTS preload header. Caddy handles certificate rotation automatically.
Per-API-key rate limiting at 600 req/min. Standard headers exposed: X-RateLimit-Limit, X-RateLimit-Remaining, Retry-After.
Strict origin allowlist. No wildcard origins. Preflight handling with correct methods and headers.
XSS, SQL injection, and oversized body protection. All user input validated at API boundaries. SetEscapeHTML enforced on all JSON responses.
Internal error messages never leak to API responses. Stack traces sanitized. All error paths reviewed in SEC-9.
Attribute-based access control. Document classification levels. Non-admin cannot access restricted documents without explicit grants.
git log.git clone https://API_KEY@your-instance/git/workspace clones the entire knowledge base as a standard Git repository. Every document is a Markdown file. Every edit is a commit. Any tool that reads Git — CI systems, AI agents, developer tooling — reads the knowledge base directly. No export, no conversion, no integration required.We're building VanaMD in the open. Get occasional updates on progress, architecture decisions, and what we're learning.
Request early access