Install the Criterion Before the Argument
30
Occurrences
100%
Success Rate
4.6
Avg Rating
Description
Applies to a contested question that has not been argued yet - a meeting about to start, a test about to run, an escalation just received, a proposal about to be written. Peter moves first to fix the criterion, the boundary or the posture, before anyone argues the substance. The consistent effect, named explicitly in the 2026-07-29 observation, is that the other party cannot win by being more persuasive on the merits, because the merits are no longer the axis. Distinct from Reclassify to Route in mechanism: that pattern reassigns who owns a question, this one controls WHEN the criterion lands relative to the debate. The two frequently co-occur. Mined from 7 independent observations between 2026-01-20 and 2026-08-31.
Typical Approach
Decide what question is being answered and say so before the discussion opens - tell the interviewer whether this is a sell or an evaluation, tell the team what test decides go or no-go before the benchmark runs, open the customer meeting by naming the one question it will answer. Set commercial thresholds before engineering evaluation begins rather than after feasibility discussion has created momentum. Where facts are still moving, give a criterion instead of a verdict and time-bound the criterion so it expires rather than hardening into standing policy. Use whichever medium the argument is already happening in - a numbered list in a DM, a purpose restatement in a staff meeting, a binary question across a negotiating table. When someone asks you to generalise a single call, take the invitation and convert it into a standing rule on the spot so the next instance does not require you in the room. The criterion is the decision; the verdict is downstream.
Trigger Conditions
Last applied: November 3, 2026
Created: September 11, 2026
Example Decisions (30)
Datacenter business needs its own team and deals that pay now - stop signing engineers up for work far outside their remit
Nov 3, 2026 · strategy
Keep Stratum out of the Core42 IRIS deployment - take the win we have; Stratum can go into Grenoble
Nov 3, 2026 · strategy
2027 engineering budget - current reqs plus only two unallocated heads, one org-wide gathering every six months, cloud spend modeled as growth-tied
Oct 30, 2026 · strategy
GDC contract redline - air-gapped scope only, FIPS module is priced (75K plus lab fee) or dropped, 14-day critical/high SLA with the clock starting when a patch is identified upstream
Oct 30, 2026 · strategy
Apptainer - hold Bjorn to zero engineering hours and let things fall on the floor so the maintenance cost becomes visible
Oct 23, 2026 · strategy
Peter personally drives NVIDIA to commit, to Google, that it will support CIQ-built RLC on NVIDIA hardware
Oct 23, 2026 · strategy
Core42 - hold to the SOW: stock Kubernetes plus Fuzzball before Oct 31, no CIQ-installed CozyStack, technical pushback routes to Peter
Oct 23, 2026 · strategy
Get CIQ onto the embargoed security lists, Linux first - treat the absence as our failing; give upstream hours from the Stratum engineers to wherever Tim directs, and let Tim move without waiting on Peter
Oct 21, 2026 · strategy
Justin org becomes the platform team - and for more than Linux; deep Linux knowledge is needed to build the platform, not to run it
Oct 21, 2026 · strategy
Core42 Kubernetes - never let anyone at Core42/G42 say CIQ cannot do Kubernetes; ask questions only, route Stratum to Bjorn
Oct 21, 2026 · strategy
Desktop - all investment behind one opinionated desktop; stock upstream GNOME ships only as a zero-investment bridge for 10.2 and Everfox
Oct 21, 2026 · strategy
Core42 is a CIQ Engineering engagement, not Support - Ryan on point, Peter, Wolford and Nathan stay on the calls
Oct 16, 2026 · strategy
Get Core42 a Kubernetes demo from the head of the Kubernetes team - in person in Abu Dhabi if his schedule allows
Oct 2, 2026 · strategy
Desktop V1 - a minimum-requirements section from Product, a December to first-week-of-January window, latest-only as the working assumption, and an accepted black eye
Oct 2, 2026 · strategy
Endorse forward-deployed Fuzzball AI outright; make observability a buy/partner/build discussion after the functionality is written down; ask for a written path to profitability on existing products
Oct 1, 2026 · strategy
Endura goes into RLC-H as a feature, not a standalone product - and no public noise until engineering has audited and stands behind it
Oct 1, 2026 · strategy
Desktop v1 ships at minimum scope - a concrete acceptance-test list to hold Nathan to, one desktop environment first, no date until the design plan exists
Oct 1, 2026 · strategy
Unhold the security-engineer req and carry it to Greg in conversation rather than clicking approve
Sep 23, 2026 · strategy
Documentation and training stay in Ryan org - development work does not belong there
Sep 23, 2026 · strategy
Affirm CIQ needs an OSPO and commit engineering time to upstream contribution as the entry ticket to new ecosystems
Sep 23, 2026 · strategy
Adopt Bjorn no-US-eyes-only call as the operating assumption - and force the principle question to be settled separately from its effects
Sep 23, 2026 · strategy
Tell Bjorn the Wallace org is not over-staffed and may still need to grow - and hold the security-engineer ask for a couple of months
Sep 16, 2026 · strategy
Refuse to build the non-OS Core42 work on top of Ubuntu - getting moving is fine, doing the work entrenches the competitor
Sep 16, 2026 · strategy
Ignore AMD until someone escalates - and decline to have an opinion on whether to confront them
Sep 11, 2026 · strategy
Cap Binarly at validation-size investment - portfolio status buys no lower evidentiary bar
Sep 11, 2026 · strategy
Make the bleeding-edge driver the RLC-AI default over Dawson stability objection - explicitly a 3 to 6 month posture
Sep 11, 2026 · strategy
Refuse an SDLC release-cadence contract that would bind engineering - prioritization authority stays with Product
Sep 7, 2026 · strategy
Hire Jori Koolstra now - go into the interview intending to sell, then compress the loop to days
Aug 31, 2026 · people
Reclassify the GDC MIP-listing disclosure question as a contract-timing call and route it to Kelly Hall with a decision criterion
Jul 24, 2026 · strategy
Icicle viability gate: AI inference benchmark on H100 decides go/no-go
May 7, 2026 · technical
Pattern ID: e6821e17-3398-4423-ae6f-3890c91e32e3