Peter Nelson
Jan 23, 2026 - Jul 9, 2026
59
Decisions
0
Active Todos
8
Patterns
Decisions (59)
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.
Pass on Patrick Culp for now (no black mark), re-engage in 3-6 months
In the Round Table hiring debrief for candidates Ben Howard and Patrick Culp, Peter decided to pass on Patrick Culp for now - explicitly not a hard rejection - with intent to re-engage him in three to six months. Stated reason: he wants breadth of past experience coming into Nathan org right now. Peter committed to co-drafting the decline and re-engage message with Bree Clasen.
Support Nathan CVE-first prioritization over the Google minimal-kernel delivery; own the customer comms
Nathan flagged that in-flight critical local-privilege-escalation CVEs collided with the committed 6.18 minimal-kernel delivery to Google and called for CVE remediation to come first. Peter backed that call rather than making it: agreed to a bounded slip (no more than a week, not three), was comfortable asking the team to work a weekend to verify already-built patches, and took personal ownership of communicating the slip to Google - framed as value-add (surface only the CVEs Google benefits from), not an apology. Peter wrote and sent the explanatory email to Tissa and the Google team the same day.
Restructure the Tuesday staff meeting to org-by-org TPS ownership and un-fork the TPS report to one shared source
Peter is firmly changing how he runs his Tuesday staff meeting: instead of Peter walking the team through the TPS report, each org owner presents their own section and owns that part of the meeting. He also committed to un-fork his drifted TPS report back to a single shared report, visible to everyone three days ahead.
Reinforce that an automated Linux CI/CD pipeline is one of the top-3 H2 company objectives
Peter had already set an automated Linux CI/CD pipeline as one of CIQ three top company objectives for H2 (base decision not previously captured). In the Max 1:1 and Engineering Weekly he reinforced to people that it is there and that it is critical to Linux delivery - a company objective, not just a Nathan-team objective. Logged as reinforcement.
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.
Set kernel-independence north star; justify RESF-CIQ pipeline convergence investment as the path to it
In the C-Suite Sync, after conceding to Bjorn that CIQ must keep racing Red Hat on critical CVEs today (customer parity is a non-negotiable sales requirement for Citadel, Rakuten, Veeam), Peter named an explicit north star: a future where CIQ is far less tightly bound to the Red Hat kernel via an opinionated, upstream-first posture. He validated with Greg and Bjorn that this is a real future option, then framed the present-day decision as investing now in the RESF and CIQ pipeline and tooling convergence as the infrastructure that makes the north star reachable later. He was explicit that this changes nothing for customers today.
Mandate 24-hour Sev-1 outage auto-escalation to estaff and AE
After the Fyr Fuzzball outage ran roughly 5 days without surfacing to leadership and the customer had to ping Horn directly to force escalation, Peter directed that any Sev-1 or customer outage open past 24 hours must automatically notify estaff and the account AE, built into tooling so it does not depend on a human judgment call. Ryan operationalized it as Zendesk automation plus CCing named-account AEs at ticket creation.
Fix performance-review confirm-receipt acknowledgment — hand-deliver packets now, push HR for global wording change
When Andrew Jorgensen objected that Ripplings mid-year review flow forces employees to click confirm receipt before they actually have the packet, Peter sided with him. In his lane he directed an interim fix: managers download and hand-deliver packets directly so employees physically have them before acknowledging (told Nathan to send Andrew his packet; floated telling all his managers to email packets to everyone this round). As advocacy in HRs lane, he asked Mariah to change the button globally to access your packet and remove the receipt-confirmation sentence. Final wording decision deferred to the 6/16 C-Suite.
Sensitive Decision
Sensitive Decision
Sensitive Decision
Greenlight Chris Wolford on continuous recruiting — always be fishing, no open req required
Peter granted Chris Wolford standing latitude to recruit continuously: fill his two current open reqs, but also keep feeding recruiter Bree candidate profiles and interviewing strong people even with no open req. Extends Chris a trust-gated operating model to build a faster-paced bench rather than hiring only against approved headcount.
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.
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).
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.
Coach Mariah toward sharper, peer-level feedback posture — Reno trip offered
Following a heated DM disagreement about how to handle a senior IC's return-from-leave conversation, Peter offered Mariah an explicit choice: be treated the way Peter treats Bjorn and Greg (sharp, direct, unvarnished disagreement) or stay softer. Peter framed the conversation as investment, named that Mariah is undersized for where she could be ('I would like to see you pulled more into the core of things here'), and offered to be in Reno end of next week (Thursday) to discuss over lunch.
Ryan to POC AI-driven Veeam image builder, gated on Justin-approved test suite
Ryan will POC an AI-driven image builder, starting with Veeam, that automates custom image builds, testing, and documentation. Hard gate: AI-generated images must pass a Justin-approved test suite to prevent hallucinations. Long-term vision: a 'Chipotle line' image configurator letting users compose custom, repeatable builds from validated components.
Tighten Jira-as-system-of-record into active enforcement — instruct teams to ignore Slack-only requests
All significant work must be in Jira to count as a commitment. Peter will instruct teams to actively ignore requests that exist only in Slack. This escalates the Apr 18 quality decision from policy ('ticket your work') to enforcement ('we will refuse to act on un-ticketed requests'). Justin owns the enforcement in Build/Test/Deployment, the function most contaminated by ad-hoc Slack asks.
Ryan Smith owns docs.ciq.com
docs.ciq.com was orphaned after Gwen's departure. In Ryan's 1:1, Peter assigned ownership to Ryan, who will coordinate with Arian and Steven on the existing work.
Sensitive Decision
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.
Defer ARM64 Pro Hardened build until Core42 commits — group decision Peter endorsed
In Apr 26 Sovereign AI response review meetings, the team — with Peter participating — decided the response language to Core42 will acknowledge that Pro Hardened on ARM64 (and FIPS-143 ARM certification) is contingent on a client commitment, not unilateral CIQ investment. ARM64 build estimated weeks not months once committed; FIPS-143 ARM is ~$200k / 4-6 months and gates on a deal commitment. Peter explicitly told the room: "We are going to need Nathan to say when. I am not going to be able to say on this call."
Sensitive Decision
Block Max's calendar — don't schedule anything for the time being
In a DM (4/17 11:10 AM Pacific), Peter directed Sarah (assistant) to stop scheduling anything for Max Spevack for the time being. This operationalizes the indefinite-leave posture triggered by Christina's 4/16 7:45 PM call telling Peter that Max needs time away. Rather than letting Max's calendar keep generating missed-meeting signals to the org (like the 4/16 1:1 and interview no-shows), Peter chose to block new scheduling entirely until further notice.
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.
Open hiring for a dedicated Ascender engineer
In the Design Sync, Peter took the action item to draft an Ascender Engineer job requisition and start the hiring process. Root cause: engineers Jimmy and Larry rejected a UI update PR for Ascender Pro citing the internal Quantic design system is not open source — an objection that is irrelevant since Ascender Pro is a closed-source commercial product. Bjorn will handle the immediate Jimmy conversation next week. Peter's move is structural: create an engineering owner whose role explicitly covers the closed-source Ascender Pro commercial mandate, so the category of blocker goes away.
Quality initiatives must be ticketed visible work, prioritized by Product
In the Brian/Brady weekly sync, Peter reinforced that quality cannot live as implicit expectations — Product must define and prioritize quality initiatives as explicit tickets that compete for resources against feature work. Engineering will only prioritize what is tracked. Companion frame: Exit Criteria are the product promise (Product owns, Engineering can challenge via debate); QA is delivery validation, split between Engineering (general releases) and Ryan's org (customer-specific fixes in mirrored environments). Brady to split test automation from build automation into a high-priority CI/CD ticket. Peter to verify with Justin that the build process at minimum runs a boot test.
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.
Shaped Ryan's H-1 strategic plan with specific direction
Reviewed Ryan's H-1 plan and gave specific strategic direction: reframe team skill tracking to outcome metrics, loop Product into GTM translation validation, create simplified 4-page sales pitch deck, align with Max on Rocky Linux upstream strategy (pure RESF vs hybrid best-of-breed) before engaging community, and present AI-assisted goal-setting process at Engineering Weekly Sync.
Expanded NVIDIA licensing ask to include Fabric Manager + NVISM
Expanded the NVIDIA licensing negotiation scope beyond DOCA-OFED to include Fabric Manager, NVISM, and other critical InfiniBand components not currently in the CUDA bundle. Sent email to Scott Hara while Bjorn was drafting the DOCA-OFED amendment language.
Committed to aggressive NVIDIA GPU Operator self-certification timeline for GTC
Led GPU Operator Self Certification meeting with NVIDIA. Committed CIQ to building pre-compiled GPU driver containers for Rocky Linux (mirroring Ubuntu model) and pursuing self-certification targeting preliminary completion by end of next week to support a GTC announcement.
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.
Approve Jason Rodriguez performance exit path
Approved Nathan's plan to tell Jason Rodriguez he's 'not meeting expectations' and create an exit path. A 1-month exit plan is acceptable if Jason agrees. Performance gaps include missed deadlines (shim review for Rocky 9 late, Rocky 7 review pending) and unshippable code (large PR unlikely to pass review).
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.
Established 'what vs how' framework for Product-Engineering communication
In weekly sync with Brady and Brian, established a clear framework: Product defines the 'what' (exit criteria with specific, aggressive targets like 'ISO builds <4 hours'), Engineering defines the 'how'. Vague communication to leadership creates unnecessary reactive work and must stop. Escalation path defined: weekly syncs or on-demand to Peter for process breakdowns only.
Committed to creating CVE remediation value driver for GTM
Committed to creating a value driver for CVE remediation work after learning that remediation volume jumped from 1 to 86 per week. Timeline is ~2 months to develop the story after validating the new process is sustainable.
AMD RLC Plus Strategy: Speed-to-Market with Minimal Scope
Decided to prioritize speed-to-market for the RLC Plus AMD co-marketing launch. The initial build will use upstream AMD packages (pre-built ROCm), the kernel driver (not upstream DKMS), and enable EPEL. Deferring the more robust in-house rebuild until market traction is proven. Justin Haynes to draft proposal and decision matrix.
Time-based releases concept - trains leave on schedule
Consider moving to time-based releases where engineering ships whats ready on a fixed cadence (e.g., monthly or bi-weekly). Product must scope features to fit the timeline rather than engineering stretching to fit scope. The train leaves whether youre ready or not.
PRD first drafts are gravel - meant to be thrown away
Get product to understand that the first iteration of a PRD exists to be thrown away. Its gravel, not precious. Engineering questions should come fast and furious, and the document should go through massive churn. Pride of authorship must be eliminated.
Stop coaching product, move to SLAs
Stop trying to teach product managers (Brady, Brian, Dawson) how to do their jobs better. Instead, provide prescriptive SLAs - clear timelines and direct questions. If they dont like the dates, they can restructure their requirements. Leave it on the floor and walk away.
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.
Project Shackleton - RESF contingency infrastructure
Build a parallel mirror of all RESF infrastructure in AWS (Git repos, Koji, vault/pub, Mattermost history) with goal of restoring Rocky Linux builds within two weeks if Lewis triggers his kill switch. Everything built with CDK and Ansible for repeatable deployment.
Servant leadership requires clear targets
Servant leadership and mentoring are fine, but must be paired with clear targets. Without clear targets, you cannot train the system. The AND between servant leadership and clear targets is mandatory - you cannot have one without the other.
Quality investment must serve velocity
Quality and automation investments are acceptable if the thesis is this will massively increase velocity in 3 months. Quality for its own sake is not the priority. Every quality investment should have a velocity payoff hypothesis attached.
Find the ceiling approach to velocity
Rather than incrementally improving 5% at a time safely, push until something breaks, then figure out if the breakage is fixable or a real ceiling. Air cover provided for aggressive experiments. Nobody gets fired for trying to go fast and breaking things.
Trustless processes over building trust
Focus on building contracts and processes that work without trust, not on building relationships. Good fences make good neighbors. Trust becomes a bonus, not a requirement. Contracts are what matter - relationships are nice to have.
PR standards in AI era - own the test suite, not the code
In an AI-enabled world, engineers should own the test suite and exit criteria, not necessarily every line of code. Quality comes from tests passing, not from reading every line. Engineer accountability shifts from I wrote this code to I own that this code passes these tests.
Team building over individual protection - Machiavellian approach
Stop protecting individuals at the expense of team success. The body being taken care of is the team, not individual engineers. Every day spent betting on someone who wont make it hurts the team. You already know who youre going to fire - just convince yourself youve done due diligence.
Trinity backfill for RLCAI/RLCH work, not maintenance
Use Trinitys backfill headcount to hire for RLCAI and RLCH work, not maintenance. Look for someone who can hold their own technically with Maple but will push AI adoption aggressively. Jamin identified as strong candidate - automation-first thinker, delivers and iterates, QA mindset.
Aggressive goal-setting philosophy - undercut estimates, force innovation
Set targets that seem impossible (e.g., 2 months instead of historical 6 months) and let the team figure out how. Success is not just hitting the target - its learning and attempting new approaches. The managers job used to be to pad estimates; now its to undercut them.
AI ownership standard - own everything you submit
Engineers must fully own everything in documents and code they submit, regardless of whether AI generated it. Using AI is expected and assumed. Submitting AI output you dont understand or endorse is not acceptable. Quality and accountability matter, not authorship.
Nathan job redefined - build a team, not deliver outputs
Nathan deliverable is a team that can adapt and learn, not technical outputs. Focus shifts from figure out how to deliver X with current team to build a team that can deliver what CIQ needs. This is fundamentally different from traditional engineering management.
Transfer Depot operations from Justin team to Steve team
Depot operations will transfer from Justin team to Steve team. Justin team will define the architecture for moving Depot to object storage, then hand off execution to Steve team for provisioning, infrastructure, and monitoring.
Address Damen visibility/recognition gap through demos
Damen will present at the Monday demo day (11 AM PST, on Bazel) to increase visibility. Peter will attend to show support. Peter committed to investigating and fixing the systemic visibility gap for all engineers, not just Damen specific case.
Pursue NVIDIA self-certification path for NVAIE integration
CIQ will pursue the self-certification path for NVIDIA NVAIE integration, targeting a GTC announcement. Will adopt NVIDIA preferred embedded license model, integrating NVAIE license cost (~$4,500/GPU) into CIQ product and providing L1/L2 support.
Related Patterns (8)
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.
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.
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.