An architect is only as good as their evidence. Vera shows hers. Here's her first two weeks.
Share a read-only export of your code and the documents that describe it: specs, process docs, design decisions. Nothing in your systems changes. Her manager, usually your enterprise architect, gives her the list of people and roles.
DAY 1Vera reads the code bottom up and the documents top down, and builds Atlas: one model linking business functions, processes and custom code.
DAYS 2–5Email her, message her in Teams or open her chat page. Ask in plain English, or assign a job. Assess a change before you make it, scope a migration from what the code does, reconcile docs with code.
FROM WEEK 2Vera keeps her own list of what she’s working on, what she’s waiting for and what she owes. Urgent things go to the right person straight away, with her reasons. The rest goes in her Monday note. She suggests who should decide, and never decides for them.
EVERY WEEK AFTERBacked by source. Links to the code line or document page.
Vera's reasoning from what the source shows. Marked so you know to check it.
The source is silent. Vera says so instead of making something up.
The documents, the code or two people say different things. Both shown side by side, with who said what.
30 minutes. Your estate. Vera answers, with the source line to prove it. No awkward small talk.