What an AI application is
Strip away the demos and an AI application is a normal enterprise system with three new parts: a model you do not control, retrieval that feeds it context, and tools it is allowed to call. Everything around those three is engineering you already know: networks, databases, identity, integration, operations and cost.
That is why the map above has lenses. Pick one and the same system turns into a networking problem, a data problem or an identity problem, with the components that matter for that discipline lit up.
The shape that survives production
- Edge and API gateway own the way in: TLS, WAF, authentication, rate limits.
- Agent decides what happens next. In most systems it is a supervisor with a small set of specialist workers.
- LLM gateway is the only way out to a model: routing, budgets, redaction and one place to trace every call.
- Retrieval supplies the knowledge the model was never trained on, filtered by who is asking.
- Ingestion keeps that knowledge fresh from the systems that own it.
- Tools are typed MCP servers with explicit permissions in front of real enterprise APIs.
Where teams get hurt
Observability arrives too late, evaluation is a spreadsheet, identity stops at the web app, and the deployment story is "it runs on my laptop". The guides attached to each component address these in order.
Node by node
Web App
Frontend3 linked
Identity
SSO · OBO2 linked
Understand
- ExplainerYour agent should not be a superuser
Operate
API Gateway
AuthN · limits4 linked
Secrets
Vault · KMS1 linked
Operate
Agent
Orchestration34 linked
Understand
- ExplainerWhy complex AI questions need decomposition
- ExplainerWhy reflection only matters when tied to evidence
- ExplainerWhy agents need outcomes, boundaries, and stop conditions
- ExplainerWhy agent behavior is a loop, not a single prompt
- ExplainerWhy planning reduces wasted AI actions
- 19 more on the map
Implement
Decide
Use
- ToolOpenAI Agents SDK
- ToolLangGraph
Reference
- ReferenceBuilding Effective Agents
Audit
Every call7 linked
Understand
- ExplainerWhy multi-agent systems need decision rules
- ExplainerWhy governance belongs in the architecture
- ExplainerYou cannot instruct a model into data protection
- Architecture patternPattern: the outbox for agent actions
Operate
LLM Gateway
Route · budget10 linked
Understand
Observability
Traces · evals18 linked
Model
Provider API13 linked
Understand
- ExplainerWhy model choice is rarely the first production AI problem
- ExplainerWhy LLMs feel intelligent but still generate one step at a time
- ExplainerWhy tokenization quietly affects cost, limits, and reliability
- ExplainerWhy more context can make an AI system worse
- ExplainerWhy vague prompts become vague systems
- 3 more on the map
Implement
Operate
- ChecklistWhen to bring in a compliance review
Use
- ToolLiteLLM
- ToolGuardrails
Reference
- ReferenceAttention Is All You Need
Sources
Docs · tickets · DBs5 linked
Understand
Operate
- ChecklistWhen to bring in a compliance review
Ingestion
Chunk · embed8 linked
Understand
Vector Index
Embeddings · hybrid4 linked
Retrieval
Hybrid · rerank23 linked
Understand
- ExplainerWhy confident AI answers still need evidence
- ExplainerWhy RAG is an evidence design problem, not a buzzword
- ExplainerWhy keyword search and semantic search both matter
- ExplainerWhy hybrid search is often the practical default
- ExplainerWhy relevant data can still be unauthorized data
- 12 more on the map
Operate
- ChecklistRAG production-readiness checklist
- Failure storyThe retrieval cache that served stale policies
Use
- ToolLlamaIndex
- Toolpgvector
- ToolRagas
Reference
Tools
MCP servers20 linked
Understand
Decide
Operate
Use
- ToolInstructor
Reference
- ReferenceModel Context Protocol
- ReferenceOWASP Top 10 for LLM Applications
Enterprise APIs
ERP · CRM · ITSM2 linked
Understand
Decide
Memory
Session · long-term6 linked
Understand