An AI assistant can produce an architecture diagram from a short idea, but a diagram is only useful when it reflects the real problem. For an automation project at Thora Vietnam, I would start with a compact design brief that separates known requirements from assumptions. The first output should make the system easier to question, not harder to understand.
Describe a complete user task
Choose a task that has an input, an observable result and a responsible person. For example, an internal user submits a request, a reviewer checks a suggested classification, and the system records the approved result. Label this as an illustrative workflow until it has been validated with a user.
List the unhappy paths too: incomplete information, duplicate submissions and a reviewer rejecting the suggestion.
State the boundary before choosing technology
Identify the people and external systems around the application. Then describe the major running parts and the information exchanged between them. The C4 model offers useful levels of architectural description; a small project can begin with context and containers rather than every internal class.
Ask the assistant to explain the responsibility of each part in plain language. A queue or service without a clear responsibility is a question, not automatically an improvement.
Give the assistant a bounded design prompt
Provide the user task, access rules, expected failure handling, deployment constraints and open questions. Ask for one simple design and one alternative. Require assumptions to be marked rather than silently filled in.
Design task: request intake with human approval.
Show: actors, system boundary, data flows and failure paths.
Compare: one deployable application and one service split.
Do not assume: traffic volume, existing clients or infrastructure.
Return: tradeoffs, unanswered questions and a first testable slice.Review one path end to end
Trace a single request through identity checks, storage, model output and approval. Check which component owns each decision and which facts the assistant invented. Use the reviewed brief as the input to implementation. Update the diagram when coding reveals a different boundary instead of leaving documentation behind.
Further reading
Background for the method; the Thora Vietnam workflow above is a proposed application.
C4 model — Software architecture diagrams
