Greg Kurtzer
Dec 22, 2025 - Sep 7, 2026
144
Decisions
0
Active Todos
17
Patterns
Decisions (144)
An ambiguous interview verdict is a no - hold the bar rather than adding interviewers
Steve Wallace reported on the security engineer req that he had interviewed Jared, a contact of Greg, and had told Brianne and Greg that he was not a yes but not a no. Wallace proposed pushing the candidate on to CeeLo or TJ to gather more input. Peter closed it on the spot: not a clear yes and not a clear no means no, leave it as a no. He framed the rule rather than the case - he would rather hold a high bar, and if a candidate is not a giant yes, move on.
Sensitive Decision
Stay current on NVIDIA drivers - build the automation, and do not ship RLC-AI again without the latest drivers
Greg flagged in #distinguished-leaders that the NVIDIA contract obliges CIQ to distribute the latest drivers within 30 days of release, and that CIQ has drifted. Peter took it to Nathan Blackham and Justin Haynes in their group DM the next morning, told both that he had not had the 30-day obligation in his head either, and asked them to put some sort of process in place to stay current. Nathan opened ENGD-839 for the automation; Peter told him to slot it right around where the next RLC-AI drop lands. Separately he told Product the gate plainly: it makes no sense to put out RLC-AI again without updating to the latest drivers at the very least.
Broken-in-production is an automatic fast path - small thing with embarrassing impact jumps the queue regardless of the size of the epic around it
In the 2026-08-25 Exec Product Prioritization session the errata CPE-to-product mapping item had drifted to number 30 on the board. The specific defect was that CIQ was shipping images identified as Rocky Linux when they should have been identified as RLC Pro. Peter moved it into the top ten on the spot. Brian Dawson stopped and asked what criterion drove the move, and Peter generalised it: something broken that we are shipping is an automatic fast path. He bounded it in the same breath - the broader errata epic is genuinely large and stays where it is; only the shipping-the-wrong-identifiers piece jumps, because fixing that piece is not dramatic at all. In the same meeting he pushed the reciprocal direction, arguing that some net-new items should be prioritized above keep-the-lights-on work because a two-month effort sitting at number 34 becomes a six-month effort.
Shut down department-heads as an intake path for engineering work - I raised it to product, they will either ask for it or they will not
In a #department-heads thread about who owns and maintains the C3 RPMs and about hardware certification playbooks, Ryan Smith offered to tweak Gauntlet to run certification playbooks and asked for hardware to be sent to him. Peter cut it off directly: this channel is not how work gets in front of engineering. He restated the path he had actually used - he asked who maintains it, got back currently nobody, and took the follow-up question of whether it should be publicly visible to product, where Brady Dibble owns it. If product asks for it, it becomes a project and gets the right people and the right hardware support.
Sensitive Decision
Accept Bjorn conclusion on the Stratum name while refusing his reason - dont make a decision now that you dont have to make
Naming the new CIQ Kubernetes product. On Aug 23 in the executive group DM, Bjorn Hovland put up five candidates - CIQ Lattice, CIQ Stratum, CIQ Formation, CIQ Maestro, CIQ Marshal. Peter opened against the field with his own pick: my vote is Lattice, Marshal does not fit. Bjorn raised an SEO conflict, that an HR platform already owns Lattice, and Peter switched in one message - Stratum for the win, shrug. Chris Wolford independently backed Stratum and noted Lattice is also Quantum object storage system. Chris Baek started the trademark search. In the Aug 24 Kubernetes sync Bjorn laid out his actual reasoning - that over time he expects to combine the back ends into one and simply route a workload to Kubernetes or Fuzzball, but that is not the world today, so calling it the Fuzzball Kubernetes engine would muddy the waters too early and he needs to run keywords against Kubernetes as a discrete product. Peter agreed with the destination and rejected the route: he gets to the same place for totally different reasons, does not believe Bjorn story about the way the world ends up, and points out that if you do not believe it then you want the thing to have its own referenceable name anyway. Peter also asked that the final form match the naming convention used elsewhere.
Sensitive Decision
Trade a company-wide VP definition to get Greg to ratify the engineering ladder - structure first, names later
In the Aug 24 1:1, Peter walked Greg through the engineering leveling spreadsheet. He deliberately separated ratifying the STRUCTURE from mapping the PEOPLE, saying he wanted Greg bought into the structure and cared much less about the mapping for now. The ladder collapses roughly 27 levels to four IC levels - Engineer, Senior, Principal, Distinguished - plus Technical Fellow retained as a title outside the ladder rather than a level, and leadership reporting to Peter as either VP or Director with no Senior anythings. Greg objected to VP on optics grounds. Peter did not defend the word, he defended the need: I wanted a senior leader and a junior leader title, what we call them I am far less interested in. The two then jointly settled a company-wide convention: VP spans organizations and reports to a C-suite, SVP means junior C-suite where no CXO title is being given, Directors can report to either. Peter committed unilaterally: you will never see me arguing for a VP that does not report to me. Greg accepted, and asked that the ladder not be built in a vacuum but be made cross-applicable and run as an org-wide initiative with Mariah. Peter agreed and took the write-up. They ended at Peter stating they were 85 percent aligned.
Approve the NVIDIA-supported Fuzzball hackathon at SC - with a Wolford engineer on site a day early and a month of hardware notice from NVIDIA
In the L/P Quick Sync on 2026-08-18, Lindsay Aamodt brought the NVIDIA hackathon she has been building - in person in Chicago, Friday November 13 kickoff, build Saturday and Sunday, judging Monday, winner presented in the booth Tuesday as SC opens - and asked Peter to name the risks that would make it a flop in person. Peter approved it and attached conditions: someone who works for Chris Wolford goes on site a day ahead to stand the clusters up, explicitly not Lindsay; and NVIDIA must confirm exactly what hardware they are providing a month in advance so the networking is handled beforehand. He committed himself as a judge alongside Bjorn, Greg and Scott, and Wolford as mentor staying through Saturday.
Sensitive Decision
Ask Greg to take Peter off the RESF directive so it reads as CEO-to-RESF instead of CEO-correcting-his-CTO - and pair it with a standing Lee status cadence
In the 2026-08-18 C-Suite Sync, Greg proposed DMing Peter, Dieter, Lee and possibly Brian to reiterate that more CIQ people need to be involved and that things need to move faster on the RESF side. Peter agreed to the substance but asked to be removed from the recipient list: So yes, but play this game with me. I think if you send that DM to the list of people you said, which includes me, and now I ask myself how I can perceive that from Brian perspective. I can perceive it as Greg telling his employee, Peter, to involve more people, and you are just notifying Brian that Peter has been told. If I am not on the email, and it is just going to Brian and Lee and Dieter, do you see what I am saying? I think you can speak really differently. He asked instead for a copy sent separately - I would just send it directly to them and then send me a copy of it just so I know exactly what you said - and suggested Greg tell them he expects Peter to be receptive to anything they ask. Separately Peter asked Greg to secure a standing status cadence with Lee, explaining that Lee is the one with the broad overview but does not work for Peter in this capacity, whereas Dieter will supply status on request. Greg agreed to have Sarah set up a weekly or biweekly Peter-Lee meeting, and Peter accepted.
Refuse to debate the cause of the Rocky download reversal until the metric itself is validated - either it is the number we track and it warrants attention, or we track a different one
Ryan Smith sent Peter a note that Rocky usage via Fedora DNF count-me stats had reversed for the first time since RESF started, correlating with Alma rise, and that Brian Clemens attributed it mainly to Neil and Lewis leaving with Lewis publicly promoting Alma since. Peter posted the whole note to #distinguished-leaders on 2026-08-18 flagged for the next morning meeting, and rejected the attribution: I do not buy that caused 250k less downloads of Rocky Linux. Something smells funny there. When Greg asked for his gut feeling, Peter declined to give one on causation and reframed the agenda instead: What I want to talk about is whether we believe the number is the number we should be looking at. If we do, then I think it warrants attention. If it does not, then I want us tracking a different numbers. In the C-Suite Sync the same morning he repeated the magnitude objection to Greg and named where the analytics capability should sit - that is what Dieter should plug it into.
Mondays session with the Linux org is universally positive - period, full stop - and any fix-things conversation goes to a separate meeting
Gregs company-wide 1:1s surfaced that the Linux organization - Nathans and Justins teams together - is measurably less optimistic about the future of the company than the rest of CIQ. Not massively unoptimistic, but a clear differential. Peter checked the instrument before trusting it: he watched a couple of recordings of Gregs 1:1s just to make sure that he was not leading the witness and asking the question the same way in all of them, and judged he was doing a pretty good job of it. His response is a Monday session with Nathans team, and he set a hard constraint on its contents. Content: state the finding transparently to the team, then walk them through what he is seeing in the Middle East from his second trip and from the Axiom Space meetings - we are seeing a massive uptick in our ability to do business - then walk them through what dealing with Google over the last week and a half has been like, explicitly attributing his own ability to do it to their groundwork: I got to do that because of the work that your team has done, laying the groundwork, and I want them to hear that, understand it, I want to thank them for it. Constraint: It should be just a universally positive meeting with your team on Monday. Period. Full stop. And I really want it to stay focused on being a universally positive meeting. If there are places where we want to talk about fixing things or tweaking things, that can be another meeting. But I do not want to muddy the message at all. He also gave Nathan the entire rationale in advance rather than staging it - I will say all of this to them, super transparently.
Run a Monday state-of-the-Linux storytelling session on pipeline, and have Baek carry the same rah-rah into the all-hands
Acting on a morale signal that surfaced in Gregs round of one-on-ones, Peter committed to sitting down with the Linux org on Monday to walk them through what he is seeing in the Middle East and with Google. He framed it explicitly as storytelling and cheerleader rah-rah about why he feels so bullish, not as a status update, and asked Chris Baek to sprinkle a little bit of the same into the upcoming company all-hands. He gave the diagnosis comparatively - the Linux org is meh on our future while Fuzzball is gangbusters and Ryans org is gangbusters, and there is no reason for Linux to be less positive about our future than everybody else - and bounded the response with it is not a risk right now. Sarah had already blocked Monday for the session.
Sensitive Decision
Endura scope for CIQs own pipelines - include Fuzzball, Warewulf, Ascender and Depot; exclude Apptainer
Eric Sheridan of Infrared Security updated Peter on the Endura proposal for securing CIQ build pipelines, noting Nathan and Justin had reviewed the Koji integration strategy positively and that Bjorn was excited about using Endura to protect Rocky core packages. Eric asked whether scope should extend beyond Rocky to Fuzzball, Warewulf, Apptainer and Ascender. Peter replied to include Fuzzball, Warewulf and Ascender, said Apptainer should not be necessary, and added a product Eric had not asked about - Depot - on the grounds that projects which serve CIQ products to customers should be included as well. Pricing follows this scope, and a call with Greg and Bjorn was set for Wednesday.
Pause the AI Data Management policy approval and route it to Greg
Steve Wallace asked for Peter Google-Doc approval on the AI Data Management Policy (an effective-date fix). Rather than approve it, Peter flagged that Greg is now exploring training open-source models and said the whole approach may need to be revisited, telling Steve to get the doc in front of Greg to ask what he wants to do. Peter declined to ratify a policy that an in-flight strategic pivot could immediately obsolete.
Approve GPU hardware spend and drive hours-not-days urgency for the Fuzzball/Arcee test cluster
Peter approved procuring and standing up GPU hardware for a Fuzzball test cluster - routing ~240K of GB200 cards he had in hand to the Reno office, approving a ~60K server plus InfiniBand switch (and more if needed), and greenlighting installing cards into the office servers Brady was using. He pushed hard on speed: hours matter, not days. The goal is to get a cluster online fast for Chris Wolford Arcee/Fuzzball work and the board/Nvidia demos.
Willing to pull C3 into engineering, gated on Product confirming it is a priority
In his 1:1 with Art Tyde, Peter said he is willing to pull C3 into his engineering org, conditional on Product (Bjorn) actually confirming it is a priority. C3 ownership is currently ambiguous (Peter was told Greg owns it, which he called a terrible answer, and nobody under Peter owns it), it is degraded (reported ~50 percent down, Fathom-approximate), and it is blocking a Huawei evaluation. Peter made a note to figure out who is responsible for keeping it up and how to fix that.
Sensitive Decision
Reverse the No on one non-Amazon-only Linux candidate and open Roxana backfill req immediately
After learning Roxana (a Linux contractor under Nathan) is leaving - the second Linux departure after Gomez - Peter reversed his 7/6 stance of declining both Amazon-background candidates. He will remove his No on the one candidate with breadth beyond Amazon, get him in now, and open a replacement req for Roxana immediately, while still holding the general ideally-not-Amazon preference.
EU Cyber Resilience Act - scope hinges on legal definitions; Bjorn to engage lawyers; aim to publish our own definitions
On the CRA thread (raised by Leigh Hennig re a Sept 11 deadline for RESF/Rocky/CIQ), Peter directed that the entire scope hinges on two definitions - vulnerability and actively exploited - and delegated Bjorn to engage lawyers to weigh in. Strategic aim: ideally CIQ/RESF publishes its own definitions, reframing CRA compliance as living up to our stated market promises rather than being exposed to outside interpretation. Until legal responds, nothing to do.
Sensitive Decision
Sensitive Decision
Establish 3 as the performance-review norm — close alignment with Bjorn and Greg
Peter established that a 3 on the 5-point scale is the expected/solid norm in performance reviews (not a 5), and closed alignment on this calibration standard with Bjorn and Greg, resolving a leadership split that had become visible to the org during the active review cycle.
Sensitive Decision
Mandate CIQ build/test pipeline converge with the RESFs — one unified project, Nathan accountable, coordination over speed
Peter laid down a mandate that CIQs Linux build/test pipeline will become functionally identical to the RESFs over time — a single consolidated project rather than parallel tooling. Nathan drives and is held accountable for closing the CIQ-to-RESF gaps (hardware parity, cut over to Koji, mirrored build infrastructure, a full validation framework that runs PR-specific tests). Justins build world must sign on and use it everywhere. Ryans gauntlet/outfitter tooling and Leighs RESF-side work are welcome only if they plug into the one project rather than forking. Peter explicitly chose coordination over speed even though it slows Ryans faster build-it-now instinct.
Performance-engineer rec stays under Greg/research for now; likely transitions to engineering later
In the HR Weekly (6/02), Greg offered Peter the performance-engineer rec, saying performance does not belong in research under the new charter and that the rec should go to Peter. Peter chose to leave the rec under Greg/research for now (roughly the first four months), with shared agreement that it likely transitions to Peter/engineering long-term once there is something concrete to manage toward. Peter framed it as a stance to leave the meeting with unless someone had an epiphany that evening; the stance held.
Take on Value Drivers Board restructure as the next coordination lever after JPD doctrine
In the 6/01 Leadership Roundtable, Peter committed to bring a formal proposal to restructure the Value Drivers Board, explicitly sequenced as the next move now that the product-priorities board (the JPD-doctrine work, closed 5/29) is aligned where he wanted it. Took the Fathom action item to draft the proposal and share with Chris Baek and the group within a couple of days. Triggered by Lindsay surfacing marketing/product misalignment (premature RLC+AMD announcement before AMD validation; Fuzzball multicloud date churn May 28 to June 4).
Sensitive Decision
Kyle move conditions: permanent (no return) and gated on RLC completion
If/when Kyle moves to Gregs research team, the move is permanent with no path back to Wolfords org. The gate is Kyle completing his current RLC commitments first, not just Wolford filling the backfill rec. Greg owns the conversation and setting expectations with Kyle on self-management and performance; Greg will update Peter and Bjorn on Kyles decision.
Cedric placed full-time on Gregs research team; Kyle still pending Gregs conversation
After the C-Suite Sync surfaced the Kyle/Cedric risk asymmetry (Kyle = low performer needing hard deadlines, Cedric = high-output engineer well-suited for rapid POCs), the research-team assignment from yesterday flipped: Cedric is now the firm full-time mover to Gregs research org, while Kyles move is still open and gated on Greg-owned conversation + Kyle finishing his RLC commitments first. The Wolford backfill rec opens regardless of which one moves.
Hire dedicated cloud-security engineer — Steve drafts JD, Peter champions, dovetail with Nathan STIG/FIPS gap
In Steve 1:1 5/21, TJ flagged CIQ is doing the bare minimum on infrastructure security across 4-5 clouds. Peter asked Steve to have TJ (or Steve) draft a quickie JD describing what the role does and is responsible for — explicitly NOT urgent, but needed as a champion artifact so Peter can take it to Bjorn/Greg with a concrete ask. Steve flagged that the same hire could dovetail with Nathans STIG/FIPS expertise need on the technical side; Peter agreed ("Awesome"). QBR 5/22 made it official as a Steve-owned area requiring formal assessment and potentially a new headcount.
Joseph compensation bump approved; future raise asks must come with story not tenure
Joseph asked Peter directly for a comp bump citing financial hardship — Peter approved on the spot. In the Justin 1:1 5/21 Peter ratified this with Justin and used it to articulate the process going forward: raise asks should not be tenure-based ("we havent given Fred a raise in a year"); they should come with replacement-cost analysis, criticality justification, and a clear story. "In general I will say yes to that."
Firewall Greg AI prototyping team — company makes no plans against their output
Peter explicitly framed Gregs AI prototyping work as a separate research division that the rest of the company cannot bet on. No items show on the value drivers board for this work; nothing is committed to customers; deliverables are not on engineering plans. If they emerge with a usable nugget, fine — Wolfords or Nathans team will productize it. Until then, planning treats the team as if it does not exist.
Sherif RESF hardware: Wallace owns directly — escalation triggered by Greg
When Greg pinged Peter in #distinguished-leaders saying the RESF (Sherif) had been waiting on systems and Sherif had been emailing Moody for weeks, Peter took the heat publicly ("I do not need thanking. This is a disaster.") and re-assigned ownership directly to Steve Wallace. Steve had it on Moodys plate and it slipped while Moody was out for a bereavement. Peter then DMed Steve to take ownership ASAP — Steve confirmed and committed to staying on top of it through the vendor build/ship.
Kyle conditional move to Greg AI role gated by filling Wolfords rec first; Cedric written off the Fuzzball team
Kyle reached out to Greg directly about the AI role reporting into Greg. Peter aligned with Greg and Chris Wolford on the following: (a) Kyle stays in Wolfords org through end of June while the new tickets land; (b) Wolford receives Gregs open rec immediately and starts hiring; (c) Kyle does not move until that rec is filled; (d) Kyle is told this is a job change, not a trial — if it does not work in Gregs world he is out, same as any other role mismatch; (e) Peter will tell Greg that Cedric is NOT meaningfully delivering on Fuzzball today (he is a part-time advisor at best while building for Greg), and Wolford will plan as if Cedric does not exist on the team going forward.
Dedicated cloud security engineer role to be championed — dual-purpose JD covering cloud + STIG/FIPS
Committed in Steve 1:1 5/21 to champion a new dedicated cloud security engineer role. Steve will work with TJ to draft the JD; Peter will champion it to budget owners (Bjorn/Greg). Triggered by TJ flagging current cloud security as bare minimum and the proactive supply-chain projects (TJ on GitHub workflow SHA pinning, CeeLo on NPM package securing) needing a dedicated owner. Dual-purpose JD: also serves Nathans STIG/FIPS security expertise needs — one hire, two demand surfaces.
Kyle AI transfer approved with hard conditions; Gregs AI team codified as research firewall
Approved Kyles move from Wolfords Fuzzball team to Gregs AI team. Conditions: (1) Kyle stays on Fuzzball through end of June to finish RC tickets, (2) Chris receives Gregs open AI rec immediately to start backfill hiring, (3) transfer only happens after replacement rec is filled, (4) move is permanent — not a trial; failure to perform in AI role = out (not back to Fuzzball). Same turn with Wolford codified the broader doctrine: Gregs AI team operates as a research division firewall — the company plans nothing based on its work until a proven nugget of gold is delivered, and Cedric is now assumed unavailable for Fuzzball planning.
CVE response strategy — three-pillar overhaul (process + tooling + strategic kernel review)
In Engineering Weekly Sync, Peter operationalized the 5/11 Leadership Roundtable vuln-handling commitment into three concrete pillars: (1) Chris Baek to restructure the embargo/CVE comms doc with Jamie, separating process from tooling/templates; (2) tooling strategy — Peter commits to email Greg requesting Claude Opus 4.7 whitelist for CIQ accounts AND to set up unbridled internal LLM models on Fuzzball for vuln investigations; (3) schedule strategic kernel philosophy review for early June, with Nathan and Justin to provide a list of downstream automation efforts to prioritize.
Open strategic review of RLC/RLK identity + upstream binding (Dirty Frag triggered)
Saturday 5/9 in #department-heads, in immediate response to Justin's Dirty Frag status table and Nathan's note about CIQ patches being shared with the RESF, Peter announced he wants the leadership team to take up a strategic question next week: what recurring vulnerabilities imply about CIQ's kernel posture, how tightly to bind to upstream, how to work with the RESF, and what it means going forward to be RLC and RLK. Aimed at framing input for the mid-to-late June LA in-person product-strategy session with Bjorn and Greg.
Commit engineering to vuln-handling infra/automation at Leadership Roundtable
At the 5/11 Leadership Roundtable, Peter accepted an explicit action item to prioritize vulnerability-response infrastructure and automation work in engineering, and to update Chris Baek as the interim process owner. The commitment converts the 5/8 internal-to-engineering commitment (build/test infra to eliminate reactive interrupts) into a cross-functional commitment with Bjorn, Greg, Chris, and Lindsay in the room.
Sensitive Decision
Prioritize build/test infrastructure to eliminate reactive engineering interrupts
After Dirty Frag CVE took Linux engineering offline for 24 hours, Peter committed to prioritize building robust build/test infrastructure as the proactive response. Told Brady/Brian this requires Product leadership to de-prioritize other work to make room. Surfaced publicly in #department-heads thread asking how to structure infra for the new normal of AI-assisted exploit cadence.
Senior leadership candidate engagement: open to talk, not under pressure, will not give away the kingdom
On the senior leadership candidate Greg/Bjorn surfaced (described by Bjorn as a bit all over the place and by Greg as starting like she is that much of a gift to us), Peter took a disciplined position: happy to talk, would like another senior person, but not feeling pressure right now and will not concede equity/scope/title to land her. Also flagged: expects steady-state of senior candidate flow for a while.
PPL is being misused — push Bjorn to realign it to strategic priorities
The Product Priority List has drifted from a strategic-priority list (epic-level) into a granular project tracker, obscuring strategic priorities (RLCAI on Spark buried at #88) and creating bottlenecks (Ollama package delayed to May 15). Peters position: PPL must return to defining company strategy at epic level; granular tasks belong in JIRA. Will engage Bjorn directly to realign — this is the framing decision; the implementation is the negotiation with Bjorn.
Three-tier Rakuten kernel proposal — 8.10 preferred, 8.6 sustaining, $800k-$1M PS for full 8.6
Push Rakuten to migrate RLC 8.6 to 8.10. Three-tier proposal: (1) preferred — full support on 8.10 with CIQ vendor coordination to accelerate hardware recertification; (2) alternative — sustaining support on 8.6 with no new patches/backports (security risk on Rakuten); (3) PS engagement — $800k-$1M/year to fund two dedicated kernel engineers for full 8.6 support, framed explicitly as Professional Services cost not mainline engineering. June renewal is the forcing function. The original handshake-pricing deal with Tarek is void.
Everfox: require ~$2M front-loaded year-one payment, reject back-loaded $600k structure
Peter is requiring a large upfront payment ($2M floor with the proposal team; $4-6M float with Greg) for the new Everfox custom work (legacy CPU support, custom desktop) and rejecting the back-loaded $600k year-one structure. The $20M/10-year deal will be restructured to front-load payments, potentially by reducing total contract value if needed. CIQ will not absorb non-reusable engineering work without immediate funding.
Ship CIQ kernel patch with extra fix; contribute upstream; race to be first/best on CVE response
Linux kernel CVE response: CIQ shipping 10 fixes vs CentOS Stream's 9 (CIQ found and is fixing an extra issue related to the CVE). Extra commit submitted upstream to centos-stream and acknowledged for inclusion. CIQ pushing to be first EL distro to release, with primary goal of customer reassurance and secondary goal of public proof point that CIQ contributes to security and is large enough to serve big customers. Also pushing patches to RLC kernels as fallback in case RH doesn't move quickly.
Sensitive Decision
Manage Wesley via Greg; set boat-anchor trigger with Chris (preserve optionality)
In the Chris W 1:1, Peter decided to manage Wesley's performance situation through his Greg relationship rather than moving Wesley onto a PIP or active weekly-1:1 performance track like Cole and Thomas Chin. Assessment: Wesley is capable but slow, requires handholding, won't operate at senior/principal level, but is not a net negative. Chris asked to proactively flag if Wesley becomes a boat anchor on team productivity — that is the threshold for escalation.
Core42: pivot from Fuzzball sale to full-stack compliance partnership
After the Core42 Tech Dive Part 2 surfaced Core42 wants a single OS vendor for their full UAE compliance stack (NIST 800-53, BIS, IDAM, physical security) across three EOY-2026 GPU clusters, Peter immediately convened an internal Impromptu Zoom to reposition the opportunity. CIQ will propose a comprehensive partnership framing CIQ as the only group that can provide all requirements, with RLC Pro Hardened + Fuzzball + Ascender as the core stack and partners filling the remaining ~20%. Consultative play: CIQ will advise Core42 on which requirements in Eric Grundstrom's doc would cause unacceptable performance degradation vs. which can be met. Nathan to draft the proposal doc by EOD Saturday so CIQ can deliver an answer by Monday.
Escalated Dieter/RASF urgency to Greg publicly — secured EOW commitment
Publicly escalated Dieters stress and lack of RESF authority in #distinguished-leaders (When are we actioning Dieter? Hes super stressed and feeling unsupported), forcing Greg to commit End of week is my target on finalizing the RASF.
Sensitive Decision
Committed CIQ Engineering Resources to Unblock RESF
Committed CIQ engineering resources (specifically Max Spevack) to unblock RESF, positioning RESF health as critical to CIQ success. Committed to asking Nathan to prioritize providing new AWS contacts for Leigh to bypass stalled Duncan access. Directed Chris to lock down internal-rasf Slack channel for Leigh's weekly write-ups. Clarified Max's role as Chief Architect for Everything Linux focused on upstream health and AI-automated CVE remediation. Agreed Brian's value is limited to admin tasks — Leigh will communicate this assessment to Greg.
Set Sales Scope Discipline on Nokia Opportunity
In MPDM with Adam Jackson, Bjorn, Greg, and Jonathon, set firm boundaries on product scope for the Nokia deal. CIQ should sell what it has and is good at, not build custom solutions to close individual deals. The bar for adding new capabilities is company-level strategic pivot territory — not deal-level customization. Stated 'enough money is a LOT' and 'its not going to be for another 500k, or just to close the deal.'
Sensitive Decision
Shaped Interview Panel with Veto Condition for Performance Engineering Hire
When Greg wanted to add Cedric to the interview panel and reduce from 5 to 4 interviewers, agreed Bjorn could be dropped but set a condition: a NO from Max or Peter must count as a veto.
Set Lab-to-Production Boundary — Nothing Ships Without Engineering Productization
Established with Bjorn that nothing from Greg's Innovation Group/Lab (Cedric) goes directly to production. Everything must pass through Engineering for productization, validation, and integration with build/signing pipelines. CIQ does nothing with RLC-Performant until the lab produces something viable.
Defended Global Prioritization Model with Per-Team Computed Views
Convinced Greg that product prioritization must remain a single global list, not grouped by team. Agreed to add a computed property showing priority within each team for visibility. Fuzzball was reprioritized into top 20 in Exec meeting; Greg's remaining concern about Fuzzball not being high enough was resolved via the global+computed-property approach.
NVIDIA Partnership - Resource Commitment for Grace Vera Patch Support
Committed to assessing headcount needs for NVIDIA Grace Vera patch support — both for the first 6 months and then ongoing. Forwarded NVIDIA patch list to Nathan for SWAG assessment. Nathan estimated 3-6 months for RLC, faster for CLK 6.18. Communicated requirements to Scott Hara: hardware access, test suites, functional and performance targets.
RESF Restructure - Confirmed Proceeding Despite Greg's Hesitation
Confirmed CIQ should proceed with the Dieter RESF restructure plan, overriding Greg's expressed concern that the restructure doc might disrupt RESF's current momentum under Leigh. Bjorn aligned with Peter. Greg deferred rather than blocking.
Agent IQ: Requiring Bjorn to Justify Before Supporting
Peter directed that Bjorn must articulate how Agent IQ augments CIQ's portfolio before it gets engineering resources. Not killing the project outright but requiring strategic justification.
AI/Data Security Audit Commitment to Greg
When Greg raised concerns about CIQ leaking data through AI agents/bots/services, Peter committed to getting Michelle's oversight team to do an assessment/audit of what's running and with what access.
Michael Young Termination Communication Approach
Peter set communication boundaries for Michael Young's termination: don't tell RESF people WHY, only 'we decided to part ways.' Advised Greg not to write specifics down. Declined to reply to Michael directly.
Empower Dieter as RESF Infrastructure Lead + Stock Grant
Peter decided to push Greg to give Dieter formal authority as RESF technical infrastructure lead, and approved a stock grant for Dieter with Bjorn's support to tie him more closely to CIQ.
Sensitive Decision
Established Fuzzball AI validation process
Committed to validating Greg's Fuzzball AI marketing claims before they go external. New process: Greg/Jonathan provides desired story, Peter documents engineering tests required, engineering validates and gives thumbs-up/down. HumanX conference in 2 weeks is the forcing function.
Sensitive Decision
RESF — Orchestrated demand-pull approach for CIQ help
Directed that CIQ help should come through RESF team requests (especially Taylor/Sherif) rather than being imposed from above. Reinforced 'CIQ will help if you ask' messaging through Greg and Leigh. Wants RESF work driven like a project with visibility into requests.
RESF — Deliberately accepted engineering capacity hit for RESF support
Explicitly committed to accepting CIQ engineering disruption from RESF support work. Stated he'd be 'upset' if there isn't impact on engineering — signaling this is the right priority trade-off and meaningful work should be happening.
RESF — Committed CIQ resources (Dieter/Nathan) and proposed tech lead structure
Committed Dieter and Nathan to near-full-time RESF work. Proposed Dieter as RESF tech lead reporting to Peter for ~1 year. Told Leigh both are available immediately (Dieter now, Nathan when back from vacation). Scheduled Tuesday alignment meeting with Greg/Bjorn/Max to formalize structure and authority. Briefed Max on strategy: unified front with Bjorn, carrots and sticks approach for Greg meeting.
Fuzzball SaaS Prepaid Token Billing Model with Unified Portal Backend
Drove adoption of prepaid token ('CIQ Tokens') billing model for Fuzzball SaaS MVP, with unified Portal backend as single source of truth for all user accounts and token balances. Free tier deferred to fast-follow. MVP requires account + credit card to run workflows.
Gate Fuzzball SaaS GTM on Working Prototype — Assign Michelle
Agreed to move forward on Fuzzball SaaS GTM but gated it on having a working prototype first. Suggested Michelle as the resource to stand up a prototype on top of existing Fuzzball, accepting she's not the ideal person but can make progress. Rejected doing it 'out of band' — keep in normal product flow.
Personally Invest in Retaining Mustafa at RESF
Proactively reached out to Mustafa, scheduled a 1:1 for Monday March 23 at 9:30am PST. Shared outreach in #distinguished-leaders and declared 'I will invest HARD in the good ones.' Providing executive-level support to counter harassment from Taylor and Sharif.
Sensitive Decision
Sensitive Decision
Google Deal — Engineering Owns Resource Projection
Directed that engineering (not finance/biz dev) should own projecting what the Google deal requires in terms of team size and capacity. Participated in Google Deal review meeting where consolidated $6M/yr development fee proposal was developed, including engineering guardrails (live patching scope limits, early renewal trigger). Deal structure: $6M dev fee for 5-7 senior engineers, uncapped variable usage fees (removing $1M cap), 15-25% margin on premium listings + MDF, early renewal trigger if scope exceeds funded team capacity.
RESF Communication & Information Control Strategy
Established multi-layered communication control for RESF transition: (1) Posted own #engineering message with different language than Greg's draft, emphasizing visibility requirement. (2) Told eng-management nobody talks on RESF Zoom calls because RESF members can hear. (3) Asked Lindsay to confirm no social media leaks. (4) Told Max to keep RESF off Department Heads agenda Thursday.
RESF Operational Framework — CIQ Resources Work Under RESF Direction
Established and communicated to entire engineering org that all CIQ work for RESF must be done 100% at RESF direction, with every request flagged for Peter's visibility. Reinforced individually with Ryan (get accounting of in-flight work, ensure RESF person directing), Nathan (hold then green-light Taylor contact with specific messaging), and Mustafa (offer resources under RESF direction, recommend MatterMost for coordination).
Louis — No Acting Role for Next Couple Years
Decided Louis cannot have any acting role in RESF for the next couple of years. Technical contributions may be allowed later by whoever runs RESF. Priority is not muddying the transition message.
Excluded Brian from RESF Pre-Transition Planning
Decided to exclude Brian from pre-transition RESF planning based on synthesizing risk signals from multiple sources. Brian's role will be carefully managed post-transition.
RESF Monday Cutover — Finalized 3 PM PT Execution Plan
Finalized the RESF infrastructure cutover plan for Monday March 16 at 3 PM PT, including DNS NS record flip, AWS VPC firewalling, account disabling (Lewis, Neal), and security audit — accepting up to 24 hours of DNS-related downtime.
Enforcing Product Process for Greg's RLCAI Requirements
Enforcing the correct process by directing all of Greg's RLCAI requirements to the Product team rather than allowing Greg to bypass Product and give direct requirements to Engineering. Brian Dawson raised the concern; Peter is supporting and enforcing.
Asset Management — Backend-First, Bridge to Views
Advocated for deciding where the asset management backend should live first, then building bridges to expose it wherever needed (Jira, Rippling). Explicitly disagreed with Greg's framing that building bridges adds unnecessary complexity.
Brian Clemens — Loop In After Front Door Closes
Decided Brian Clemens should be brought into RESF matters only after the front door is closed, acknowledging he'll be critical for reconstruction but the current phase requires operational security. Conditional on his behavior: 'If he hasn't gone off the reservation at that point.'
Sensitive Decision
Prioritize GPU Optimization to Define Team Capability Needs
Directed that GPU utilization optimization be prioritized for Fuzzball/RLC AI, using the priority as a diagnostic to reveal what in-house capabilities the team needs.
Prioritize Google Exec Meeting — Adjust Reno Travel
Agreed to meet a confidential new Google executive (distinguished engineer from Google Cloud, came through Tissa) for Monday dinner or Thursday lunch. Thursday option requires returning from Reno Wednesday night. Directed Greg to cover Toyota in person on Wednesday if needed.
RESF Option A — CIQ-Led Transition with Narrative Reframing
Adopted Option A (CIQ-led transition) as the only viable path for RESF. Reframed narrative for Greg as 'skeleton' foundation for future vibrant community, not 'threadbare' end state. End-state vision: Rocky Linux displaces Alma and Ubuntu as de facto enterprise OS. Identified critical leadership gap requiring new empowered leader ('mystic unicorn') deputized by remaining board. Internal story: 1-year transition to 501(c)(6).
Push for Continuous Sales/Support Enablement
Aligned with Greg on pushing for continuous product enablement (demos, walkthroughs) for Sales and Support on every new engineering feature, overriding Bjorn's resistance. Peter committed to re-engaging Bjorn on this.
Sensitive Decision
Aligned with Max on RESF Option A (Skeleton Independent) as the best path
After reading Max's RESF decision framework document ('The Future of the RESF: A Decision Framework for CIQ'), Peter agreed with Max that Option A — maintaining the RESF as an independent entity in the lightest possible form with one CIQ-employed full-time RESF leader — is the best path. This is Peter's position alignment with Max, not yet a company decision. Next step is presenting to Bjorn and Greg for buy-in.
Aligned with Max on RESF Option A (Skeleton Independent) as the best path
After reading Max's RESF decision framework document ('The Future of the RESF: A Decision Framework for CIQ'), Peter agreed with Max that Option A — maintaining the RESF as an independent entity in the lightest possible form with one CIQ-employed full-time RESF leader — is the best path. This is Peter's position alignment with Max, not yet a company decision. Next step is presenting to Bjorn and Greg for buy-in.
Demanded measurable success criteria for LinuxLM project
Greg proposed training/fine-tuning a Linux-expert foundation LLM (LinuxLM). Peter pushed back by demanding explicit success criteria — deployment plan, evaluation methodology, and clear value proposition — before endorsing the project.
Decided to carefully surface Icicle results to Bjorn
After validating Icicle test methodology with Ryan (BIOS change applied before both with/without comparisons — apples-to-apples), and learning Ani was told by Bjorn to stand down on Icicle, Peter decided to personally and carefully bring the validated results to Bjorn's attention.
Set NVIDIA positioning: benchmarks are AMD-only, offer to collaborate on tuning
Defined strategic positioning for NVIDIA benchmark situation: frame existing benchmarks as AMD-only, and offer to work with NVIDIA to tune Rocky Linux for their platform. This turns a potential embarrassment into a partnership opportunity.
Approved retention check-in strategy for must-keep employee list
Approved the must-keep employee list prepared by Mariah and Chris. Committed to personally leading retention check-ins with must-keep engineering employees. Bjorn leads check-ins for his org. Mariah and Chris excluded their own teams (already monitored closely).
Sensitive Decision
Initiated proactive top performer temperature checks
After Ian Kaneshiro's resignation, Peter directed the senior leadership group in #distinguished-leaders to split up and individually meet with top performers to take their temperature. This is a systematic retention check rather than just crisis management for the single departure.
Escalated Ian Kaneshiro retention to CEO level
After learning Ian Kaneshiro (PIC team, reports to Chris Wolford) resigned to join an AI startup, Peter immediately directed a retention escalation: told Mariah to get Greg talking to Ian, told Greg to do anything to keep him. After learning Ian had already accepted and wouldn't go back on it, shifted to ensuring the door stays open for a future return.
Commit to benchmark accuracy sign-off by tomorrow
Committed to signing off on the accuracy of the RLC-AI benchmark document by Feb 21, gating its release. Greg conditioned approval on numbers being '100% accurate' and verifiable. Bjorn shared both internal and external draft documents for review.
Assign Max as RLC-AI benchmarking plan owner with RHEL comparisons
Assigned Max Spevack as owner of the RLC-AI benchmarking plan in response to Greg's question about ownership. Directed that RHEL comparisons be added to exit criteria. Bjorn owns product definition (what to benchmark), Max owns technical execution (how to benchmark accurately). Max will create a one-page methodology document for the Humane pitch.
Sensitive Decision
Pushed for March ARR review, rejected April as too late
Directed Sarah and Greg to schedule an ARR targets review meeting in March, pushing back on an April date as too late. Wants to ensure the company is on track for revenue targets and can pivot anything needed. Offered personal availability and said format doesn't matter.
Sensitive Decision
Leveraged TPS report visibility to drive accountability with Justin
Proactively messaged Justin that the Release All Things section of the TPS report looks bad, with a 2.5-hour deadline before C-Suite Sync presentation. Gave Justin a window to update Jira tickets to reflect reality.
Core42 Technical Assessment - Multi-Product Positioning in UAE
Attended Core42 meeting in Abu Dhabi with Greg, Bjorn, Max, and Adam Jackson. Provided real-time technical assessment to the team via Slack, identifying product-customer fit across four CIQ product lines: RLC-H for defense customers (CVE remediation pain), Rocky as guest OS on Signature Cloud, Fuzzball as potential replacement for their unhappy AI cloud orchestration partner, and Ascender Pro for their heavy Ansible usage. Followed up personally with Raghu (EVP Engineering, Core42 US) offering in-person meetings.
Approved RLC+ and Pro product hierarchy with new naming and de-risked launch cadence
Approved a new product hierarchy: Stock Rocky (pure community mirror), RLC+ (free with NVIDIA/AMD drivers), RLC Pro (paid tiers). The RLC name now signifies CIQ value-add. Also approved a de-risked 3-phase launch cadence: Phase 1 (Feb) bundles RLC Pro + RLC Plus NVIDIA; Phase 2 (Feb) RLC Pro AI; Phase 3 (Mar) RLC Plus AMD partnership. Identified backporting vs roll-forward policy gap as a pre-launch blocker.
Enforced Product-owns-prioritization process with Greg
Pushed back directly on Greg when he tried to route engineering work outside the established prioritization process. Insisted Product owns the priority list and work requests must flow through the proper channel. Simultaneously reminded Chris Baek that his team owns signoff authority and should use it rather than escalating through Greg.
Google Partnership Strategy - Build Rapport with Tissa
Decided to shift the Google contract renegotiation strategy from confrontational to collaborative. Peter will personally meet with Tissa (Google) to build rapport and empathy, framing CIQ's financial pain as a shared problem to solve together. Greg will be excluded from this meeting to ensure a non-antagonistic conversation.
RESF Strategy: Remove Lewis with Legal Leverage, Engage Neil Collaboratively
Approved plan to remove Luis (Lewis) from the RESF board using a Quinn Emanuel memo documenting a potential federal law violation and breach of fiduciary duty, then send a collaborative letter to Neil offering a path forward to avoid a public fight. Greg will present the memo to board members to secure their support. Shadow infrastructure (Koji, clones) is confirmed ready.
AI-First PR Process - Tests Over Human Review
Decided that PR process should evolve to prioritize automated test suites over human code review for AI-generated code. If a comprehensive test suite passes, the code is considered production-ready regardless of its origin.
New Engineering Mandate - 2x Velocity in 6 Months
Set new mandate for Justin and Nathan: top priority is building a team that can deliver twice as fast in six months. This is a shift from the previous coaching model to a performance-driven one - setting ambitious targets, holding people accountable, and replacing underperformers.
CODE2 Values Redefinition - From Traits to Behaviors
Proposed redefining CIQ CODE2 values from character traits (what people are) to observable behaviors (what people do). Created comprehensive framework translating each value (Customer Centric, Optimistic, Dedicated, Efficient, Excellent) into concrete, measurable actions for engineering. Shared draft with Bjorn first for alignment, then presented to Greg in 1:1.
Advocate for in-person Anduril POC kickoff in Seattle
Decided to advocate for an in-person technical kickoff meeting in Seattle for the Anduril POC, with both Peter and Max attending. Set clear boundaries on duration - a day or two is fine, but two weeks would break February delivery dates.
Recommend partial bounty payout for Fuzzball single-binary work
Recommended paying out half of the originally established bounty to the team members who completed the Fuzzball single-binary work. Want to use bounties as a repeatable, low-friction model across engineering and ensure all of engineering knows about the payout.
RESF crisis comms - single source of truth
In a RESF crisis, publish one official blog post as the central source of truth. All responses on social media (Hacker News, LWN, HPC forums) link back to that post. Do not engage in real-time debates. Own the traditional news cycle, not social media.
Escalated Visa support model concerns to Greg
Escalated concerns about CIQ support arrangement with Visa to Greg and Bjorn. Questioning why CIQ is on the hook to support Rocky Linux (which CIQ does not build) for Visa, rather than having Visa use RLC so CIQ can actually fix their issues.
Clarified bonus evaluation framework - above and beyond for step-function impact
Clarified to Steve Wallace that bonuses are awarded for actions that are above and beyond standard role expectations and provide a step function for CIQ - not for standard job performance, which is covered by salary. Also confirmed TJ bonus (Greg approved Jan 23 via private DM) and committed to close the loop with Greg.
Sensitive Decision
Advocated for PIC team progress to Greg
Reported to Greg (CEO) about satisfaction with Chris Wolford team improvement and transparency. Thanked Greg for going into PIC Demos meeting with open mind despite having strong opinions. Highlighted Ian Kaneshiro as fantastic.
Performance review redesign - define traits with observable behaviors
Committed to drafting a proposal to fix the performance review system for the April/May cycle. The approach keeps existing traits but defines each with observable behaviors so managers and employees have shared understanding of what success looks like.
Committed to ensuring Greg technical direction reaches Justin
Committed to redirecting Justin to follow Greg architectural guidance on object storage/depot, and to be the conduit ensuring Greg technical direction reaches engineering clearly. Greg flagged that depot work was not in line with past directives.
Approved Greg-Cedric engagement starting Monday
Approved Greg beginning conversations with Cedric on Monday to provide context on upcoming PIC work. Cedric will continue participating in epic scoping sessions to stay connected to the tactical work.
Instituted ARR and CVE gap metrics visibility at weekly meetings
Decided to communicate both current ARR (as determined by finance) and CVE gap metrics at weekly meetings. Proactively communicated this to Bjorn and Greg, anticipating potential concerns but proceeding anyway.
Engineering dates commitment by Friday - reprioritize for revenue impact
Committed to publishing updated engineering dates/milestones by Friday for Monday group review. Acknowledged January deliverables are unrealistic - many items were newly added and cannot complete in remaining ~10 days. Will reprioritize toward revenue-impacting items first. Tomorrow all-day session with Chris Baek to rework H1 plan into aggressive but achievable targets.
Board presentation narrative: AI as lean maintenance enabler
Finalized board presentation framing AI as the solution to lean, automated maintenance org. Key talking points: heavy AI usage across engineering, all builds automated with zero public issues in 3 months, leaning out maintenance to free devs for RLC-AI/H, RESF contingency infrastructure (3 heads, 5 weeks), CVE automation story (net-snmp 40-day p50 to 14 days), expectation to reduce manual CVE team by 75% in 6 months.
All-Hands messaging: acknowledge Q4 miss, pivot to pipeline optimism
Aligned with leadership on All-Hands messaging strategy: directly acknowledge Q4 revenue miss, then pivot to optimistic outlook highlighting $22M H1 pipeline and unified GTM plan. Peter to present tech updates (service endpoints, Nerf) and guide Mural board walkthrough. No naming specific deals to avoid premature expectations.
Sensitive Decision
Strategic Map Framework - Value Drivers vs Internal Efficiency Separation
Established new H1 strategic planning framework that separates customer-facing Value Drivers from Internal Efficiency Drivers. Framework uses three lanes: middle lane for Value Drivers (the WHY), top lane for GTM activities, bottom lane for engineering deliverables. Also established phased estimation process: low-confidence ballpark dates first, then engineering-only session to raise confidence.
Justin Coaching - Ambiguity Tolerance and Explicit Pushback
Coached Justin on the Depot/Portal bounty disconnect. Addressed two issues: (1) Justin needs to get comfortable moving through ambiguity and letting his team explore before designs are fully baked - unlearning 10 years of Amazon training. (2) When Peter pushes for something, Justin needs to either do it or explicitly debate/push back - not quietly not execute.
Marketing ICP Validation - Collaborative Research Approach
Pushed for marketing to validate ICPs with real data rather than just executing on what was decided in the planning room. Established that ICPs are hypotheses to test, not fixed targets, and Lindsay has permission to explore outside defined ICPs if data warrants.
H1 Planning Framework - 3-Lane Model
Pushed for the team to focus on ICPs, goals, and milestones rather than getting lost in metrics and mid-level tactics. Established a 3-lane framework (GTM, Value Drivers, Engineering) to align all work.
Verify Justin Offered Bounty Work Broadly
Investigating whether Justin followed direction to offer bounty work opportunities to everyone. Greg believes it was not offered to Westley. Peter committed to verify this week.
Friday Layoff List Finalized
Finalized the layoff list for Friday Jan 9: Eli, Derek, Chris Short, Craig, and Trinity. Jason deferred due to ISO certification needs.
Commitment to Present Engineering-to-GTM Messaging Framework
Committed to presenting a framework next week that ties engineering work to changes in market state and corresponding go-to-market messaging. Triggered by Fuzzball Service Endpoints press release that was 98% HPC-focused, missing the critical AI angle despite AI being the strategic priority.
Advocate for Ryan's Strategic Seat
Committed to securing Ryan Smith a seat at the strategic decision-making table for RESF/Rocky Linux matters. Specifically promised to advocate for his inclusion in key meetings with Bjorn and Greg.
RESF Management Model Needed
Identified that RESF needs a clear management person or model as part of short-term response. The lord of the flies approach does not work. Does not matter if its Leigh or someone else, as long as they have personal energy/bandwidth. But it needs to be managed/run with clear accountability.
Sensitive Decision
RESF Infrastructure Independence - Technical Execution
Directed Nathan to mirror all RESF repositories and initiated build environment duplication. Created #internal-resf-escalation channel with strict confidentiality rules. Keeping technical circle small (Nathan, Max, Justin, Dieter) while moving quickly.
RESF Crisis Response - Infrastructure Independence
After learning of hostile plans by RESF board members (Louis, Neil, Brian Clemens) to publicly attack CIQ, dismantle Rocky Linux infrastructure, and damage the project, initiated emergency response to replicate RESF infrastructure for Rocky 8, 9, 10 with minimal team awareness.
Planning RESF Relationship Improvement Strategy
Initiated planning meeting with Greg and Bjorn to address concerns about RESF function and plan improvements to the relationship
Related Patterns (17)
Proactive Talent Pipeline Investment
Invest in building leadership bench and talent relationships before there is an urgent need. Use proven relationships from past experience to create optionality.
Accountability Follow-Through
When you issue a warning or mandate with stated consequences, you follow through. Warnings are not threats - they are commitments. The credibility of future accountability depends on following through now.
Executive Sponsorship for Strategic Partnerships
Strategic cross-company initiatives and major client partnerships require executive-level accountability to move at the right pace and ensure proper prioritization.
Small Circle for Sensitive Operations
When executing sensitive strategic operations, keep the circle of informed people as small as possible to prevent leaks that could accelerate hostile action or undermine the initiative.
Protect Engineering Capacity
When external demands threaten to overload engineering capacity, protect capacity by either requiring the demand to come with additional resources, or forcing hard prioritization choices upstream.
Lead by Example with New Tools
When championing new tools or processes, personally use them and share results rather than just advocating. Learning by doing and demonstrating value through example is more effective than mandates.
Protect Engineering Focus Through Process
When faced with requests that would disrupt engineering focus (from sales, governance, product, or other stakeholders), establish processes that protect engineering ability to innovate while still satisfying legitimate concerns. Prefer systematic solutions over ad-hoc responses.
Three-Lever Talent Management
When pursuing a velocity or performance mandate, simultaneously operate on all three talent levers — upgrade (hire better), retain (protect key people), and exit (remove blockers) — rather than sequentially. This creates compounding momentum: exits free capacity for upgrades, retention preserves institutional knowledge during transitions, and upgrades raise the performance bar that justifies further exits.
Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict
When a question arrives at Peter framed in one domain, he often does not answer it in that framing. He reclassifies it into the domain that actually governs the outcome, which relocates ownership to whoever owns that lane, and then hands down a decision criterion rather than a verdict. The reclassification IS the decision - it determines who decides. He does this rather than adjudicating on the merits himself, even when he was explicitly cc-ed and even when a direct report challenges him on the substance.
Purpose Is the Decision Procedure
When someone asks how a process, board, tool or artifact should handle their specific case, Peter refuses to answer on the askers terms. He re-derives the answer from what the artifact is for, states that purpose as the only decision procedure, and lets the answer fall out. Anything found to be serving a second purpose is deleted rather than debated. Tools and views are explicitly subordinate to definitions. He will accept that the askers real problem is simply not solved by this artifact rather than widen the artifact to cover it.
Demonstrate the Standard, Then Collect It
When a new leadership expectation has to land across multiple orgs, Peter does not write a spec. He runs a live exemplar in public with the strongest performer first, says openly that the ordering was deliberate, keeps the form of the deliverable open so the ask stays about the thinking rather than the artifact, lets the delta be self-evident to the people who will have to close it, and then collects the same from everyone else on a named rotation. He prefers showing imperfect work now over polished work later.
Route Non-Differentiating FTE Classes to Partners
When CIQ would otherwise need to staff a function whose work does not differentiate the company — compliance bureaucracy, audit/cert paperwork, ongoing regulatory attestation, etc. — Peter routes the load to a partner who already owns adjacent capability rather than adding the FTE class internally. Org-shape decision dressed as a partnership decision.
Decide on the Precedent, Not the Case
When a request arrives framed as a one-off, Peter does not evaluate the one-off. He evaluates the rule that granting it would write, and answers that instead. Peter generalized this himself on 2026-08-11: it is always about understanding precedent - whether it is a comp change or anything that structurally affects the company. It is therefore NOT a compensation pattern; the domain of the presenting request is incidental. The tell that this pattern is live is that the stated reason for the answer refers to future cases rather than to the merits of the present one.
Redesign Conditions Over Policing Symptoms
When a direct report names a vulnerability and proposes surveillance-style verification mechanisms (breathalyzers, daily check-ins, monitoring rituals), Peter accepts the disclosure but pushes back on the surveillance model. Treats the verification proposal as a signal that the underlying environment needs redesign — and offers to change the conditions that produced the vulnerability rather than instrument the symptom. Costs Peter optionality (e.g., committing to broker work-hour expectations directly with the partner/spouse) — the asymmetry signals genuine retention vs transactional.
Metrics Must Follow Strategy
When shifting team priorities or strategic direction, the communication alone will not drive behavior change. Engineers may acknowledge the new direction but continue existing behavior patterns without clear, explicit metrics holding them accountable.
Constrain the Mechanism, Not the Access
When AI or automation raises a governance concern, Peter does not restrict who or what may reach the data. He constrains HOW the reach happens, so the pathway becomes auditable and deterministic. The failure mode he designs against is non-determinism, not leakage - a wrong filter in inspectable static code is a bug you fix once, while a model that sometimes pulls the wrong field is an unbounded, unauditable liability. He will therefore accept imperfect filtering and eventual leakage as the price of adoption speed, but will not accept a non-inspectable pathway.
Resource Optimization Through Triage
Apply cost-benefit analysis to avoid spending disproportionate time and energy on low-impact activities. Conserve resources for high-impact work.