Pillar 03 · Knowledge

Knowledge that outlives turnover.

When someone leaves, what they knew stays. When someone joins, what they need is already there. Documentation isn't a separate task. It's a byproduct of doing the work.

Wiki, read and edit

Lives in your knowledge repo. Every change goes through a merge request. Owner and Lead self-approve. Members go through review. Native edit, no third-party rendering.

Save-to-Knowledge flow

Drop any artifact (task, meeting note, chat thread, file) into the knowledge repo via MR. The wiki grows from work, not parallel to it.

Repo map graph

Force-directed visualisation of project ↔ repo ↔ template relationships. RBAC-filtered. What lives where, who owns what, all in one view.

How it survives turnover

The decision made five years ago is one search away.

  • Append-only history. Git-backed. No one can rewrite the past, including admins. The discussion that led to the decision lives next to the decision.
  • Role-filtered access. Developers see what developers need. Sales sees what sales needs. Finance sees what finance needs. One repo, many views.
  • Every page cites source. No hallucination. Hover any wiki section and see exactly which file, decision, or meeting note it came from.
  • Ask Sarthy on any page. Don't learn the wiki structure. Ask. Sarthy already knows the page, the linked decisions, the citation graph.

See it on your knowledge base

Bring your wiki. We'll show you traceability.

Twenty minutes. We install Sarthy on your server with a sample of your existing knowledge. You see role-filtered, traced, queryable knowledge in real time.

Book a demo