Hold the Google 6.18 image as contract leverage - nothing ships to Google without Peter say-so

Situation

Both 6.18 kernels (default and minimal) were built and validated by 7/17, but Peter instituted a delivery-control gate: no kernels go to Google without his explicit say-so, and delivery-timing questions route to Kelly Hall. The build is done; the only remaining gate is contractual, so CIQ holds the finished image as leverage until GDC signs and resolves the outstanding payment. The ultimate release decision Peter deferred to Bjorn and Kelly.

Reasoning

Engineering did the work six months ago in good faith on the expectation Google would sign a contract, which they have not. The leverage that actually moves Google is withholding the thing they now urgently need. Peter kept himself as the single control point so the negotiating posture could not leak or be undercut by an eager engineer, and routed comms through Kelly to keep one voice. He deferred the final release call to Bjorn and Kelly because the remaining decision is commercial and contractual, not technical - his lane is technical confidence plus the control gate, theirs is the money.

Additional Context

Peter confirmed the loggable decision is the say-so control gate itself (his own act), distinct from the 7/9 decision to slip delivery for CVEs. ~400K SOW plus a disputed 300K ELTS bill. Peter also told the kernel team not to attend Google request to validate the numbers - Here are the numbers, sign it yes or no.

Observed Evidence

7/15 group DM: nobody gives kernels to Google without my say-so; let Kelly respond on delivery time. 7/17 #google: holding off on image until Monday. 7/20 Kelly DM: I would wait till you get these resolved; open to releasing if you and Bjorn tell me to. Fathom 7/17: Here are the numbers, Google. Sign it yes or no.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis