When Should AI Follow? Task Structure and Joint Adaptation by Human and AI Agents

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2504.20903v4 Announce Type: replace-cross Abstract: How should organizations divide and sequence decision tasks between human and artificial agents? We develop a computational model of joint sequential adaptation in which two agents differ in a single, precisely specified way: the memory regime governing how past decisions shape subsequent ones. A recency-weighted regime, motivated by behavioral evidence on human adaptation, privileges recent outcomes; a uniform-memory regime, motivated by the scale-free consistency of algorithmic updating, weights a window of past outcomes equally. Situated in the lineage of NK/NKC models but developed on its own terms as a sequential-adaptation model, the framework varies task scope (N), within-task coupling (K), and cross-agent coupling (C) across modular and sequenced task structures. Three mechanisms organize the results. First, threshold dynamics create absorbing high- and low-payoff regimes, so adaptation compounds whatever it inherits. Second, uniform memory amplifies inherited trajectories, for good and for ill, whereas recency weighting corrects locally but is volatile at scale. Third, memoryless stochastic adaptation, though inferior on average, functions as an escape mechanism when inherited trajectories are poor. Consequently, joint performance is maximized not by the prevalent "AI-first" design, but when scale-free adaptation follows a high-performing human; broad stochastic search instead rescues sequences initiated by low-performing humans. The model and its experimental validation (a separate study) offer …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2504.20903
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.