Reflections
50+ recent reflections
Tuesday, May 12, 2026
Tuesday after a long Monday window. Three decisions, all execution-layer follow-throughs on the structural-lever arc. D1 converts the 5/11 Leadership Roundtable vuln-handling commitment into three operational pillars (process redesign with Chris Baek, tooling commitments to ask Greg for Claude whitelist + stand up unbridled LLM on Fuzzball, kernel philosophy review pulled forward to early June). D2 puts a named boundary and revisit trigger on a direct reports personal-health leave extension (6/5 cap with Bjorn co-consulted on the generous-leaning decision; Mariah flagged precedent in writing). D3 sets the 5/22 Engineering QBR as a collaborative working session with three named topics — the third (streamline communication and increase work visibility) is the load-bearing one because it is the same theme that drives the Jira-as-record arc. Customer/sales meetings on the calendar today (Spectro Cloud, Cadence, SSC/Ascender) were NOT Peter — Dave Dickerson and Scott Benson recorded them; Peter not in participant lists.
Wins
- Converted yesterdays LRT commitment from C-suite promise into specific Jira-ticketable work across process / tooling / strategy layers within 24 hours — the externalize-then-operationalize cadence is now visible across three consecutive days (5/8 internalize → 5/11 externalize → 5/12 operationalize) - Got an explicit boundary + revisit trigger on the Max leave extension in writing with Bjorn pre-consulted — Mariahs precedent flag now lands against a named structure rather than open-ended generosity - Used Fuzzball as the answer to two strategic problems at once: vuln-investigation tooling gap AND the AI sovereignty dogfooding story Brady/Brian have been developing - Sarah/Peter sync surfaced Yordan absence from QBR as a separate signal worth direct conversation — caught early enough to act on this week
Challenges
- Five Greg-asks now queued in the same week (Claude whitelist, AWS Mirror Manager, Citadel support duration, Joseph Tate comp from 5/11, Ascender JD coming Thu/Fri via Bjorn-scheduled Jimmy meeting) — risk of asks-in-a-bundle diluting individual signal weight - Brady de-prio carryover from Fridays reflection still not visibly closed three business days later - Yordan QBR-absence conversation has not yet happened — the longer it waits the more it reads as benign neglect rather than deliberate omission - Mid-year performance reviews due 5/24 with the cycle only ~50% complete at the midpoint — Mariah flagged at HR weekly that directs are behind
Monday, May 11, 2026
Three-day window (5/8 PM through Monday 5/11). Light calendar Monday — Greg 1:1 + Leadership Roundtable. Three decisions, all extending the structural-lever arc into new domains. D1 executes the 4/17 Joseph Tate retention commitment — formalized in an email to Greg+Mariah after verbal alignment in the 1:1. D2 externalizes the 5/8 internal build/test infra commitment to LRT — cross-functional commitment now binding Bjorn, Greg, Chris Baek, and Lindsay; Chris owns short-term process definition, Peter owns long-term infra. D3 opens the strategic question Saturday in #department-heads: what Dirty Frag means for kernel posture, upstream binding, RESF relationship, and RLC/RLK brand meaning — staged as agenda input for the mid-to-late June LA product-strategy session with Bjorn and Greg. Customer/sales meetings on Monday calendar (UMS, UND, IMMIX, NLIT-Sandia, SHI, Fyr, Wisk, Zymo) were NOT Peter — recorded by sales team, Peter not in participant lists.
Wins
- 4/17 Tate retention commitment closed with formal proposal in 24 days — inquiry → formal ask sequence completed before attrition risk converted to attrition - Saturday #department-heads message converted Dirty Frag exhaustion into agenda input for the LA session — same exhaustion-as-diagnostic playbook that drove the 5/8 internal commitment, now applied at the strategic-identity layer - LRT vuln-handling commitment paired deliberately with Chris Baek's short-term process work; Chris pulled in Lindsay/Ramesh/Melissa to expand the doc — companion alignment achieved without separate negotiation - Nathan's team receiving $2,500 OPA for Dirty Frag remediation; Greg taking lead on the announcement (Peter approved Greg's draft) — Nathan's public credit visible to engineering org without Peter needing to author the praise - Joel/Ashish intro (5/8) — personal-network connection brokered between IAG Capital and former employer; relationship-capital deposit
Challenges
- Friday's reflection named Brady de-prioritization follow-up, LGU+ contract language verification, and NVIDIA/Scott Monday AM as Monday priorities — none of those visibly happened. Monday calendar was Greg 1:1 + LRT only; the named priorities slip into Tuesday or later - D3 RLC/RLK question opens four entangled strands but the venue is mid-to-late June LA session — risk that the framing decays between now and then if not actively kept warm in Nathan/Justin 1:1s next week - Bjorn DM about Ascender JD reveals memory/handoff drift: Peter recalls a JD coming across his desk but didn't generate one — ambient knowledge gap on hiring inventory
Friday, May 8, 2026
Short window (5/7 PM through 5/8 AM, after the 5/7 morning reflection covered Nathan/Steve/Ryan 1:1s). Two decisions, both extending the structural lever set into new layers. D1 prioritize build/test infrastructure to eliminate reactive engineering interrupts — committed in Brady/Brian sync after Dirty Frag took Linux engineering offline 24 hours; same lever as paved-paths Jira (5/7) and strategy/tactics coaching (5/5), now applied to the incident-response layer. D2 reject open-ended LGU+ RHEL/OEL support commitments — same-day intervention before signing, surfaced by Justin → Nathan → Peter; third member of the GDC/Rakuten contract-discipline arc, with Peter explicitly comparing in the Nathan DM. Hard Rock Digital sync (Greg/Patrick/Scott from CIQ) and Sovereign AI Continuity Focus (Dave Dickerson recorded) were NOT attributed to Peter — calendar attendee ≠ attendance, and neither showed Peter as participant in Fathom.
Wins
- Dirty Frag response: kernel team patched and shipped overnight with clean handoff across timezones; Brady noted in #department-heads this is a big shift from a year ago — credit Nathan for geo-diverse team design that made the round-the-clock progress possible - Brady arrived at the Brian/Brady sync ASKING for a de-prioritization proposal (per next-steps), which means the 5/5 strategy-first/tactics-second coaching has landed in his framework - LGU+ contract intervention happened pre-signing rather than post — earlier in the lifecycle than GDC or Rakuten interventions; pattern is moving forward in the contract lifecycle - Used the Mythos framing in #department-heads to publicly recast incident response as a structural problem rather than a heroics problem — sets the frame before Brady proposes what gives
Challenges
- TPS deltas continue to age 1 day each: Citadel OOM 7d→8d, Kernel CI Auto M2 7d→8d, RLC Pro Hardened 9.7 10d→11d, Self-Serve Portal Bootc 13d→14d, AMD Fuzzball POC 37d→38d (still 0%) - One fresh date-change-near-deadline: Justin pushed RLC Pro 9 AMD GPU Support May 8 → May 15 the day before deadline. Not yet post-deadline like the 5/5 fires, but the pre-deadline edge is the precursor pattern - Brady still needs to come back with the actual de-prioritization list — the build/test infra commitment is announced but not yet funded; risk of drift is real - LGU+ contract resolution is in flight — Bjorn pushed back lightly (we agreed to give answers); if final language drifts back toward SR-ticket commitment, the engineering veto becomes performative
Thursday, May 7, 2026
Two-day window covering 5/6 (San Jose office day) and 5/7 (Reno QBR day-trip) — eight decisions across hiring, performance evaluation, process structure, and technical gating. The structural lever Peter set yesterday (3-tier board hierarchy + strategy-first/tactics-second framing) executed at the operational layer this window: Justin 1:1 mandated paved-paths Jira initiative + Jira-as-system-of-record (D3) — direct response to Brady CVE post-mortem. Nathan 1:1 approved Veeam-related kernel hire (D1) and set explicit AI-inference benchmark gate for Icicle (D4) — no more drifting on synthetic results. Ryan 1:1 resolved the Owen ambiguity (D2) by routing him to Maxs AI tooling for definitive evaluation; same meeting Peter committed to ask Bjorn to deliver ARR/Series-B/dilution rationale to engineering (D7) — Product owns the why. Steve 1:1 set Moody senior-or-managed expectation framed as response to his growth ask (D6) and aligned on late-August dedicated security hire (D8). #distinguished-leaders thread surfaced senior leadership candidate position (D5): open to talk, no pressure, will not give away the kingdom — paired with Mirantis-acquired and Core42 smaller-deal context. Day-trip to Reno for QBR executed cleanly per yesterdays coverage plan.
Wins
- Yesterdays 3-tier board hierarchy converted into operational-layer execution: Justin 1:1 landed paved-paths mandate AND Jira-as-record AND ready-for-eng accuracy requirements in a single meeting — same lever, deeper layer - Owen ambiguity resolved by structured experiment (D2) rather than picking a side between Bjorn/Max/Nathan/Ryan disagreement — defensible and observable - Icicle gate (D4) is sharp: real AI inference on H100, not synthetic; prevents the project from drifting through ambiguous data - Veeam hire approval (D1) lets Nathan run Sergei + Twitter/EC2 referral in parallel — kernel bench grows ahead of urgency - Moody framing (D6) preserved development path while applying senior-bar — coaching, not punishment - Reno QBR day-trip executed cleanly per yesterdays Mariah-lunch + C-suite-intro plan; no schedule failure
Challenges
- TPS deltas continue to age: Citadel OOM and Kernel CI Auto M2 now 7d overdue (was 5d on 5/5), RLC Pro Hardened 9.7 now 10d overdue (was 8d), Self-Serve Portal Bootc 13d overdue (was 11d), AMD Fuzzball POC 37d at 0% - The post-deadline date-change failure mode that hit Wolford and Wallace 5/5 (3 fresh post-deadline changes in one day) did not produce new fires today — but the existing slips are not closing either - Senior leadership candidate flow is steady-state but each one consumes leader time at the C-suite layer; cost amortization comes only if the bar holds (D5) - Owen evaluation experiment is right but takes ~3 weeks to deploy (Max returns from leave) — gap between decision and signal is real
Tuesday, May 5, 2026
Tight 21-hour window dominated by structural execution of yesterdays push. Peter and Bjorn formalized the Three-tier board hierarchy (Strategic EPICs / Value Drivers / Tactical Jira) across three meetings — C-Suite Sync, Eng Weekly Sync, Peter/Bjorn 1:1 — with Greg agreeing to disagree-and-commit once rules are documented. The personnel consequence is staged: Brady role moves to project/program management. Peter coached Brady on the 2-step framework (strategy-then-tactics) in their weekly 1:1, then enforced it live 90 minutes later in a CVE post-mortem group DM when Brady tried to skip step 1 — Your only job is prioritization. Step one is answer my question. Step two will never happen absent step one. Never. Not one time. Brady eventually conceded. Reno QBR coverage locked: Peter delivers C-suite intro Thursday morning (Bjorn arrives PM, Greg in Houston). Justin added to tomorrow Binarly meeting; debrief sequenced AFTER not before to preserve unfiltered take.
Wins
- Three-tier board hierarchy landed across three forums in one window — yesterdays push to Bjorn converted into a structural commitment with Greg disagree-and-commit pathway - Coached Brady on the strategy-first framework in 1:1, then live-enforced it in DM 90 minutes later when Brady deviated — boundary visible to Brian as well - Auto-logged 2 high-confidence decisions (D1 93%, D2 92%); D3/D4 confirmed without correction - Yesterdays PPL-realign todo (sort 8) executed today — the alignment with Bjorn happened in the 1:1 - Reno QBR coverage solved without single-point failure: Peter early Thursday, Bjorn afternoon, Greg in Houston
Challenges
- TPS deltas continued worsening: Citadel OOM and Kernel CI Auto M2 each now 5d overdue (was 4d), RLC Pro Hardened 9.7 now 8d overdue (was 7d), Self-Serve Portal Bootc 11d overdue (was 10d), AMD Fuzzball POC 35d at 0% - THREE new post-deadline date changes happened TODAY: Fuzzball Volume Provisioners and Fuzzball hostpath volumes (Chris Wolford, 6d after deadline) and Unified Cloud Distribution Azure (Steve Wallace, 31d slipped, 5d after deadline) — exactly the failure mode Peter has been pushing on since 4/14, now with Chris W and Steve W signatures - OLAMA/VLLM ticket hygiene exposed leadership info gap because Nate is out — single-person dependency on the Ready-for-Engineering transition - Brady CVE post-mortem in DM showed how much resistance the strategy-first frame still draws from a tactical-by-default Product muscle - $5k/$15k Rippling decision drift: Wallace acknowledged the slow surfacing pattern but the meta-process fix is parked for Friday rather than decided today
Monday, May 4, 2026
Three-day window dominated by structural fixes to the Product-Engineering interface. Peter formalized three companion decisions that all share the same shape — externalize friction back to the requester so layer separation holds: (1) docs delivered via Jira exit criteria, (2) Engineering veto required on custom deals, (3) PPL must return to strategic epics with granular tasks pushed to JIRA. Two large-customer commercial calls held the line on the same principle: Rakuten gets a three-tier proposal where 8.6 support carries an $800k-$1M PS price tag, and Everfox gets a $2M front-loaded year-one floor (rejecting the $600k back-loaded structure). HR weekly opened a broader performance review window across direct reports; Mariah was authorized to escalate Stephen Moody delays directly to Peter, bypassing Wallace as a near-term workaround. CVE response continued: 9 of 10 Copy.Fail patches landed; Peter pushed back on Greg framing about the patches and committed to driving the Dieter conversation about upstreaming the work to RESF.
Wins
- Structural fixes landed as a coherent set: docs process + Engineering veto + PPL realignment all share the same layer-separation lever — three companion decisions in one window - Held the Everfox $2M front-loaded floor without softening, applying the 1/29 precedent that worked - Three-tier Rakuten proposal makes 8.10 migration the easy path and prices 8.6 support at real cost — preserves CIQ kernel team capacity - Auto-logged 2 high-confidence decisions (D2 92%, D4 93%); zero corrections through the walkthrough - Caught a 6-week Moody/Rippling pattern that Wallace had not escalated; surfaced into Peter visibility chain before the broader Wallace conversation
Challenges
- TPS deltas worsening across the week: CLK 6.18 slipped 16d (Apr 29 → May 15) AND date changed AFTER deadline by 5d, RLC Pro Hardened 9.7 now 7d overdue (was 4d), Citadel OOM 4d overdue (was 1d), Self-Serve Portal Bootc 10d overdue (was 7d), Kernel CI Automation Milestone 2 now 4d overdue - Pattern of date-changes happening AFTER deadlines (CLK 6.18, RLC+ 9 ISOs, RLC Pro 9 ISOs, RLC Pro Hardened 9.7, RLC Pro 9 AMD GPU) — exactly the date-hygiene failure mode Peter has been pushing on since 4/14 - AMD Fuzzball POC now 34 days overdue at 0% confidence — needs explicit kill-or-revive call - Ryan-Nathan Icicle testing wires-crossed: each thought the other had it, testing got de-prioritized, Ani patent window 1-2 weeks - May launch cadence (RLCAI 5/14) at risk because Ollama/VLLM tickets still in Ready for Engineering — forcing Peter to commit to firm dates by 5/5 11am
Friday, May 1, 2026
Two-day window dominated by an all-hands Linux kernel CVE response: CIQ found and is shipping an extra fix that RH/CentOS missed, contributed it upstream (acknowledged for inclusion), and pushed to be first EL distro to release. Customer reassurance is the primary goal; public proof point that CIQ contributes to security and is large enough to serve big customers is secondary. Coreweave deal closed in parallel ($10M ARR threshold crossed). Senior IC return-from-leave conversation framed by Peter as PTO + path-forward, not corrective communication; Peter held that line firmly with HR. Ryan's scope expanded materially: docs.ciq.com ownership + AI-driven Veeam image builder POC. Justin instructed to enforce Jira-as-system-of-record by refusing Slack-only requests. Mariah offered explicit peer-tier coaching with a Reno Thursday in-person follow-up.
Wins
- Found a kernel patch RH missed and gave it back upstream (acknowledged for merge) — credibility move that lands in the same news cycle as Coreweave closing - Coreweave booked, $10M ARR threshold crossed for the first time - Held the line with HR on senior IC return-from-leave framing — protected against the worst-case (no return) at the cost of mild discomfort with HR - Ryan's portfolio meaningfully expanded: docs.ciq.com + AI image builder POC + Intelligence Hub repurposed as data lake - Mariah received explicit peer-tier coaching offer + in-person Reno follow-up — used a moment of friction as a coaching window
Challenges
- Three TPS items overdue beyond prior reflection: RLC Pro Hardened 9.7 Image Release now 4 days overdue (was 2), Self-Serve Portal Bootc OCI 7 days overdue (was 5), Citadel OOM newly overdue 1 day, CLK 6.18 newly overdue 2 days, Kernel CI Automation Milestone 2 newly overdue 1 day - New 29-day slip on GCE ARM Mellanox CX-7 RDMA (Apr 30 → May 29, Nathan), and 29-day slip on RLC Pro AI OCI Container Images (Apr 30 → May 29, Justin) - RESF infrastructure project blocked 1.5 months on AWS access; pre-provisioned account bleeding ~$10k/month while idle; threatens May Rocky point release stability - RESF Board Resolution items still ~33 days overdue - LinkedIn FUD claiming CIQ behind on the CVE — public messaging response still pending Lindsay/Nathan coordination
Wednesday, April 29, 2026
Two-day window centered on Day 1 of the IAG Silicon Valley Summit. Linux engineering bench-building continued — activated the dormant Serge Hallyn introduction by handing the relationship to Nathan. While at IAG Peter assigned Justin (not Nathan) ownership of the Binarly engineering relationship, empowered Nathan to defer the Hassan/Google secure-boot working session if Engineering was not ready, and sent IAG/Sam a structured operational due-diligence note on Raven Resonance with explicit scope bounds.
Wins
- Linux engineering hiring pipeline continues unaffected — Serge Hallyn intro activated and routed to Nathan - Nathan empowered to make a real call (defer or proceed) on the Hassan working session — leadership growth signal - IAG operational note on Raven Resonance lands with disciplined scope (operational mechanics yes, market opinion no) — preserves credibility for future LP assessments
Challenges
- Three TPS items still overdue from prior reflection: RLC Pro Hardened 9.7 Image Release (74%, now 2 days overdue), Self-Serve Portal Bootc OCI Acceptance Testing (100%, 5 days overdue), Fuzzball on Oracle Cloud (95%, target slipped to May 1) - RESF Board Resolution items now 33+ days overdue (was 31 last reflection — getting worse, not better) - RLC Segmentation: RLC Pro 9 Cloud Marketplace remains BLOCKED at 96%, Chris Baek slip now 20 days - New concern surfacing: FIPS 140-3 for CIQ Linux Kernel 6.18 at only 37% confidence for Jul 31 target
Monday, April 27, 2026
Friday, April 17, 2026
April 17 was a process-discipline and positioning day. Peter repositioned Core42 from a Fuzzball-only sale to a full-stack compliance partnership — using the Tech Dive Part 2 scope revelation as a positioning lever and applying his reshape ambiguous customer asks into defensible structure play (same move used with Tissa a day earlier). He reinforced a broader quality mandate with Brady and Brian: quality initiatives must be ticketed as visible work competing for resources, grounded in the Trexel FIPS/disk encryption failure. Structural people moves: opened hiring for a dedicated Ascender engineer to fix the Quantic/Jimmy-Larry PR rejection pattern at the source, and decided to manage Wesley via the Greg channel with a Chris boat-anchor trigger rather than putting him on active performance management. GLibC/Jeremy Allison escalation root-caused as Product-prioritization bypass. Nathan shared the Core42 BIS Export License compliance matrix DRAFT later the same day.
Wins
- Fuzzball [Engineering] Observability shipped today (was overdue at 80% on Apr 16) - RLC Pro AI OCI Container Images moved to Ready for Release at 91% confidence - Core42 opportunity expanded from Fuzzball to full-stack partnership — positioning momentum - Chris Wolford committed to two weeks of perfect Jira hygiene to validate Product's post-ship change metrics (continuation of Apr 14-15 Jira hygiene arc) - Peter reshaped Wesley conversation from all-perf-issues-are-PIPs to trigger-based escalation, preserving Chris's bandwidth
Challenges
- Release CLK 6.18 now overdue by 1 day (was on target Apr 17) - RLC+ 9 ISOs and Netboot overdue by 1 day - Self-Serve Portal P4 Centralized License Management overdue by 1 day (still Acceptance Testing at 91%) - RLC Segmentation RLC Pro 9 Cloud Marketplace now 8 days overdue (was 6 days on Apr 16) — BLOCKED status continuing - Trexel FIPS/disk encryption failure surfaces that the only confirmed automated check is does it boot — CI/CD gap is broader than one customer - GLibC/Jeremy Allison work bypassed Product prioritization entirely — process failure requiring Brady to split tickets
Thursday, April 16, 2026
Wednesday, April 15, 2026
Tuesday, April 14, 2026
April 11-14 covered board meeting prep, partner alignment, retention, and accountability. Peter mediated between Greg and Max to get the Dieter/RESF justification ready for the board meeting, translating between Max's technical perspective and Greg's political needs. He proactively ran a skip-level retention check-in with Alex de Wergifosse after Ian's departure from Fuzzball, establishing a mutual transparency pact and recurring 3-4 month cadence. In Leadership Roundtable, he publicly committed to a tough date hygiene conversation with directs after ongoing estimation failures (58% miss rate), requesting magnitude data from Chris Baek. He escalated a Google/NVIDIA messaging discrepancy to Bjorn for same-day resolution — Google giving NVIDIA conflicting info about Rocky usage while engineering work is on track. He also delayed an HR action pending his own 1:1 assessment with Chris.
Wins
- Successfully mediated Greg/Max/Dieter justification chain for board prep - Proactive retention check-in with Alex surfaced positive feedback about Justin's management - Google engineering milestones confirmed on track in CIQ 6.18 meeting - TJ Gohl's AWS Identity Center self-service access management deployed — recognized by Peter and Steve Wallace - Performance review framework docs submitted to Greg via Mariah - $100k Ascender deal in procurement (created Apr 1, expected to close this month)
Challenges
- Google/NVIDIA messaging discrepancy undermining CIQ credibility with partners - Engineering date slips continue — CLK 6.18 overdue 4 days, multiple items with 28-30 day slips - Steve Wallace pushed HR Onboarding 49 days and RESF Mirror Manager 31 days - Multiple OSPO items 18 days overdue - Bjorn's flight delayed for board meeting today — may need to cover opening
Friday, April 10, 2026
April 10 was a heavy strategic alignment day. Peter defended the global product prioritization model to Greg (post-Exec meeting where Fuzzball was elevated to top 20), resolving Greg's concern with a per-team computed property. He set a critical Lab-to-Production boundary with Bjorn — nothing from Cedric's lab goes to production without Engineering productization. In the Brian/Brady sync, Peter reinforced that Product owns exit criteria (triggered by Engineering unilaterally removing NVIDIA CUDA from RLC Pro 9.6 LTS), surfaced a 58% estimation miss rate, and committed to attending Engineering Weekly for accountability. He then forwarded that meeting recording to Bjorn and Baek for alignment on the prod/eng interface. In #distinguished-leaders, Peter shaped the performance engineering hire interview panel, retaining veto power for himself and Max when Bjorn was dropped to make room for Cedric. The day closed with a Value Drivers Board Review where Peter, Bjorn, and Baek agreed to an 'Uber Value Drivers' two-tier framework for strategic clarity.
Wins
- Resolved Greg's Fuzzball prioritization concern with the global+computed-property framework — Greg confirmed: 'I feel much better now' - Aligned with Bjorn on Lab-to-Production boundary before the formal handoff meeting - Clear prod/eng interface directive delivered and shared with leadership (recording to Bjorn + Baek) - 3 PIC items now Ready for Release (NextSilicon Maverick-2, fuzzball-cli cloud, Consolidated Fuzzball interfaces) - Kernel CI Automation Milestone 1.5 completed; FIPS 140-3 moved to In Progress
Challenges
- 58% engineering estimation miss rate — most changes occurring after target dates - Multiple TPS items with date slips continuing (secure boot key blocked, CLK 6.18 due today at 82%) - Lab/Cedric delivery gap — Greg's vision for 'performant' space still vague - Need Greg's buy-in on the Lab-to-Engineering handoff boundary (not yet secured)
Thursday, April 9, 2026
April 8 was a high-intensity partnership day — Google GDC follow-up and NVIDIA EBC at NVIDIA HQ back-to-back. Peter coached Brady and Nathan with detailed communication directives before the Google meeting, emphasizing controlled messaging, distinguishing technical infeasibility from resource constraints, and maintaining CIQ's calm/capable/dedicated image. He personally bookended the engineering meeting with success criteria. In parallel, Peter scoped the NVIDIA Grace Vera partnership, committing to Scott Hara to assess headcount needs and forwarding patch lists to Nathan (SWAG: 3-6 months RLC). On the people front, Peter initiated proactive retention check-ins after Ian's departure — Sultan confirmed widespread team fear and thought the meeting was a termination notice. Peter clarified Michael Young's departure was performance-based and reaffirmed the A-player upgrade strategy. In #distinguished-leaders, Peter and Bjorn confirmed proceeding with the RESF Dieter restructure despite Greg's hesitation about disrupting Leigh's momentum. Peter also set a value-first attendance framework for Nathan at Google NEXT — only go if there's a concrete business objective. NARF automation progressed with 9 packages shipped to production.
Wins
- NVIDIA EBC at HQ with VPs — strong executive engagement on both sides - Google FIPS 618 meeting had productive outcome — new libcrypto collaboration with Google maintainer - Tissa acting as strong internal champion, setting 2-week deadline for Madhu's scale numbers - NARF shipped 9 packages to production (Andrew driving while Max OOO) - Nathan delivered quick SWAG on NVIDIA patch assessment same day - CIS Benchmarks Barricade Combined Playbook completed
Challenges
- Widespread team fear confirmed by Sultan — the culture of fear is deeper than expected - Nathan's team stretched thin: Google FIPS 6.18, NVIDIA patch assessment, Google NEXT question all competing for same bandwidth - Multiple Fuzzball items overdue (Volumes 6d, Observability 10d, GCP integration 6d) - Still no scale numbers from Madhu at Google — Tissa escalation is the backstop - RLC Pro Hardened 9.6 LTS slipped again (now Apr 24)
Tuesday, April 7, 2026
Day dominated by the Google FIPS crisis escalation and strategic clarity push. Peter took personal control of all GDC communication for the next month after identifying that inconsistent, over-transparent messaging was weakening CIQ's negotiating position. In the Brian/Brady weekly sync, Peter called the ~50 value drivers a 'shotgun approach' and demanded consolidation to ~3 core drivers, requesting a 1-year product vision for RLCAI/RLCH from Brian. By evening, with Google's Madhu stalling on revenue projections, Peter drew the line: FIPS delivery depends on getting a ramp or a new contract. The FIPS execution continued — Tissa authorized, atsec contract signed, Nathan directed to begin Option 2 engineering work. Peter shared Anthropic's Glasswing article with leadership, sparking interest in AI security auditing of open source code (Jeremy Allison flagged potential CVE wave in 20-year-old NFS code). Ryan Smith delivered a comprehensive RESF team-by-team status update showing strong operational progress. Steve Wallace's surgery went well. Ryan Smith will be OOO Apr 11-18.
Wins
- Tissa authorized FIPS work and atsec contract signed same day — fast execution - Strategic clarity emerging: ~50 value drivers being forced to ~3 core drivers - Ryan's RESF operational update shows momentum across all teams - Steve's surgery successful - Anthropic Glasswing conversation opened potential AI security angle for CIQ
Challenges
- Google appears to be stalling on revenue projections, possibly exerting leverage - GDC communication has been inconsistent — required Peter to centralize control - ~50 value drivers reveal lack of company-level strategic clarity - Multiple TPS items slipping: CLK 6.18, Cloud Marketplace, HubSpot integration all pushed by Brady - Ryan OOO Apr 11-18 creates coverage gap during critical RESF momentum period
Monday, April 6, 2026
Sunday work day dominated by the Google GDC relationship crisis. Peter took personal ownership by drafting and sending a strategic email to Manu at Google, offering FIPS 6.18 acceleration at certification cost only (~$180k, absorbing NRE), directing a shared git repo for co-development, and requesting revenue ramp projections. This is the execution of the FIPS leverage strategy identified in the Apr 3 reflection. Simultaneously, the GCE side of Google is thriving — Hassan from GCE will pitch Rocky Linux to NVIDIA VPs Wednesday, armed with data showing explosive Rocky growth vs flat Ubuntu on GCE accelerators. At Leadership Roundtable, Peter set a specific miss target (3-6 items) for April's ~50 engineering deliverables. In Andrew's 1:1, Peter reinforced the Order of Operations prioritization model using CentOS Bridge as a concrete example and committed to improving team bandwidth visibility in Nathan's Monday meeting. Steve Wallace announced rotator cuff surgery (out Mon-Fri). TPS report v2.0.0 shipped with Justin's refactor into importable Python library.
Wins
- Strategic email to Manu sent same-day with Bjorn review — fast execution on relationship repair - GCE relationship strong: Hassan preparing NVIDIA VP pitch with explosive Rocky Linux growth data - Thermo Fisher agreed to AWS Fuzzball POC — new pipeline opportunity - TPS Report v2.0.0 shipped with 261 tests, importable Python library (Max + Justin collaboration) - Google GCE March ADCH numbers: every month in Q1 2026 beat 2025
Challenges
- Google GDC relationship at critical point — 90-day termination-for-convenience clause - ~50 April deliverables list too large, contains mis-categorized items and placeholder dates - CentOS Bridge customers at risk due to conscious deprioritization - Steve Wallace out for surgery this week — VP Engineering coverage needed - Multiple TPS items continuing to slip: RESF Board items 10d+ overdue, Fuzzball Observability 7d overdue - RLC+ 9 ISOs/Netboot confidence dropped to 0%
Friday, April 3, 2026
Dense 4-day window covering a termination, RESF infrastructure crisis, Google commercial strategy, and a major Fuzzball demo. The dominant theme is organizational discipline: Peter applied California employment law to keep Michael Young's termination clean, used FIPS 618 as leverage to convert Google from a loss-leader to a paid relationship, and required Bjorn to justify Agent IQ before committing resources. On the RESF front, Peter is executing a two-pronged fix — pushing Greg to give Dieter formal authority as infrastructure lead while sweetening with a stock grant. The RESF Powwow revealed the full scope of fragility (builds depend on 2 people, Taylor gatekeeping access, no JIRA tracking) and Peter directed an honest JIRA date reset to give marketing reliable timelines. Separately, Peter committed to Greg to get Michelle's team to audit AI agent data exposure across CIQ. The Core42 Fuzzball demo went well with a follow-up scheduled for compliance deep-dive. Rakuten trip to Düsseldorf booked for Apr 20-23.
Wins
- Core42 Fuzzball demo went well — follow-up compliance deep dive scheduled - Yahoo Finance AI hallucination attributed $24B AMD stock move to CIQ partnership — leadership leveraging for marketing - NARF Submit at Scale + Release Pipeline completed - Google CME Test Image completed - Self-Serve Portal P4 in Acceptance Testing at 91% - Fuzzball volumes/interfaces hitting 90-95% confidence on deadline - CIQ Intelligence Hub ready for limited rollout - Second PS partner (Cutting Edge) onboarded - Academy Software Foundation partnership initiated — ASWF General Membership approved
Challenges
- RESF infrastructure deeply fragile — builds depend on Skip and Dieter only, Taylor gatekeeping access - Michael Young termination fallout — he disagreed, Justin recorded it on Fathom (Mariah trying to redirect) - Multiple TPS items slipping: LKRG 28d, GCP deprecations 30d, RLC Pro AI Ollama at 0% confidence - RESF Board items 7+ days overdue across the board - Live patching for Google requires a hire that doesn't exist yet - Agent IQ/shiny object risk from Greg - C3 launch happened without proper RACI — Ryan and Peter both blindsided - Mustafa blocking Dieter's RESF role over title concerns
Monday, March 30, 2026
Tuesday, March 24, 2026
Afternoon dominated by the critical RESF Structure meeting — the culmination of weeks of coalition-building. Peter, Max, and Bjorn proposed a two-person RESF leadership model (Nathan as GM, Dieter as Tech Lead) to Greg. Mixed results: Dieter as tech lead appears viable, but Greg has personal resistance to Nathan. Post-meeting debrief with Max showed frustration that core arguments haven't landed with Greg. Earlier, Peter established a Fuzzball AI validation process in #distinguished-leaders — committing to validate Greg's marketing claims before HumanX (2 weeks out). Greg's 3-pillar Fuzzball AI vision (sovereign LLMs, Open Code, agentic infrastructure) is ambitious. Also accepted CLK 6.18 slip to Mar 31 from Jonathan Maple, reinforcing proactive escalation behavior. Engineering Weekly Sync confirmed RESF as #1 priority with Skip and Dieter dedicated, NARF shipped 9 packages, and Pro-Hardened images hitting STIG validation issues.
Wins
- Fuzzball AI validation process established — gives Greg the story while protecting engineering credibility - RESF Structure meeting happened — even if mixed results, the proposal is on the table - Maple's proactive CLK 6.18 escalation shows communication culture working - 9 NARF-built packages shipped to customers - Marketplace listings updated with new 3-tier vCPU pricing
Challenges
- Greg's personal resistance to Nathan as RESF GM threatens half the leadership proposal - Max frustrated that his arguments haven't landed with Greg despite weeks of preparation - Greg characterized as 'massively risk averse' — structural barrier to the change needed - Pro-Hardened images failed STIG validation - Lee's 'Operational Lead' appointment creates direct conflict with Dieter's proposed authority - Mirror Manager blocked by Neil's access suspension
Monday, March 23, 2026
Monday dominated by RESF crisis response. Greg flagged urgent need first thing in #distinguished-leaders — Skip made his first formal ask for help. Peter responded with a full-day RESF mobilization: 1:1 with Dieter to propose tech lead role, outreach to Leigh offering resources, coordination with Max on strategy for Tuesday's Greg alignment meeting, and sustained engagement in #distinguished-leaders managing Greg's urgency while constructing demand-pull approach. Deliberately accepted engineering capacity hit. Also confirmed Dieter for May Saudi training, participated in Leadership Roundtable covering GTM priorities and Toyota GCP expansion. Light weekend activity (Rakuten resolved by Ryan on Saturday).
Wins
- Executed on RESF resource deployment: Dieter engaged as tech lead candidate, Nathan committed, Leigh informed - Built coalition with Max and Bjorn before Tuesday's critical Greg meeting - Managed Greg's urgency without reactive moves — kept strategic approach intact - Completed existing todo: Dieter confirmed for Saudi training - NARF CVE automation progress (Max reported 13 more packages triaged/patched)
Challenges
- RESF team still not asking for help despite repeated offers — cultural/structural barrier - Greg's urgency creates pressure for reactive moves vs Peter's deliberate approach - Taylor/Sherif remain blockers who control without contributing - AWS root account access for RESF infrastructure still stuck - Ryan flagged as out of loop on support page content by Lindsay
Friday, March 20, 2026
Wednesday, March 18, 2026
Massive 5-day window dominated by RESF transition execution and its aftermath. Louis Abel departed RESF — Peter established the operational framework: CIQ works under RESF direction only, all requests flagged for his visibility. Executed multi-layered communication control (different messages for different audiences, Zoom silence, social monitoring, agenda management). Participated in Google deal review ($6M/yr dev fee proposal) and directed engineering to own the resource projection. Initiated Friday RESF people planning session with Max to transition from crisis to sustainable resource model. Shared Mini-Me source code internally after organic demand from Ryan, Nathan, Michelle. Week included H1 mid-year review, board meeting, NVIDIA GTC, Toyota Reno visit, Binarly meeting, and Core42 booth meeting — all while managing RESF transition remotely.
Wins
- RESF operational framework established cleanly across multiple audiences (engineering, direct reports, RESF contacts) - Mirror Manager outage handled smoothly by team without Peter's direct involvement - Google deal proposal crystallized with engineering guardrails - Organic demand for Mini-Me source code — AI adoption spreading naturally
Challenges
- RESF consuming bandwidth across the entire senior engineering team during an already packed week - Ryan's team was driving RESF work without formal RESF direction — needed course correction - Release pipeline pressure continues (RLC 9.7 26 days overdue, multiple items slipping) - Managing all this while traveling (SFO→Reno→SFO, GTC, Toyota, board meeting)
Friday, March 13, 2026
Day dominated by RESF transition execution planning and organizational decisions. Finalized the Monday 3 PM PT infrastructure cutover plan (DNS, AWS, accounts). Made key people calls: excluded Brian from pre-transition planning, blocked Louis from any RESF acting role for two years. Controlled internal comms strategy — Slack post over AMA to avoid crisis optics, with Nathan handling engineering team Q&A. Pivoted AI governance to single-track ISO 42001 model after realizing CIQ products now directly integrate AI. Decided on consolidated deliverable reset post-RESF rather than incremental delay announcements. Reaffirmed speed-first culture to Brady before his leave.
Wins
- RESF cutover plan locked with clear timeline, owners, and war room coordination - Clean comms strategy that manages two audiences (broad org + affected engineers) - AI governance pivot recognized changing product reality before it became a compliance gap
Challenges
- RESF transition consuming engineering bandwidth with downstream impact on March deliverables - People decisions (Brian exclusion, Louis block) carry relationship risk that must be managed post-transition - Brady leaving for 3 weeks during a high-tempo period
Tuesday, March 10, 2026
Day dominated by RESF execution prep and cross-functional coordination. Peter endorsed Bjorn's Linux prioritization framework (Parity, Value, Access, Integration) right before H1 planning — giving Product a defensible rubric. Coordinated Nathan's Google post-mortem doc with Bjorn to prevent misalignment before Bjorn's Thursday contract call. Decided Brian Clemens gets looped into RESF after the front door closes, balancing operational security against relationship risk. Weighed in on asset management architecture with Greg (backend-first, bridge to views). Enforced product process for Greg's RLCAI requirements — holding the line even when the CEO bypasses Product. Committed to a single consolidated Marketing alignment meeting to communicate RESF delivery impact cleanly. Engineering Weekly covered Fuzzball POC blocker (Docker Compose deprioritized behind storage), CVE automation decomposition into milestones, Portal launch imminent pending Brady sign-off, and Veeam PowerPC opportunity (~$300k). Brian/Brady/Peter sync clarified RLCH vision is clear while RLCAI is intentionally undefined — will be shaped by market adoption. Next 1.5 weeks challenging with travel and scattered focus.
Wins
Linux prioritization framework endorsed — clear product direction heading into H1 planning. Google post-mortem coordinated across engineering and product tracks. RESF execution plan on track with timing guidance set. Engineering acknowledged as a 'predictable engine' in Brian/Brady sync. RLC Pro Hardened passwdqc and RESF Security Advisories completed. CVE automation ahead of schedule (50 items done).
Challenges
RLC+ 9 Launch confidence crashed 31pts (40%→9%). RLC 9.7 still blocked at 18 days overdue. Fuzzball customer POCs blocked on deprioritized Docker Compose stack. Greg bypassing Product process for RLCAI. RESF may delay March deliverables 3-4 weeks. Next 1.5 weeks scattered — Peter traveling, Brady out 3 weeks, Nathan potentially traveling.
Monday, March 9, 2026
Weekend dominated by RESF infrastructure takeover preparation — Peter declared it the highest priority for all CIQ engineering for the next two weeks. RESF Sync meeting established phased execution plan (Mon action list, Tue assign owners, Wed review, Fri test). War room channel active with detailed DNS cutover and credential recovery planning. Operational security tight — information compartmentalized until board action. Justin 1:1 covered Portal (ready, blocked on legal), image builds (nightly plan by EOM), Depot progress, and TPS report accountability — Peter needs independent visibility and directed Justin to add Portal/Depot/Releases workstreams. Zorina LOA meeting: Peter decided to grant 5 weeks PTO if FMLA denied — retention over bureaucracy. Delegated execution to Justin and Mariah. Leadership Roundtable (brief, 8 min): Portal self-service launching next week, RLCI launch March 12, C3 pushed to April 2. Engineering commitments uncertain next week due to RESF. Fuzzball GCP/Azure confirmed unaffected. RLC AI direction set: ship iteratively, discover the vision through market interaction rather than planning. Claude government guidance issued: don't ship government products with Claude embedded, internal use fine. Proportionate response to Anthropic designation. Big week ahead: H1 planning Monday, board Tuesday, NVIDIA, Toyota Reno, Google. Peter recovering from illness + time change.
Wins
RESF execution plan established with clear phased approach. War room operational. Zorina retention decision made quickly. Portal nearly ready for launch. Single Binary Fuzzball completed. Basil API integration shipped by Max (changelog.ciq.com). NVIDIA partnership narrative defined from Scott/Bjorn meeting.
Challenges
Still recovering from illness + time change. Packed travel week ahead with limited ability to direct RESF execution. TPS report visibility still needs work. RLC 9.7 blocked at 17 days overdue. Multiple items slipping across teams.
Saturday, March 7, 2026
Friday, March 6, 2026
Wednesday, March 4, 2026
Monday, March 2, 2026
Three-day window (Feb 27 evening through Mar 2 evening) covering a sick day push-through, RESF strategic alignment, and organizational discipline. Peter was sick all weekend into Monday ('feels like when I had mono in college') but chose to push through for the Leadership Roundtable at Chris Baek's request. Despite feeling terrible, he engaged substantively on multiple fronts. Most significant: Max delivered his RESF decision framework document ('The Future of the RESF: A Decision Framework for CIQ') — three options ranging from skeleton independence to full absorption. Peter read it and aligned firmly with Option A (skeleton independent RESF with one CIQ-employed leader). Next step is sitting down with Max and Bjorn to build alignment before presenting to Greg. The board composition question is live — Peter exploring pragmatic inclusion of someone Greg lacks confidence in. Greg proposed LinuxLM (training a Linux-expert LLM) in #distinguished-leaders. Peter demanded measurable success criteria before endorsing: deployment plan, evaluation methodology, clear value proposition. Greg was receptive, framing it as hypothesis validation. Nathan escalated the LTS 9.6 i686 package crisis — multilib packages were never built for 9.6, customer impact possible (Siemens). Peter set maximum urgency without micromanaging the fix. Peter redirected Chris Baek on Leadership Roundtable agenda: March priorities should come from Bjorn (Product), not Engineering. Reinforcing Product-led prioritization as organizational muscle. Leadership Roundtable set March launches: CLK Mar 5, ProAI Mar 12, Portal Mar 19, C3 moved to Apr 2. Fuzzball blog to fill marketing gap. Google plan discussion scheduled for Mar 3.
Wins
RESF strategic alignment with Max — Option A framework is thorough and actionable. Pushed through illness to stay engaged on critical week. LinuxLM success criteria demand was well-received. LTS 9.6 crisis acknowledged quickly with appropriate urgency.
Challenges
Sick all weekend and Monday — energy management. LTS 9.6 i686 crisis is a customer-facing gap. RLC 9.7 still BLOCKED at 11 days overdue. Multiple TPS items deteriorating (RLC Pro Hardened 9.6 LTS at 0% confidence, passwdqc slipping).
Friday, February 27, 2026
One-day window (Feb 26-27) centered on people management execution and strategic product positioning. Peter's Justin 1:1 was a dense coaching session: directed aggressive performance management for Michael using a 'net good' framework (weeding the garden, Expedition 33 metaphors), differentiated low performers (manage out) from high-potential mismatches (coach/move with Brady), explored moving Wesley to Fuzzball as Ian replacement, and mandated JIRA Engineering Incepted tracking for engineering-led work visibility. Jason Lewis termination executed today — Mariah confirmed completion, Steve drafted the departure announcement, Peter reviewed and posted to #department-heads with deliberate scope limitation (eng leadership only, not company-wide, because Jason was an IC). Steve now owns Security & Compliance. AI Committee met to hand off ISO 42001 to Steve, decided Claude enterprise plan migration by Mar 1, and retained ChatGPT as $2k/mo backup. On the product/strategy front, Peter validated Icicle test methodology with Ryan (BIOS change was apples-to-apples), then committed to carefully surfacing results to Bjorn despite Ani being told to stand down. RESF lockdown planning advanced — Bjorn finishing messaging drafts this weekend, Peter organizing execution planning meeting next week with Nathan, Max, Justin, Dieter. Two Sr. Linux Engineer interviews conducted (Jamin Collins, Ben Cressey). Design Sync with Greg, Bjorn, Brad Christensen. Peter asked Chris Wolford about Fuzzball white paper for NVIDIA positioning.
Wins
Justin 1:1 coaching was substantive — specific framework, metaphors, and action items for Michael performance management. Jason Lewis departure communicated cleanly. RESF execution planning moving forward with right people invited. Icicle data validated and path to Bjorn identified. Two engineering interviews completed.
Challenges
RLC 9.7 still BLOCKED at 7 days overdue. NVIDIA container image confidence dropping (RLC Pro AI OCI crashed 25pts to 55%). Multiple items due today/tomorrow with uncertain confidence: passwdqc (55%), Errata updateinfo.xml (72%), Atomicorp STIG Guide (75%). Jason Lewis departure creates ISO 42001 ownership transition.
Thursday, February 26, 2026
Wednesday, February 25, 2026
One-day window (Feb 24-25) dominated by people/retention decisions and strategic partnership positioning. Peter approved $30K in targeted salary adjustments for three below-market Support engineers (Simpson, Cabrera, Van Der Wal) with explicit instruction to keep quiet and not set precedent. This was coordinated with Greg and routes through Mariah/Ryan for execution. Separately, Peter mandated Justin and Nathan double engineering delivery pace in 6 months — a concrete operationalization of the earlier step-change philosophy. Personally drove to San Jose for a full-day planning session with Justin, Nathan, and Max. On the strategic side, Peter committed to delivering a Google contract restructure proposal within one week after securing Google senior management's openness to renegotiation. Also set the NVIDIA positioning: frame existing benchmarks as AMD-only and offer to collaborate on Rocky tuning — turning a vulnerable claim into a partnership opportunity. Retention remains a major theme: approved the must-keep employee list and committed to personally leading engineering retention check-ins, formalizing the systematic response to Ian's departure. Evening follow-up reflection covering the full workday after this morning's 8am reflection. Peter spent the entire day in San Jose for a 4-part Linux Leadership Sync (10am-3:30pm) with Nathan, Justin, and Max — the tactical execution session for yesterday's 2x velocity mandate. Four decisions captured from the session: 1. Personnel action plan from effort/impact matrix review — comprehensive performance assessment of ~20 engineers resulting in specific actions: replacements, improvement timelines, performance conversations, and task reassignments. Uses data-driven framework to identify who is contributing vs. blocking the 2x velocity goal. 2. Release artifact ownership — Nathan owns RPMs, Justin owns images. Clear 'throat to choke' accountability that gives each owner autonomy to improve their process without permission-seeking. 3. Risk tolerance recalibration — 'push and be wrong' philosophy for low-risk releases, with two CVE fixes shipped immediately as precedent. Child of the big leaps mandate. 4. Rocky project contingency war room — proactive infrastructure security planning ahead of legal action against former members with access to critical systems. Also: RLC Pro AI GA completed (major milestone), and Peter expanded the NVIDIA licensing ask to include Fabric Manager and NVISM via email to Scott Hara (not logged as decision per user direction).
Wins
Secured Google senior management commitment to consider contract restructure. NVIDIA meeting produced a concrete path forward (weekly sync, benchmarking collaboration, containerized driver session). Multiple completions in TPS: Security Chatbot, Google Rocky Mirrors Migration, Project Hyper Guide, Apptainer CI/CD, CVEParser updates. Board meeting included Mini-Me demo. RLC Pro AI GA completed — Feb 25 target hit. Full-day strategic planning session produced actionable personnel, process, and risk decisions. Pipeline >$5M weighted (46% of $11M ARR goal), nearly $9M ARR. Sandia Fuzzball expansion closed ($182k).
Challenges
RLC Pro AI GA target is TODAY (Feb 25) at 80% confidence with benchmark integrity questions still unresolved. Errata updateinfo.xml confidence dropped 7pts (79%→72%) near Feb 28 deadline. Brian Dawson had a cardiac event — health concern for a key contributor. RLC 9.7 still in acceptance testing, 5 days overdue. RESF Testing Team resources slipped massively (Feb 27→Jun 30) by Ryan Smith without confidence update. Greg skeptical about NVIDIA partnership value. RLC Pro Hardened passwdqc confidence crashed 42pts (80% to 38%) near Feb 27 deadline — new risk. RLC 9.7 still 5 days overdue at 97% confidence. Errata updateinfo.xml at 72% near Feb 28 deadline. Rocky project faces credible hostile takeover threat requiring contingency planning.
Tuesday, February 24, 2026
Four-day window (Feb 20-24) dominated by two threads: people/retention and technical integrity. Ian Kaneshiro (PIC team) resigned to join an AI startup. Peter immediately escalated to CEO level for retention, then pivoted to a proactive org-wide response: directing leadership to split up and do 1x1s with all top performers to sense flight risk. This reactive-then-proactive chain happened same day, showing how a single departure triggers systematic organizational response. Separately, Peter personally interrogated the RLC-AI 9-10% performance claim by going straight to Damen Knight (the engineer who ran the benchmarks). Discovered the gains largely disappear when code is properly optimized. Asked Damen to audit Brian's marketing write-up for accuracy. This was motivated by convergent pressures: Google explicitly requesting RLC-AI benchmarks, board meeting today, and RLC Pro AI GA targeting tomorrow. A fourth candidate decision (Boot-E knowledge transfer to Nathan tied to Google strategy) was identified but skipped by user.
Wins
Google roadmap meeting went well -- Peter assessed 'We have more leverage with them than we act like we have' and praised Brady's performance. Kernel CI Automation Milestone 1 completed. LTS Kernel Consolidation completed. Ian retention was attempted at the highest level possible.
Challenges
Ian Kaneshiro departure is a real talent loss for PIC team, especially during ongoing restructuring. RLC-AI performance claims may need messaging correction before external use. Multiple items overdue (updateinfo 25 days, Depot CLI 25 days, Self-Serve Portal 12 days, RLC 9.7 4 days). RLC Pro AI GA is tomorrow with benchmark integrity questions unresolved.
Friday, February 20, 2026
Heavy people-decision day focused on reshaping Linux engineering leadership. Five decisions captured, all interconnected around a single strategic thread: strengthening the engineering leadership layer between Peter and the teams. The centerpiece is Max Spevack's transition to oversee Nathan and Justin — addressing Greg's eroding confidence in their ability to serve as reliable windows into engineering. This is the execution phase of what Peter committed to after the Justin communication crisis on Feb 19. Complementary moves: overriding the hiring freeze to bring in Ben (competing with Anthropic) and Jamin (Oracle), while approving Jason Rodriguez's exit path for underperformance. Net effect: upgrading talent composition while installing trusted leadership. Separately, assigned Max as RLC-AI benchmarking plan owner (responding to Greg's direct question) and committed to sign off on benchmark accuracy by Feb 21 to gate the document release for the Humane pitch. TPS report shows RLC 9.7 went BLOCKED on its target date (today, Feb 20) but Justin confirmed in #department-heads it was released. RLC Pro 9.7 still building. Product naming shifting from 'RLC-H' to 'RLC Pro Hardened' across multiple items.
Wins
RLC 9.7 released today per Justin's confirmation in #department-heads. Kernel CI first milestone completed (automated builds and kselftest for multiple LTS branches) — posted in #hey-pete-look. Improved interactive Fuzzball jobs advanced to ACCEPTANCE TESTING. Max leadership transition plan in motion with clear contingency (NARF handoff).
Challenges
Three sensitive people decisions in one day (Max transition, hiring freeze override, Jason exit) — execution risk is high if any piece doesn't land. Google contract renegotiation Monday (unprofitable deal paying ~1% of new customer rates). Benchmark accuracy sign-off needed by tomorrow with limited bandwidth.
Thursday, February 19, 2026
Active two-day period (Feb 17-19) back from travel with a full meeting schedule. Six decisions captured across people management, strategy, operations, and technical domains. Heaviest activity on Feb 19 with 1:1s (Ryan, Steve, Chris Wolford) plus AMD troubleshooting and Azure transition meetings. Most significant decision: intervening on the Justin/Greg communication crisis. Greg questioned whether Justin understands or owns the architecture of what's being built. Peter mediated across three channels — told Justin to send a design doc instead of explaining in Slack, coached Justin with Max on CEO communication style, and committed to Greg to evaluate Justin's understanding. Privately told Bjorn he may need to restructure under Justin. Also set AI adoption/spending policy (pace > cost, fund passion tokens), directed RESF counter-narrative to prevent premature escalation by Bjorn, pushed back on last-minute Volvo meeting coordination, demanded March ARR review (rejected April as too late), and directed Fuzzball team on observability after AMD troubleshooting exposed logging gaps. TPS report shows RLC 9.7 due tomorrow (Feb 20, 97% confidence). RLC Pro AI GA rescheduled Feb 13 → Feb 25 (changed on Feb 19). RLC Pro 9 Launch slipped to Feb 27 with confidence drop. Updateinfo still BLOCKED at 20 days overdue.
Wins
Chris Wolford prototyped Fuzzball Azure/GCP support in days using AI — validating the AI acceleration thesis. UCSF Warewulf training was a big win for Ryan's team. Google Rocky Mirrors Migration completed. LOTA acceleration for Fuzzball on CoreWeave completed. RLC-AI naming work done rapidly, nearing ship. Steve's team unblocked RESF Mirror Manager epic.
Challenges
Justin/Greg communication breakdown is the most acute concern — Greg questioning Justin's competence as information relay. RLC Pro AI GA slipped again (Feb 13 → Feb 25). RLC Pro 9 Launch confidence dropped 10pts. Updateinfo and Depot CLI still blocked and overdue. Volvo meeting coordination highlighted ongoing gap in sales/engineering planning.
Tuesday, February 17, 2026
Lighter activity period (Feb 12-17): return travel from Riyadh/Dubai to SFO, Presidents' Day holiday, first full day back today. Three decisions captured: (1) Set Google GDC meeting strategy — Peter attending exec meeting to build direct relationship, managing Nathan to protect Brady's roadmap presentation, GDC on-site Feb 23-24. (2) Directed AMD inclusion in Project Odin approach document — ensuring multi-vendor positioning. (3) Engaged external network for AI knowledge exchange through IAG Capital — accepting CTO introduction from Cornelis Networks and booking Paydock consultation, actively demonstrating AI system externally. Pending decisions surfaced from Kelly/Peter meeting: Kernel Light/kpatch strategy for Google, Rocky 8.6 ELTS extension, AWS Peter DeSantis technical document. These need action before GDC on Feb 23. Correction received: when Peter takes point on customer meetings without Greg, the motivation is building direct rapport for relationship management, not organizational signaling about hierarchy.
Wins
Sovereign Generative AI workflow completed (was 95% acceptance testing). Project Odin first draft received and reviewed on holiday — shows strong engagement. External AI network expanding through IAG Capital connections (Cornelis CTO + Paydock).
Challenges
RLC 9.7 and RLC Pro AI GA both 4 days overdue. Self-Serve Portal P1 regressed from Acceptance Testing to BLOCKED. Updateinfo security advisories 18 days overdue. Limited digital trail from travel period. Several pending Google/GDC decisions need resolution before Feb 23.
Thursday, February 12, 2026
Travel-heavy day (Riyadh, flying to Dubai then SFO) with most activity in-person. Humain meeting in Riyadh went 'as well as it possibly could have' per Bjorn - aligns with Sovereign Generative AI workflow getting new target (Feb 13, 95% confidence). Continued NVIDIA DOCA OFED escalation via email to Scott Hara - CIQ engineering confirmed ready, waiting on NVIDIA written approval. Attended RLC cross-functional standup: three launches imminent (Pro Feb 19, Pro AI Feb 26, Plus AMD Mar 4), RLC Pro AI declared ENG ready, Azure RLC AI delayed to late March due to Microsoft hardware. JW Koebel leaving CIQ end of February - transition plan being organized. Second reflection today (evening update). Two decisions captured since earlier reflection: used TPS report visibility as accountability lever with Justin ahead of C-Suite Sync, and explicitly approved priority churn as Justin's team pivots to Pro/Plus launches. Light activity day — most substantive work happening in-person in Riyadh (C-Suite Sync, dinner with leadership team). Now in transit: Riyadh → Dubai → SFO. Second reflection today (evening update). Two decisions captured: used TPS report visibility as accountability lever with Justin ahead of C-Suite Sync, and explicitly approved priority churn as Justin's team pivots to Pro/Plus launches. The TPS nudge proved highly effective — Justin's updates revealed two previously-overdue items are actually completed (Azure RLC-AI GTM SOW, Self-Serve Portal P1), RLC 9.7 pulled in from Feb 20 to Feb 13 at 93% confidence, and new Pro launch work appeared. Now in transit: Riyadh → Dubai → SFO. Third reflection today (late evening). Two new decisions captured from post-last-reflection activity: mandated accelerated product cadence with coordination accountability in Department Heads meeting, and directed Nathan to surface eng-product communication gaps in a 30-minute post-meeting coaching session. Corrected one attribution error: RLC Pro AI naming delay was Bjorn's decision, not Peter's. Completed Justin follow-up todo as Dept Heads meeting addressed RLC Pro confidence levels. Still in transit: Riyadh to Dubai to SFO. Department Heads meeting was the key event: Peter framed the accelerated cadence as non-negotiable ('make or break' period, $30B revenue goal). Drew a sharp accountability line - engineering protected for speed mistakes but NOT for coordination failures. All decisions to be made in public channels. Value driver board reviewed with RLC Pro launch next Thursday (only hard blocker: Segmentation M1), RLC Pro AI delayed ~1 week for naming (Bjorn's decision), RLC Plus AMD on track for early March. Post-meeting, Peter coached Nathan for 30 minutes - praised his handling of the meeting despite frustration, then directed him and Justin to proactively surface instances where engineering communicates but product claims ignorance. Told Max afterward he was 'pretty happy with the way Nathan handled that meeting.'
Wins
Humain meeting was a major success - Bjorn's enthusiasm suggests strong alignment with the Saudi sovereign AI opportunity. RLC Pro AI declared engineering-ready. Sovereign Generative AI workflow moved from 19-day overdue to new target with 95% confidence. TPS accountability mechanism worked as designed — Justin updated Jira tickets within 13 minutes of Peter's message. The system creates natural pressure without requiring micromanagement. TPS accountability mechanism produced outstanding results. Justin updated Jira within 13 minutes, revealing: two overdue items actually completed (Azure RLC-AI, Self-Serve Portal), RLC 9.7 accelerated by a week (Feb 20 → Feb 13, 93% confidence), new RLC Pro 9 launch item surfaced (Feb 19, 55%), and Depot CLI confidence jumped 75% → 93%. The report now accurately reflects the pivot to Pro/Plus work. Department Heads meeting successfully communicated the accelerated cadence mandate to the full leadership team. Nathan handled a tense meeting well despite frustration. Peter invested 30 minutes coaching Nathan immediately after, reinforcing the standard 1:1.
Challenges
NVIDIA DOCA OFED written approval still pending - hard blocker for RLC Pro AI GA. RLC Pro engineering readiness still uncertain - Justin providing status by EOW. JW Koebel's departure creates transition risk for Azure relationship and marketplace listings. Still in transit — limited ability to drive work forward. RLC Pro engineering readiness still uncertain pending Justin's EOW update. RLC Segmentation M1 (RLC Pro 9 Launch) is only at 55% confidence with Feb 19 target — 7 days away. Still in transit limiting ability to drive. NVIDIA DOCA OFED still pending. One person_id error this session - attributed Bjorn's RLC Pro AI naming decision to Peter. Limited digital trail from in-person Riyadh activities. Still in transit limiting ability to drive work forward.
Wednesday, February 11, 2026
Active day despite continued Middle East travel (Doha to Riyadh). Three decisions logged, all centered on driving urgency and accountability ahead of critical RLC Pro/AI release dates and a Saudi partner meeting. Peter demanded engineering either commit to marketing's published dates (Feb 19 RLC Pro, Feb 26 RLC Pro AI, Mar 5 RLC AMD) with a war-room or provide GTM with confidence ranges. Separately mobilized the team for a Saudi RLC-AI opportunity - personally escalated NVIDIA DOCA OFED approval blocker via email to Scott Hara and set a 24-hour deadline for technical answers. Coached Max to be more assertive with engineering: 'Start telling not asking, and CC me.'
Wins
Team responded quickly to escalation - Justin committed to lead meeting for clear timelines, Brian Dawson and Damen Knight began answering Max's technical questions within hours, Bjorn committed to calling Scott at NVIDIA. Errata CSAF Security Advisories completed (moved to Recently Completed on TPS). Basil deployed company-wide via Okta.
Challenges
NVIDIA DOCA OFED written approval still pending - hard blocker for Feb 27 RLC Pro AI GA. RLC 9.7 slipped 21 days (Jan 30 to Feb 20) without confidence update. Engineering-marketing alignment tension on release dates. Max's technical questions to engineering initially went unanswered.
Tuesday, February 10, 2026
Light activity day - Peter in transit from Abu Dhabi to Doha. No decisions logged. Primary activity was NVIDIA partnership follow-ups (scheduling in-person meeting via Katie O'Malley, confirming CUDA build availability to Scott Hara) and external AI networking (Paydock/IAG introduction, Fraction CTO call scheduling). Neither rose to decision-level per Peter. Notable org context: marketing published release dates (Feb 19 RLC Pro, Feb 26 RLC Pro AI, Mar 5 RLC AMD) while Justin flags engineering dates are still soft. Basil tool now live via Okta. Nathan adding delivery metrics to WBR doc.
Wins
NVIDIA partnership momentum maintained while traveling - Katie engaged to schedule in-person meeting, CUDA builds confirmed to Scott. Basil deployed and accessible company-wide. Nathan continuing to improve engineering visibility tooling.
Challenges
Travel day with limited decision-making activity. Marketing/engineering date alignment tension emerging around RLC Pro release dates.
Monday, February 9, 2026
One decision from the Dubai/Abu Dhabi trip: Core42 Technical Assessment - Multi-Product Positioning. Peter attended the Core42 meeting with Greg, Bjorn, Max, and Adam Jackson, providing real-time CTO-level technical assessment via Slack. Identified four product-customer fit angles: RLC-H for defense (CVE pain), Rocky as guest OS on Signature Cloud, Fuzzball as replacement for Core42's unhappy AI cloud orchestration partner (flagged as highest-value opportunity), and Ascender Pro for their heavy Ansible usage. Personally followed up with Raghu (Core42 EVP Engineering US) offering in-person meetings. Light activity day overall - Peter is traveling in UAE.
Wins
Core42 meeting identified a multi-product opportunity with a major UAE cloud infrastructure company. Peter's real-time technical notes gave the GTM team (Bjorn) clear direction for the formal follow-up email. CEM v1.0 released (Sam Thornton) - automated CSAF 2.0 security advisory pipeline, directly supporting the errata/CVE remediation work tracked in TPS.
Challenges
Limited activity window - Peter is traveling internationally and operating at odd hours (3am messages). Most leadership roundtable action items assigned to others (Ramesh, Lindsay, Bjorn, Kelly).
Saturday, February 7, 2026
Three decisions across Feb 6-7: (1) Established 'what vs how' framework with Brady and Brian - Product defines exit criteria with specific targets, Engineering defines implementation. Triggered by vague ISO build time comment that cost Peter and Justin an hour of reactive work. (2) Sent detailed handoff email to Nathan and Justin before Dubai trip, covering performance reviews, RLC confidence, Jason R, Shackleton, NVIDIA DOCA, win criteria, and 9.7 release - with explicit instruction to aggressively fill blanks Product leaves. (3) Shared Mini-Me delegate access with Bjorn for collaborative todo management during travel week.
Wins
Product-Engineering process continues to mature with a concrete 'what vs how' framework. Clean handoff to directs before a week of travel shows the management system (todos, emails, process) working as designed. Mini-Me expanding from personal tool to collaboration instrument with Bjorn.
Challenges
Brady still triggering reactive work through vague communication to Greg - the cultural change is not yet embedded despite multiple rounds of process reinforcement. Travel week means limited ability to course-correct if things drift.
Friday, February 6, 2026
Five decisions across Feb 4-6: (1) Enforced Product-owns-prioritization process directly with Greg, insisting work requests flow through Product not CEO. (2) Approved RLC+/Pro product hierarchy with new naming and 3-phase de-risked launch cadence separating AMD dependency. (3) Coached David Godlove on sales-focused approach during AMD Fuzzball overview. (4) Delegated Jason Lewis termination coordination to Mariah for March 3, while Peter travels to Dubai. (5) Committed to creating CVE remediation value driver after 86x improvement in weekly volume.
Wins
RLC product strategy crystallizing with clear hierarchy and de-risked launch plan. Fuzzball AMD demo went well despite earlier deployment issues. CVE remediation 86x improvement creates powerful GTM narrative. Process enforcement with Greg is protecting engineering focus.
Challenges
Ongoing tension between Greg's desire to get in the weeds and the Product prioritization process. Brady and Brian still not consistently using the tools they've been given. Dubai travel next week means delegating several in-flight items.
Tuesday, February 3, 2026
Three strategic decisions today: (1) RESF board strategy approved - remove Lewis using Quinn Emanuel memo on federal law violation, then engage Neil collaboratively to avoid public fight. Shadow infrastructure ready. (2) AMD RLC Plus strategy - prioritize speed-to-market with minimal scope using upstream packages, defer full rebuild until market traction proven. (3) Jason Lewis termination ready to action now that ISO 27001 certification letter received. Also reinforced 2x velocity mandate and tiered performance reviews in Engineering Weekly Sync.
Wins
RESF strategy has clear execution path with legal leverage. AMD scope decision unblocks partnership timeline. Jason Lewis blocker (ISO cert) cleared. CODE2 values proposal from yesterday well-received.
Challenges
Rocky updateinfo security advisory gap remains a competitive issue vs Alma. RPM Testing Automation at 10% confidence is concerning given velocity mandate.
Monday, February 2, 2026
Five decisions focused on engineering velocity and culture. Major initiative to redefine CODE2 values from character traits to observable behaviors - addressing the Damon situation where vague definitions caused conflict. Set new 2x velocity mandate for Justin and Nathan, shifting from coaching to performance-driven model. Evolved PR process to prioritize automated tests over human review for AI-generated code. Approved $10K infrastructure savings with velocity-protection condition. Flagged critical Rocky vs Alma competitive gap on security update tagging.
Wins
CODE2 redefinition addresses a real problem with concrete solution. Clear alignment with Greg and Bjorn on the approach. 2x velocity mandate sets clear expectations for engineering leadership.
Challenges
Rocky security update tagging is a competitive disadvantage that needs urgent attention. Wesley placement decision pending validation of RLC transformation impact.
Sunday, February 1, 2026
Four decisions from the weekend. Made strategic decision to launch RLC Plus/Pro re-architecture under a new non-Rocky brand to decouple from expected community fallout around Lewis/Neil departure - this spawned a new pattern (Decouple to Protect Momentum). Protected Max from meetings for 3 days to focus on NARF streamlining. Committed to Anduril attendance with Max. Shared AI development velocity article with Max to guide NARF approach.
Wins
Created new strategic pattern about decoupling to protect momentum. Clear alignment with Bjorn on brand strategy and value driver breakdown.
Challenges
The Lewis/Neil situation continues to require careful navigation. Brand separation adds complexity to GTM.
Friday, January 30, 2026
Five decisions from Friday. Set CVE automation as February #1 priority over RLC-AI (Max to lead). Recommended partial bounty payout for Fuzzball single-binary work to establish repeatable incentive model. Positioned Bjorn as escalation for Tenable business-side readiness. Advocated for in-person Anderil POC kickoff in Seattle (Peter + Max attending). Created #hey-pete-look channel for engineering visibility and recognition.
Wins
Created structural solution for recognition gap (#hey-pete-look). Bounty program paying out - builds credibility. Clear February priority established.
Challenges
RESF board situation requires careful coordination. Multiple Jan 30 deadlines hitting today. Need to balance customer visits with February deliverables.
Thursday, January 29, 2026
Wednesday, January 28, 2026
Landmark leadership offsite day with 24 decisions spanning operational philosophy reset, team structure, and strategic direction. Morning Everfox meeting established clear commercial threshold (ARR-target-level deal required to justify engineering pivot). Leadership offsite with Max, Nathan, Andrew, Justin covered: meeting cadence reset to owner-driven Slacks, Nathan role redefinition from firefighter to accountability owner (critical), AI tooling ownership standard, PRD contract model with mutual accountability, trustless processes philosophy, find-the-ceiling velocity approach, quality-serves-velocity principle, Jason Rodriguez evaluation timeline, Trinity backfill as RLCAI/RLCH priority, team-building over floor-protection philosophy (critical), CVE automation architecture, LTS roll-forward policy, Shackleton infrastructure contingency, and RESF crisis communications.
Wins
Massive strategic alignment achieved in single day. Leadership team aligned on accountability structure (Nathan owns follow-through), velocity philosophy (find ceiling first), AI adoption standard (build with AI or lose it), PRD contract model (mutual accountability), and team-building philosophy (protect ceiling not floor). Clear commercial framework established for Everfox partnership discussions.
Challenges
Jason Rodriguez situation requires careful handling with clear evaluation timeline. Shackleton contingency reveals infrastructure dependencies needing monitoring. RESF crisis requires coordinated response with Lindsay.
Tuesday, January 27, 2026
Reinforced Product-Engineering handoff process with tighter SLAs. Committed to performance review redesign using observable behaviors. Explored Max for Product role while expressing frustration with Brady. Approved contractor full-time offer. Advocated for PIC team progress to Greg.