Jason
Dec 19, 2025 - Oct 23, 2026
21
Decisions
0
Active Todos
14
Patterns
Decisions (21)
Fuzzball plus Stratum - one identity and one pane of glass, no duplicated functionality, Engineering owns the developer experience
At the 10/23 Fuzzball plus Stratum alignment session, Bjorn locked the product split (Fuzzball for R&D, training and research; Stratum for production and inference) and Peter agreed. Peter own calls were architectural invariants: (1) one identity and one set of permissions across both products, with views varying by role and the Stratum UI living within the Fuzzball UI if they coexist; (2) no duplicated functionality - anything both platforms use lives once, in Stratum or in a third shared repo, and Fuzzball reaches through to Stratum hooks; (3) Engineering, not Product, owns the CIQ developer experience of building these products. Process: Jonathon writes the vision for a second review, Wolford draws stock K8s versus Stratum with shared components broken out, Bjorn and Jonathon build an environment by use-case matrix to prune with, and a follow-up next week. Whether Fuzzball requires Stratum stays open between Greg and Bjorn.
Sensitive Decision
Give the principle then ask for a map of the ChatGPT license ask - fund frontier-tool access for key people, but see the shape first
In the Sept 10 weekly 1:1, Steve Wallace raised that Moody had been pinged in one of the AI channels about getting more ChatGPT licenses, said he wanted to run it by Peter before enabling anything, and offered that what he owed Peter first was probably what this would cost. Peter neither approved nor refused. He named a specific person he was comfortable licensing, confirmed Sultan already has one, and asked Steve to get a map of the ask. He then supplied the governing principle: these tools leapfrog each other, so some of CIQ key people having access to the competing vendor tools is critical, and it is fine.
Say yes to the Nikola Kolev hire only against a handshake that it starts a timer on Jason Rodriguez - and reject the three-or-four-more-people gate outright
Mariah reported that Nathan had told her he needs three or four more people in before anything moves on Jason Rodriguez, and would not be ready to start until October. Peter told Mariah flatly that is not going to be true, then took it to Nathan in their 1:1 the same afternoon. He drew the line precisely: he will shake hands on you can hire a Jason Rodriguez replacement before we do anything about Jason, but not on we filled every role that we could possibly fill before we are doing something. He then made Nikola conditional - if you want to move forward on Nick because you think it will allow you to remove Jason, then I will say yes, but I would like it to come with a handshake that you are getting super aggressive then with Jason. Nathan agreed to the handshake. In the roundtable an hour earlier Peter had held the same question open in front of the panel, saying the manager conversation had to happen separately.
Late-August dedicated security hire timing (6 months post-Jasons departure)
Aligned with Steve in 1:1 that a dedicated security resource hire is appropriate in late August — six months after Jasons departure. Options on the table: full-time hire, fractional resource, or expanding the Shin Brothers role. Steve currently at 70% capacity on ISO 42001 documentation; workload expected to normalize after this week, with SOC 2 and ISO 27001 audits expected to be lighter.
Sensitive Decision
Approve Jason Rodriguez performance exit path
Approved Nathan's plan to tell Jason Rodriguez he's 'not meeting expectations' and create an exit path. A 1-month exit plan is acceptable if Jason agrees. Performance gaps include missed deadlines (shim review for Rocky 9 late, Rocky 7 review pending) and unshippable code (large PR unlikely to pass review).
Delegated Jason Lewis termination coordination to Mariah for March 3
While preparing for Dubai trip, delegated coordination of Jason Lewis termination logistics to Mariah Rippee, asking her to work with Steve Wallace during the week Peter is out, targeting the first Monday of March (March 2).
Jason Lewis Termination - Ready to Action
Confirmed readiness to proceed with Jason Lewis termination now that the ISO 27001 certification letter has been received. Will coordinate with Steve Wallace and Mariah Rippee (HR) to execute. Jason recently requested a seat at the table for self-service discussions, unaware of the pending action.
Sensitive Decision
Addressed Nathan tendency to shield his people from criticism
Identified and communicated to Max that Nathan pattern of shielding his people from criticism is counterproductive and puts them at risk rather than protecting them. Aligned with Max to give same message to Nathan that we dont have time for this.
Require mandatory tagging of all fully AI-generated content
AI Committee established policy that all fully AI-generated content must be tagged to manage user expectations. Applies only to fully AI-generated content, not human-reviewed or AI-assisted work. Format and placement of tags is flexible.
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.
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.
Jason Lewis Termination Timeline
Jason Lewis is slated for termination by end of January. Timing is delayed to allow ISO certification work to complete over the next two weeks, as his name is on that work.
Public Acknowledgment of Jason Scott Leadership Transition
Posted public thank you in #department-heads: "Thanks for your leadership and steady hand Jason. Looking forward to this new chapter with you and really glad youre a part of this team."
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.
Championing AI Butler Adoption Internally
Shared detailed Slack MCP setup instructions with team members. Hosted/recorded AI Dashboard session demonstrating Butler setup. Personally using and advocating for meeting prep automation.
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.
Championing AI Butler Internal Adoption
Hosted and recorded the AI Dashboard/Butler setup session to drive internal adoption of Claude-based personal productivity tools across CIQ. Shared personal use case of creating meeting prep notes from Slack/email/docs.
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.
Related Patterns (14)
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.
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.
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.
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.
Small Circle for Sensitive Operations
When executing sensitive strategic operations, keep the circle of informed people as small as possible to prevent leaks that could accelerate hostile action or undermine the initiative.
Protect Engineering 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.
Purpose Is the Decision Procedure
When someone asks how a process, board, tool or artifact should handle their specific case, Peter refuses to answer on the askers terms. He re-derives the answer from what the artifact is for, states that purpose as the only decision procedure, and lets the answer fall out. Anything found to be serving a second purpose is deleted rather than debated. Tools and views are explicitly subordinate to definitions. He will accept that the askers real problem is simply not solved by this artifact rather than widen the artifact to cover it.
Demonstrate the Standard, Then Collect It
When a new leadership expectation has to land across multiple orgs, Peter does not write a spec. He runs a live exemplar in public with the strongest performer first, says openly that the ordering was deliberate, keeps the form of the deliverable open so the ask stays about the thinking rather than the artifact, lets the delta be self-evident to the people who will have to close it, and then collects the same from everyone else on a named rotation. He prefers showing imperfect work now over polished work later.
Redesign Conditions Over Policing Symptoms
When a direct report names a vulnerability and proposes surveillance-style verification mechanisms (breathalyzers, daily check-ins, monitoring rituals), Peter accepts the disclosure but pushes back on the surveillance model. Treats the verification proposal as a signal that the underlying environment needs redesign — and offers to change the conditions that produced the vulnerability rather than instrument the symptom. Costs Peter optionality (e.g., committing to broker work-hour expectations directly with the partner/spouse) — the asymmetry signals genuine retention vs transactional.
Name It Without Staffing It
Applies when a structural change is directionally clear but the specific person, budget or reporting line is not settled. Peter names the structure - the role, the reorg, the governance reform, the ladder - and deliberately does not attach a name, a req or a commitment to it. The 2026-05-21 observation states the economics plainly: cost of naming is near-zero, cost of premature commitment is high, and he consistently chooses naming. The 2026-08-24 observation adds the sequencing reason: once a specific person is attached to a framework, the framework stops being the subject. Mined from 6 independent observations between 2026-01-12 and 2026-08-24.
Different Diagnosis, Different Remedy
Applies when a directive or a problem spans several people or cases that superficially look alike. Peter refuses a uniform answer and sorts by diagnosis first, then applies the remedy that diagnosis calls for. The 2026-08-28 observation states the consequence for recording his decisions: when he gives a directive spanning several cases, the decision is almost never any single remedy - it is the rule that produces DIFFERENT remedies, and four cases with four different answers under one rule means the rule is the decision. The 2026-04-17 observation confirms he holds this as an explicit framework rather than an instinct. Related to Three-Lever Talent Management but distinct: that pattern runs hire, develop and exit in parallel, this one is about diagnosis determining which lever a given case gets. Mined from 6 independent observations between 2026-02-03 and 2026-08-28.
Constrain the Mechanism, Not the Access
When AI or automation raises a governance concern, Peter does not restrict who or what may reach the data. He constrains HOW the reach happens, so the pathway becomes auditable and deterministic. The failure mode he designs against is non-determinism, not leakage - a wrong filter in inspectable static code is a bug you fix once, while a model that sometimes pulls the wrong field is an unbounded, unauditable liability. He will therefore accept imperfect filtering and eventual leakage as the price of adoption speed, but will not accept a non-inspectable pathway.
Conscious Tech Debt for Execution Speed
When facing time pressure, explicitly acknowledge and accept technical debt rather than blocking progress. The key is making the trade-off consciously and visibly so it can be addressed later.