# Polylane Knowledge Base

> Polylane's Knowledge Base records every confirmed root cause, how your services fit together and how your team works, so each investigation starts from it.

Every incident teaches Polylane something it won't forget. Polylane writes down every root cause it proves, how your services fit together and how your team likes things done, in a knowledge base you can read and edit. Every investigation starts from it.

- **Every investigation leaves notes for the next one.** When Polylane learns how a service works or why it broke, it writes it down in plain markdown files. Nobody has to set them up, and you can read and edit every one.
- **When a problem comes back, Polylane already knows the cause.** Every root cause Polylane proves is saved. The next time the same thing breaks, it checks the known cause first instead of starting from scratch.
- **Tell Polylane your team's rules once.** Deploy freezes, who owns what, how you like fixes written: put them in a file and Polylane follows them in every investigation. It never rewrites them.
- **Every investigation starts briefed.** Each new investigation reads the knowledge base's index and the last three days of notes, then searches the rest for anything that matches.
- **Every night, Polylane dreams.** While your team sleeps, Polylane goes back over the day. It writes a daily note, learns from the fixes you merged as they were and the ones you changed, checks every saved fact against your infrastructure and code, and deletes what's no longer true. Each step is its own commit, so you can undo any of it.

## Questions

### Can I see and edit it?

Yes. Browse it in the console under Settings, Memory: open any file, edit it or add your own. It's a git repository, so every change is tracked.

### What does Polylane save?

Findings it has confirmed with evidence, each with the resource and the date. It doesn't save guesses or anything already in the context graph.

### How does Polylane use the knowledge base?

Every new investigation starts with its index and the last three days of notes, then searches the rest for anything related.

### Can I add something myself?

Yes. Add your own files, or ask in any thread: “Save a note: the payments sandbox times out under parallel load.”

## More of the product

- [Swarms](https://polylane.com/product/swarms) ([markdown](https://polylane.com/product/swarms.md)): Many agents on one problem, sharing one board.
- [Investigations](https://polylane.com/product/investigations) ([markdown](https://polylane.com/product/investigations.md)): From an issue to a proven root cause.
- [Autofix](https://polylane.com/product/autofix) ([markdown](https://polylane.com/product/autofix.md)): Reviewed fixes, opened in your repository.
- [Impact assessments](https://polylane.com/product/impact-assessments) ([markdown](https://polylane.com/product/impact-assessments.md)): Checks each pull request against production.
- [Anomaly detection](https://polylane.com/product/anomaly-detection) ([markdown](https://polylane.com/product/anomaly-detection.md)): Finds problems nobody set an alert for.
- [Context graph](https://polylane.com/product/context-graph) ([markdown](https://polylane.com/product/context-graph.md)): Every resource and repository, in one live graph.
- [Advisories](https://polylane.com/product/advisories) ([markdown](https://polylane.com/product/advisories.md)): Misconfigurations, found and fixed per resource.
- [Escalations](https://polylane.com/product/escalations) ([markdown](https://polylane.com/product/escalations.md)): One clear ask when a person is needed.
- [Console](https://polylane.com/product/console) ([markdown](https://polylane.com/product/console.md)): The web app: graph, threads, issues.
- [Slack](https://polylane.com/product/slack) ([markdown](https://polylane.com/product/slack.md)): Ask about production where you already talk.
- [GitHub](https://polylane.com/product/github) ([markdown](https://polylane.com/product/github.md)): Mention @polylane on any pull request.
- [MCP and plugins](https://polylane.com/product/mcp) ([markdown](https://polylane.com/product/mcp.md)): Production context for Claude Code, Cursor and Codex.
- [CLI](https://polylane.com/product/cli) ([markdown](https://polylane.com/product/cli.md)): Polylane from your terminal.
- [API](https://polylane.com/product/api) ([markdown](https://polylane.com/product/api.md)): Everything in the console, over REST.

Get started with one command: `curl -fsSL https://polylane.com/setup | bash` installs the CLI, connects your coding agents, and creates the account.
