Whether you meet App Architects near Gyeonghuigung or join remotely on Seoul time, the quality of an architecture review tracks the quality of the packet you send three working days ahead.
Bring design documents for the change under discussion, even if they are incomplete. Bring exports or screenshots of metrics for the paths in scope. Bring a named technical contact who can answer ownership questions within a business day. Bring a one-page note on recent incidents related to those paths — honesty beats polish.
Leave behind slide themes, aspirational roadmaps, and tool catalogs that are not tied to the release or migration you asked us to review. Application architecture analysis for service dependencies and performance bottlenecks needs concrete edges, not aspiration.
If Korean and English documents mix, label the authoritative version. Ambiguity about which contract is current wastes workshop hours that should be spent on ranked risks.