Yes to anointing Andrew NARF tech lead - but Max confers it, so it does not set a precedent that the CTO blesses tech leads
Situation
Max proposed formally naming Andrew tech leader for NARF with full review and merge authority. Peter interrogated why Andrew could not simply claim it, and Max explained Andrew is afraid of stepping on Maxs toes and needs to be told it is his ballgame. Peter approved - we will say yes to this - while stating plainly that he does not personally believe in the anointed tech lead model. He then separated the approval from the ritual: on learning Max could confer the title himself, Peter routed the naming to Max specifically so the org would not learn that authority flows from a CTO blessing. Max will speak to Andrew before their Thursday 1:1.
Reasoning
Peter approved a model he does not hold because the argument came from a domain where he conceded he lacks standing - I do not have a history in Linux the way you do, I do not understand the people and the culture that has been generated for the last 30 years, and I cannot change that culture. Max argued the Linux world runs on benevolent dictators and people must know who the final decision maker is. Peter accepted that on Maxs authority. What he objected to was never Andrew getting authority - it was the precedent of Peter Nelson needing to bless somebody. Having Max confer it makes it a handoff of Maxs own project, which is why it transfers - they will take it from you, because it was yours - without creating a queue at the CTOs door. Peter also accepted a share of the blame out loud: my problem is a Peter-created problem of I am not creating the right environment. The generalised takeaway he drew was broader than Andrew - where Max is taking point and proving things out, handoffs must be aggressive and intentional rather than assumed.
Additional Context
Peters own model is the opposite - find somebody doing the thing you want done and shine lots of sunlight on them rather than put a fancy hat on them. He also wants Maxs vision still plugged into NARF as strategic approver while Andrew runs it day to day, which is why Max was hired to be a catalyst rather than a maintainer. Peter confirmed this reading as correct.
Observed Evidence
Direct quotes across the full arc - the objection, the approval, and the explicit routing of the naming act to Max to avoid the precedent.
Matching Patterns
Confidence Breakdown
Reasoning Depth Analysis
Related Context
fathom
Cards on the table. I will do the TLDR first. We will say yes to this. We will do it this way. ... I am not a massive believer in the anointed tech lead model, but I come from a different world than you do.
fathom
What I am worried about is sending a message to the company, sending a message to the engineering org of Peter Nelson needs to bless somebody being the tech lead. ... Peter: Do I need to do that? Max: No, I can do it. And then it does not set a precedent that you have to deal with.
Outcome
The mechanism held exactly as designed - Max recommended it in his own doc and the Aug 3 announcement had him handing over stewardship, so no CTO-blesses-tech-leads precedent was set. But the underlying work got worse: NARF Peridot-to-Release dropped 12 points to 70 percent and slipped to Aug 21.
Rating: 3/5
Decision ID: d99e09fd-4e6b-4863-a88f-031d28ea6e1a