Field note /
Request construction became part of the treatment
A request-fidelity audit moved authoritative task context out of agent-written summaries and into deterministic host code.
How the claim changed
Belief
Typed request schemas, payload bounds, exact receipts, and explicit skill guidance were enough to make a successful semantic call a faithful representation of the underlying decision problem.
Evidence
In the fresh SWE-Lancer manager study, 20 treatment attempts successfully called Jev and every dispatched request was preserved exactly by the host-side receipt path.
Contradiction
None of those 20 calls passed the frozen context-completeness check. The complete authoritative task and proposal material fit inside the host limits; the loss occurred earlier when the coding agent summarized the source material before dispatch.
Correction
The next treatment generation uses a deterministic generic request builder plus a task-specific SWE-Lancer policy adapter. Exact title, description, and full proposal text are loaded from the pinned source; the agent contributes separately sourced repository evidence rather than recreating authoritative task content.
Current claim boundary
The v2 treatment has passed live qualification on an already-observed manager task and is preregistered for a fresh 30-pair cohort. That qualification proves request fidelity for the tested path, not an effectiveness improvement.