“there were new consumers between the time where the eval was written and the time it the evaluation was run. So the context graph is not only important to populate, but it's equally important that you keep it up to date, and any delays in syncing your context graph with the ground truth uh creates gap in the result.”
Video moment · 13:00 · youtube.com
From “We Mapped 115 Microservices for Our Coding Agents — Kamalakannan Nandagopal, Postman”, found 2026-10-15.
An impact-analysis eval failed because new API consumers had appeared since the graph was built. Postman found about 75% of PRs in its top 10 repos touch an API surface, so stale shared context quickly leads to wrong answers and lost developer trust. Quoted from YouTube’s auto-generated captions.