Route the RLC-AI latest-driver override through Bjorn rather than overrule Dawson in the public channel

September 11, 2026 at 3:03 PMoperationalmedium

Situation

Peter pushed in #product-rlc-pro-ai that RLC-AI should not sit on an LTS NVIDIA driver, told Brian Dawson to have a conversation with Bjorn that day because Bjorn wanted to go out with benchmarks on Tuesday, and stated that if CIQ is bundling LTS driver versions it should NOT be going out with benchmarks. He then took the resolution off the public channel: in the group DM with Nathan Blackham and Brett Mastbergen he wrote that he had talked to Bjorn, that the team should get moving on the latest driver in RLC-AI right now, and explicitly that he was not putting this in the public channel because he did not want to publicly defang Dawson - Bjorn would talk to Dawson and the team would see a note greenlighting it.

Reasoning

The technical answer was already settled in Peter head - an AI product cannot ship on an LTS driver, and the contract with NVIDIA is for latest. What was in play was not the answer but who would be seen to deliver it. Overriding Dawson in the channel he owns would have cost Dawson standing with the engineers for no gain, so Peter got Bjorn - the Product authority Dawson actually answers to on launch content - to carry the same decision publicly while Peter unblocked the engineers privately. The engineers get to start immediately, and the public record shows Product deciding rather than Engineering overruling Product.

Additional Context

This extends the Sept 7 decision to stay current on NVIDIA drivers and never ship RLC-AI without the latest. The new element is the routing choice: Peter separated the instruction to engineers from the announcement to the org, and paid the cost of a two-step to protect a direct-adjacent leader.

Observed Evidence

Direct quote naming the reason for the channel choice - not wanting to publicly defang Dawson - plus the public-channel message that set up the Bjorn conversation and the DM to Bjorn supplying the contract argument.

Matching Patterns

45%
Small Circle for Sensitive Operations(deliberately narrows the audience for the decision, executes quickly in private while the public version is arranged)
40%
Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict(names the owner of the lane - Bjorn on launch content, supplies the criterion, no benchmarks if we ship LTS drivers)

Confidence Breakdown

35/35
Evidence
22/30
Pattern
20/20
Source
14/15
Corroboration

Reasoning Depth Analysis

Org Signal:Signals that Peter will protect a leader standing in public even while overriding their technical position in private, and that Product owns what goes out the door while Engineering owns what gets built.
Who Affected:Dawson, who never had to absorb a public reversal. Bjorn, who was handed the announcement. Nathan and Brett, who got permission to start without waiting for the public note. The engineers reading #product-rlc-pro-ai see a Product decision, not an Engineering fight.
Precedent:Establishes that a disagreement with Product gets resolved leader-to-leader and lands publicly as a Product decision, which makes future overrides cheaper to run and less damaging to the person overridden.
Consequences:Real: work started before the public greenlight, and the benchmark announcement content changed as a result.
Timing:Now because the Tuesday announcement was imminent - waiting for a clean public process would have meant either announcing benchmarks on an LTS driver or missing the date.

Source

reflection

AI Confidence

91%

Related Context

💬
Group DM with Nathan Blackham and Brett Mastbergen

slack

Talked to Bjorn. Let us get moving on getting latest driver into RLC-ai right now. I am not putting this in the public channel because i do not want to publicly defang Dawson. Bjorn will talk to him shortly and I am sure you will see a note from him soon greenlighting this.

💬
#product-rlc-pro-ai thread

slack

You need to have a conversation with Bjorn today. He wants to go out with benchmarks, on Tuesday. Agree on what the goal there is. IF we are bundling LTS versions of the driver, we should NOT be going out with benchmarks.

💬
DM with Bjorn Hovland

slack

And the agreement with Nvidia is for latest is my understanding. So there is that too.

Outcome

No outcome recorded yet.

Decision ID: ef4184d4-28a4-47d5-8157-d3a60e459474