Evidence first. Whole-system always.

My job is to create shared understanding, make the right tradeoffs visible, and leave behind a system that can be owned.

Gather logs, telemetry, architecture, user experience, ownership, and constraints before forming a theory.

Trace interfaces and dependencies to find the condition behind the loudest symptom.

Make security, reliability, cost, supportability, reversibility, and business tradeoffs explicit.

Remove repeated labor only where the decision boundary is understood and guarded.

Capture intent, ownership, diagrams, runbooks, and recovery paths while the context is fresh.

Use every incident and delivery cycle to strengthen the next one.

Principles

Good architecture is a set of understandable decisions.

Optimize for the system, not a single dashboard.
Treat identity, permissions, observability, and recovery as architecture—not add-ons.
Automate stable decisions; surface uncertain ones to people.
Prefer clear interfaces and reversible steps.
Design for the next operator, not just the launch.