Skip to main content
Most of what your team knows about your infrastructure already lives in a Confluence page, a runbook, a CSV inventory. Feeding that into 2501 lifts a lot of heavy work — operational rules, host mapping, the role of each machine — without writing them by hand. It is similar to telling a coding agent “respect the coding style already in place.” Same idea, applied to infrastructure.

​
What gets extracted

Upload PDFs, DOCX, CSV, or Markdown to Command Center → Knowledge. The engine parses each document and creates:
Extracted intoWhat it looks like
Operational Rules”When restarting a Docker container with MongoDB on Ubuntu, do X then Y.” Tagged os:linux, tech:docker, tech:mongodb.
Host Knowledge facts”host db-01 runs Postgres 15 with replication to db-02.” Attached to the host record.
Blacklist entries”Never run vgremove on storage nodes.”
See Knowledge configuration for file types, size limits, and the ingestion status pipeline.

​
How knowledge reaches agents

Two paths, both automatic:
  • Programmatic — host description and tags get matched against operational-rule tags. Relevant rules and host facts ship with the task at dispatch time.
  • Dynamic — the gateway and the agent can pull additional rules + facts on demand if the task’s scope evolves.
You don’t tell the agent “remember the runbook”. The runbook is already in its context when relevant.

​
Managing extracted knowledge

Auto-generated rules can be edited or marked outdated from the Knowledge UI. A few things to know:
  • Re-upload replaces extraction. Uploading a newer version of the same document replaces the old extracted rules and facts. Your manually-curated rules are untouched.
  • Conflicts: prefer your own rule. If extracted knowledge contradicts what you want, create your own operational rule and disable the extracted one. Manual rules outrank extracted ones in conflicts.
  • Don’t expect 100% extraction quality. Review what was extracted after each upload, especially for the first few documents.

​
What to upload first

In order of payoff:
  1. Runbooks — they translate directly into operational rules (procedures).
  2. Infrastructure inventory spreadsheets — they translate into host knowledge facts.
  3. Internal “don’t do this” guides — they translate into constraints + blacklist entries.
  4. Architecture docs and network diagrams — useful only if your tenant has a multimodal model configured (diagrams need vision).
  5. Tribal-knowledge pages (“the old way we restart auth-service”) — high payoff but review extraction carefully.