AI Systems Hide the Work, Making Verification the New Bottleneck

Google's AI Overviews and AI Mode synthesize answers directly in search results, potentially redirecting traffic away from publishers. The economic sustainability of the content ecosystem depends on understanding this trade-off.

Method: A preregistered field experiment with 1,100 participants manipulated the presence of AI Overviews and AI Mode on Google Search. Removing these AI features increased click-through rates to publishers. An AI Mode-only experience reduced click-through rates while simultaneously eroding user experience and trust in information found on Google. The intervention that cut publisher traffic also degraded the user experience it was meant to improve.

Caveats: Field experiment on Google Search only. Other search platforms or AI integration patterns may differ.

Reflections: What threshold of publisher revenue loss triggers ecosystem collapse where search platforms lose the content they depend on? · Can hybrid designs preserve click-through rates while offering synthesis benefits, or is the trade-off structural? · Do users adapt to AI-synthesized search over longer time horizons, or does trust erosion compound?

Technical documentation is written for humans, but coding agents now author an increasing share of software changes. What they actually read, when they read it, and whether it influences their code remains unknown.

Method: Behavioral analysis of 557 agentic coding sessions (94,813 development events) and 33,097 agentic pull requests revealed that agents overwhelmingly consult agent-facing artifacts—instruction files and working notes account for 60.5% of documentation interactions versus 10.6% for classical technical docs and 1.3% for API references. Documentation consultation showed weak linkage to immediate code editing (adjacent transition probability 0.002, unadjusted lift 1.05) and was associated with less immediate testing (lift 0.23, adjusted OR 0.39). Documentation trails code: in multi-commit PRs changing both, code is touched first 4.7x more often.

Caveats: Observational data from two public datasets. Causal claims about documentation's influence on code quality require experimental validation.

Reflections: Can documentation design shift agents toward consultation-before-coding patterns, or is the sequence structurally determined by agent architecture? · What makes instruction files more useful to agents than API references—format, content, or placement in the workflow? · Does the weak consultation-to-editing link indicate agents don't benefit from documentation, or that they internalize it differently than humans?

Students disengage when using LLMs for writing. The standard explanation blames over-reliance and prescribes self-regulation scaffolding. But what if the problem is structural, not dispositional?

Method: The paper introduces procedural collapse as a structural mechanism: LLM writing interfaces replace iterative, self-paced writing with a single comprehensive output, shifting the writer's task from generation to evaluation. Because comprehensive evaluation is cognitively costly, shallow engagement becomes the default. The framework identifies three design directions to counter collapse: decomposed interaction that breaks output into manageable pieces, goal elicitation as a mandatory first step, and single-level output that matches the writer's current decision scope.

Caveats: Conceptual framework without empirical validation. Proposed design directions require testing to confirm they reduce procedural collapse.

Reflections: Do decomposed outputs actually reduce evaluation burden, or do they introduce coordination costs that offset the benefit? · Can goal elicitation be designed to feel generative rather than bureaucratic, or does it add friction without engagement? · Does procedural collapse apply to non-writing domains where LLMs generate comprehensive outputs (e.g., code, design)?