# Operational amendment v1.9: pending provider order

Issued on 2026-08-09 after live execution had started. At issuance, exactly one
cell had completed: a Prism `gpt-5.5` tau2 cell, which passed the official
evaluator. One official-DeepSeek ToolSandbox attempt had then failed with an
infrastructure `TypeError` before a generation trajectory was produced. Both
records are retained. The completed Prism result cannot be moved, erased, or
excluded.

The operator requested that the remaining work expose lower-risk providers
before Prism and official DeepSeek because Prism reliability was uncertain.
This amendment changes only the execution order of the 35 incomplete cells:

1. first pending QwenPlus cell;
2. first pending Token Rhythm `glm-5.2` cell;
3. all other pending QwenPlus and Token Rhythm cells in their prior relative
   order;
4. all official-DeepSeek cells in their prior relative order, including the
   failed cell as a bounded retry;
5. all remaining Prism cells in their prior relative order.

No cell, provider, task, outcome, metric, cap, baseline, hypothesis, or
analysis rule is removed or changed. The exact pending order and the live-log
hash at issuance are frozen in
`artifacts/model-arm-private/pending_order_amendment-v1.9.json`.

## DeepSeek infrastructure diagnosis

The ToolSandbox environment pins an OpenAI SDK version that constructs its
HTTP client with a `proxies` keyword removed by the installed `httpx` version.
The failure occurred during client construction, before a paid model request.
ToolSandbox runner v2 injects an explicitly constructed compatible HTTP client
and closes it during teardown. This is an engineering compatibility repair;
the model, prompt, tools, task, and evaluator are unchanged.

The targeted ToolSandbox mock layer must pass with v2 source hashes, and its
resume replay must be byte-identical, before further live execution.
