Core42 - hold to the SOW: stock Kubernetes plus Fuzzball before Oct 31, no CIQ-installed CozyStack, technical pushback routes to Peter

October 23, 2026 at 10:55 PMstrategyhigh

Situation

On 10/23 Core42 took Fuzzball out of the Oct 31 plan (no Fuzzball before deployment, look at it together later). Peter refused to let CIQ become a pure system integrator. As soon as the network is up, CIQ installs Ascender and Fuzzball; if Kubernetes is not there, CIQ installs stock K8s for Fuzzball to sit on, without CozyStack, and Core42 can add CozyStack later. Any pushback from Maxim or Sergei gets the scripted SOW answer (after consultation with Core42 engineering we have been told to follow the SOW; Fuzzball is an integral part of the CIQ stack and does not affect any other Kubernetes offering), and technical pushback routes to Peter. Builds on the 10/22 Ryan 1:1 where Peter made stock K8s plus Fuzzball plan A. The stock-K8s-then-Fuzzball shape was proposed by Bjorn; Peter adopted it and owns the engineering plan and the pushback routing.

Reasoning

Installing none of CIQ software breaks the commercial thesis of the deal; once customers are onboarded nobody installs Fuzzball. The SOW, backed by Alex Trafton note that deviation needs Core42 signing authority, lets CIQ hold the line without debating technology with people who do not want CIQ there. Fuzzball runs on stock K8s today and not on CozyStack, so installing stock K8s removes the dependency on Core42 internal disputes. Routing technical pushback to Peter keeps engineers out of the political argument.

Additional Context

Peter confirmed the hypothesis as presented.

Observed Evidence

Slack 10/23: system integrator quote; route technical pushback to me; stock K8s without CozyStack; scripted SOW response; Alex Trafton note that the SOW cannot be deviated from without Core42 signing authority. Ryan 1:1 10/22: plan A is stock K8s plus Fuzzball.

Matching Patterns

55%
Promise Only What Is Inside CIQ Control(handoff commitment conditional on network)
50%
Reclassify to Route(technical pushback routed to Peter, contract question to Bjorn and Adam)

Confidence Breakdown

33/35
Evidence
15/30
Pattern
18/20
Source
14/15
Corroboration

Reasoning Depth Analysis

Org Signal:CIQ holds contractual scope under deadline pressure
Who Affected:Wolfgang and Wolford team install sequence; Bjorn and Adam account conversation; Ryan plan of record
Precedent:In a politically divided customer, the SOW is the shield
Consequences:Real - Fuzzball either lands before Oct 31 or the deviation is on Core42 record
Timing:Core42 announced the change on the 10/23 morning call, eight days before the date

Source

reflection

AI Confidence

80%

Related Context

💬
#core42-build-and-deploy

slack

Now we are not installing ANY of our software and are just a system integrator, which is what we said we were not going to do/be.

💬
#core42-build-and-deploy

slack

After consultation with Core42 engineering, we have been told to follow the SOW. Fuzzball is an integral part of the CIQ stack.

🎥
Ryan <> Peter Weekly 1:1

fathom

They want off-the-shelf Kubernetes. Fine. I would make that our plan A ... It will not run on top of CozyStack right now. So we are not going to install that.

Outcome

No outcome recorded yet.

Decision ID: 3af634e9-49a8-4ad5-a45c-4fa1ab571f3d