Core42 is a CIQ Engineering engagement, not Support - Ryan on point, Peter, Wolford and Nathan stay on the calls
Situation
Peter classified the Core42 deployment as CIQ engineering handling rather than Support, with Ryan Smith taking point. Peter, Chris Wolford and Nathan stay on the calls. Ryan on-call rotation was judged necessary but not sufficient - senior engineering (Peter, Nathan, sometimes Ryan, often Adam) must be on the Core42 calls when available. Bjorn was told he is not the overnight coordinator, and Core42 HLD/LLD documents go to Peter and Ryan org.
Reasoning
First secured data center in the Middle East guarantees surprises, and network/architecture surprises need people who can make engineering calls in the moment - a support escalation path cannot. Classifying it as engineering keeps senior engineering accountable without taking point away from Ryan. Made explicit during peak Ryan-Bjorn friction over overnight ownership.
Additional Context
Confirmed by Peter as stated.
Observed Evidence
Slack DM to Bjorn 10/11 classifying as engineering not Support; DM to Ryan 10/9 on-call necessary not sufficient; Fathom 10/8 declining Bjorn as overnight coordinator and routing HLD/LLD to Ryan org.
Matching Patterns
Confidence Breakdown
Reasoning Depth Analysis
People Involved
Source
reflection
AI Confidence
75%
Related Context
slack
I feel good about Ryan taking point. I will continue to be on the calls. Wolford and Nathan too. I would class this as CIQ engineering handling, not Support.
fathom
It is not you, Bjorn... this is a game about information
Outcome
No outcome recorded yet.
Decision ID: be784518-1ec7-4fb6-9453-9fe61e56aaba