Chapter 08 / 20
8. Architecture & Technical Strategy: Can We Change and Undo Safely?
Provisional draft. These short chapters are not approved for publication. Original practitioner interviews, deeper reporting and author review remain outstanding.
A new engineer can find the source code for a service. Can they find who owns it? Can they run the tests with ordinary access? If a release harms users, can they say what rollback would reverse and what it would leave behind? An agent with broad repository access faces the same missing map, plus the ability to act on a mistaken guess at scale.
Rippling's code-ownership account describes a catalog connecting code paths to teams and on-call channels. Infrastructure engineers reportedly found an on-call rotation in about 30 seconds after adoption. This supports easier owner discovery in that setting, not a measured first-day success rate for new hires. A catalog can be accurate and still fail to say how to test a service or reverse a migration.
AI can help explain an unfamiliar code path, propose a bounded refactor, or draft an architecture decision for human scrutiny. It cannot give an old dependency the rollback semantics it never had. The non-AI work may be more valuable first: establish owners, reduce coupling, make test commands reproducible, document data migrations and external side effects, and rehearse recovery. Then an AI assistant has context worth retrieving and an engineer has a way to check its advice.
Decisions about architecture should name the trade-off. A shared platform might make many changes easier but raise the cost of a failure that affects everyone. A migration may reduce maintenance effort while temporarily raising operational risk. Write down the alternative considered, the verification plan, the cutover owner, and the stopping condition. Revisiting that decision when facts change is a sign of maturity, not evidence that the first decision was careless.
At the junction: Run a consensual tabletop exercise with someone new to a service. Give them a service name, not the veteran's phone number. Observe the first broken link, unavailable credential, stale owner, failed test, or unclear rollback step. Do not ask them to perform an unapproved production rollback. Fix the path before granting an agent the same permissions.