Red Hat family · 101 cards
RHEL, OpenShift, Ansible Automation Platform, Satellite, DNS, SELinux, storage, boot, and disconnected lifecycle themes.
Practical content from the first evaluation
Start with focused troubleshooting knowledge—not an empty search box.
The Mimir repository includes 195 Mimir-authored troubleshooting cards that can be seeded into four starter-pack families spanning Red Hat, Cisco, Microsoft, and VMware environments. Each delivery should verify what was loaded, indexed, reviewed, and approved for that customer.
Vendor names describe coverage
The starter cards are Mimir-authored—not vendor-authored or vendor-certified.
Red Hat, Cisco, Microsoft, VMware, OpenShift, RHEL, and related marks identify the technologies addressed by the content. The starter packs do not imply endorsement, certification, or replacement of current vendor documentation and customer procedures.
01 / Starter coverage
Four technology families, organized for field-oriented triage.
The current content repository contains 101 Red Hat-family cards, 26 Cisco-family cards, 34 Microsoft-family cards, and 34 VMware-family cards. The cards are structured around common symptoms, first checks, evidence to collect, actions to avoid, escalation points, and supporting references.
The starter set is intended to accelerate a pilot and demonstrate the knowledge-pack model. It is not a claim of comprehensive product coverage. Before operational use, the loaded content should be reviewed against exact versions, local configurations, current vendor publications, applicable security policy, and the team’s own escalation procedures.
Cisco family · 26 cards
Layer 1–3 isolation, switching, VLANs, routing, firewall, reachability, and safe configuration triage themes.
Microsoft family · 34 cards
Windows Server, Active Directory, DNS, authentication, services, endpoints, and common platform-health themes.
VMware family · 34 cards
ESXi, vCenter, clusters, HA, networking, storage paths, datastores, virtual machines, and service-health themes.
Counts describe the current repository as audited on September 1, 2026. Loaded production content and approval status must be verified for each release.
02 / Card design
Structure answers around safe, inspectable support steps.
A useful troubleshooting response should help a qualified person establish scope, collect evidence, compare expected and observed state, avoid a destructive first move, and identify when to escalate. Mimir cards make that structure retrievable so the model has more than a long manual passage to work with.
In the initial product posture, connected diagnostics are intentionally bounded and read-only. Mimir can collect approved evidence through controlled interfaces and pair it with cited guidance, but it should not become an unsupervised administrator that changes infrastructure based on generated output.
Symptoms and scope
Clarify what is failing, what remains healthy, when behavior changed, and which users or components are affected.
First checks
Surface low-risk observations and commands appropriate to the platform and the team’s approved workflow.
Do-not-do guidance
Call out actions that could destroy evidence, expand impact, break quorum, or complicate recovery when performed too early.
Escalation evidence
Help users assemble logs, state, timestamps, versions, and context that make the next support handoff more effective.
03 / Customer tailoring
Turn starter content into a mission-owned knowledge release.
The most valuable material is often local: site architecture, naming, approved versions, known deviations, maintenance windows, support contacts, escalation thresholds, and lessons learned. During a pilot, starter cards can be paired with that customer-approved content and tested against representative questions from the intended users.
A governed update process records source revisions, card changes, review decisions, evaluation results, and the pack version promoted to users. In a disconnected environment, the published pack can move through the approved transfer chain separately from a larger application or model release.
Map the environment
Identify platforms, versions, topology, mission owners, governing publications, and current escalation paths.
Review the starter set
Remove irrelevant content, correct version-specific details, and link each topic to approved supporting sources.
Test with operators
Use real questions and qualified reviewers to measure retrieval, citations, usefulness, ambiguity, and abstention.
Publish deliberately
Promote a named version with an owner, review record, release notes, and a rollback path.
Continue the mission thread
See how the pieces work together.
Related capability
Maintenance support
Apply governed technical knowledge beside maintainers while keeping the current manual authoritative.
Related capability
Defense RAG
Understand how retrieval, reranking, local generation, citations, and evaluation work together.
Related capability
Expeditionary edge
See how local troubleshooting knowledge can support compact OpenShift and forward operations concepts.
Plan the deployment
Bring the mission and the constraints. We’ll map the system to both.
A Mimir briefing covers the operating boundary, approved knowledge, deployment pattern, security evidence, and the people the system is intended to support.