Research and releases
We follow published software-engineering research and upstream changes that may affect how software is built, tested and operated. Each note states the source type and limits the delivery implication to what the source supports.
Reviewed 21 August 2026
Research in use
These sources inform a method. Engagement results and the three-person pod shape remain separate operating decisions.
Software development
Research-program update · not peer reviewed
24 February 2026
METR reports that selection effects and unreliable time measurement prevent its late-2025 experiment from producing a dependable estimate of AI-assisted developer productivity.
How it affects the work
We measure AI assistance on the work and team using it, including review and rework. Fixed AI productivity multipliers stay out of engagement plans.
Quality engineering
Software-engineering preprint · not peer reviewed
6 July 2026
In the studied tasks, tests generated after faulty model-written code detected faults less often than tests generated independently: 14% compared with 25%.
How it affects the work
For AI-written code, we retain a validation path derived independently from the implementation, such as acceptance checks based on the requirement or contract.
Testing and review
ICSE-SEIP conference paper
2024
Google reports that prioritising uncovered code by similarity to tested or frequently executed production code improved coverage and produced modest review-efficiency gains in its environment.
How it affects the work
We use coverage with change risk and production context to decide where another test may help. Release readiness requires evidence beyond a raw coverage percentage.
Release watch
This dated sample shows the type of watchlist we maintain. Each engagement follows the client's actual stack and support policy.
Application framework
Official security notice
20 August 2026
Vercel announced an August 26 security release covering one critical vulnerability and identified 16.3.3 and 15.5.24 as the planned updates. Technical details remain withheld until release.
What we would check
Identify affected applications and prepare an upgrade test window. Confirm the planned versions against the published release before applying them.
Browser testing
Official patch release
30 July 2026
The patch fixes TypeScript-configuration regressions and accessibility-snapshot problems around the 1.62 release line.
What we would check
Pin the selected version and rerun monorepo configuration, browser and accessibility-snapshot checks before adopting the 1.62 component-testing changes.
JavaScript runtime
Official LTS release
3 August 2026
The LTS release includes configurable HTTP-header validation, TLS negotiation information and per-event-loop delay sampling.
What we would check
Trial the LTS update under the application's integration, dependency and operational checks. Use new diagnostics only where they answer a recorded reliability question.
The pod shape is an Anystack operating choice. Research, releases and advisories inform technical decisions alongside the constraints and evidence in the client system.