Four layers, and someone to run them.
Every engagement opens with a public-surface review — non-invasive, permission-first, and the thing that scopes and prices whatever follows. None of the four requires the others. Take what you need.
The layer your users touch: auth and session edges, roles and permissions, exposed data paths, and the surface your integrations and AI agents open up.
See what gets reviewed → H.02What it all sits on: cloud access and blast radius, deployment and rollback safety, secrets and environments, backups, recovery, and observability.
See what gets hardened → H.03For data that is not yours to send: data boundaries, private inference, dedicated GPU capacity, and internal assistants that respect the permission model.
See what gets designed → O.01What the other three leave behind: uptime and incident response, backups proven by restore, releases and documentation, and one monthly account of what changed.
See what continues →