The agents were reading something else
What coding agents actually open when they read documentation, an incident agent that starts from a file it wrote itself, and a reporting deadline three weeks out.
How we organise
What coding agents actually read
Across 557 agentic coding sessions, instruction files and working notes took 60.5 per cent of every documentation interaction. Classical technical documentation took 10.6 per cent, and API references 1.3. Agents opened documentation because they chose to far more often than because something had failed.
We tell a client that the documentation it maintains and the documentation its agents read are two different sets. Only one of them has an owner. Nobody in most firms reviews the instruction files or knows who wrote them. This is observational work on public datasets.
How we build
Anthropic’s first responder for continuous integration failures
An agent on first response posts a grounded analysis a median of 14 minutes after an incident opens. The speed comes from a lessons file the agent appends to itself after each incident, holding what happened and what fixed it. Every investigation starts by reading it.
Our position is that the durable asset is the file, not the agent. The file is what makes the first hypothesis a good one. Somebody still has to decide when a recurring pattern is promoted into the skill. Anthropic is reporting its own figures.
How we assure
Assembling the evidence for the EU Cyber Resilience Act
The Act starts asking for reports on 11 September. It wants a manufacturer to show that a control operated, not that a policy exists. A framework tested on one product generated 70 assurance cases, which experts rated middling for plausibility.
We judge conformity as a tracing problem before a writing problem. That is why grounding matters here more than fluency. Reporting is the part nobody can assemble retrospectively. The authors say small manufacturers carry the cost worst, and this is one case study.