Git backing

Mana treats your knowledge base as a real git repository, not as data trapped inside an app database.

Your raw sources, wiki pages, syntheses, and templates live as plain files. When the agent improves the wiki, it edits those files and records the result as a git commit so every change has a diff, a message, and a place in history.

What lives in git

A Mana wiki is organized around files you can open with any Markdown editor:

• Raw sources: papers, transcripts, articles, voice notes, and other inputs you want the agent to read.
• Wiki pages: durable notes the agent links, cites, and refines over time.
• Synthesis pages: answers and summaries that become reusable pages instead of disappearing into chat history.
• Templates and playbooks: repeatable checklists or workflows that improve after each run.

Because these are files, you can clone them, search them, back them up, or edit them outside Mana.

How agent edits become commits

When Mana works on your wiki, it follows the same shape as a careful human collaborator:

1. Read the relevant sources and existing pages.
2. Make focused Markdown edits.
3. Add citations, links, and cross-references where they help.
4. Commit the finished change to git.

The commit is the review boundary. You can inspect what changed, keep it, revert it, or build on top of it.

Why this matters

Git backing gives the wiki durable memory and user control:

• Reviewability: every agent action is visible as a diff.
• Portability: your knowledge is plain Markdown, not a proprietary export.
• History: you can see when an idea changed and why.
• Reversibility: unwanted edits can be reverted with normal git tools.
• Offline access: cloned files remain useful even without Mana running.

Mana should make your knowledge base easier to maintain without making it harder to leave.