AIDA customer knowledge base — org-managed runbooks, SOPs, and pipeline patterns indexed for contextual AI responses
under review
C
Civic Parrotfish
This is the specific implementation ask for PayPal: AIDA has no awareness of PayPal's internal pipeline patterns, DPE runbooks, OPA rules, or the Raptor/Kraken template structure our CI/CD platform uses. When AIDA gives advice, it gives generic Harness answers that don't apply to our configuration. For SonarQube token failures, AIDA has no knowledge of PayPal's DPE-managed auth pattern. DPE's institutional knowledge in Confluence and DPEIR is completely unavailable to AIDA.
We need a customer-owned knowledge base that DPE seeds and maintains:
- DPE uploads internal runbooks, SOPs, template docs, known-issue guides via a management UI.
- AIDA indexes PayPal-specific content and prioritizes it over generic Harness answers.
- OPA policy library awareness — AIDA understands our quality gate rules.
- Failure → runbook mapping: AIDA surfaces the relevant DPE runbook for a recognized failure pattern.
- KB management UI editable by DPE without Harness involvement or a support ticket.
This must be customer-controlled, not a shared Harness KB.
Business value
Transforms AIDA from a generic responder into a PayPal-aware assistant. Scales DPE knowledge to 1,000+ developers without proportional support headcount growth. Addresses 54% AIDA uselessness rating.
Log In
Rohan Gupta
marked this post as
under review