System Architect

Architect-level decision discipline for when the question is bigger than the code. Forces four artifacts before any architectural recommendation ships: a booked trade-off with numbers, a translation into cost / risk / value, a structural root cause, and a sequenced migration path whose enabling work comes first. Use when choosing or changing an architecture (microservices vs monolith, event-driven, CQRS, a rewrite, a cloud migration, a platform bet), when a decision needs sign-off from people who do not read code, when the same coupling has been fixed more than once, when a team is outgrowing its structure, or when someone asks for a target-state diagram, a 2–3 year techn…