TL;DR.
Fortress Legacy
They were standing at opposite gates of the same fortress, each accurately reporting the weather on his side.
From outside, the wall looked newly climbable because execution had become cheap. From inside, the corridors looked expensive because coordination still had to be paid for in meetings, memory, trust, and signatures.
The wall is not the code.
The code is merely visible stone. By coordination structure, I mean the tacit, undocumented logic by which people, routines, judgment calls, and local exceptions actually get work done.
The founder could ship a function and then discover the next constraint from live use.
The bank would have to ship a committee before it shipped the function, because in a bank the committee is not overhead. It is where many buried promises still have legal names.
I could see three rational moves.
You can patch the fortress and learn where AI is genuinely useful. You can selectively rebuild rooms whose shape was dictated by scarce expert labor. Or you can grow something outside the wall, fund it, buy it, or at least study it before the parent institution teaches it to speak in meeting minutes.
This is why software moved first.
Not because programmers are braver or cleaner people, though some will happily imply both, but because code is unusually checkable. Tests fail. Builds fail. Pull requests leave tracks. When Anthropic launched Claude 4 on May 22, 2025, it pointed to Rakuten's seven-hour Claude Code run less as a circus trick than as a proof that long machine execution can be made boring when the checking machinery is strong. The exciting part was not autonomy. It was bounded autonomy with a red pen nearby, awake, the whole time.
Quick Synthesis
“Fortress Legacy is the moat that became the floor plan, and then started charging admission to anyone trying to redraw the house.”
Generated by Intelligence Unit
AI-synthesized from article content