Bjorn
Dec 19, 2025 - Jul 10, 2026
176
Decisions
6
Active Todos
11
Patterns
Decisions (176)
Rule the Toyota kernel patch a feature not a bug; no automatic queue jump, escalate through normal priority
Nathan flagged a Toyota/Yoshi request (relayed via Art/sales) framed as a bug fix. Peter ruled it is a feature, not a bug, so it does not automatically jump the engineering queue on the bug argument. Support may still be offered, but the bug framing is off the table. If the business wants it prioritized it must go through normal escalation and trade-off (Peter + Bjorn), not a backdoor via mislabeling severity. Reinforced later the same day in the Ryan 1:1 (Peter rebuked Art for taking the bug-vs-feature fight to engineering).
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.
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.
Gate Rakuten 8.6 / RT-kernel support work on a signed 1.6 to 1.8M expansion that funds dedicated headcount
Decided that the risky, currently unsupportable Rakuten 8.6 / RT-kernel support work will either not be done at all or only be delivered tied to a signed contract expansion in the 1.6 to 1.8M range that funds dedicated Rakuten headcount on CIQ side. The bar is enough to cover roughly two dedicated engineers, not an arbitrary large number. Peter forwarded the engineering teams infrastructure objections to Bjorn to arm the customer conversation.
Sensitive Decision
Sensitive Decision
Everfox desktop-OS: require explicitly scoped and funded eng-investment before supporting the deal
On the Everfox desktop-OS deal, Peter framed it as a fundamentally different business (be like Ubuntu while also being like RedHat, not add desktop support to Rocky) and insisted the unknowns around hardware enablement / driver support and a dedicated lab be made explicit. His engineering-side conditions: the MSA must fix the hardware scope with out-of-scope hardware priced separately, and CIQ should proceed only with an explicit commitment to fund the engineering regardless of revenue. He tasked Max to assess technical feasibility with Nathan before committing. Relates to the prior logged Everfox decision d1ea8ed9; this is the engineering-stewardship condition layer.
Champion Kubernetes-by-CIQ as an H2 engineering deliverable (build on the standard)
Peter is actively pushing for a CIQ-branded Kubernetes offering, built on the standard rather than reinvented, to be an H2 engineering deliverable that eliminates a recurring objection in sales conversations. He green-lit Chris Wolford putting Kubernetes by CIQ on his H2 doc. It fits the broader turnkey/easy-button vision (single installable image combining Rocky Hardened plus Fuzzball substrate). Peter acknowledges final product prioritization authority sits with Bjorn/Product; his action here is advocacy and engineering-roadmap steering, not a prioritization decree.
EU Cyber Resilience Act - scope hinges on legal definitions; Bjorn to engage lawyers; aim to publish our own definitions
On the CRA thread (raised by Leigh Hennig re a Sept 11 deadline for RESF/Rocky/CIQ), Peter directed that the entire scope hinges on two definitions - vulnerability and actively exploited - and delegated Bjorn to engage lawyers to weigh in. Strategic aim: ideally CIQ/RESF publishes its own definitions, reframing CRA compliance as living up to our stated market promises rather than being exposed to outside interpretation. Until legal responds, nothing to do.
Hold the margin line - willing to walk from bad-economics deals (currently applied to Rakuten)
In his 1:1 with Baek, Peter articulated a generalized stance and named its current target: stop playing the tell-the-customer-yes-to-anything game, and hold a hard line even if it means losing the deal. He will not spend 2M to capture 400K. He confirmed this is a generalized principle that at this moment absolutely applies to Rakuten as those negotiations finalize.
Veeam CVE-escalation response: tell the honest intentional-tradeoff story, diagnose via Dickerson first
Ahead of a 5 AM Monday call with Veeam on a roughly 1M deal Bjorn flagged as at-risk, Peter set the response strategy. Tell Veeam the honest story: CIQ made an intentional trade-off (criticals 9-plus, known-exploit CVEs, and high-8s are handled; behind on some low-7s) because it is investing in CVE automation to handle the coming flood, and this is NOT a reaction to being caught. Step one is to reach out to Dickerson first to learn Veeams actual expectations and what specifically unblocks their signature. Nathan owns the technical scanner-nuance explanation (stack-protection downgrades, scanners scoring off non-Red-Hat CVEs).
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.
Gate NVIDIA/Spark announcement on engineering supportability — eng-only until then, then hand to GTM
With NVIDIA engagement happening at very high levels over the next week, Peter decided to say nothing publicly and not pre-announce anything until CIQ has something it can support — something it would actually ship and point a customer at the support org for. Until then the Spark/Rocky-on-Spark work stays purely engineering (get it on Nathan, Wolford, Westley, and Peter own Sparks; validate it works), explicitly not a Bjorn/GTM item. Once it is supportable, GTM is unleashed.
Intent to move Ascender to Zorina with dedicated headcount; stays under Justin for now
Peter decided the direction for Ascender (and Ascender Pro; Ledger Pro pending a Bjorn confirmation): move it under Zorina as a clean, dedicated product home, with headcount Peter has secured for Zorina to hire a team (Bay-Area-first, lightly). For now Ascender remains under Justin — NOT Nathan — and the move to Zorina is directional intent, not yet executed. Larry and Jimmy (original engineers) move to sales-support under Bjorn. Intent is to productize Ascender like any other shippable product rather than leave it an orphan.
Prioritize RLC 10.2 to the top, drop AI+H work — and validate the JPD deprioritization as correct
After a Citadel-driven escalation (10.2 needed for a ~$200k contract + expansion), Peter pulled Nathan, Justin and Max into a 5-minute call, made 10.2 priority-one for Linux eng above RLC AI and H work (only 3 critical CVEs rank higher), and was willing to drop other work if needed. He then posted an actionable timeline range to #department-heads (inner bound Fri 6/19, outside June 30, gated by CVEs). Crucially, he endorsed that the team had correctly deprioritized 10.2 per the JPD board and framed the whole episode as a communication failure (Bjorn got a single June-30 date without the range/assumptions), NOT an execution failure.
Establish 3 as the performance-review norm — close alignment with Bjorn and Greg
Peter established that a 3 on the 5-point scale is the expected/solid norm in performance reviews (not a 5), and closed alignment on this calibration standard with Bjorn and Greg, resolving a leadership split that had become visible to the org during the active review cycle.
Performance-engineer rec stays under Greg/research for now; likely transitions to engineering later
In the HR Weekly (6/02), Greg offered Peter the performance-engineer rec, saying performance does not belong in research under the new charter and that the rec should go to Peter. Peter chose to leave the rec under Greg/research for now (roughly the first four months), with shared agreement that it likely transitions to Peter/engineering long-term once there is something concrete to manage toward. Peter framed it as a stance to leave the meeting with unless someone had an epiphany that evening; the stance held.
Take on Value Drivers Board restructure as the next coordination lever after JPD doctrine
In the 6/01 Leadership Roundtable, Peter committed to bring a formal proposal to restructure the Value Drivers Board, explicitly sequenced as the next move now that the product-priorities board (the JPD-doctrine work, closed 5/29) is aligned where he wanted it. Took the Fathom action item to draft the proposal and share with Chris Baek and the group within a couple of days. Triggered by Lindsay surfacing marketing/product misalignment (premature RLC+AMD announcement before AMD validation; Fuzzball multicloud date churn May 28 to June 4).
JPD board scope locked to ordered priority list — Peter drew the line in writing to Nathan
In a long Slack DM thread on 5/27 (~25 Peter messages, 09:15–09:41 AM PDT), Peter rejected Nathan's draft framing for JPD scope and replaced it with an absolute definition: JPD is an ordered list of product's priorities used to drive company strategy, and nothing else. Not project planning, not marketing coordination, not a control surface for engineering order-of-operations. Tickets should be as large as possible and only split when product strategically cares about sub-priority. Value Drivers carry GTM linkage and dates. Every time someone tries to widen JPD scope, Nathan is instructed to push back. Reinforced same day in Baek 1:1 (Peter-recorded Fathom) and surfaces in the RLC cross-functional standup where Nathan is tasked with drafting the formal product-board structure proposal.
RHEL patching support: same-day customer-facing document with explicit Ubuntu carve-out
Peter wrote and shared a Google Doc same-day (within 32 minutes of the Leadership Roundtable action item) outlining CIQ Engineerings agreed scope for supporting RHEL patching. Sent to Bjorn and Ramesh for review with the intention of forwarding to Art for customer-facing use (lead-gen + knowledge-transfer). The doc explicitly does NOT cover Ubuntu — Peter made the Ubuntu carve-out explicit in the DM thread when Ramesh raised Canonicals different model.
Peter Computex condition: product must be production-ready, not a POC
For the proposed early-June Computex Fuzzball-on-DGX-Spark announcement, Peter set one engineering-side condition: the product must be production-ready (not just a POC). Bjorn separately set the GTM-cadence gates (max 6-week lag between announcement and delivery; sufficient PR-runway for Lindsay and Cathay). Peter held the engineering line cleanly and let Bjorn hold the product-marketing line.
Engineering hiring forecast: 2-3 engineers every 6 months, Linux Security next, Bay Area preference
Peter committed to a 12-month engineering hiring cadence of 2-3 net new engineers every 6 months. Next 6 months: Linux Security Engineer (target hire 4-6 months out), plus potentially one more for Nathans team contingent on bug volume. Hiring location preference: Bay Area. Mariah updates the shared headcount/salary forecast spreadsheet to reflect this for Bjorn.
Kyle move conditions: permanent (no return) and gated on RLC completion
If/when Kyle moves to Gregs research team, the move is permanent with no path back to Wolfords org. The gate is Kyle completing his current RLC commitments first, not just Wolford filling the backfill rec. Greg owns the conversation and setting expectations with Kyle on self-management and performance; Greg will update Peter and Bjorn on Kyles decision.
Cedric placed full-time on Gregs research team; Kyle still pending Gregs conversation
After the C-Suite Sync surfaced the Kyle/Cedric risk asymmetry (Kyle = low performer needing hard deadlines, Cedric = high-output engineer well-suited for rapid POCs), the research-team assignment from yesterday flipped: Cedric is now the firm full-time mover to Gregs research org, while Kyles move is still open and gated on Greg-owned conversation + Kyle finishing his RLC commitments first. The Wolford backfill rec opens regardless of which one moves.
Hire dedicated cloud-security engineer — Steve drafts JD, Peter champions, dovetail with Nathan STIG/FIPS gap
In Steve 1:1 5/21, TJ flagged CIQ is doing the bare minimum on infrastructure security across 4-5 clouds. Peter asked Steve to have TJ (or Steve) draft a quickie JD describing what the role does and is responsible for — explicitly NOT urgent, but needed as a champion artifact so Peter can take it to Bjorn/Greg with a concrete ask. Steve flagged that the same hire could dovetail with Nathans STIG/FIPS expertise need on the technical side; Peter agreed ("Awesome"). QBR 5/22 made it official as a Steve-owned area requiring formal assessment and potentially a new headcount.
Reward Yesh for responsible disclosure — CIQ first-ever bug bounty
When Yesh (pentestine@gmail.com) reported a ciq.com vulnerability on 5/21 via email, Peter responded within minutes to Steve Wallace and Bjorn: I would like us to reward here to encourage this behavior. He immediately forwarded the bug detail to Justin Haynes for the fix and aligned with Steve on severity. The reward is still pending execution as of 5/26 — this is the first bug bounty CIQ has ever paid.
Dieter Middle East trip proceeds; Peter shifts to off-loading other stress vectors
After the Nathan 1:1 5/21 raised the Middle East trip as a stress concern, Peter and Bjorn aligned: the trip business value holds, Dieter ships. The landed decision is upstream — Peter recalibrates his support for Dieter to be much more sensitive to overload signals and actively off-loads other stress vectors (release pressure framing, recognition, vacation enforcement post-release, board-proposal ghostwriting timing) so the Middle East trip is the one stressor, not stacked on top of others.
Refuse holiday-weekend pressure on people — Mariah review deadline AND Ryan reviews
Two paired actions on 5/24. (1) When Mariah pushed Peter Sunday evening that mid-year reviews were 50% complete on the day-of deadline, Peter held the line — no pushing direct reports who are on a 3-day holiday weekend. Drew distinction between the people who plan ahead (will finish on time) and those who do not (will finish Tuesday night either way). Committed to thinking about better engagement separately. (2) Same evening Peter DMed Ryan: I am not going to read your reviews today or tomorrow — you should take a break. Same posture applied to a direct report Peter could see was burning out from a hard week.
Hardware lab: paint the full picture and buy the whole complement upfront
When Nathan proposed buying one server per quarter to build out the engineering hardware lab, Peter pushed back: do it backwards. Define what we want the lab to be, then buy the full complement, not slice by quarter. Only chunk it if there is a real reason (cooling, ops bandwidth) — not for budget reasons. Tied to: NVIDIA H100/GB300/B200, AMD parity, and figuring out where to put it (Reno closet vs Texas DC).
Firewall Greg AI prototyping team — company makes no plans against their output
Peter explicitly framed Gregs AI prototyping work as a separate research division that the rest of the company cannot bet on. No items show on the value drivers board for this work; nothing is committed to customers; deliverables are not on engineering plans. If they emerge with a usable nugget, fine — Wolfords or Nathans team will productize it. Until then, planning treats the team as if it does not exist.
Ascender ownership moves to Nathan org with possible Zarina-led sister team
Peter decided Ascender does not stay parked between Jimmy and Larry as a half-supported side-project — it needs a real owner. Not adding a direct report to Peter; not adding to Justin who is at his limit. Lands in Nathans org. Possible structure: a sister group under Nathan (parallel to Justins org) for customer-facing delivery — would hold externally-facing Depot AND Ascender, led by Zarina, with one new engineer hired in for Ascender work. Decision contingent on Zarinas current Depot-Sodor commitment and the Wesley situation resolving.
Kyle conditional move to Greg AI role gated by filling Wolfords rec first; Cedric written off the Fuzzball team
Kyle reached out to Greg directly about the AI role reporting into Greg. Peter aligned with Greg and Chris Wolford on the following: (a) Kyle stays in Wolfords org through end of June while the new tickets land; (b) Wolford receives Gregs open rec immediately and starts hiring; (c) Kyle does not move until that rec is filled; (d) Kyle is told this is a job change, not a trial — if it does not work in Gregs world he is out, same as any other role mismatch; (e) Peter will tell Greg that Cedric is NOT meaningfully delivering on Fuzzball today (he is a part-time advisor at best while building for Greg), and Wolford will plan as if Cedric does not exist on the team going forward.
Dieter wellness three-layer intervention — trip offer + Mattermost kudos + RESF governance reform
Triggered by Nathan flagging Dieters stress (release delays + planned Middle East trip), Peter committed to a three-part response: (1) Trip cancellation offer — confirm trip status with Bjorn first, then directly ask Dieter if cancelling helps reduce his stress. (2) Community recognition — post in RESF Mattermost thanking community for 9.2/10.8 release efforts, coordinated with Nathan via #hey-pete-look. (3) RESF governance reform — Nathan to draft governance proposals (term-based board and team-lead seats, monthly status reports from team leads to board) for Dieter to present. Also reframed how Dieters performance gets evaluated: from absolute targets to pre-Dieter vs post-Dieter comparison. Stack to take ownership of release sign-off so Dieter does not carry that burden.
Dedicated cloud security engineer role to be championed — dual-purpose JD covering cloud + STIG/FIPS
Committed in Steve 1:1 5/21 to champion a new dedicated cloud security engineer role. Steve will work with TJ to draft the JD; Peter will champion it to budget owners (Bjorn/Greg). Triggered by TJ flagging current cloud security as bare minimum and the proactive supply-chain projects (TJ on GitHub workflow SHA pinning, CeeLo on NPM package securing) needing a dedicated owner. Dual-purpose JD: also serves Nathans STIG/FIPS security expertise needs — one hire, two demand surfaces.
Moody Citibank card hard cutoff 6/15 — force-action via past-tense framing after 9 months of soft asks
After Kelly Wall described 9 months of soft asks to Steve Moody to switch from the personal-history Citibank card to the Ramp card (forcing manual finance journal entries every month), Peter directed Kelly to send Moody a notice that the card has been disabled and will stop working on June 15. CC Steve Wallace. Phrase it past-tense (has been disabled) plus future-fact (stops working 6/15) — not request language. Peter explicitly affirmed his prior gate (Kelly checks with him before shut-offs) while greenlighting this one because Kelly is giving a month notice — the notice IS the legitimacy gate.
Discretionary bounty offered for Yeshs vulnerability disclosure — case-by-case mode, no formal program
Yesh privately disclosed a vulnerability in ciq.com on 5/19. Peter forwarded to Greg/Bjorn asking if CIQ has paid bounties before. By 5/21 Peter emailed Steve+Bjorn endorsing reward: This is well done on his part, both technically and from a good-actor perspective. I would like us to reward here to encourage this behavior. Steve drafted a response: We do not currently operate a formal public bug bounty program, but would like to offer a discretionary reward for your efforts once validation is complete. Peter explicitly endorsed via DM (Yup!). Peter separately forwarded the disclosure to Justin to fix. Bjorn aligned on the wording earlier. Steve owns the response thread; Justin owns the fix; Bjorn owns sign-off; precedent-setting case for future disclosures.
Bjorn/Victoria HR-leader intro — proactive talent pipeline cultivation
Peter introduced Victoria (most recently head of HR for Celestial) to Bjorn via email 5/13 evening after a 30-minute Zoom call with her Wed 5/13 18:00-18:45 PDT. Framing: comes highly recommended by one of the best engineers I know. Email cc'd Victoria + Bjorn; Bjorn now owns the next step. No defined role slot at CIQ — Mariah Rippee is the current Head of HR.
Bjorn/Victoria HR-leader intro — proactive talent pipeline cultivation
Peter introduced Victoria (most recently head of HR for Celestial) to Bjorn via email 5/13 evening after a 30-minute Zoom call with her Wed 5/13 18:00-18:45 PDT. Framing: comes highly recommended by one of the best engineers I know. Email cc'd Victoria + Bjorn; Bjorn now owns the next step. No defined role slot at CIQ — Mariah Rippee is the current Head of HR.
Ascender Pro Dev JD scope finalized — application engineer to de-risk Jimmy, pulls Ascender dev into Peter org
Joint Peter/Bjorn/Jimmy/Brianne meeting 5/14: title is application engineer (intentionally NOT Ascender-engineer — allows cross-project use), $180k mid-senior, 6-8 years experience, React + Python primary (50/50 front-end/back-end), Go a plus, go-getter required (must keep pace with Larry and Jimmy who are both super-fast). Interview panel: Brianne, Jimmy, Larry, Chris Wolford. Peter optional final (Bjorn pushed Peter onto panel: I trust Peter's interviewing). Brianne posts JD by weekend / Monday. Will report into Peter's org, location-within-org TBD. Bjorn's framing: pull all Ascender development under [Peter's org] form.
Values framework endorsed for Adam coaching — efficient and excellent covers team-player, no stacking bodies
Bjorn surfaced an Adam culture issue in #distinguished-leaders 5/18 morning (hothead, dismissive of colleagues, will address directly. No amount of potential deals is worth poisoning the culture) and asked which CIQ value it falls under. Peter provided the framework: efficient and excellent covers being-a-team-player. Used the Apple coaching mandate as historical reference (we want you to learn to accomplish the same level of stuff you're doing now — but to do it without stacking up all the dead bodies). Extended the framing: the values are not just about Adam. If he keeps others from being efficient and excellent, he hurts the company. The wise-man-told-you-to-stack-fewer-bodies callback closed the loop.
Rakuten RFQ prioritized over Board prep + vulnerability response — scope-discipline enforced at line-item level
After conferring with Bjorn 5/15 afternoon, Peter reordered the week to put Rakuten RFQ response above both Tuesday 5/19 board prep and continued kernel vulnerability work. Held the boundary against scope creep in the submission itself: stripped runc nohz_full / ACC100 commits (Reqs 19, 37, 10, 38), scrubbed AI-generated CIQ Rapid Security Patch SLO Framework (48h/72h/14d commitments), softened Validated-for-[hardware] to Supported-on, kept RT kernel position to vmcore-dump-analysis-plus-recommendations only — no hands-on-keyboard custom patches. Deal size is $2M/year per Ramesh — different business with Rakuten than the existing engagement.
Extend personal-health leave to 6/5 with explicit cap and revisit trigger
Peter agreed via DM with Mariah to extend a direct reports unpaid personal-health leave through 6/5, while explicitly stating that extending past 6/1 pushes past his comfort level and that any extension beyond 6/5 will trigger a revisit. The decision balanced Bjorns prior generosity preference (Bjorn was consulted before responding) against Peters own concern about open-endedness. Mariah immediately flagged precedent implications.
CVE response strategy — three-pillar overhaul (process + tooling + strategic kernel review)
In Engineering Weekly Sync, Peter operationalized the 5/11 Leadership Roundtable vuln-handling commitment into three concrete pillars: (1) Chris Baek to restructure the embargo/CVE comms doc with Jamie, separating process from tooling/templates; (2) tooling strategy — Peter commits to email Greg requesting Claude Opus 4.7 whitelist for CIQ accounts AND to set up unbridled internal LLM models on Fuzzball for vuln investigations; (3) schedule strategic kernel philosophy review for early June, with Nathan and Justin to provide a list of downstream automation efforts to prioritize.
Open strategic review of RLC/RLK identity + upstream binding (Dirty Frag triggered)
Saturday 5/9 in #department-heads, in immediate response to Justin's Dirty Frag status table and Nathan's note about CIQ patches being shared with the RESF, Peter announced he wants the leadership team to take up a strategic question next week: what recurring vulnerabilities imply about CIQ's kernel posture, how tightly to bind to upstream, how to work with the RESF, and what it means going forward to be RLC and RLK. Aimed at framing input for the mid-to-late June LA in-person product-strategy session with Bjorn and Greg.
Commit engineering to vuln-handling infra/automation at Leadership Roundtable
At the 5/11 Leadership Roundtable, Peter accepted an explicit action item to prioritize vulnerability-response infrastructure and automation work in engineering, and to update Chris Baek as the interim process owner. The commitment converts the 5/8 internal-to-engineering commitment (build/test infra to eliminate reactive interrupts) into a cross-functional commitment with Bjorn, Greg, Chris, and Lindsay in the room.
Reject open-ended LGU+ RHEL/OEL support commitments — best effort only
Nathan surfaced (via Justin) a CIQ <> LGU+ contract proposal requiring CIQ to provide workarounds and answer customer SR tickets for RHEL 6 (already EOL), RHEL 7/8/9, and OEL 6/7. Peter intervened in the same-day group DM with Bjorn, Art, and Ramesh to draw the line at best effort only — no commitments to deliver workarounds or answers. Asked Nathan if it is not yet in force so he can get in front of it before signing.
Prioritize build/test infrastructure to eliminate reactive engineering interrupts
After Dirty Frag CVE took Linux engineering offline for 24 hours, Peter committed to prioritize building robust build/test infrastructure as the proactive response. Told Brady/Brian this requires Product leadership to de-prioritize other work to make room. Surfaced publicly in #department-heads thread asking how to structure infra for the new normal of AI-assisted exploit cadence.
Ask Bjorn to deliver ARR/dilution/Series-B rationale to engineering org
Committed to ask Bjorn to clarify the link between doubling ARR (to $20M), Series B funding with minimal dilution, and employee stock value — to be delivered in All Hands or in Peters org meeting. The intent is for Bjorn to walk the team through the knife-edge: failure forces more investor funding with significant dilution; success enables Series B with minimal dilution and a clear path to profitability.
Senior leadership candidate engagement: open to talk, not under pressure, will not give away the kingdom
On the senior leadership candidate Greg/Bjorn surfaced (described by Bjorn as a bit all over the place and by Greg as starting like she is that much of a gift to us), Peter took a disciplined position: happy to talk, would like another senior person, but not feeling pressure right now and will not concede equity/scope/title to land her. Also flagged: expects steady-state of senior candidate flow for a while.
Icicle viability gate: AI inference benchmark on H100 decides go/no-go
Set a clear decision gate for the Icicle project: viability is determined by performance on a real-world AI inference workload, not synthetic benchmarks. Omer to run the RLC Pro AI benchmark on an H100 GPU. 2-3x synthetic CPU/memory degradation is acceptable IF power savings are significant for AI inference; otherwise project gets punted.
Reassign Owen to Maxs AI tooling for definitive performance evaluation
In Ryan 1:1, decided to assign Owen to Maxs AI tooling projects when Max returns from leave (~3 weeks). Defines the project with Nate beforehand so it is ready to deploy day one. Resolves conflicting feedback: Ryan sees senior Golang engineer underutilized; Bjorn questions value; Max and Nathan have called recent work AI slop.
Peter delivers Reno QBR C-suite intro Thursday — covering Bjorn late arrival
Peter will deliver the C-suite intro at Reno QBR Thursday morning, since Bjorn arrives Thursday afternoon. Peter arrives 8:45 AM Thursday. Greg travels to Houston with Adam for a 1 PM Thursday sales meeting.
Three-tier board hierarchy formalized — Strategic EPICs / Value Drivers / Tactical Jira
Aligned with Bjorn on a 3-tier hierarchy: Strategic Board (EPICs requiring CEO-level prioritization), Value Drivers Board (GTM stories), and Tactical Boards (Jira execution). The current PPL board converts to the Strategic Board. Top ~50 only; anything below is wasted prioritization that will need redoing by the time it is worked on. Greg agreed to disagree-and-commit once Peter+Bjorn document the rules and walk him through.
PPL is being misused — push Bjorn to realign it to strategic priorities
The Product Priority List has drifted from a strategic-priority list (epic-level) into a granular project tracker, obscuring strategic priorities (RLCAI on Spark buried at #88) and creating bottlenecks (Ollama package delayed to May 15). Peters position: PPL must return to defining company strategy at epic level; granular tasks belong in JIRA. Will engage Bjorn directly to realign — this is the framing decision; the implementation is the negotiation with Bjorn.
Everfox: require ~$2M front-loaded year-one payment, reject back-loaded $600k structure
Peter is requiring a large upfront payment ($2M floor with the proposal team; $4-6M float with Greg) for the new Everfox custom work (legacy CPU support, custom desktop) and rejecting the back-loaded $600k year-one structure. The $20M/10-year deal will be restructured to front-load payments, potentially by reducing total contract value if needed. CIQ will not absorb non-reusable engineering work without immediate funding.
Engineering veto required on custom deals and new lines of business
Peter is implementing a formal process where Engineering has review-and-veto authority on custom deals and new lines of business. Engineering must be consulted to assess cost and feasibility before any deal is finalized. Discussed in Peter <> Chris 5/1 and applied immediately to the Everfox proposal restructuring on 5/4.
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.
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.
Fuzzball PoC ownership belongs to Sales Engineering, supported by Engineering
When Bjorn asked who should own Fuzzball PoCs (Sales Engineering vs Wolfgang/Godlove vs Support), Peter answered definitively: Sales Engineering, supported by Engineering. Bjorn agreed with the framing — pushback was strictly about Sales Engineering not being enabled on Fuzzball today (resourcing gap), not the principle. The default routing stands.
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."
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.
Core42: pivot from Fuzzball sale to full-stack compliance partnership
After the Core42 Tech Dive Part 2 surfaced Core42 wants a single OS vendor for their full UAE compliance stack (NIST 800-53, BIS, IDAM, physical security) across three EOY-2026 GPU clusters, Peter immediately convened an internal Impromptu Zoom to reposition the opportunity. CIQ will propose a comprehensive partnership framing CIQ as the only group that can provide all requirements, with RLC Pro Hardened + Fuzzball + Ascender as the core stack and partners filling the remaining ~20%. Consultative play: CIQ will advise Core42 on which requirements in Eric Grundstrom's doc would cause unacceptable performance degradation vs. which can be met. Nathan to draft the proposal doc by EOD Saturday so CIQ can deliver an answer by Monday.
Escalated Dieter/RASF urgency to Greg publicly — secured EOW commitment
Publicly escalated Dieters stress and lack of RESF authority in #distinguished-leaders (When are we actioning Dieter? Hes super stressed and feeling unsupported), forcing Greg to commit End of week is my target on finalizing the RASF.
Committed CVE categorization + kpatch estimates to Google by Monday
After Tissa agreed no one can answer Madhus blanket questions, committed CIQ to deliver a CVE-type classification table with kpatch coverage estimates by Monday. Reshaping an unanswerable request into a structured, defensible answer by category.
Sensitive Decision
Set Sales Scope Discipline on Nokia Opportunity
In MPDM with Adam Jackson, Bjorn, Greg, and Jonathon, set firm boundaries on product scope for the Nokia deal. CIQ should sell what it has and is good at, not build custom solutions to close individual deals. The bar for adding new capabilities is company-level strategic pivot territory — not deal-level customization. Stated 'enough money is a LOT' and 'its not going to be for another 500k, or just to close the deal.'
Escalated Google/NVIDIA Rocky messaging discrepancy to Bjorn
Peter flagged in Leadership Roundtable that Google is giving NVIDIA conflicting information about Rocky Linux usage. One Google contingent confirmed usage to Peter/Bjorn/NVIDIA last week, while a separate contingent is now telling NVIDIA Rocky is not being used. Peter escalated to Bjorn for same-day resolution.
Agreed to Uber Value Drivers Framework for Strategic Clarity
Agreed with Bjorn and Chris Baek to restructure value drivers into a two-tier system: 'Uber Value Drivers' (Theme/Epic level) that group related granular drivers. This resolves the tension between strategic clarity (too many granular items fail to communicate corporate strategy) and operational granularity (engineering/marketing need precise items to sync on).
Shaped Interview Panel with Veto Condition for Performance Engineering Hire
When Greg wanted to add Cedric to the interview panel and reduce from 5 to 4 interviewers, agreed Bjorn could be dropped but set a condition: a NO from Max or Peter must count as a veto.
Reinforced Product Owns Exit Criteria — Engineering Cannot Unilaterally Remove Requirements
Directed Brady and Brian that Product defines the 'what' and the 'when' while Engineering owns the 'how'. Engineering cannot unilaterally remove requirements from exit criteria. The correct response when a requirement is challenged is 'When can you deliver it?' not to debate or remove it. Forwarded the meeting recording to Bjorn and Chris Baek to align them on this prod/eng interface vision.
Set Lab-to-Production Boundary — Nothing Ships Without Engineering Productization
Established with Bjorn that nothing from Greg's Innovation Group/Lab (Cedric) goes directly to production. Everything must pass through Engineering for productization, validation, and integration with build/signing pipelines. CIQ does nothing with RLC-Performant until the lab produces something viable.
Defended Global Prioritization Model with Per-Team Computed Views
Convinced Greg that product prioritization must remain a single global list, not grouped by team. Agreed to add a computed property showing priority within each team for visibility. Fuzzball was reprioritized into top 20 in Exec meeting; Greg's remaining concern about Fuzzball not being high enough was resolved via the global+computed-property approach.
Reinforced Product Ownership of Exit Criteria
Engineering unilaterally removed the NVIDIA CUDA toolkit requirement from RLC Pro 9.6 LTS exit criteria, citing lack of automation. Peter clarified in the Brian/Brady sync that Product owns exit criteria and prioritization, Engineering owns the solution and date. When a requirement is challenged, Product asks When can you deliver it - not whether to include it.
Google NEXT - Value-First Attendance Framework for Nathan
When Kelly asked if Nathan should attend Google NEXT (April 21-24), set a value-first framework: Nathan goes only if there's a concrete business objective. Pushed Kelly to define the business case rather than defaulting to sending people.
NVIDIA Partnership - Resource Commitment for Grace Vera Patch Support
Committed to assessing headcount needs for NVIDIA Grace Vera patch support — both for the first 6 months and then ongoing. Forwarded NVIDIA patch list to Nathan for SWAG assessment. Nathan estimated 3-6 months for RLC, faster for CLK 6.18. Communicated requirements to Scott Hara: hardware access, test suites, functional and performance targets.
RESF Restructure - Confirmed Proceeding Despite Greg's Hesitation
Confirmed CIQ should proceed with the Dieter RESF restructure plan, overriding Greg's expressed concern that the restructure doc might disrupt RESF's current momentum under Leigh. Bjorn aligned with Peter. Greg deferred rather than blocking.
FIPS Delivery Contingent on Google Commercial Commitment
Peter stated CIQ needs to make clear to Google soon that FIPS delivery depends on either getting a revenue ramp projection or a new contract. Google can't have the deliverable without the commercial commitment. This came after Bjorn reported Google's Madhu is delaying projection estimates and 'feels like they are trying to exert leverage.'
Taking Personal Lead on All GDC Communication for Next Month
Peter decided to personally lead ALL Google GDC communication for the next month, replacing the current multi-voice approach. New framing: 'we are technically capable; let's discuss the contract' instead of 'we can do it if you pay us.' All GDC work must be categorized into two buckets: work CIQ would do anyway (GDC accelerates it) vs work done only for GDC.
FIPS 6.18 Option 2 Engineering Kickoff
After Manu at Google did not respond to the relationship reset email sent Sunday, Peter escalated the FIPS proposal to Tissa via Kelly. Tissa authorized CIQ to proceed. Peter then directed Nathan to begin engineering work on Option 2 (faster timing path) while awaiting the Atsec contract. Engineering was held in reserve until external confirmations landed to avoid thrashing.
Set April Engineering Delivery Miss Target at 3-6 Items
Set a specific target of missing 3-6 items out of ~50 April engineering deliverables at Leadership Roundtable. The list contained mis-categorized items, granular sub-tasks, and placeholder dates. Follow-up: Chris Baek and Bjorn to prune the list tomorrow, engineering leads must update Jira with realistic dates by 9am.
Google GDC Relationship Reset via CTO Email to Manu
Drafted and sent strategic email directly to Manu at Google Engineering, acknowledging communication disconnect, offering FIPS 6.18 acceleration at certification cost only (~$180k, CIQ absorbs NRE), directing shared git repo setup for co-development transparency, and requesting Google revenue ramp projections. Reviewed draft with Bjorn before sending; forwarded final to Max crediting his input.
Agent IQ: Requiring Bjorn to Justify Before Supporting
Peter directed that Bjorn must articulate how Agent IQ augments CIQ's portfolio before it gets engineering resources. Not killing the project outright but requiring strategic justification.
Empower Dieter as RESF Infrastructure Lead + Stock Grant
Peter decided to push Greg to give Dieter formal authority as RESF technical infrastructure lead, and approved a stock grant for Dieter with Bjorn's support to tie him more closely to CIQ.
Established Fuzzball AI validation process
Committed to validating Greg's Fuzzball AI marketing claims before they go external. New process: Greg/Jonathan provides desired story, Peter documents engineering tests required, engineering validates and gives thumbs-up/down. HumanX conference in 2 weeks is the forcing function.
Sensitive Decision
RESF — Deliberately accepted engineering capacity hit for RESF support
Explicitly committed to accepting CIQ engineering disruption from RESF support work. Stated he'd be 'upset' if there isn't impact on engineering — signaling this is the right priority trade-off and meaningful work should be happening.
RESF — Committed CIQ resources (Dieter/Nathan) and proposed tech lead structure
Committed Dieter and Nathan to near-full-time RESF work. Proposed Dieter as RESF tech lead reporting to Peter for ~1 year. Told Leigh both are available immediately (Dieter now, Nathan when back from vacation). Scheduled Tuesday alignment meeting with Greg/Bjorn/Max to formalize structure and authority. Briefed Max on strategy: unified front with Bjorn, carrots and sticks approach for Greg meeting.
Fuzzball SaaS Prepaid Token Billing Model with Unified Portal Backend
Drove adoption of prepaid token ('CIQ Tokens') billing model for Fuzzball SaaS MVP, with unified Portal backend as single source of truth for all user accounts and token balances. Free tier deferred to fast-follow. MVP requires account + credit card to run workflows.
Google Deal — Engineering Owns Resource Projection
Directed that engineering (not finance/biz dev) should own projecting what the Google deal requires in terms of team size and capacity. Participated in Google Deal review meeting where consolidated $6M/yr development fee proposal was developed, including engineering guardrails (live patching scope limits, early renewal trigger). Deal structure: $6M dev fee for 5-7 senior engineers, uncapped variable usage fees (removing $1M cap), 15-25% margin on premium listings + MDF, early renewal trigger if scope exceeds funded team capacity.
Brian Clemens — Loop In After Front Door Closes
Decided Brian Clemens should be brought into RESF matters only after the front door is closed, acknowledging he'll be critical for reconstruction but the current phase requires operational security. Conditional on his behavior: 'If he hasn't gone off the reservation at that point.'
Coordinated Google Post-Mortem Alignment Between Nathan and Bjorn
Ensured Nathan's Google post-mortem document was reviewed by Bjorn before sending to Google, because Bjorn has a Thursday call about contract changes and the doc could undermine his asks.
Endorsed Bjorn's Linux Prioritization Framework
Endorsed Bjorn's four-principle framework for prioritizing Linux work (Parity, Value, Access/ubiquity, Integration) and directed him to provide concrete examples demonstrating the framework in action.
Sensitive Decision
Prioritize GPU Optimization to Define Team Capability Needs
Directed that GPU utilization optimization be prioritized for Fuzzball/RLC AI, using the priority as a diagnostic to reveal what in-house capabilities the team needs.
Prioritize Google Exec Meeting — Adjust Reno Travel
Agreed to meet a confidential new Google executive (distinguished engineer from Google Cloud, came through Tissa) for Monday dinner or Thursday lunch. Thursday option requires returning from Reno Wednesday night. Directed Greg to cover Toyota in person on Wednesday if needed.
Sensitive Decision
Toyota POC — No Hotfix, Demo MPI and PBS Separately
Decided NOT to rush a hotfix for Toyota's urgent out-of-scope MPI-via-PBS request before their Thursday director meeting. Team will demo MPI and PBS as separate working components, explain the integration bug is known, and commit to fix in ~1 week by the March 17 Reno meeting.
Ascender Developer Hiring — Network-First Sourcing Strategy
Decided to hire a dedicated AWX developer for Peter's team to offload maintenance from Jimmy Conner, freeing him for strategic architecture, sales engineering, and customer engagement. Hiring strategy: Jimmy sources from AWX network first (leveraging dissatisfaction with project's shift to internal repos), Brianne as fallback. Compensation: culture-forward, candidates may accept $25-50K pay cut for culture/stock options, $100K+ gap is non-starter.
RESF Option A — CIQ-Led Transition with Narrative Reframing
Adopted Option A (CIQ-led transition) as the only viable path for RESF. Reframed narrative for Greg as 'skeleton' foundation for future vibrant community, not 'threadbare' end state. End-state vision: Rocky Linux displaces Alma and Ubuntu as de facto enterprise OS. Identified critical leadership gap requiring new empowered leader ('mystic unicorn') deputized by remaining board. Internal story: 1-year transition to 501(c)(6).
Push for Continuous Sales/Support Enablement
Aligned with Greg on pushing for continuous product enablement (demos, walkthroughs) for Sales and Support on every new engineering feature, overriding Bjorn's resistance. Peter committed to re-engaging Bjorn on this.
Unified Google Proposal — Present Combined GDC/GCE to Rohan
Aligned Kelly and Bjorn on presenting a unified GDC/GCE proposal to Rohan (Google senior director) instead of negotiating separately. Reframing from pro-serve/ticket model to value-driven partnership with a large fixed annual fee ($8-9M).
Sensitive Decision
Directed March engineering priorities to come from Bjorn (Product)
When Chris Baek asked Peter to present engineering deliverables for March at the Leadership Roundtable, Peter redirected: the top priorities for March should come from Bjorn (Product), not from Engineering. Peter offered to go over them but insisted the framing should come from Product.
Aligned with Max on RESF Option A (Skeleton Independent) as the best path
After reading Max's RESF decision framework document ('The Future of the RESF: A Decision Framework for CIQ'), Peter agreed with Max that Option A — maintaining the RESF as an independent entity in the lightest possible form with one CIQ-employed full-time RESF leader — is the best path. This is Peter's position alignment with Max, not yet a company decision. Next step is presenting to Bjorn and Greg for buy-in.
Aligned with Max on RESF Option A (Skeleton Independent) as the best path
After reading Max's RESF decision framework document ('The Future of the RESF: A Decision Framework for CIQ'), Peter agreed with Max that Option A — maintaining the RESF as an independent entity in the lightest possible form with one CIQ-employed full-time RESF leader — is the best path. This is Peter's position alignment with Max, not yet a company decision. Next step is presenting to Bjorn and Greg for buy-in.
Demanded measurable success criteria for LinuxLM project
Greg proposed training/fine-tuning a Linux-expert foundation LLM (LinuxLM). Peter pushed back by demanding explicit success criteria — deployment plan, evaluation methodology, and clear value proposition — before endorsing the project.
Committed to RESF day-of execution planning meeting next week
Committed in #internal-resf-escalation to organizing a meeting next week to build an execution plan for the RESF day-of lockdown. Directed Sarah to invite Nathan, Max, Justin, and Dieter. Bjorn is finishing messaging drafts this weekend, so technical execution planning must be ready to match the communication track.
Decided to carefully surface Icicle results to Bjorn
After validating Icicle test methodology with Ryan (BIOS change applied before both with/without comparisons — apples-to-apples), and learning Ani was told by Bjorn to stand down on Icicle, Peter decided to personally and carefully bring the validated results to Bjorn's attention.
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.
Set NVIDIA positioning: benchmarks are AMD-only, offer to collaborate on tuning
Defined strategic positioning for NVIDIA benchmark situation: frame existing benchmarks as AMD-only, and offer to work with NVIDIA to tune Rocky Linux for their platform. This turns a potential embarrassment into a partnership opportunity.
Approved retention check-in strategy for must-keep employee list
Approved the must-keep employee list prepared by Mariah and Chris. Committed to personally leading retention check-ins with must-keep engineering employees. Bjorn leads check-ins for his org. Mariah and Chris excluded their own teams (already monitored closely).
Committed to Google contract restructure proposal within 1 week
Secured commitment from Google's senior management to consider a contract restructure addressing financial unsustainability. Peter committed to delivering a formal proposal for new contract terms within one week.
Challenged RLC-AI performance claims before NVidia/Humain use
Peter personally interrogated the RLC-AI 9-10% performance advantage claim by going directly to Damen Knight (engineer who ran benchmarks) and Max Spevack. Discovered gains largely disappear when benchmarking code is properly optimized (uses torch.compile, etc.). Then asked Damen to evaluate whether Brian's marketing write-up is accurate or misleading: 'makes it sound awesome instead of pointless for data center deployments.'
Initiated proactive top performer temperature checks
After Ian Kaneshiro's resignation, Peter directed the senior leadership group in #distinguished-leaders to split up and individually meet with top performers to take their temperature. This is a systematic retention check rather than just crisis management for the single departure.
Escalated Ian Kaneshiro retention to CEO level
After learning Ian Kaneshiro (PIC team, reports to Chris Wolford) resigned to join an AI startup, Peter immediately directed a retention escalation: told Mariah to get Greg talking to Ian, told Greg to do anything to keep him. After learning Ian had already accepted and wouldn't go back on it, shifted to ensuring the door stays open for a future return.
Commit to benchmark accuracy sign-off by tomorrow
Committed to signing off on the accuracy of the RLC-AI benchmark document by Feb 21, gating its release. Greg conditioned approval on numbers being '100% accurate' and verifiable. Bjorn shared both internal and external draft documents for review.
Assign Max as RLC-AI benchmarking plan owner with RHEL comparisons
Assigned Max Spevack as owner of the RLC-AI benchmarking plan in response to Greg's question about ownership. Directed that RHEL comparisons be added to exit criteria. Bjorn owns product definition (what to benchmark), Max owns technical execution (how to benchmark accurately). Max will create a one-page methodology document for the Humane pitch.
Directed RESF counter-narrative to Bjorn to prevent premature escalation
Directed Steve Wallace to email Bjorn (CC Peter) with evidence of positive RESF engagement through Mirror Manager project before Bjorn potentially takes aggressive action. Steve's team has made progress with Neil — environment access granted, Mirror Manager epic unblocked — while other teams report significant friction.
Sensitive Decision
Directed AMD inclusion in Project Odin approach document
Peter reviewed Adam Jackson's first draft of the Project Odin approach document and approved it with one specific direction: slides 6/7 should include AMD. Otherwise approved as a great first draft.
Mandated accelerated cadence with coordination accountability
In Department Heads meeting, mandated announcements every 2-4 weeks as non-negotiable. Drew accountability line: engineering protected for speed mistakes but NOT for coordination failures (status updates, product priorities, public channel decisions). Framed as make-or-break period driven by $30B revenue goal and Middle East partnership success.
Leveraged TPS report visibility to drive accountability with Justin
Proactively messaged Justin that the Release All Things section of the TPS report looks bad, with a 2.5-hour deadline before C-Suite Sync presentation. Gave Justin a window to update Jira tickets to reflect reality.
Mobilized team for Saudi meeting prep and escalated NVIDIA DOCA blocker
Peter personally intervened to prepare team for critical Saudi Arabia partner meeting on RLC-AI. Posted in #product-rlc-ai asking about CUDA/DOCA availability, discovered NVIDIA written approval for DOCA OFED still pending. Emailed Scott Hara (NVIDIA) directly to advance the approval. Tagged Nathan, Justin, Jeff Uphoff, and Damen Knight demanding they answer Max's detailed technical questions within 24 hours. Set hard deadline: '24 hours from now.' Bjorn committed to calling Scott to reaffirm DOCA modification rights.
Demanded war-room or date ranges for RLC Pro release dates
Marketing (Lindsay Aamodt) published release dates in #department-heads: Feb 19 RLC Pro, Feb 26 RLC Pro AI, Mar 5 RLC AMD. Justin Haynes responded that dates were 'written in light pencil.' Peter directed Justin: if dates aren't confident, either commit with a war-room to hit them, or provide GTM with ranges now so they can plan. Justin acknowledged and scheduled time with leads.
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.
Shared Mini-Me delegate access with Bjorn for collaborative todo management
Gave Bjorn delegate access to Mini-Me web app so he can see Peter's todo list, enabling collaborative work on shared priorities during Dubai travel week. Walked him through the limited view and how it works. Also instructed Bjorn to have Sarah coordinate with Moody for Google/Slack permissions setup for a new person.
Coached David Godlove on sales-focused approach for AMD Fuzzball presentation
During the AMD Fuzzball overview meeting, coached David Godlove via DM to maintain a sales mindset rather than defaulting to engineering transparency about product limitations. Emphasized that the goal was to make AMD want to recommend Fuzzball, not to give a technical peer review.
Approved RLC+ and Pro product hierarchy with new naming and de-risked launch cadence
Approved a new product hierarchy: Stock Rocky (pure community mirror), RLC+ (free with NVIDIA/AMD drivers), RLC Pro (paid tiers). The RLC name now signifies CIQ value-add. Also approved a de-risked 3-phase launch cadence: Phase 1 (Feb) bundles RLC Pro + RLC Plus NVIDIA; Phase 2 (Feb) RLC Pro AI; Phase 3 (Mar) RLC Plus AMD partnership. Identified backporting vs roll-forward policy gap as a pre-launch blocker.
Travel SLA Commitment to Max - 2 Weeks Notice Minimum
Committed to Max that he will have at least 2 weeks notice before any required travel, unless the company is in crisis. This gives his family (Christina) the ability to plan around his absences.
RESF Strategy: Remove Lewis with Legal Leverage, Engage Neil Collaboratively
Approved plan to remove Luis (Lewis) from the RESF board using a Quinn Emanuel memo documenting a potential federal law violation and breach of fiduciary duty, then send a collaborative letter to Neil offering a path forward to avoid a public fight. Greg will present the memo to board members to secure their support. Shadow infrastructure (Koji, clones) is confirmed ready.
CODE2 Values Redefinition - From Traits to Behaviors
Proposed redefining CIQ CODE2 values from character traits (what people are) to observable behaviors (what people do). Created comprehensive framework translating each value (Customer Centric, Optimistic, Dedicated, Efficient, Excellent) into concrete, measurable actions for engineering. Shared draft with Bjorn first for alignment, then presented to Greg in 1:1.
Shared AI development velocity guidance with Max
Forwarded the MultiversX 20x Development Velocity article to Max with specific direction to apply its agent testing approach to NARF.
Launch RLC Plus/Pro re-architecture under new non-Rocky brand
Decided to launch the RLC Plus/Pro product re-architecture under a completely new brand name, deliberately decoupling it from the Rocky name to avoid getting caught in the PR fallout from Lewis and Neil departure.
Advocate for in-person Anduril POC kickoff in Seattle
Decided to advocate for an in-person technical kickoff meeting in Seattle for the Anduril POC, with both Peter and Max attending. Set clear boundaries on duration - a day or two is fine, but two weeks would break February delivery dates.
Position Bjorn as escalation point for Tenable business readiness
Decided to position Bjorn as the escalation point for Brady to resolve Tenable business-side roadblocks on the Nessus plugin integration. Technical pipeline (Sam's work) is ~95% unblocked and can deliver data within weeks, but business side may not be ready.
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.
Escalated Visa support model concerns to Greg
Escalated concerns about CIQ support arrangement with Visa to Greg and Bjorn. Questioning why CIQ is on the hook to support Rocky Linux (which CIQ does not build) for Visa, rather than having Visa use RLC so CIQ can actually fix their issues.
Explored Max taking Product role for Linux
Floated the idea of Max potentially taking a Product role for Linux (or the head of Product for Linux role) while acknowledging his preference not to manage people. Framed as a question to explore optionality.
Performance review redesign - define traits with observable behaviors
Committed to drafting a proposal to fix the performance review system for the April/May cycle. The approach keeps existing traits but defines each with observable behaviors so managers and employees have shared understanding of what success looks like.
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.
Established escalation protocol for Product blockers
When Product (specifically Dawson) does not respond to meeting requests blocking engineering work, Nathan should explicitly request the meeting, then escalate to Peter and Bjorn via Slack if no response within 1-2 days. This creates a documented pattern of Product blocking Engineering.
Jason Lewis layoff with Steve Wallace as compliance owner
Decided to proceed with Jason Lewis departure (structured as layoff) due to expectation misalignment and damaged relationship with Bjorn. Steve Wallace will assume all compliance responsibilities (ISO 27001, SOC 2, ISO 42001). Budget reserved for full-time replacement after 6-month layoff waiting period. Fractional hire and external auditor approved for interim.
Instituted ARR and CVE gap metrics visibility at weekly meetings
Decided to communicate both current ARR (as determined by finance) and CVE gap metrics at weekly meetings. Proactively communicated this to Bjorn and Greg, anticipating potential concerns but proceeding anyway.
Redirected Brady to use prioritization tools instead of pushing hard
Directed Brady Dibble to use the order of operations (prioritization list) as his tool for influencing engineering priorities, rather than pushing uncomfortably hard on individual teams. Emphasized that the prioritization list is his lever to move all of engineering, and if the order of operations is wrong, the fix is to change it formally with Peter, Bjorn, and Justin.
Value Drivers document cannot be automated from Jira - fills a gap Jira lacks
Clarified that the Value Drivers Release Plan document cannot be automated from Jira. The document was created specifically to fill a gap in Jira - linking engineering deliverables to GTM deliverables around WHY certain work is being done. Since Jira does not contain this linkage data, automating from Jira would just reproduce the gap.
COGS data access unblocked for Ryan - Bjorn to grant via Kelly
Convened Bjorn and Ryan to resolve Ryans 6-month block on accessing official COGS data. Ryan had been forced to recreate the data independently, which conflicted with Bjorns H1 directive to use a single official source. Bjorn agreed immediately and will email Kelly Marlin today to grant Ryan full access.
NVIDIA partnership scope agreed - CIQ Rocky Linux for NVIDIA AI at GTC
Agreed with Scott Hara on NVIDIA partnership deliverable: CIQ will deliver a free CIQ Rocky Linux for NVIDIA AI (with AI patches + NVIDIA drivers) for GTC showcase in ~8 weeks. No requirement to upstream to community Rocky short-term. Support cadence: 1-2h kickoff Q&A, then 3 weekly 1h sessions, then ad hoc. CIQ maintains distro with minimal NVIDIA intervention; NVIDIA supplies patches, system access, and optimization guidance.
Board AI narrative delivered - positioned NARF as lean maintenance enabler
Delivered board presentation with AI positioned as lean maintenance enabler. Sent high-resolution release plan to board members after meeting. Board reception was stable but not as enthusiastic as expected for NARF - described to Max as uneventful, well received but not a giant splash.
Board presentation narrative: AI as lean maintenance enabler
Finalized board presentation framing AI as the solution to lean, automated maintenance org. Key talking points: heavy AI usage across engineering, all builds automated with zero public issues in 3 months, leaning out maintenance to free devs for RLC-AI/H, RESF contingency infrastructure (3 heads, 5 weeks), CVE automation story (net-snmp 40-day p50 to 14 days), expectation to reduce manual CVE team by 75% in 6 months.
All-Hands messaging: acknowledge Q4 miss, pivot to pipeline optimism
Aligned with leadership on All-Hands messaging strategy: directly acknowledge Q4 revenue miss, then pivot to optimistic outlook highlighting $22M H1 pipeline and unified GTM plan. Peter to present tech updates (service endpoints, Nerf) and guide Mural board walkthrough. No naming specific deals to avoid premature expectations.
Product Roadmap Overload - Challenge Product on Prioritization
Directed Chris Wolford to push back on Product for a clear separation of critical path vs nice-to-have items in the H1 roadmap. Current roadmap is overloaded and risks critical path items.
Jason Lewis Retention Review - Requested Written Impact Case
Paused final decision on Jason Lewis role and requested Steve write a formal case detailing the operational impact of Jason departure - specifically on ISO 27001/42001 certifications and CIQ Federal work.
Google TDX Work - Funding Requirement
Rejected doing Google TDX work if it only means 2-3 months of paid engineering time. Set requirement that the work must add headcount to CIQ to be worth pursuing - otherwise CIQ is just spending scarce resources on Google priorities instead of its own.
Strategic Map Framework - Value Drivers vs Internal Efficiency Separation
Established new H1 strategic planning framework that separates customer-facing Value Drivers from Internal Efficiency Drivers. Framework uses three lanes: middle lane for Value Drivers (the WHY), top lane for GTM activities, bottom lane for engineering deliverables. Also established phased estimation process: low-confidence ballpark dates first, then engineering-only session to raise confidence.
COGS Visibility - Escalate Finance Data Access via Bjorn
Committed to scheduling a tri-party meeting with Ryan and Bjorn to secure finance data access (loaded rates) for Ryan's Intelligence Hub. Finance (Marlon, Kelly) previously denied Ryan's direct requests.
Trinity Quirk & Chris Short Terminations Executed
Terminated Trinity Quirk for failing to progress NARF/CVE automation integration despite clear expectations. Terminated Chris Short for failing to deliver on critical RESF-related goals. Sent transparent communication to all of engineering explaining the WHY behind these decisions.
Leadership 1:1s with Maple, Dieter, Andrew
Decision to begin regular 1-on-1s with Maple, Dieter, and Andrew (when onboarded) to build trust and ensure unified messaging.
Friday Layoff List Finalized
Finalized the layoff list for Friday Jan 9: Eli, Derek, Chris Short, Craig, and Trinity. Jason deferred due to ISO certification needs.
Commitment to Present Engineering-to-GTM Messaging Framework
Committed to presenting a framework next week that ties engineering work to changes in market state and corresponding go-to-market messaging. Triggered by Fuzzball Service Endpoints press release that was 98% HPC-focused, missing the critical AI angle despite AI being the strategic priority.
Jason Scott to Document WareWulf/Rocky/Fuzzball Integration Vision
Directed Jason Scott to write a 2-pager outlining his thinking on how WareWulf, Rocky, and Fuzzball should integrate end-to-end, including the value proposition of WareWulf Pro. Document to be shared with Peter and Bjorn.
Build Culture That Moves With Ambiguity
Committed to teaching the org to start moving with imperfect information rather than over-designing before committing. Will provide cover from Bjorn holding teams accountable for early SWAG estimates, enabling faster iteration and learning.
Bounty Program Design: Open Incentives Over Prescribed Work
Established that bounties at CIQ should be open to all engineers, not targeted at specific individuals. Rejected Bjorn approach of incentivizing Jesus and Alex specifically to work over holidays on Portal. Bounties should be available for anyone to claim if they want to accelerate delivery.
Advocate for Ryan's Strategic Seat
Committed to securing Ryan Smith a seat at the strategic decision-making table for RESF/Rocky Linux matters. Specifically promised to advocate for his inclusion in key meetings with Bjorn and Greg.
RESF Management Model Needed
Identified that RESF needs a clear management person or model as part of short-term response. The lord of the flies approach does not work. Does not matter if its Leigh or someone else, as long as they have personal energy/bandwidth. But it needs to be managed/run with clear accountability.
Fuzzball SaaS - Defer Pending Technical Alignment
Rather than making a call on Fuzzball SaaS viability concerns raised by Chris Wolford, directed Chris to align with Jonathan (who has pitched cloud-native ideas) to form a unified stance. If they reach opposing conclusions, escalate to Peter. H1 planning docs to proceed with caveat that SaaS initiative is pending alignment.
Product-Engineering Quick Estimation Process
Articulated position on providing quick, low-confidence estimates for Product prioritization. Engineering should provide 20% confidence SWAGs on demand so Product can do early prioritization - these are not commitments engineering can be held to. Distinguished between committing to work without a design (bad) vs providing a quick guess marked as such (good).
Sensitive Decision
Culture Document Feedback - Focus on PMF Over Morale Programs
Gave negative feedback on culture document. Called morale initiatives (swag, customer presentations) rearranging deck chairs on Titanic. Only endorsed product training to build product-led company. Identified redundant work (H1 planning already happening) and premature planning (5-year plan).
RESF Infrastructure Independence - Technical Execution
Directed Nathan to mirror all RESF repositories and initiated build environment duplication. Created #internal-resf-escalation channel with strict confidentiality rules. Keeping technical circle small (Nathan, Max, Justin, Dieter) while moving quickly.
RESF Crisis Response - Infrastructure Independence
After learning of hostile plans by RESF board members (Louis, Neil, Brian Clemens) to publicly attack CIQ, dismantle Rocky Linux infrastructure, and damage the project, initiated emergency response to replicate RESF infrastructure for Rocky 8, 9, 10 with minimal team awareness.
Planning RESF Relationship Improvement Strategy
Initiated planning meeting with Greg and Bjorn to address concerns about RESF function and plan improvements to the relationship
Pushing OpenDrives POC Forward at Executive Level
Continued pushing the OpenDrives POC by confirming Bjorn will talk to Robert B. Originally elevated this to COO/President level to drive strategic partnership.
Escalating OpenDrives POC to Executive Level
Decided to drive the OpenDrives + CIQ POC at a higher level by bringing in the COO/President (Bjorn). Pushing Bjorn to connect with OpenDrives leadership to progress the partnership.
Active Todos (6)
Brief Bjorn: visibility into Support value (QA, docs, PS, validation) must be invested in during H2 — COGS cannot be the only lens
C3. What's it for? Who owns it? How do we fix?
Review titles and comp across org
AMD - engineering is doing work.
NASA case study - where are we and what needs to happen?
Cyber Resiliance Act
Related Patterns (11)
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.
Resource Optimization Through Triage
Apply cost-benefit analysis to avoid spending disproportionate time and energy on low-impact activities. Conserve resources for high-impact work.
PMF Focus Over Morale Programs
At startup stage, finding product-market fit is the real driver of morale, not swag or programs. Resources should focus on core business problems rather than premature organizational investments.
Decouple to Protect Momentum
When components, initiatives, or products can be separated, decouple them so each can proceed independently. Unnecessary coupling creates fragility - one problem cascades into many. Decoupling limits blast radius and keeps as much as possible moving forward.