GDC full kernel with IBT off is not just sign the kmod - say no unless it fits, do not reopen the contract, Peter and Kelly own the Tissa conversation

October 30, 2026 at 7:16 PMstrategyhigh

Situation

On 10/29, with the GDC contract about to be signed, Google asked for a 6.18 full kernel with IBT off for the following week. Peter framed it in #google-partnership-governance: the ask pushes CIQ from just sign our kmod into supporting kernel development, which CIQ told Google it must staff up for and is still hiring for; it falls back into the CIQ needs to do the live patching work bucket and cannot be delivered in a couple of days. If Justin path works, fine; otherwise the answer is no. He told Nathan he did not need to manage the contract, stopped the engineering thread (Let us spend no more time on this and Kelly and I will talk to Tissa), and refused to change the order of anything or reopen any question while the contract was being signed. He emailed and then called Tissa; Tissa dropped the full-kernel requirement, and Peter confirmed in writing the plan is the minimal kernel with IBT disabled for next week, with Kelly, Nathan and Justin on the thread.

Reasoning

The kmod-signing arrangement was Google own shortcut around CIQ staffing constraint; an ask that reaches past it is new kernel work and must be named as such, not absorbed. Holding the line protects the near-signed contract and the commercial ladder (live patching gets priced and staffed). Peter takes the commercial conversation himself so engineers are not negotiating scope, and resolves it by finding what Google actually needs (minimal kernel only) rather than by saying yes to the stated ask.

Additional Context

Continuation of 9/25 (no live-patch work before Google pays) and 10/1 (near-zero-cost flags only before commercials). Peter also asked Kelly how much the contract grows year over year to size how material the ask is.

Observed Evidence

Slack: We need GDC to realize that the things they are asking push this from just sign our kmod into supporting kernel development. / If Justin path works, fine. But otherwise we tell them no. / Nathan - you do not need to manage the contract. / Let us spend no more time on this and Kelly and I will talk to Tissa. Email to Tissa: Minimal kernel + IBT disable is the plan.

Matching Patterns

65%
Promise Only What Is Inside CIQ Control(scope held to what CIQ can deliver, same customer)
65%
Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict(reclassified ask as kernel development not kmod signing)

Confidence Breakdown

33/35
Evidence
26/30
Pattern
19/20
Source
13/15
Corroboration

Reasoning Depth Analysis

Org Signal:Engineering does not negotiate contract scope with the customer; commercial pushback routes to Peter and Kelly.
Who Affected:Nathan and the kernel team (protected from unscoped work), Kelly (contract close), Google GDC engineers.
Precedent:Any Google ask beyond the kmod-signing shortcut is classified as staffed kernel work and priced, not absorbed.
Consequences:Real: the full-kernel work is off the table for next week; minimal kernel with IBT disabled ships Monday.
Timing:The contract was within a day or two of signature; reopening scope then risked the close.

Source

reflection

AI Confidence

91%

Related Context

💬
#google-partnership-governance

slack

we need to tell Tissa that this falls back into the CIQ needs to do the live patching work bucket and cannot be delivered in a couple of days

💬
#google-partnership-governance

slack

We are trying to get them to sign a contract as we speak. Do not want to change the order of anything or re-open any questions.

📧
Re: Full Kernel with IBT off

email

Verified with the team here. Minimal kernel + IBT disable is the plan. We are aligned then.

💬
#google-partnership-governance

slack

Talked with Tissa. They are dropping the full kernel requirement. Just minimal kernel with IBT disabled for next week. Done.

Outcome

No outcome recorded yet.

Decision ID: 4a330287-b3f8-4cad-a969-67c9cfd51f15