Put the Core42 deployment on Ryan org to resource - Nathan stays advisor and the unfilled Forward Deployed Engineer goes on the contract list

Situation

While assembling the supported-contacts list for the Core42 contract, Nathan Blackham asked Peter whether he knew who from Ryan Smith team he wanted on it or whether Nathan should reach out to Ryan himself. Peter answered by pointing at the unfilled role first: He is hiring a new guy specifically to do work like this. So we definitely put down an entry for the Forward Deployed Engineer TBH. And then anyone else you want from Ryan world is fine - you have the pick of the litter. Nathan then reminded him of an earlier commitment - And remember when you told me that the deployment management was not going to be on my list.... - and asked whether Ryan himself should get access or only engineers. Peter drew the boundary explicitly: Definitely add Ryan. He will be tasked with the bulk of this work is the plan. You will be there as advisor. But I do not want you getting sucked into managing this. So do not pack the list with your folks either. LEt ryan spend resources as much as possible.

Reasoning

Peter is making the Aug 24 forward-deployed org design load-bearing on its first live contract rather than letting it stay a plan. He put the role under Ryan because support is the org built as a funnel that absorbs deployment fallout, and staffing Core42 out of Nathan org instead would have quietly undone that decision on the very first deployment - which is also the prototype for clusters two through fifty. The second half is capacity protection with a specific target: Nathan is the Core42 technical brain, so the pull to let him run the deployment is strong, and Peter capped him at advisor the moment Nathan surfaced the earlier promise rather than renegotiating it. The instruction not to pack the list with Nathan people is the operative constraint - without it the advisor framing survives on paper while the work still lands in Linux Engineering. Putting a TBH entry on a real customer access list is a forcing function on the requisition, making the unfilled role visible against a live contract instead of a headcount plan.

Additional Context

Confirmed by Peter during the 2026-08-31 reflection. Same hour as the Core42 timeline decision and the joint Core42/NVIDIA customer call, so resourcing was settled before the delivery clock started. On the same impromptu call Bjorn Hovland had committed Scott Shinn, Michael and Jimmy to pre-deployment work and said he would keep it a Scott and Jimmy problem for as long as possible until a signature.

Observed Evidence

Nathan: Do you know who all from Ryan team you want on the Core42 contract, or do I need to reach out to Ryan? Peter: He is hiring a new guy specifically to do work like this. So we definitely put down an entry for the Forward Deployed Engineer TBH. And then anyone else you want from Ryan world is fine - you have the pick of the litter. Nathan: And remember when you told me that the deployment management was not going to be on my list.... / Also should I be adding Ryan for access or just engineers? Peter: Definitely add Ryan. He will be tasked with the bulk of this work is the plan. You will be there as advisor. But I do not want you getting sucked into managing this. So do not pack the list with your folks either. LEt ryan spend resources as much as possible.

Confidence Breakdown

Reasoning Depth Analysis