Core42 Kubernetes - never let anyone at Core42/G42 say CIQ cannot do Kubernetes; ask questions only, route Stratum to Bjorn

October 21, 2026 at 5:23 PMstrategyhigh

Situation

After a Core42 email raised Kubernetes questions, Peter set the posture: answer with capability (extensive K8s experience, a K8s offering in a month, able to configure or work with any K8s cluster); present Stratum as an option while saying off-the-shelf K8s is fine if required; do not tell Core42 what is unsupported, ask what they are trying to accomplish; stand nothing up; no engineer-to-engineer resolution - anything Stratum-shaped goes to Bjorn and their customer-facing people. On 10/21 he applied it by asking Sergei for a call with the CIQ Kubernetes team to learn whether they want CozyStack and why.

Reasoning

Core42 teams are jockeying for position, so a technically accurate engineering remark (CozyStack unsupported, not doing K8s here) becomes ammunition and can close the Grenoble Stratum door. Iris bought Fuzzball, not Stratum; whether Stratum should be in play is a commercial call in Bjorn lane. Engineering must not let a true sentence foreclose it.

Additional Context

Extends the 9/25 rule of no new commitments until end-customer discovery with its inverse - no new denials either. Brian Dawson framed the same guidance in the call: assume we support anything, question to understand, do not replace their proposed solutions. Applied 10/21 (Core42 call 194812267): Peter declined Ryan proposal to stand up CozyStack against Fuzzball that day - understand the context before spending senior people time - and told Bjorn Iris will not be the first Stratum deployment, because the first Stratum deployment is going to fail; Bjorn agreed.

Observed Evidence

Any time this comes up, the answer is not we are not doing that here, it is let me put you in touch with our Stratum people, then route it back to Bjorn. I do not want engineer talking to engineer. 10/21 to Sergei: whether you WANT CozyStack or it is just what you are familiar with.

Matching Patterns

65%
Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict(Stratum question routed to Bjorn, criterion not verdict)
35%
Promise Only What Is Inside CIQ Control(ask rather than commit or deny)

Confidence Breakdown

32/35
Evidence
20/30
Pattern
19/20
Source
13/15
Corroboration

Reasoning Depth Analysis

Org Signal:CIQ engineers on Core42 calls act as company representatives, not individual experts
Who Affected:Bjorn owns any Stratum conversation; Ryan team and Wolford stop at questions
Precedent:In a politically contested partner org, capability claims flow up and denials do not happen
Consequences:No technical work committed; discovery call with Sergei is the next step
Timing:Grenoble Stratum evaluation landed the same week as the Kubernetes questions

Source

reflection

AI Confidence

84%

Related Context

🎥
Core42 Deployment Follow-up 10/20

fathom

I do not want anybody within Core 42 or G42 saying to somebody else, CIQ cannot do Kubernetes. I just do not want that sentence uttered.

📧
Re: Points raised by Max on the Approach (to Rohit)

email

We have extensive K8s experience on the CIQ team (and will have a K8s offering available in a month). At any point, we are technically capable of configuring or working with a K8s cluster.

💬
#core42-build-and-deploy

slack

make clear that Stratum deployment is an option, but if required we can work with off-the-shelf K8s and are expert there.

🎥
Core42 impromptu call 10/21

fathom

Our first deployment of Stratum is going to fail. Do you want this to be our first deployment of Stratum?

Outcome

No outcome recorded yet.

Decision ID: 8f18359b-b704-4bb2-a416-cea53f27e117