The incident starts at eleven on a Tuesday night. By midnight there is a bridge call. The platform lead is on. The vendor is on. An engineer who left the programme eight months ago is on, because somebody still had her number and knew the integration layer lived in her head.
Nobody called the EA.
Not out of malice. Not even out of oversight. The question never formed. When the system was on fire, nobody on that call believed the architecture function had anything to offer the fire.
Here is what that silence tells you.
Trust is built in the terrain, not the strategy deck. The EA had presented at every quarterly review. The roadmap was endorsed. The target state was praised. The capability model was admired. None of that was trust. It was attendance.
Trust accumulates in small denominations. The design session where the architect caught the dependency nobody else saw. The trade-off called at speed and defended afterwards, in front of the people who would wear the consequences. The week spent in the delivery team's standups when the migration started slipping. The unglamorous hours in the terrain, where the work is actually true.
The engineer got called at midnight because she had spent years in that terrain. The EA had spent those years in the governance forum, reviewing the terrain from a distance, through artefacts the terrain had stopped resembling.
You cannot mandate your way onto the bridge call. There is no operating model that grants it, no accountability matrix that confers it, no title that survives first contact with a severity-one incident. The invitation is earned in increments, in the field, long before the phone rings.
Every organisation has two org charts. The one on the intranet, and the one that assembles on a bridge call at midnight. Only one of them tells the truth about who is trusted.
The EA was on the first one.