Rule the Toyota kernel patch a feature not a bug; no automatic queue jump, escalate through normal priority

July 10, 2026 at 3:13 AMoperationalmedium

Situation

Nathan flagged a Toyota/Yoshi request (relayed via Art/sales) framed as a bug fix. Peter ruled it is a feature, not a bug, so it does not automatically jump the engineering queue on the bug argument. Support may still be offered, but the bug framing is off the table. If the business wants it prioritized it must go through normal escalation and trade-off (Peter + Bjorn), not a backdoor via mislabeling severity. Reinforced later the same day in the Ryan 1:1 (Peter rebuked Art for taking the bug-vs-feature fight to engineering).

Reasoning

Defends the integrity of the prioritization process: a bug gets fixed automatically, so relabeling a feature as a bug is a way to skip the line, and Peter is closing that loophole. Keeps the priority question where it belongs, as a business trade-off Peter and Bjorn own, rather than letting a technical-severity mislabel dictate resourcing. Still willing to support the customer; this governs how the work is prioritized, not whether the customer is helped. Especially costly to allow queue-jumping during the live 0-day CVE crunch.

Additional Context

Confirmed by Peter with no correction. Connected to the same sales-driven kernel-ask pattern seen with Rakuten and Everfox.

Observed Evidence

Nathan 1:1: just tell them it is not a bug fix, take that off the table; we may still offer support. Ryan 1:1: Linux has decided this is not a bug, we are not going to undo that.

Matching Patterns

40%
Protect Engineering Focus Through Process(force asks through the process, protect the queue from out-of-band demands, same category)
32%
Resource Optimization Through Triage(prioritization trade-off, cost-benefit gating)

Confidence Breakdown

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

Reasoning Depth Analysis

Org Signal:You cannot game engineering prioritization by renaming your request; severity labels will not be a backdoor to resourcing.
Who Affected:Sales and all customers making severity-framed kernel asks (Rakuten/Everfox pattern); Bjorn as the co-owner of the priority call.
Precedent:Sets a durable rule for how sales-driven feature-vs-bug disputes are adjudicated.
Consequences:Real: the ask is removed from the automatic-fix path; it survives only if the business escalates it as a priority trade-off.
Timing:During the 0-day CVE crunch, queue-jumping is especially expensive, so closing the loophole now protects the critical-path work.

Source

reflection

AI Confidence

78%

Related Context

🎥
Nathan <> Peter (Impromptu Zoom), 7/9

fathom

So you just tell sales, no, this is not a bug fix... just tell them, hey, I have talked to Pete. It is not a bug fix. We may still offer support, but take that off the table.

🎥
Ryan <> Peter 1:1, 7/9

fathom

I smacked Art down... Linux has decided this is not a bug. We are not going to undo that here because you think it is a bug.

Outcome

No outcome recorded yet.

Decision ID: 9212ffb0-89e9-4862-8e70-e71cb6cfed0c