How to build an Agent policy
Agents need a policy. Don’t reinvent governance. Apply what you already do with people: review, limit, escalate, grow trust. Reality begins not when the model speaks, but when it starts doing.
AWS feels different. Here’s how that changes my approach.
Something has changed in how AWS absorbs mistakes. Benevolence hasn’t disappeared, but it’s no longer where many practitioners expect it. This essay examines what happens when discretion moves into systems, contracts become the floor, and old assumptions stop holding.
FinOps tools are consolidating: Flexera–ProsperOps, DoiT’s buying spree, and the platform endgame
FinOps tooling is consolidating into CloudOps platforms. Flexera buys ProsperOps (vertical execution) and Chaos Genius (horizontal data scope). DoiT is buying across Kubernetes, security and Snowflake. PE speeds change. Policy turns intent into action; plan for vendor risk. Next: AWS 'normal' era...
FinOps wants to become a discipline, but most teams are still a heroic side quest
Cloud cost management won’t scale as a heroic side-quest run by one FinOps practitioner. Borrow proven management systems, give FinOps a mandate, and add programme management so dashboards turn into decisions, and decisions turn into delivery.
The Shape of Top-down FinOps
FinOps fails when it starts at the bottom.
Top-down FinOps ties every optimisation to strategy: leadership sets intent, platform allocates time, managers put work in the backlog, and engineers deliver with recognition.
That is how cloud savings become real impact.
(paid) Graph clarity toolkit
Why architecture fails to impress executives, and how the FC method solves it
Most architecture diagrams fail because they show components, not meaning. The FC method fixes this by mapping use cases and shaping components by cost, revealing how value flows, where money goes and how intent becomes architecture, risk and spend.