Compounding

Mana is designed so useful work compounds.

A chat answer helps once. A maintained page can help again next week, link to related pages, receive backlinks, and become better after each follow-up.

Each run leaves something behind

When you ask Mana to work on your knowledge base, the intended output is not only a message in a chat thread. The agent creates or updates Markdown pages and commits the change to git.

That means the result becomes part of the repo:

• a source page you can revisit;
• a synthesis page that answers a recurring question;
• a checklist or template you can reuse;
• a correction that improves an existing page;
• links that connect the new work to old work.

Links create memory

The compounding effect comes from links and backlinks.

A new page should point to the pages it depends on. Existing related pages can point back to the new page. Over time, those connections turn individual edits into a navigable knowledge graph.

This is different from a chat archive. In a chat archive, the next useful answer is often buried in a past conversation. In Mana, the answer should become a page that future runs can read, update, and connect.

Repetition improves the system

Repeated work should improve the underlying structure:

• travel planning creates reusable checklists;
• research creates source overviews and synthesis pages;
• repeated decisions produce playbooks;
• corrections make future answers more accurate;
• backlinks make related material easier to discover.

The repo becomes more useful because each edit changes the artifact future edits build on.

Git makes the compounding visible

Because Mana commits changes, compounding is visible in history. You can see when a page was introduced, how it changed, which files were edited together, and which ideas accumulated over time.

The point is simple: Mana should make your knowledge base better with each use, not just produce another disposable answer.