Jason Scott
Dec 19, 2025 - Oct 23, 2026
8
Decisions
0
Active Todos
10
Patterns
Decisions (8)
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.
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.
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 (10)
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.
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.
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.