Customer-specific asks go through Work Ingestion and RAT build/validation - no side channels, even under deal pressure

October 23, 2026 at 10:57 PMoperationalmedium

Situation

On 10/23 two escalations from Justin hit the same rule. Toss (Viva Republica) AWS private offers, tied to a $2.4M TCV deal with a frustrated customer: Peter joined the channel to ensure the ask goes through regular Work Ingestion - in Jira, with Product visibility, balanced against other work - and aligned with Bjorn that it goes on the product priority list. OCI HPC base image being built outside the normal path: if CIQ will stand behind it, it must come through the main RAT org, which runs the consistent build and validation process; same message in #team-asia-pacific.

Reasoning

Intake only means something if it holds when a large deal and an angry customer are behind the ask; Peter held it visibly in the channel. An image CIQ stands behind carries a support and security commitment that only RAT validation backs. Peter backed Justin, whose lane both threads were in, turning his position into the org position. The Toss ticket lacked business impact; with the deal context added, normal prioritization ranks it correctly.

Additional Context

Peter confirmed the hypothesis as presented.

Observed Evidence

Peter messages in three channels within two minutes on 10/23; Bjorn: it needs to go on product priority list; Peter: Then we are aligned; Justin had pushed back on the OCI image on 10/20.

Matching Patterns

60%
Purpose Is the Decision Procedure(intake exists so work competes for priority)
45%
Protect Engineering Focus Through Process(make implicit work visible so Product owns the trade-off)

Confidence Breakdown

33/35
Evidence
18/30
Pattern
18/20
Source
10/15
Corroboration

Reasoning Depth Analysis

Org Signal:Deal size and customer heat do not buy a bypass of intake or validation
Who Affected:Korea sales and BD, Brady on product timing, field engineers building images
Precedent:Field-built or customer-specific artifacts need RAT validation before shipping under the CIQ name
Consequences:Toss ticket raised in priority via normal path; OCI image work rerouted to RAT
Timing:Two escalations within minutes - moment to back Justin publicly

Related Context

💬
#toss-vivarepublica-privateoffer

slack

I asked to be added because I want to make sure this ask goes through our regular Work Ingestion process and does not short circuit prioritization.

💬
#product-rlc

slack

This NEEDS to come through the main engineering RAT org if CIQ is going to stand behind this image.

Outcome

No outcome recorded yet.

Decision ID: fea3be86-4afd-41ff-926e-832c8be8cae9