Operational Decisions
50+ recent decisions
Public CVE claims match what is in customers hands - fixed internally is not fixed; engage fast with accurate words
Nov 3, 2026 · operational · medium82% confidence
During the CVE-2026-98432 (MPTCP) news on 11/1, Greg drafted Rocky Linux Pro had this fixed yesterday, CIQ customers are safe. Peter said no and rewrote it to separate fixed internally from delivered: We had a fix before you posted this, and are rolling it out across our distros in the next 36 hours. He had already pushed Greg to engage publicly right away. When Justin noted packages reach repos almost immediately and only images lag, Peter accepted patched kernel packages as accurate wording.
People: Greg Kurtzer, Justin Haynes, Bjorn Hovland
Advertise the Kubernetes req on launch Thursday - no extra week of waiting
Oct 30, 2026 · operational · low74% confidence
On 10/27 HR said Wolford wanted to delay advertising the Kubernetes open req another week. Peter checked with Wolford and confirmed in the HR thread that the req can be advertised Thursday, Stratum launch day, with Wolford aligned.
People: Chris Wolford, Mariah Rippee, Bjorn Hovland
Reinforce: confidence numbers are machine-read interfaces between teams and must be right in real time
Oct 30, 2026 · operational · medium72% confidence
At the 10/27 Engineering Weekly Sync (Stratum shown at 30 percent confidence on launch day) and in the Wolford 1:1, Peter reinforced that confidence numbers are no longer read only by humans - agents generate reports, go-to-market triggers and automatic meetings from them - so they must be kept right in real time. He picks on a reliable leader publicly so others see it is about the process, not the person, and wants high numbers to mean good numbers.
People: Chris Wolford, Nathan Blackham
Title mapping rules for Justin org - no senior or junior variants, map to the lower bound and promote later, no comp or promotions in the exercise, no zealotry where someone gets hurt
Oct 30, 2026 · operational · low68% confidence
In the 10/23 Justin 1:1 Peter gave the mapping rules for collapsing titles: no senior or junior variants of any title; when torn, translate someone to the lower bound and keep the ability to promote them; do not bring promotions into the exercise; no salary changes, names only; have an honest conversation about who would be hurt and keep a wart (a senior prefix) rather than generate pain for a simpler map.
People: Justin Haynes
The RESF operations lead joins department heads so the RESF can ask CIQ for help without knowing who will provide it
Oct 30, 2026 · operational · low72% confidence
Peter had the RESF operations lead invited to the Thursday department heads meeting (Eng Sync 10/27) and stated at the 10/29 meeting that he wants the RESF to be aggressive in asking CIQ for help without knowing who on the CIQ side provides it; department heads find people to solve the problem of the day.
People: Chris Baek
Core42 10/29 - CIQ is not the bottleneck; the only CIQ task is a best-practice doc for Warewulf in secure environments, routed to Michael Shinn
Oct 30, 2026 · operational · low70% confidence
After the 10/29 Core42 calls Peter stated it is very clear to Core42 leadership that CIQ is not the bottleneck and network is. The only immediate CIQ deliverable is a best-practice design doc for deploying Warewulf into a secure environment (ILO, FE, OOB network requirements, where Warewulf sits, what must be open between zones), mirroring other secured deployments, to Core42 security. Peter routed it to Michael Shinn with Adam as the delivery path.
People: Michael Shinn, Adam Jackson, Bjorn Hovland
Grenoble pitch - Peter quarterbacks the technical answers and capabilities due within 6-8 weeks are presented as in final test
Oct 30, 2026 · operational · low62% confidence
In the 10/26 Grenoble prep, with Bjorn unavailable for part of the call, Peter quarterbacked who answers which questions. The spreadsheet had been answered affirmatively although some items need six to eight weeks of development; the agreed posture was to engage on them as capabilities in final dev and test that will exist by rollout. Bjorn set the sales posture of not pushing the full stack on a customer that wants Stratum.
People: Bjorn Hovland, Adam Jackson, Chris Wolford, Michael Shinn
ISMS council - accept Risk 33 (vendor breach) and accept a binding legal-review obligation for externally shared incident reports
Oct 30, 2026 · operational · low70% confidence
At the 10/29 ISMS governance council Peter accepted Risk 33 (third-party SaaS vendor breach, high impact, unlikely, score 10) and, after questioning whether to tie CIQ hands, accepted the IR plan change obligating legal review before any incident material is shared with a customer or external party.
People: Steve Wallace, Kelly Wall, Mariah Rippee
Every engineering team takes every product training, due in 30 days - manager carve-outs overridden
Oct 30, 2026 · operational · low70% confidence
Mariah collected per-manager input on which product trainings teams should take; some managers narrowed the list (e.g. Rocky and Ascender only) or wanted 60 days. In the 10/27 HR sync Peter overrode the narrowing for his org: trainings are quick, and the rationale for the PIC team taking Rocky applies equally to the Linux teams taking Fuzzball and Warewulf. Everyone takes all trainings, 30 days. We got feedback otherwise, and we are ignoring it.
People: Mariah Rippee, Bjorn Hovland, Justin Haynes
No data gatekeeping - access to company data by default unless a signed compliance or legal rule requires a block; tool owners can request features but cannot stop work
Oct 30, 2026 · operational · medium76% confidence
After a contractor building internal data tools waited about 10 weeks for Google Analytics and BigQuery access, Peter set the rule: people get access to company data unless there is a compliance or legal reason under a guideline Peter has signed (federal data a non-US person cannot see is a legitimate block). The business owner of an internal tool can ask for features but cannot ask that work not happen; outcomes decide whether work continues. Blocks should be raised immediately, not after weeks. Peter had Steve deliver the message to the RevOps data owners first, planned to reinforce it at the Thursday meeting, and on 10/29 told the contractor BigQuery access should be open and a RevOps meeting would be set up.
People: Steve Wallace
Customer-specific asks go through Work Ingestion and RAT build/validation - no side channels, even under deal pressure
Oct 23, 2026 · operational · medium79% confidence
On 10/23 two escalations from Justin hit the same rule. Toss (Viva Republica) AWS private offers, tied to a $2.4M TCV deal with a frustrated customer: Peter joined the channel to ensure the ask goes through regular Work Ingestion - in Jira, with Product visibility, balanced against other work - and aligned with Bjorn that it goes on the product priority list. OCI HPC base image being built outside the normal path: if CIQ will stand behind it, it must come through the main RAT org, which runs the consistent build and validation process; same message in #team-asia-pacific.
People: Justin Haynes, Bjorn Hovland, Brady Dibble, Kelly Hall, Arthur Tyde
AI spend - the 100k card limit stays as a runaway tripwire while Baek plans 120k per month for 2027
Oct 21, 2026 · operational · low74% confidence
Peter approved the AI budget moving from 75k to 100k per month (actual current spend). When Chris Baek proposed budgeting 120k per month through 2027, Peter agreed for planning but kept the credit-card limit at 100k so a runaway process is caught.
People: Chris Baek
Bjorn post-training / sovereign-stack ask goes on the Value Drivers board as a product block; engineering hangs a learn-first research effort off it
Oct 21, 2026 · operational · medium79% confidence
Bjorn asked for help understanding late-stage training of open-weight models on customer proprietary data as a use case pairing Stratum, Fuzzball and Open Waldo. Peter said yes, framed it as a use case for the existing portfolio rather than a new product, and refused to run it out of band: Bjorn puts a single block in the middle of the three-tier Value Drivers board saying CIQ wants to support this use case; that block triggers Peter to attach engineering (people from across CIQ engineering, possibly external contractors); step one is educating Bjorn and Peter before deciding whether anything goes into Jira. He applied the same move to Fuzzball/Stratum being agent-deployable - a block in the middle of the board with work hanging off both sides.
People: Bjorn Hovland, Lindsay Aamodt, Chris Baek
Core42 - the last line in every shared thread is the Core42 action item; project-manage our own work and stay out of their internal accountability fights
Oct 21, 2026 · operational · medium68% confidence
Extending the 10/16 Core42 posture, Peter set a mechanism and a boundary. Mechanism: the last thing on the shared WhatsApp thread is always what CIQ needs from Core42 next - Wolfgang reposts the current blocker list (CIQ is blocked; this is what is blocking us), and Peter nudges when the thread goes quiet. Boundary: CIQ project-manages its own commitments hard and hits every at-bat as if the date holds, but does not hold any Core42 org accountable, because the org held accountable may be the one that ends up in the chair. Peter also suggested to Bjorn and Adam backchanneling to Alex that Core42 needs its own project manager - one adult in the room, and it cannot be a CIQ person - only if it can be done without blowing things up.
People: Ryan Smith, Wolfgang Resch, Bjorn Hovland, Adam Jackson, Nathan Blackham
Blockers get raised at department heads so the whole company hears them
Oct 16, 2026 · operational · medium72% confidence
When Nathan reported 10.2 Hardened compliance work slipping because the engineer doing it is on jury duty, Peter set the expectation that blockers like this come up at department heads, raised exactly the way Nathan raised it to him, so the whole company hears it.
People: Nathan Blackham
Wolfgang on-site role ends at the pre-VPN window - no extra travel, send someone only if a problem appears, Peter is the backstop, bonuses earned
Oct 16, 2026 · operational · medium74% confidence
Peter bounded Wolfgang Resch hands-on role in Abu Dhabi to the window before VPN access exists; after that Ryan team picks it up, and his priority until then is whatever makes the VPN useful. Nobody else gets flown out. Once VPN was up on 10/15: Wolfgang comes home, nobody replaces him, and if a problem appears Peter will go himself. Peter intends to get Wolfgang bonuses, and wants someone more senior available to assist on future installs.
People: Wolfgang Resch, Ryan Smith, Bjorn Hovland
Core42 partner posture - plan only in CIQ-only rooms, never program-manage Core42, zero friction, Adam coordinates
Oct 16, 2026 · operational · high78% confidence
During the Core42 deployment Peter set operating rules: all CIQ planning and coordination happens in CIQ-only rooms, not the shared WhatsApp group; CIQ does not program-manage Core42 work (the network work is theirs); zero friction for two weeks - asking where to look for updates is fine, pinning people down for updates is not; Core42 should experience CIQ as the easiest partner in the world; Adam Jackson owns ensuring the right CIQ people are on each Core42 call and requests elsewhere route through him; visibility comes through documents (HLD/LLD) and introductions to their networking owners rather than chasing.
People: Duane Carson, Chris Baek, Adam Jackson, Ryan Smith
Jira confidence and date updates - the goal is org visibility, not leads pushing buttons; automate the manual part
Oct 2, 2026 · operational · medium65% confidence
Chris Wolford apologized for late Jira and value-driver updates. Peter said the goal is org visibility of confidence numbers and target dates, not that Chris personally pushes buttons in Jira, and if the second can be pulled out of the process he is all for it. He wants to discuss automating it at the next staff meeting. Chris noted he uses the updates as a check-in with engineers.
People: Chris Wolford, Justin Haynes
Approve the Spark benchmark claim in the RLC Pro AI press release - correct and defensible beats preferred wording
Oct 2, 2026 · operational · low62% confidence
Lindsay asked Peter to confirm the final RLC Pro AI on DGX Spark benchmarks (Dawson had confirmed; Bjorn routed her to Peter). Peter confirmed them, noted they are not yet published on Spark Arena, and approved the first-paragraph claim: comfortable with it, does not love the wording, but it is correct and defensible. Separately told Bjorn the word four is doing a lot of lifting since there are many more tests than four.
People: Lindsay Aamodt, Bjorn Hovland, Brian Dawson
Internal tools come under Wallace IT umbrella - he owns the map, hosting, DR and access, builders keep maintaining, and unused tools get an evaluation date and are shut down
Oct 2, 2026 · operational · high76% confidence
Every internal tool any part of CIQ sits on (Mother Brain, C3, Intelligence Hub, Outfitter, Gauntlet and others) moves under Steve Wallace as IT. Wallace owns visibility and overall management: a map of what exists, where it is hosted and who maintains it, plus uniform hosting, disaster recovery, backups and Okta access. Resources stay where they are - the original builder can keep maintaining Intelligence Hub from Wolford org, Ryan team can keep building. Start with Wallace maintaining a map. The SRE team carries the run-and-manage weight, partly as a dispassionate owner watching usage: each tool gets an evaluation date, and if nobody uses it (about three months) it is discussed at Peter staff meeting and shut down a month later if still unused.
People: Steve Wallace, Ryan Smith, Brian Dawson, Brady Dibble
Approve the SOC 2 three-year extension on Steve renegotiated terms - same rate, payment deferred, penalty-free cancellation
Oct 1, 2026 · operational · low70% confidence
The SOC 2 auditor opened at 14,976 per year flat for three years, payable on SOW execution (about 10 months early). Peter supported Steve going back; Steve renegotiated to 1,040 at signing and nothing until about June 2027, milestone billing at Net 30, penalty-free termination with the 1,040 refundable before Year 1 fieldwork, and re-pricing requiring both signatures. Peter approved and signed the DocuSign after Steve verified it was the right version.
People: Steve Wallace
Put dates out even at low confidence so the board shows reality, and leads keep evolving their metrics - dropping the ones that get gamed
Oct 1, 2026 · operational · medium72% confidence
At Eng Sync, when Nathan could not get the RLC-H compliance deliverables above 50 percent and did not know if four weeks of scope remained, Peter said to put the dates out even if low confidence so CIQ is communicating reality; same for desktop (we do not have a designer, but let us make some dates up). He set a standing ask that each lead update covers how their metrics thinking is evolving - which are valuable, which are not, and why - and that unvaluable metrics get dropped because they are anti-valuable and get gamed. He shaped Justin Thursday company walkthrough: pink (humans) goes away, triggers at the top, a column of what is true at each stage; an assembly line, not a loop, held against Ryan SDLC-loop framing.
People: Nathan Blackham, Justin Haynes, Ryan Smith, Chris Wolford, Steve Wallace
Jira stays the system of record - a shared git context repo is welcome, a centralized program-management engine everyone must use is not
Oct 1, 2026 · operational · medium64% confidence
Brady described his non-technical program-management agent: ingest Fathom meetings, file action items to a headless Jira project, keep program context in a git repo, and gently ping owners. Peter gave unreserved support to the Jira-backed action-item tracking and the git context repo, but drew the line at publishing one opinionated engine or reference model that everyone is forced to work through; the data should stay open so people stand up their own personal agents, with git as the point of coordination. Brady agreed and plans to hand it to Chris Baek as a proof of concept; Peter flagged he will have this same debate with Chris Baek, who likes to centralize control.
People: Brady Dibble, Chris Baek, Michelle Novicio, Jamie Brooks
Vera Rubin to Google - commit to a bounded duration (at most 3 weeks after node access), not a date, and invite Google to supply its own hardware
Oct 1, 2026 · operational · medium74% confidence
Replying to Tissa request for Vera Rubin timelines, Peter wrote that NVIDIA has committed lab time but cannot confirm when; once CIQ has a node it needs at most 3 weeks to validate Rocky, ensure full functionality and performance, and fix issues; CIQ will update as soon as it has visibility; and if Google has a node it could provide, CIQ would happily do the 3 weeks on that instead.
People: Tissa Senevirathne, Scott Hara, Nathan Blackham, Sultan Alsawaf
Everyone owns their AI spend - no gates or guardrails, but unaware spending is unacceptable
Oct 1, 2026 · operational · high78% confidence
At the AI Committee, the spend dashboard showed Jamin at roughly 33-39k for September. Peter said he will not put gates or guardrails on AI usage, but every person at the company (not just engineers) must know their own spend, the caps and overage thresholds of the tools they use, and treat token spend as part of their cost to the company. A deliberate, informed overage is backed even if Peter would disagree with the math; blind spending is not. Michelle was approved to tell the whole company this is on each person. Ryan 1k overage notification line accepted as reasonable; only Jamin, Sultan and Justin warrant an actual conversation.
People: Michelle Novicio, Stephen Moody, Ryan Smith, Justin Haynes, Jamin, Sultan Alsawaf, Brian Dawson
Vera Rubin access is drop-everything, the goal is proving it works for Google rather than benchmarks, and kernel pre-work starts now
Sep 25, 2026 · operational · medium82% confidence
NVIDIA is working to give CIQ a short window (likely about 5 days, one node) on Vera Rubin hardware, with no advance notice of when it opens. Peter set three things: when the window opens, whoever is involved drops all other work; the goal is getting Rocky/RLC working so CIQ can tell Google it works, not benchmarking; and Sultan starts pre-work now (patch identification, test branch) so the window is productive.
People: Nathan Blackham, Justin Haynes, Sultan Alsawaf, Scott Hara
Build Engineering All-Hands section on Bjorn joint-win narrative - no separate engineering highlights
Sep 24, 2026 · operational · low54% confidence
At AH Prep for the 10/2 All-Hands, Bjorn proposed celebrating momentum as team wins - the biggest wins (RC, Core42) came from engineering and sales working together, and engineering work now lets sales close deals like Toss without engineering involvement. Chris proposed Bjorn and Peter open on it together. Peter agreed, said he wants to focus where Bjorn is pushing, that it is about coordination between engineering and go-to-market, and that he has nothing else to hit - so the engineering section drops its usual standalone call-outs. Before agreeing he asked whether there was a counter-example where CIQ lost something because the teams did not work well together; neither he nor Bjorn had one.
People: Bjorn Hovland, Chris Baek
Treat every RCA as a legal document - Legal review plus Peter personal clearance before it goes to a customer
Sep 23, 2026 · operational · high82% confidence
Peter and Arthur Tyde issued a standing rule to all department heads: unless a customer contract specifically addresses liability, fault and the delivery of a Root Cause Analysis, an RCA is to be treated as an internal document. Before any RCA is shared externally, Legal must review it and confirm it is appropriate to provide, and it must be cleared with Peter personally. The stated reason is that an RCA is a legal document that can unintentionally create legal exposure through statements about fault, causation, or obligations beyond what CIQ has agreed to contractually. Arthur posted the note to #department-heads under a joint Peter-and-I attribution while Peter was in a critical meeting, at Peter request that it be posted with his agreement on the record.
People: Arthur Tyde, Justin Haynes, Ryan Smith, Melissa Kivisto, Dave Dickerson
Clear Wolfgang for the UAE, cut the on-site window to week one, and hand the final pick to Wolford
Sep 23, 2026 · operational · medium95% confidence
Following the 9/16 decision to put a technical body on the ground in the UAE, Peter closed out the open questions in three moves across two days. He talked to Wolfgang, who wants to go. He asked Adam Jackson directly whether a German national can be sent and got a yes the same morning. He told Bjorn in the C-Suite Sync that he does not think the engineer needs to be there for the entire deployment - just the first week or so, when we are going to need to push a button. Then, when Chris Wolford raised Randy as an alternative, Peter said he is fine with it being Randy, that he does not mind, that it is 100 percent Wolford call, and attached the only real constraint: if it is Randy, tell Adam now so the security paperwork starts now for whoever is chosen.
People: Chris Wolford, Bjorn Hovland, Adam Jackson, Wolfgang Resch, Sarah Almaraz
Refuse the Veeam rollback and the never-again promise - fix forward and hold the response until the RCA is understood
Sep 23, 2026 · operational · high94% confidence
Veeam escalated for the third time after a CIQ portal output change broke their CVE scraping script. Melissa Kivisto asked for a rollback and, failing that, a call from Peter explaining a path forward that ensures this absolutely will not happen again. Peter rejected both halves in #department-heads: there is no world where we promise that something will not happen in the future, rolling back is not the right solution at all, we help them move forward and doing so is not complicated. A day later a second breaking change took down their rsync; Peter told the channel there is an RCA in progress and he wants the team to fully understand what happened before responding to the customer.
People: Melissa Kivisto, Justin Haynes, Bjorn Hovland, Dave Dickerson, Ryan Smith
Route all new Shin-brothers requests through Bjorn for a month, in writing, with technical direction staying with the asking manager
Sep 16, 2026 · operational · medium83% confidence
Nathan asked how much CIQ could use Mike and Scott on work outside Core42 - specifically the RLC-H 10.2 lockdown RPMs and updating the STIG and CIS guidelines to match EL10 - because Jason is committed to CVE automation and Oleg is a month or more from starting. Peter did not know the contract limits, said so, said he would find out, and came back with the answer. He then set the interface: for the next month, new requests to the Shin brothers go through Bjorn. Nathan writes a one-page brief on what he wants done and sends it to Bjorn with Peter copied for visibility, and Bjorn makes the ask so that the work happens at Nathan direction. If request volume grows, Peter said they would probably build a pipeline or agreement to short-circuit the routing so managers could go straight to them. On Core42 work specifically, Peter told Nathan to assume they are full time working for CIQ if needed. Nathan accepted and said he would get a one-pager written.
People: Nathan Blackham, Bjorn Hovland, Mike Shinn, Scott Shinn
Put a technical body on the ground in the UAE through Oct 5 rather than run the Core42 deployment fully remote
Sep 16, 2026 · operational · high87% confidence
The Core42 SOW landed the morning of Sep 15 and hardware arrives Sep 18 with a hard Oct 5 deployment date. The deployment was nominally supposed to be fully remote. Bjorn asked whether CIQ needs a body in the UAE just in case, and offered to go himself if there were safety concerns. Peter said he would be a lot more comfortable with someone there, framed it as belts and suspenders rather than a technical necessity, and made the case on a concrete mechanism: having somebody there who can physically push a button is different from having to do this without being able to push a button. He agreed with Wolford that if CIQ sends anyone it should be a technical person. Wolford named Godlove first pick and Wolfgang second; Peter took the assignment conversations himself and said he would have them that morning, including Arsalan on the support side. Bjorn funded business-class travel and a hotel through Oct 5, and declined Adam Jackson offer to ask the customer to cover flights. Peter also declined Bjorn offer to fly out personally and declined the suggestion of sending two people. At the Leadership Roundtable the day before, when Bjorn asked where they had netted out on sending somebody, Peter answered that they should.
People: Bjorn Hovland, Chris Wolford, Adam Jackson, Katie OMalley
Serve Google security due diligence from the Core42 audit corpus rather than rebuilding it in a silo
Sep 11, 2026 · operational · medium70% confidence
Justin surfaced that a security organisation inside Google has been iterating on due-diligence requests for months - answers sent, then more questions, then demands for the actual documents, now a spreadsheet with links. Peter told him not to recreate the wheel, because the Core42 audit has already produced most of that material at a far deeper level. He confirmed he had read and approved the seven internal policy documents Steve sent him that morning, with one routed to Greg, and set the escalation line: involve Peter only if Google asks for something more technical than policy paperwork Steve can pencil-push.
People: Justin Haynes, Steve Wallace, Kelly Hall, Greg Kurtzer
Bound the NVIDIA driver auto-update ticket - 24 hours is the product ask, 30 days is the contractual floor
Sep 11, 2026 · operational · medium75% confidence
Brady brought a ticket asking engineering to move from manual to automatic NVIDIA driver updates, with a 24 hour target he said Justin and Nathan had already accepted with just prioritize it. Peter questioned whether that acceptance had been priced, then directed that both numbers be written into the ticket - 24 hours as product ask, 30 days as the contractual commitment - so engineering knows the real floor and can choose where between them to stop.
People: Brady Dibble, Brian Dawson, Justin Haynes, Nathan Blackham
Refuse to write the RLC-AI contrivance down - say it to Justin, Nathan and Andrew, never in a company-wide channel
Sep 11, 2026 · operational · medium87% confidence
Nathan asked Peter to post the full rationale for the deliberately contrived RLC-AI Spark build into the public RLC-AI channel. Peter declined outright and said he would say it to Justin, to Nathan and to Andrew, but would not write it anywhere the whole company can see. The same boundary appears in Slack the same morning, where he told Brett that he wanted the message going to Brett, Andrew and Jeff rather than wider, and said plainly that it is not a message for the whole company.
People: Justin Haynes, Nathan Blackham, Andrew Jorgensen, Brett Mastbergen
Push speed-over-perfect down into the Justin org and ask him to produce a visible failure that goes unpunished
Sep 11, 2026 · operational · high89% confidence
Peter opened the Justin 1:1 by reconstructing his own discomfort with how he had handled pushback after a talk on AI usage - the pushback was about corner cases, and Peter realised his own answer had been weak. He then asked Justin to reiterate the speed-over-perfection mantra to his people, and escalated the ask: go fast enough that a real mistake happens, so Peter can visibly decline to punish it. He paired this with a demand for QA automation investment rather than manual QA, and set up a next-week whiteboard exercise: what would have to be true to double throughput, what breaks, and what does it cost to stop each breakage.
People: Justin Haynes, Nathan Blackham, Jamin, Ryan Smith
Give the principle then ask for a map of the ChatGPT license ask - fund frontier-tool access for key people, but see the shape first
Sep 11, 2026 · operational · low82% confidence
In the Sept 10 weekly 1:1, Steve Wallace raised that Moody had been pinged in one of the AI channels about getting more ChatGPT licenses, said he wanted to run it by Peter before enabling anything, and offered that what he owed Peter first was probably what this would cost. Peter neither approved nor refused. He named a specific person he was comfortable licensing, confirmed Sultan already has one, and asked Steve to get a map of the ask. He then supplied the governing principle: these tools leapfrog each other, so some of CIQ key people having access to the competing vendor tools is critical, and it is fine.
People: Steve Wallace, Jason Scott, Justin Haynes, Moody
Abstain from the product-naming decision and pre-commit to supporting whatever Marketing picks
Sep 11, 2026 · operational · low82% confidence
In a DM with Lindsay Aamodt on Sept 10, discussing candidate product names Cake, Stratum and Wolfy, Peter removed himself from the decision. He said he does not need to be a part of any decision making on this, that he will happily support Cake, Stratum or Wolfy, and that they should just tell him what the thing is called and he will make it look that way. He added that he will not be in her way. Asked what he cares about, he said he cares that it is a good enough name, and that for him all three are. He supplied his own history and preference without converting either into a position - he told her that he and Bjorn already made a product called Cake and it failed, that he loved the name in the past, and that he will support Cake if she wants to push for it.
People: Lindsay Aamodt, Bjorn Hovland
Set a floor on personal data CIQ staff hand Core42 - passport yes, property deed no, and demand the required list
Sep 11, 2026 · operational · medium81% confidence
Core42 sent a request for personal information as part of background checks for site access ahead of the Sept 18 hardware access date. In #core-42-escalation-members Peter answered with his own position first, tagging Adam Jackson: he will give them a passport, not a deed. In the eight-person Core42 group DM he told Adam there is going to be a problem with that request for info, that he will not give them the deed to his house, that he is confident the bulk of the people on the Linux team will not either, that passports are fine, and that CIQ should be super clear about exactly what information is required. In the DM with Nathan Blackham he repeated that CIQ needs clarity on what info is absolutely required and that he has no interest in giving them his address either. He then tested the requirement himself - he submitted his address, judging it enough for a background check and public record anyway, and reported back that Core42 had emailed asking for additional info including a proof of residency document, for which they accept a utility bill.
People: Adam Jackson, Nathan Blackham, Bjorn Hovland, Dave Dickerson, Michael Shinn, Brian Dawson
Route the RLC-AI latest-driver override through Bjorn rather than overrule Dawson in the public channel
Sep 11, 2026 · operational · medium91% confidence
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.
People: Brian Dawson, Bjorn Hovland, Nathan Blackham, Brett Mastbergen
Take finance out of the hardware pre-approval chain - ramp cards to direct reports, finance documents after the fact
Sep 11, 2026 · operational · medium92% confidence
In the weekly 1:1 with Steve Wallace, Peter said he had picked a fight with finance over the last couple of weeks because people were being hounded over small hardware purchases such as a network switch needed to stand up a Spark. Resolution: finance will issue a ramp card to everyone reporting directly to Peter, good for five thousand dollars a month. Peter approval is still required and the asset-tracking obligation to Moody stays. Finance is removed from prior approval and moved into the documentation chain after the purchase. Large purchases such as one hundred thousand dollars still go through the regular process. Separately, when Erin Fong asked Chris Baek to formalize a request and Peter approval by email to accounting, Peter told Baek that is why she cannot be in the approval chain for things that need to move FAST, and that she can be in the documentation chain after things happen.
People: Steve Wallace, Chris Baek, Erin Fong, Kelly Wall, Nathan Blackham
Collapse nineteen engineering titles into four groups - and put senior principal back only if a manager makes the morale case
Sep 7, 2026 · operational · low74% confidence
In the Nathan 1:1 Peter walked the leveling sheet and set the target explicitly: nineteen distinct titles across sixty people becomes four titling groups. He opened by declining the framing Nathan offered - this is not about correcting overinflated titles, it is about simplifying titling - and said his religion is the simplification, not any specific person. He asked Nathan to validate the mappings for his own people and to build planned promotions into the exercise rather than run them separately. On the senior principal tier, which the collapse removes, he did not decide unilaterally: he asked Nathan to probe Andrew Jorgensen and Jamie Maple on how much they actually care, and said if Nathan argues that senior principals are needed to manage morale on his team, Peter can get his head around engineer plus senior engineer and principal plus senior principal. He also told Wallace the same day that the leveling has cleared Greg and Mariah and that he will sit down per-org to make a plan, committing to Wallace next week after slipping the intent to do it this week.
People: Nathan Blackham, Steve Wallace
Put the NVIDIA Spark bootable-Rocky USB on Justins org - and size it to carry meeting materials
Sep 3, 2026 · operational · low61% confidence
On 9/2 Arthur Tyde asked whether CIQ could produce a Rocky-on-NVIDIA-Spark artifact for events. Peter confirmed the current Spark version of Rocky already is a bootable USB stick and called it super doable, then named the constraints and the owner. Constraint one: the image he holds is old, the current one sits with someone who is out, and he expects to have it in a couple of weeks. Constraint two: it only runs on an NVIDIA Spark - a Mac or other target would need different packaging and drivers, which is a separate ask. He then allocated the work outright: Justins org can build something. He also specified the form factor rather than leaving it open - small ones are fine, like a 128 gig would allow us to include additional meeting materials - turning a bare boot stick into a carrier for collateral.
People: Arthur Tyde, Justin Haynes
Deliver the AI-spend message myself at an engineering all-hands instead of letting the AI committee write a policy
Aug 28, 2026 · operational · medium77% confidence
In the 2026-08-27 Ryan Smith 1:1, Ryan argued that the next AI committee meeting should produce a company-wide best practice on AI spend - consensus around spend, do not use Fable for everything, be self-aware of usage. Peter declined the policy framing but conceded the underlying point: the conversation has to happen and has to be delivered directly to engineering rather than routed through a committee or left to individual managers. He committed to an engineering all-hands the following week and flagged it verbally for capture in the moment. He scoped it explicitly to engineering, excluding Ryan own organization.
People: Ryan Smith, Chris Wolford, Steve Wallace, Steve Moody
Diagnose every AI overage case individually and apply the remedy that case calls for - without squashing AI usage
Aug 28, 2026 · operational · medium81% confidence
Facing an AI token run rate heading toward roughly 3 million dollars a year, with the top ten spenders accounting for about 95 percent of it, Peter refused both a spend cap and a single blanket fix. He directed each manager to work out why the overage is occurring for their own people, case by case, and to do whatever is appropriate for that specific cause - with the standing constraint that the answer must never be to suppress AI usage. He gave different answers for the cases he had already looked at himself: one engineer at roughly 60k a month is justified and was told to keep going; two others at roughly 100k a month between them are low-return and their manager was already digging in; Zorina team burned 12k in August purely because they were hitting the Claude API directly rather than the enterprise plan, so Justin Haynes action is a plan switch. Peter also declined Ryan Smith push to have the AI committee issue a company-wide best-practice policy on spend.
People: Justin Haynes, Chris Wolford, Ryan Smith, Nathan Blackham, Steve Wallace
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
Aug 28, 2026 · operational · medium89% confidence
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.
People: Ryan Smith, Nathan Blackham, Brady Dibble, Dave Dickerson, Greg Kurtzer
Govern AI spend by notification and trust rather than a cap - alert at a thousand over, and if the person knows what they are doing get out of their way
Aug 24, 2026 · operational · medium87% confidence
Peter met with Steve Wallace and Scott Moody on AI and cloud costs Aug 24 at 11am, then recounted the outcome to Ryan and Bjorn an hour later. What he asked for is visibility plus a Slack notification when someone goes a thousand dollars over their limit, followed by a second one. The rule attached to the notification is not a stop - it is: if you do not know you are doing that, stop what you are doing and figure it out, and if you do know what you are doing and it is right and you are a smart person and it is right, I do not want to get in your way. He explicitly declined a single best-practice standard, differentiating by workload: Sultan costs are fine because he is dealing with a CVE swarm and the right behaviour is solve it as fast as you possibly can, whereas Jason Rodriguez spinning up 13 Opus or Fable agents makes no sense - but Peter attributed that to missing visibility rather than to judgment. He named his own next step as a person-by-person conversation with each leader over what he can now see. Separately on cloud costs he closed the question rather than opening it: the split is 100 percent Fuzzball, and he told Bjorn and Ryan they just need to get used to that being the new normal, while committing to sit with Wolford to slice it up.
People: Steve Wallace, Scott Moody, Ryan Smith, Bjorn Hovland, Chris Wolford
Extend abort-the-loop authority from the hiring manager down to every individual interviewer - anybody can pull the ripcord alone, without a debrief or consensus
Aug 21, 2026 · operational · medium70% confidence
At the close of the Friday roundtable the hiring manager mentioned that he already pulls candidates before they reach a debrief, so the panel will not see a roundtable for everyone they interview. Peter extended that authority downward rather than leaving it with the manager. He said he is a huge believer, we are a small team, everybody on this call is a super smart individual, and he is really comfortable with anybody just pulling the ripcord on an interview and saying this one is not moving on. He added that in past environments he was fine with someone standing up and walking a candidate out mid-loop on the grounds of not wasting anybody else time. He explicitly declined to impose it - the hiring manager might not be comfortable with it and Peter said he would leave that up to him. The hiring manager then agreed, saying at this stage in the game he was happy to do that. The exchange happened immediately after a debrief in which the panel had spent roughly twenty minutes on a candidate they all ended up rejecting, and after two of them had traded stories about aborted loops at a previous employer.
People: Nathan Blackham, Andrew Jorgensen, Jonathan Dieter
Move the metrics conversation with Nathan off the tooling and onto the why - which metrics, which were discarded, and how the team is told the reason
Aug 21, 2026 · operational · medium89% confidence
Peter closed the Nathan 1:1 by resetting what he wants from the metrics workstream. He stood it on the foundation that if you do not measure it, it does not change. He then said Max document was a fine first cut and he does not know whether Nathan wants to use it, but that is not the conversation - it is not about what Butler shows. Butler is just building a tool and it will not show me the whys, and it is the whys I want to talk about. He named the specific agenda for the next 1:1: why this metric, why this metric, which metrics you have discarded, and how you are communicating them to your team so they understand why you are tracking certain things. He connected it to his standing complaint that he is not seeing the change in pace he wants and that pounding that drum gets him nowhere - he wants to engage in the concrete bits of what Nathan is holding people to and why, acknowledging that Nathan knows how his own org will respond to a given metric better than Peter does. Nathan took it further himself, saying he should start adding the why to the dashboard, and Peter agreed with a second reason: it keeps people from making an incorrect assumption about why you care and gaming it through misinterpretation rather than intent.
People: Nathan Blackham, Steve Wallace, Max Spevack
Restate every RESF request as a request to CIQ rather than to Nathan - publish the secure-boot ask to all of Linux Engineering so someone else can raise a hand
Aug 21, 2026 · operational · medium88% confidence
Nathan reported that Dieter had asked him explicitly to help with a secure boot POC, and that he would demo it to Sharif, Scott and Dieter on Monday, building it on CIQ hardware because CIQ needs it too. Peter approved the substance and re-cut the framing: let me tweak things ever so slightly to the RESF has asked CIQ to do this, not Nathan. It may be Nathan who is doing it, but the ask should be published in Slack to all of Linux Engineering - the RESF has asked for help with secure boot, I know secure boot, so I am sitting down with them Monday, and if anybody else is interested in understanding how this works or how they can plug into that world, here is the opening. Peter said chances are it is nobody and everyone just pats Nathan on the back, but he wants to buy the chance that one person wakes up and goes that is interesting. He tied it to the wider problem: the RESF needs to stop being five or six people who think it is their clubhouse, and Nathan should be willing to say this contributor should get a structure and a title inside the RESF. In the Steve Wallace 1:1 the same day he committed to pressing Dieter on the same point next week - nobody at the RESF is asking CIQ for things directly, and both Nathan and Steve orgs have resources available.
People: Nathan Blackham, Steve Wallace, Jonathan Dieter, Gregory Kurtzer