Jamie Brooks
Jan 12, 2026 - May 12, 2026
4
Decisions
0
Active Todos
3
Patterns
Categories
Decisions (4)
CVE response strategy — three-pillar overhaul (process + tooling + strategic kernel review)
In Engineering Weekly Sync, Peter operationalized the 5/11 Leadership Roundtable vuln-handling commitment into three concrete pillars: (1) Chris Baek to restructure the embargo/CVE comms doc with Jamie, separating process from tooling/templates; (2) tooling strategy — Peter commits to email Greg requesting Claude Opus 4.7 whitelist for CIQ accounts AND to set up unbridled internal LLM models on Fuzzball for vuln investigations; (3) schedule strategic kernel philosophy review for early June, with Nathan and Justin to provide a list of downstream automation efforts to prioritize.
Ryan to POC AI-driven Veeam image builder, gated on Justin-approved test suite
Ryan will POC an AI-driven image builder, starting with Veeam, that automates custom image builds, testing, and documentation. Hard gate: AI-generated images must pass a Justin-approved test suite to prevent hallucinations. Long-term vision: a 'Chipotle line' image configurator letting users compose custom, repeatable builds from validated components.
Google Scope Change - Hold the Line on Commercial Terms
Decided to personally join the Monday lunch meeting with Tissa to lead negotiation on Google scope change. Google was trying to bundle Rocky 8 and 9 into one version (reducing from 8 to 5 versions) and push release next format without updated commercial terms.
Google Scope Change - Hold the Line on Commercial Terms
Google is pushing scope changes that bundle 8 versions into a 5-version contract, omit EOL dates, and include undefined dev streams. This creates scope creep risk and jeopardizes the Extended LTS revenue stream (~$300k/year per product). Decision to personally attend the Monday meeting with Tissa (with Max) to hold the line. Greg will NOT attend to preserve escalation path.
Related Patterns (3)
Executive Sponsorship for Strategic Partnerships
Strategic cross-company initiatives and major client partnerships require executive-level accountability to move at the right pace and ensure proper prioritization.
Small Circle for Sensitive Operations
When executing sensitive strategic operations, keep the circle of informed people as small as possible to prevent leaks that could accelerate hostile action or undermine the initiative.
Protect Engineering Capacity
When external demands threaten to overload engineering capacity, protect capacity by either requiring the demand to come with additional resources, or forcing hard prioritization choices upstream.