AI-Agent Project Management
Expert agents collaborate via chat · act on tickets · learn from knowledge
Situation A new hire asks in chat about company accounts, benefits, and team policies all at once.
Scenario HR and Knowledge agents pull policies, onboarding docs, and FAQs from Brain, answer in the thread, open tickets when a handoff is needed, reflect assignments and reports, and leave a short summary with links in chat.
Situation A developer reports in chat that login sessions sometimes drop.
Scenario Agents turn the conversation into a ticket, ship a fix through PR, then review, QA, and merge. The change is documented and ingested into Brain so later, similar questions cite the past issue and decision.
"I have no context about your project, specs, or past decisions."
"Based on your spec v2.3, ticket #142 is blocked by the auth migration agreed on 2025-03-12."
Vector (semantic similarity) + Graph (relationship traversal) + SQL (structural hierarchy) — not just "find similar text"
Documents parsed into hierarchy (section → paragraph → sentence); RAG returns the chunk and its parent context — richer, more accurate agent prompts
Idempotent ingestion via stable entity IDs — re-processing a document never creates duplicates or knowledge drift
Every cycle feeds back: merged PRs, meeting summaries, and decisions are ingested — Brain grows smarter with each loop
- Docker Compose
- Traefik (reverse proxy)
- Vault (secrets)
- cert-manager · Let's Encrypt
- GitHub Actions (CI/CD)
- GHCR (registry)
- Kubernetes (kubeadm)
- OpenTofu (IaC)
- Vault + Agent Injector
- Traefik (Ingress)
- cert-manager (TLS)
- CSI Storage (SSD · HDD)
- Calico (CNI)
- GHCR · GitHub Actions
- Prometheus · Loki · Grafana
- All K8s tier items
- Nova · Neutron · Keystone
- Cinder (iSCSI block storage)
- Octavia (LB · Amphora)
- OpenStack CCM + Cinder CSI
- kolla-ansible (deploy)
- Glance (image registry)