01 · Mental model
Generation and assurance are different service promises
The fast path transforms sufficient architecture intent into an intermediate representation and exports editable draw.io, SVG, and PNG artifacts. The assurance path checks whether essential HLD information is present, asks up to three targeted questions when needed, and produces findings and lineage alongside the visual.
Using MCP lets the orchestrator discover and invoke these bounded capabilities without embedding rendering logic in every agent. The application still owns server trust, arguments, access, and artifact handling.
02 · Visual explanation
03 · Compare and decide
Fast generation versus assurance
| Decision lens | Generate architecture | Assure architecture |
|---|---|---|
| Goal | Create a useful editable diagram quickly | Challenge completeness and design quality |
| Input | Sufficient structured intent | Intent plus essential HLD context |
| Interaction | Usually one pass | May ask targeted clarification |
| Output | Diagram formats | Formats plus findings, manifest, and lineage |
04 · Cybersecurity example
Sentinel HLD diagram
The orchestrator receives regions, workspaces, connectors, retention, and access requirements.
It calls assurance because resilience details are incomplete.
ArchStudio returns three focused questions.
Answers update the architecture IR.
The exporter produces editable and presentation-ready formats with findings.
Outcome: The visual remains editable while the assurance record explains what was checked and what remains open.
05 · What to remember
The 60-second recall
A beautiful diagram is not evidence of architectural assurance.
Use one intermediate representation to support multiple export formats.
Clarification should be targeted, bounded, and preserved in lineage.
Teach-back prompt: Explain this concept to a teammate using the diagram, then name one failure mode and the control that stops it.
06 · Questions people ask
FAQ
07 · Primary sources