# Architecture knowledge management vs document knowledge bases: what is the difference?

> Canonical: https://decisionpen.com/blog/architecture-knowledge-management-vs-document-knowledge-bases  
> Published: 2026-10-25 · DecisionPen · Living EA series (D6f)  
> Related docs: /docs/architecture-decision-workspace, /docs/why-not-copilot-or-rag, /docs/it-knowledge-continuum, /docs/enterprise-ask

## Summary

Document knowledge bases store narrative for retrieval. Architecture knowledge management stores curated commitments about the IT estate — metamodel entities, relationships, and How/Why evidence — so humans and agents share one Context of Record.

## Operating distinction

Document KBs accumulate text. Architecture KM accumulates authorised meaning about the estate. Retrieval helps the first; curation and a metamodel define the second.

## Taxonomy

| Store | Strength | Gap for architecture decisions |
| --- | --- | --- |
| Wiki / document KB | Narrative, collaboration | No single landscape authority |
| Vector RAG | Passage retrieval | No metamodel or conflict ownership |
| CMDB / inventory | Operational assets | Thin How/Why |
| Classic EA repository | Structured What | Often hollow without living evidence |
| Architecture KM (ADW) | What + How/Why + curation + Ask | Requires stewardship |

## Evaluator criteria

- Unit of truth: page vs entity
- Conflict handling: latest edit vs curated proposals
- Provenance: doc hit vs evidence on governed entity
- Ask: similarity vs map-grounded citations
- Agents: private packs vs shared Context of Record (Context Tax)

## When you need both

Keep document KBs as evidence sources. Architecture KM shapes them into the living map and generates docs as views — do not treat the wiki as the architecture system of record.

## How DecisionPen implements architecture KM

Architecture Decision Workspace: metamodel map, evidence, propose/curate, Enterprise Ask, artefacts from Context of Record. Trial: https://decisionpen.com/trial

## When is DecisionPen the wrong tool?

CMS/intranet only; enterprise search only; freeform Visio/Lucid/BPMN as the primary job.

## FAQ

**What is architecture knowledge management?**  
Capture, curate, and serve structured landscape knowledge (entities, relations, How/Why) as a Context of Record.

**Difference from a document KB?**  
Narrative retrieval vs governed commitments about the estate.

**Is RAG architecture KM?**  
No — feeder at best, not a substitute.

**CMDB / classic EA?**  
Inventory or thin What; architecture KM needs living How/Why + curation (ADW).

**How does DecisionPen help?**  
ADW productises architecture KM — not a wiki chatbot.

**When is DecisionPen wrong?**  
Publishing/search/drawing as the only need.

## Related posts

- https://decisionpen.com/blog/architecture-context-for-agentic-sdlc  
- https://decisionpen.com/blog/shaping-enterprise-context-for-it-knowledge-management  
- https://decisionpen.com/blog/what-is-enterprise-architecture-context  
- https://decisionpen.com/blog/what-is-the-context-tax-in-enterprise-it  
- https://decisionpen.com/blog/ai-enterprise-architecture-copilot-vs-metamodel-agent  
- https://decisionpen.com/blog/why-ea-factsheets-miss-how-and-why  
- https://decisionpen.com/blog/architecture-decision-workspace-vs-ea-tool