Interactive Business Walkthrough

Turn incidents into institutional knowledge

Step through what HARP does, why it matters, and how it fits your team. Click "Next" to reveal each section.

Infrastructure knowledge is scattered

When an alert fires at 3 AM, operators scramble through Slack, wikis, and tribal memory. The knowledge exists — but nobody can find it fast enough.

📂

Knowledge Everywhere

Runbooks in Confluence, RCAs in Google Docs, scripts in Git, notes in Slack.

🕐

Search Is Broken

Ctrl+F can't find "pod keeps dying" in a doc titled "CrashLoopBackOff Recovery."

🔄

Incidents Repeat

Same issue diagnosed from scratch because the RCA from 6 months ago is buried.

AI Needs Grounding

ChatGPT gives confident answers — but has never seen your configs or your history.

From alert to evidence pack in seconds

HARP indexes your Git-tracked docs, then provides cited, source-grounded intelligence.

📥

Index Knowledge

Point HARP at any Git repo. Indexes Markdown, YAML, shell scripts, text.

🚨

Alert Fires

Prometheus detects an issue. AlertManager sends payload to HARP.

🔍

Evidence Search

Sub-second search. Every result includes the exact file path.

📄

Evidence Pack

Cited document with runbooks, RCAs, actions, and approval requirements.

What HARP does in practice

Incident

🐳 ImagePullBackOff at 2 AM

Pod can't pull its image. HARP generates an evidence pack: cites RCA-001 (containerd config_path from 3 weeks ago), links the networking runbook, suggests checking registry config (read-only) and restarting containerd (approval required).

→ Cited documents, tiered actions, sub-second response
Coverage

📊 "Do we have runbooks for all alerts?"

Coverage checker maps all Prometheus alert rules to documentation. Reports linked, partial, and gap coverage — gaps explicitly surfaced.

→ Complete alert-to-documentation mapping with honest gap reporting
Onboarding

👤 New SRE joins the team

Searches: "How does MetalLB work in our cluster?" Gets cited results from actual runbooks — not generic docs. Every answer links to real config files.

→ Institutional knowledge transfer without tribal knowledge

HARP vs the alternatives

❌ Without HARP

  • 🔴 Manual search through disparate tools
  • 🔴 AI assistants hallucinate infra specs
  • 🔴 Incident knowledge lost on rotation
  • 🔴 No audit trail of investigation
  • 🔴 Slow ramp-up for new engineers
  • 🔴 Destructive fixes without oversight

✅ With HARP

  • 🟢 Instant cross-repository search
  • 🟢 Every answer grounded in your files
  • 🟢 Historical RCA database linked to alerts
  • 🟢 Automated, auditable evidence packs
  • 🟢 Self-service onboarding
  • 🟢 Action tiers for safe remediation

Start where you are

HARP scales from a single VM to multi-cluster enterprise. Start small, prove value, then grow.

🟢 Homelab / PoC

Solo operator
  • BM25 search over Git repo
  • Evidence packs
  • CLI tools (offline)
  • Zero dependencies
Best for: homelabs, personal infra

🔵 Team

5-20 engineers
  • API authentication
  • AlertManager webhooks
  • Notification integrations
  • Multi-profile support
Best for: SRE / platform teams

🟣 Enterprise

50+ engineers
  • Hybrid retrieval (BM25+RAG)
  • Local LLM diagnostics
  • MCP server for AI agents
  • Eval harness
Best for: regulated industries

What HARP does not do

🚫

No Auto-Fix

Diagnoses only. State-changing actions require human approval via Git commit.

📊

No Monitoring Replacement

Consumes alerts from Prometheus/AlertManager. Doesn't replace them.

🧠

No Magic

Surfaces evidence and classifies risk. The human makes the call.

🔒

No Cloud Data Sharing

HARP core search runs entirely on your infra. No telemetry, no external APIs. The website may load static web assets (fonts).

Get started locally

Run HARP against your own runbook repo:

git clone https://github.com/climacs/k8s-cluster-runbook-setup
cd k8s-cluster-runbook-setup
pip install fastapi uvicorn pydantic
HARP_CONTENT_DIR=. python -m harp.api.server
# Then: curl -X POST http://localhost:8100/search \
#   -H 'Content-Type: application/json' \
#   -d '{"query":"ImagePullBackOff","top_k":3}'

60-second install on your laptop. Point HARP_CONTENT_DIR at any Git repo with Markdown docs.

View Technical Architecture → · HARP Project Hub · climacs.net

© 2026 Climacs IT Consulting — Stage B implemented. Formal eval harness pending (Stage C).

Step 0 / 7 — Click Start