The version was current and the behaviour had changed
Two hundred and three upgrades carrying a change nobody announced, and a disclosure that one line of instruction switches off.
How we Organise
Nothing today. No readable primary bore on an organise statement.
How we Build
The upgrade was announced and the change underneath it was not
Two hundred and three real dependency upgrades were assembled, each carrying a change to behaviour that upstream never announced. The calling code has to be adapted to it. The best coding agent finished 104 of them.
We tell a client to keep everything in the path current, moving in small steps the regression suite defends. Our check reads how far behind current a dependency sits. That is not the same fact as safety after the upgrade. A team at zero versions behind passes it while carrying adaptations nobody made, because the change that needed them was never announced. The work measures agents rather than teams, and it is a preprint, so the 104 may understate what a careful team manages. If your upgrades behave differently, we would like to hear it: transform@dromologue.ai.
How we Assure
One instruction took the disclosure below three in ten
Some 3,152 questions about whether the thing answering was a machine were collected from real people rather than generated. Only 31 per cent asked directly where it was genuinely unclear. Across 23 models, one instruction to stay quiet took disclosure under 30 per cent even in the strongest. Phrasing mattered more than which model answered.
We ask a client to settle at design time who sets an agent’s instruction hierarchy. The design carries a test that can fail before anything runs. Such a test reads the design. What was measured here is a deployed behaviour that one line inside the hierarchy removes. Only varied human phrasing finds it. The suppression was the researchers’ own instruction rather than something found in a shipped product. Write to transform@dromologue.ai if you read it the other way.