Knowledge Bank

The best engineers on your team carry an enormous amount of context that isn’t written down anywhere: which services are business-critical, which alerts are usually noise, what broke last time and why. Most AI tools ask you to hand that over before they can help — write the runbooks, document the exceptions, keep it all current. That gets it backwards. The agent should do the learning. Traversal builds its own understanding of your environment from the systems you’ve already connected, and Knowledge Bank is where you can see it. Browse what Traversal figured out on its own, correct anything that looks wrong, and add the last mile that only your team can know.

​

Traversal learns your systems on its own

You do not have to write anything for Traversal to work. From the moment your integrations are connected, Traversal reads them and writes itself the Traversal Wiki, assembled from the same sources it uses during an investigation:

• Code — your repositories in GitHub or GitLab, including how services are wired together and what they actually log
• Metrics — Prometheus, Mimir, Datadog, Dynatrace, AppDynamics, VictoriaMetrics
• Logs and traces — OpenSearch, Elasticsearch, Splunk, Loki, Honeycomb
• Alerts and incidents — Alertmanager, Datadog monitors, incident.io
• Documentation and tickets — Confluence, Notion, Jira, ServiceNow

The Wiki falls out of building Traversal’s Production World Model. As Traversal takes in those sources it works out how everything relates — this service to the metrics that describe it, the code that implements it, the alerts that fire on it, the traces that run through it, the tickets filed against it. Those relationships are what make the Wiki possible: each entry is written from what the model already understands about how your environment fits together, not from any one system read in isolation. And because your systems don’t hold still, Traversal keeps regenerating it as they change, so its picture of production doesn’t quietly go stale.

​

What’s in Knowledge Bank

Everything your team authors is live immediately. Nothing needs approval, and there’s no build step between adding a runbook and Traversal being able to use it. Anyone on your team can use it. Every member of your organization can browse Knowledge Bank, add skills and documentation, edit what your team wrote, comment on the Traversal Wiki, and review memories — not only admins. Skills and uploaded docs are shared organization-wide: whatever one person adds, everyone can find, use, and edit. The two sections Traversal writes for itself — the Wiki and Memories — are marked with an Auto-created chip, so it’s never ambiguous which knowledge came from your team.

​

The Traversal Wiki: what it figured out on its own

Knowledge Bank opens on the Traversal Wiki: Traversal’s own working documentation of your environment, organized by service and written entirely from the evidence in your connected systems. A page might cover what a service does and who owns it, how it’s put together, what it talks to, what it logs, or how it has broken before — the shape keeps evolving as Traversal gets better at describing your stack. That makes it useful well beyond the agent. It’s clear, current documentation your whole team can read: someone joining the team can come up to speed on an unfamiliar service without hunting down the one person who remembers, and anyone can answer “how does this actually behave in production?” by reading rather than guessing.

​

See what changed

Traversal doesn’t overwrite the Wiki in place. Each regeneration is committed against the one before it, so the Wiki carries a history rather than only a current state — and the section header reports what the latest pass did: when it ran, and how many pages it added, updated, and removed since the previous version. That makes a self-maintaining Wiki something you can keep an eye on rather than take on faith. A pass that adds a run of new pages usually means Traversal found services it hadn’t documented yet. A pass that updates a page your team relies on is worth a read.

​

Sharpen it with comments

Traversal wrote all of this without a word of input from your team — which also means it’s working from evidence alone. Where you know something the data doesn’t show, or where it drew a conclusion that isn’t quite right, leave a comment and Traversal folds that nuance in as it maintains the page.

• Open a file and switch to the Comments tab to weigh in on the page as a whole.
• Or select any passage and choose Quote in comment to attach your note to that exact line.

Your note is visible to your team in context immediately, and Traversal carries it forward as it refreshes — so the improvement compounds instead of being re-derived away on the next pass. These pages stay Traversal’s to maintain, which is why you tune them with notes rather than editing them by hand.

​

Skills: shape the steps Traversal takes

A skill is how your team’s own way of working gets into an investigation — the steps you take and the order you take them in. It’s where your preferences and rituals live: how you work a stuck worker pool, what you always pull first when the payments service alerts, which check settles the argument. Traversal reaches for the right skill when the situation calls for it.

​

Uploaded docs: give Traversal more to work with

Skills shape how Traversal works. Documentation expands what it knows. Use it for the information your systems don’t carry: the business constraint, the exception nobody wrote down, the workaround that only works on Tuesdays. Uploads accept Markdown, text, CSV, JSON, YAML, and PDF, up to 10 MB per file. You can also drag files straight onto the Skills or documentation list. The Knowledge Files API additionally accepts TSV.

​

Edit it where you read it

Skills and uploaded docs are editable in place. Open a Markdown file and choose Edit — the editor handles headings, lists, tables, links, and inline formatting, so keeping a runbook current doesn’t mean downloading it, editing it somewhere else, and uploading it again. Saving publishes immediately, and the next investigation uses the new version. If a teammate changed the file while you had it open, Traversal says so rather than overwriting their work.

​

Memories: Traversal getting better as it works

Traversal learns from working with you. When something durable comes up mid-investigation — you correct it, or tell it to remember something — it drafts a memory and asks before keeping it. The proposal appears in the session. If the investigation started in Slack, a review card is also posted in the same thread so you can approve or reject it without leaving Slack. Approve files it into Memories, where it’s available to future investigations. Reject discards it. Download gets you the file first if you’d rather read it in full. Traversal never applies its own proposal on its own — a person decides every time. Approved memories name the investigation that produced them in the Related investigation column, so you can open the session behind any memory and trace how Traversal’s understanding of your systems has grown.

​

Search

Search from the top of any section. It matches file names, folder paths, and Traversal’s one-line summary of each file — not the full text of every document — and returns files grouped by the section they live in, with the matching part of the name highlighted. The query lives in the URL, so a search worth coming back to is just a link.

​

FAQ

​

Support

Questions or issues? Email support@traversal.com.