Everfox desktop-OS: require explicitly scoped and funded eng-investment before supporting the deal

June 30, 2026 at 2:34 PMstrategymedium

Situation

On the Everfox desktop-OS deal, Peter framed it as a fundamentally different business (be like Ubuntu while also being like RedHat, not add desktop support to Rocky) and insisted the unknowns around hardware enablement / driver support and a dedicated lab be made explicit. His engineering-side conditions: the MSA must fix the hardware scope with out-of-scope hardware priced separately, and CIQ should proceed only with an explicit commitment to fund the engineering regardless of revenue. He tasked Max to assess technical feasibility with Nathan before committing. Relates to the prior logged Everfox decision d1ea8ed9; this is the engineering-stewardship condition layer.

Reasoning

The deals danger is not the revenue but opening a second front against Ubuntu that diverts the org from the core Red Hat competition. So Peters move is to make the cost visible and bounded before anyone commits: fixed hardware matrix, separate pricing for the rest, explicit engineering-investment sign-off. This is his standard protect-engineering-capacity plus scope-discipline posture on deals (same family as the Rakuten margin line and the Computex production-ready gate): he does not block the deal, he refuses to let engineering absorb undefined scope.

Additional Context

Deal ownership is Bjorn/sales lane; Peters loggable contribution is the engineering-stewardship condition, which is his lane. Related to existing decision d1ea8ed9.

Observed Evidence

Peter group DM: This is a Giant strategic question... we are trying to build an offering to compete with RedHat. This effort is essentially also compete with Ubuntu... It is not add desktop support to Rocky. It is be like Ubuntu, while also being like RedHat. Peter: My concern is the driver support. Nathan: if we have commitment that we are willing to spend the cost for engineering regardless of revenue, then I am willing to support the deal. Peter: Agreed. Everfox call: MSA must define fixed hardware scope; out-of-scope priced separately. Max 1:1: Max to assess Everfox feasibility with Nathan.

Matching Patterns

62%
Route Non-Differentiating FTE Classes to Partners(scope/cost discipline on deal, but core not routable here)
40%
Protect Engineering Capacity(guard against unbounded second front)

Confidence Breakdown

24/35
Evidence
18/30
Pattern
12/20
Source
12/15
Corroboration

Reasoning Depth Analysis

Org Signal:Engineering will not absorb undefined scope; a desktop-OS deal is a distinct business that must be explicitly funded and bounded.
Who Affected:Bjorn/sales (deal + pricing), Nathan (feasibility/risk), Max (feasibility assessment), Suzanne/Ramesh (MSA + alignment).
Precedent:Reinforces scope-discipline-on-deals: fixed scope in the MSA, out-of-scope priced separately, explicit investment sign-off (Rakuten/Computex family).
Consequences:Protects the core Red Hat competition from a second-front Ubuntu distraction; gates support on funding commitment.
Timing:Now, as the deal nears final stages and Everfox awaits CIQs written response.

Source

reflection

AI Confidence

66%

Related Context

💬
Everfox group DM + Everfox LOE call (6/28-6/29)

slack

Peter: this is a Giant strategic question; it is be like Ubuntu while also being like RedHat, not add desktop to Rocky. Concern is driver support. Proceed only with commitment to fund engineering regardless of revenue; MSA must fix hardware scope, out-of-scope priced separately.

Follow-up Todos

Suggest follow-up todo

Have Max assess Everfox desktop-OS technical feasibility with Nathan before committing

@Max

From: Max <> Peter 1:1 (6/29). Determine whether HWE/driver support is effectively free via the CLK kernel or a major new investment.

Why: The Everfox deal could open an unbounded second front against Ubuntu. Feasibility must be known before CIQ commits engineering, or the team absorbs undefined scope.

Outcome

No outcome recorded yet.

Decision ID: 4f38e9b1-e4d3-46e0-8420-1b09f41838c6