Attack the live-patching gap through Google co-development as a paid deliverable while keeping the req open - buy the timeline, do not just wait for the hire

Situation

In the 2026-08-25 Exec Product Prioritization session Peter named kernel live patching as his single biggest capability gap, and said he does not need more heads beyond the requisitions already open to deliver the top of the board - with live patching the exception. Rather than waiting on that hire, he took a 5:15pm sync with Tissa Senevirathne at Google the same day, scoped specifically to whether Google can accelerate the live-patching timeline and whether it can be added as another paid deliverable to the existing engagement. He described the approach to Chris Baek and Bjorn Hovland as throwing co-development options at the wall to see what sticks. The Rex requisition stays open, so this is an additional path rather than a substitute for the hire.

Reasoning

Peter confirmed this reading. Live patching is one of only two or three genuinely net-new Linux items Bjorn Hovland identified as marketable - almost everything else near the top of the board is commercial baseline that CIQ gets dinged for not having rather than credited for shipping. A hire closes the gap on a hiring timeline; partner-funded co-development closes it on a customer timeline. The leverage is that Tissa own timelines flat out do not work, so the party who needs it soonest is also the party who can fund the acceleration. Running both paths at once means the gap closes on whichever timeline arrives first.

Additional Context

Peter was separately confirming with Tissa by email that the Google GDC deployment targets for the Rocky builds include NVIDIA Grace Blackwell GB200 and GB300 nodes, explicitly so he can use that when asking NVIDIA for support and test hardware. Kernel live patching sits at roughly number 18 on the product board as one of the first items Bjorn described as a shiny whistle he gets to talk about publicly.

Observed Evidence

Peter named the gap unprompted in the product session and tied it in the same sentence to the Tissa meeting that evening; he had already scoped that meeting to live patching and to a paid-deliverable framing in Slack that morning. The calendar entry confirms the meeting occurred.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis