Ownership and lock-in

Mana’s durable output lives in your repository.

That is the answer to the lock-in concern: the knowledge base is made of Markdown files, YAML frontmatter, assets, and git commits in a repo you control.

What you keep

If you stop using Mana, the repository still contains the important artifacts:

• the Markdown pages;
• the raw or referenced source material;
• the links between pages;
• the frontmatter metadata;
• the commit history;
• the files needed to keep editing the knowledge base elsewhere.

Mana may provide the agent, browser UI, renderer, and managed publishing pipeline, but the archive is not trapped in Mana-only storage.

What ownership lets you do

Because the wiki is a normal git repository, you can:

• clone it;
• back it up;
• inspect diffs;
• revert commits;
• edit files by hand;
• open the Markdown in another editor;
• move the repo if your workflow changes.

If you only use Mana for a month, you still keep the repo and the work committed during that month.

The managed service is not the archive

Mana stores operational state so the product can run: authentication, selected repo, queued edits, deployment slots, and similar app data. That is not the same thing as owning your knowledge base.

Your long-term knowledge base is the repository. Mana’s job is to maintain, build, and publish it while leaving the durable record in files you own.