Know what your company knows.

Most of what your company knows is already written down, in specifications, reports, contracts, minutes and AI conversations. Rhizograph turns it into a knowledge base, complete or focused on exactly the question you care about. Every entry leads to the exact line behind it, new insights show the evidence they rest on, and every change is on record.

Talk about your use case

Focus of this knowledge baseDecisions, figures and risks for the hall 2 retrofit.

Pick a leaf or the blossom to see where it came from.

  • A leaf is an entry, rooted in the exact lines it came from.
  • A blossom is a new insight, derived from several entries.
  • A fallen leaf was replaced. It stays in the history.

Or pick a line in the soil to see what grew from it.

How this knowledge base grew

Specification

A document, week 1

    Planning chat

    AI chat, week 1

      Leak survey report

      A document, week 4

        Hall 5 report

        Another team, week 5

          What your company gets

          Most of what your company knows is already written down. The trouble is finding it, trusting it and connecting it. Rhizograph takes care of all three.

          Everything. Or exactly what you need.

          Leave the focus open, and no topic is left out. Give a knowledge base a focus, and it holds exactly what serves it: sharper, leaner, and faster and cheaper to build. The same documents can feed both, every entry traced to its line.

          What should this knowledge base know?

          Your company knows more than any single document.

          Different people find different pieces: in support tickets, in sales notes, in a customer interview. Rhizograph brings the pieces together and proposes the insights that follow. Each one shows the entries it was derived from, down to their lines, and goes in only after review.

          Weeks later, someone asks.

          A customer, an auditor or the board wants to know what a decision was based on. Here is the same question, answered two ways, with the hall 2 example from the top of the page.

          Searching the shared drive

            In the knowledge base

            Version of the knowledge base

            Nothing slips through.

            When a document comes in, every one of its lines is accounted for. New entries arrive with their lines. What would be removed, what was left out and every proposed insight goes past a person, and every decision is recorded.

            The leak survey report came in

            New entries, each with its lines

              Would be removed

                Lines not used, shown for review

                  Record

                    Everyone signs in, with one of three roles: owner, editor or read-only. Several people can work on the same knowledge base.

                    The next project starts where the last one ended.

                    People move on, projects close, teams work in different places. The knowledge stays: a finished knowledge base can be the starting point for a new one, and knowledge bases from different teams can be combined, with every source kept and overlaps recognised.

                    Where teams use it

                    Four illustrations of the work it is meant for. They are not customer stories.

                    How it works in a team

                    1. Choose sources, and a focus if you like

                      Documents of any kind, from specifications to AI conversations. Leave the focus open, or say in one sentence what the knowledge base is for.

                    2. Review what matters

                      Entries arrive with their lines. People look at what would be removed, what was left out and every proposed insight.

                    3. Keep building on it

                      Add documents as they come, combine knowledge bases, start new projects from finished ones. Every version stays readable.

                    Dig deeper. It holds up.

                    Every benefit above rests on plain guarantees. This is what Rhizograph promises, stated as exactly as it can be.

                    Proof

                    • Every entry shows where it came from: the exact source lines, or, for a new insight, the entries it was derived from, down to their lines.

                    • Every source reference is checked against the actual text before it is saved. An entry can’t point to a line that doesn’t exist.

                    • Every line of every source is accounted for: it fed the knowledge base, or it is listed for review.

                    Control

                    • Nothing is removed and no new insight goes in without review. Where a team chooses, review runs automatically, and every decision is recorded either way.

                    • New insights are proposed with their evidence and accepted or rejected as a whole, never half-applied. Overlapping entries can be merged into one that keeps the evidence of all of them.

                    • Several people can work on one knowledge base, with sign-in and three roles: owner, editor and read-only.

                    History

                    • Nothing is silently overwritten. When something is overturned, the old entry leaves the current state with its reason on record.

                    • Every update creates a new version, and every earlier version stays readable.

                    • A complete record shows how every version came about: which sources went in, what was proposed, and who decided what, when.

                    Reach

                    • Any text can be a source: specifications, reports, contracts, minutes, transcripts, AI conversations.

                    • Every knowledge base has a focus, from every topic in its sources to one narrow question. The same documents can feed several knowledge bases, each with its own focus.

                    • Knowledge bases from different teams or projects can be combined with every source kept. Overlaps are recognised instead of duplicated, and when their focus differs, what doesn’t fit the target’s focus is proposed for removal.

                    • A finished knowledge base can be the starting point for a new one.

                    And what it doesn’t do

                    • It doesn’t claim to capture everything. What it keeps, it can prove.
                    • It works with text. Pictures and drawings inside documents don’t become entries.
                    • It doesn’t decide for your team. It shows what it found, and people have the last word where it counts.

                    Traceable, even where incomplete.

                    Rhizograph doesn’t claim to capture every sentence. It guarantees that everything it keeps, every new insight included, can be traced to its source.

                    Rhizograph is in development.

                    If your company runs on documents and the decisions made from them, describe your use case: which documents, which questions, and what it would be worth to have the answers with their evidence.

                    Talk about your use case

                    Opens an email to hello@rhizograph.com.

                    The knowledge base as a list