Skip to main content
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.
The Knowledge Bank page with summary metrics, a search field, and tabs for Skills, Uploaded documentation, Memories, and Auto-created

Skills, uploaded documentation, memories, and Traversal's auto-created wiki, in one searchable place.

​
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 a wiki of your environment, 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.
Connecting your integrations is the whole setup. Everything in the Auto-created section was written without a single line of input from your team.

​
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.

​
Auto-created: what Traversal figured out on its own

Open the Auto-created tab and you’re reading 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.
An Auto-created wiki page for a service, with a folder tree, generated documentation, and a File details panel

Traversal's own documentation of a service, with a summary, links to each section, and where the entry came from.

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.

​
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.
1

Start a new skill

Open Add → Add skill.
2

Upload or write it

Upload brings in a skill file you already have. Create new lets you write one here.
3

Describe the procedure

Give it a name, a one-line description of what it does, and the instructions themselves. Optionally drop it in a folder.
4

Create the skill

Traversal saves it as a SKILL.md file and can use it on the next investigation.
The Add skill dialog with fields for skill name, description, instructions, and an optional parent folder

A skill reads like instructions to a teammate: when it applies, what to pull, and what a useful answer looks like.

Write the description for the trigger, not the content — it’s what Traversal reads when deciding whether a skill applies. “When the payments service alerts” beats “payments runbook.”

​
Uploaded documentation: 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.
1

Start a new document

Open Add → Add documentation.
2

Bring in the content

Upload files, import from a URL, or write a document directly in Traversal.
3

Choose where it lives

Drop it into an existing folder, or create one as you go.
Uploads accept Markdown, text, CSV, TSV, JSON, and YAML, up to 10 MB per file. You can also drag files straight onto the Skills or documentation list.
Make each document specific enough to act on. “During a payment-provider incident, check the provider’s status page before restarting checkout” is useful. “Payments is important” is not.

​
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.
A Traversal session where a user asks it to remember escalation routing, and the proposed memory appears with Approve, Reject, and Download actions

Ask Traversal to remember something and it drafts the memory, then waits for a person to approve it.

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 keep a link back to the investigation they came from, so you can trace how Traversal’s understanding of your systems has grown and where each piece of it came from.
The Memories section listing memories alongside their related investigations and last-modified times

Memories keep a link to the investigation that produced them.

Memories are created during investigations — they can’t be added by hand. To capture something on the spot, just tell Traversal to remember it in a session.

​
FAQ

No — and that’s the point. Traversal learns your environment from the integrations you’ve connected and investigates without any Knowledge Bank setup at all. What you add here is last-mile refinement on a foundation that’s already there.
Something that regularly changes how your team responds: a runbook you follow often, an alert everyone knows to ignore, a service whose downtime is a business emergency. Start there rather than trying to document everything.
Comment on it. Traversal regenerates these pages as your systems change, so a note is what carries forward — Traversal weighs it against everything else it knows and folds it into the next refresh, where a hand edit would just be overwritten.
Skills, documentation, and approved memories are available to the next investigation. Comments are visible to your team immediately and are folded into Traversal’s understanding as it refreshes.
It can propose a memory during an investigation, but a person approves it before it takes effect. The Auto-created wiki is Traversal’s own, regenerated from your connected systems.
The original was a place to upload your team’s context. This one starts with everything Traversal already learned on its own, adds skills and memories, and puts it all in a file system you can browse and search.
Knowledge Bank feeds every surface Traversal runs on. The sharper it is, the sharper your investigations and Workers get.

​
Support

Questions or issues? Email support@traversal.com.