Why should you care?

Without EA alignment, hospital team picks Qdrant while CRM picks Pinecone — ops inherits two runbooks and split billing.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// docs/enterprise-architecture/agentnest-capability-map.json
{
  "capabilities": {
    "crm.copilot": { "agents": ["CrmCopilotAgent"], "stores": ["postgres", "pgvector"], "models": ["gpt-4o-mini"] },
    "hospital.assistant": { "agents": ["HospitalAssistant"], "stores": ["qdrant"], "models": ["gpt-4o"] },
    "erp.explain": { "agents": ["VarianceReasoner"], "stores": ["postgres"], "models": ["gpt-4o-mini"] }
  },
  "sharedPlatform": ["audit", "quota", "apim", "keyvault"]
}

What happened?

• Capability map JSON documents which agents, stores, and models each business domain uses plus shared platform services.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Maintain capability map reviewed quarterly by architects.
2. Standardize IVectorStore adapters — avoid N vector engines without cause.
3. Map data classification to network zones in diagram.
4. Add dependency graph between capabilities and external systems.
5. Link each capability to SLO and cost center code.

Remember

Enterprise architecture maps capabilities to shared AgentNest platform. Standardize cross-cutting audit, quota, identity. Keep capability map current for ops and sales.

Architecture board approval

New analytics capability proposed with separate OpenAI subscription.

Outcome: EA review routes through shared platform — one Key Vault, unified audit, approved design.