# What does AI actually do inside an Architecture Decision Workspace?

> Canonical: https://decisionpen.com/blog/what-does-ai-do-inside-an-architecture-decision-workspace  
> Published: 2026-10-27 · DecisionPen · Living EA series (D7a)  
> Related docs: /docs/architecture-decision-workspace, /docs/incremental-modelling, /docs/enterprise-ask, /docs/why-not-copilot-or-rag, /docs/beyond-traditional-ea

## Summary

Inside an Architecture Decision Workspace, AI is a loop — ingest, propose, bind evidence, human curation, then Ask and publish from the curated map — not a chat box over documents. AI accelerates the work; humans own what becomes canonical. This capstone maps the loop and its boundaries.

## Why chat-over-documents falls short

Chat-over-docs answers “what do our documents say?” Architecture needs “what is authorised to be true of our landscape, and what follows if we change it?” That requires a metamodel, a curated state (rejections and retirements recorded), evidence bound to claims, and an accountable owner. (Copilot vs metamodel agent: see the C3 post, not repeated here.)

## The five-step AI loop

1. **Ingest** — HLDs, PDFs, wiki exports, transcripts, natural-language descriptions, CMDB/inventory spreadsheet extract.  
2. **Propose** — metamodel-aware entities and relationships (applications, capabilities, technology, integrations).  
3. **Bind evidence** — source passage/row stays with each proposal (How/Why with the What).  
4. **Curate** — humans accept, edit, reject, or defer; only ratified proposals join the living map.  
5. **Ask and publish** — Enterprise Ask and generated artefacts draw only from the curated map, with citations.

Curation sits before Ask/publish, not after.

## What AI does — and does not do

- Ingest/propose: does the transcription into metamodel drafts (cuts Discovery Tax); does not decide what is canonical.  
- Evidence: keeps source and claim together; does not invent provenance.  
- Curation support: can surface duplicates, conflicts, gaps; does not auto-approve into the Context of Record.  
- Ask: answers from the curated map with citations and should surface gaps; does not improvise topology.  
- Artefacts: documents and diagram images as views of the map; not a freeform drawing canvas.

## Solution-architect incentive and artefact flywheel

Solution architects ship designs, not repository updates, so classic EA tools go hollow: the HLD they must write and the factsheet the repository wants are separate chores. When HLDs, notes, and decision papers become inputs that AI turns into proposals — and curation is review, not retyping — the artefact already produced feeds the map. Better map → faster next design → more artefacts ingested.

## Shaped context and agentic delivery

The curated map serves people (shaped IT knowledge: views, answers, generated documents from one Context of Record — see D6e) and delivery agents (scoped context packs, accepted design written back — see D6g). The aim is a trusted plane, so every squad’s bot does not become a competing architecture office. Full method: D6h.

## Four questions to evaluate “AI inside” claims

1. Does AI propose against a metamodel, or only summarise text?  
2. Does every claim carry openable evidence?  
3. Is there a human gate before the system of record?  
4. When the map has a gap, does Ask say so?

## How DecisionPen implements the loop

Ingests documents, transcripts, natural language, and a CMDB/inventory spreadsheet extract; proposes LeanIX-aligned entities/relationships where relevant; binds evidence; architects accept/edit/reject/defer; Ask and artefacts use the curated map. Trial: https://decisionpen.com/trial

## When is DecisionPen the wrong tool?

Freeform drawing (Visio/Lucid), BPMN, a general writing Copilot, or a pure operational CMDB as the only need. DecisionPen holds living architecture context and can generate diagram images from it; it is not a summariser alone nor an ITSM replacement.

## FAQ

**What does AI do inside an Architecture Decision Workspace?**  
Ingests sources, proposes metamodel-aware entities and relationships, binds evidence, supports curation, and answers/publishes from the curated map — humans ratify what becomes canonical.

**How is this different from chat over documents?**  
Chat retrieves similar passages. The loop maintains a metamodel, a curated Context of Record, bound evidence, and cited answers that surface gaps.

**Does AI replace the architect?**  
No. AI drafts and accelerates; architects ratify. Curate-Don’t-Create.

**How does the loop help solution architects?**  
Artefacts they already write (HLDs, notes, decision papers) become inputs to proposals, so feeding the map stops being a separate chore.

**How does DecisionPen help?**  
It is an Architecture Decision Workspace implementing ingest → propose → evidence → curate → Ask/publish, including spreadsheet import for CMDB/inventory extracts.

**When is DecisionPen the wrong tool?**  
Visio/Lucid drawing, BPMN, Copilot-only text drafting, or CMDB-only operational tracking as the sole need.

## Series index (D7)

- https://decisionpen.com/blog/what-does-ai-do-inside-an-architecture-decision-workspace  
- https://decisionpen.com/blog/how-to-model-enterprise-architecture-from-structured-and-unstructured-sources-with-ai  
- https://decisionpen.com/blog/how-should-humans-review-and-curate-ai-proposed-architecture-models  

## Related posts

- https://decisionpen.com/blog/ai-enterprise-architecture-copilot-vs-metamodel-agent  
- https://decisionpen.com/blog/how-ai-accelerates-automated-enterprise-discovery  
- https://decisionpen.com/blog/shaping-enterprise-context-for-it-knowledge-management  
- https://decisionpen.com/blog/architecture-context-for-agentic-sdlc  
- https://decisionpen.com/blog/from-automated-discovery-to-durable-architecture-context  
- https://decisionpen.com/blog/what-is-enterprise-architecture-context  
- https://decisionpen.com/blog/why-solution-architects-rediscover-the-landscape