Socioduality: A Relational Process Framework for Human-AI Interaction

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:2608.11322v2 Announce Type: replace-cross Abstract: Human-AI research often evaluates individual capabilities, joint performance, or final outputs, but these approaches can lose the interaction process that produced the result. This article introduces socioduality: a sequential, reciprocal, and history-carrying process in which one party's response becomes part of the observable conditions shaping the other party's next contribution, judgement, decision, or action. For human-AI dyads, the framework identifies moves, candidate episodes, confirmed episodes, and maximal pathways. A minimum episode A1 -> B1 -> A2 requires evidence that B1 responds to A1 and that B1 then enters the formation of A2; candidates are classified as confirmed, non-sociodual, or indeterminate. A frozen coding protocol was calibrated on three natural human-AI records using two separate model-based evaluator series. A supplementary exploratory analysis then compared frozen Sociodual pathways with blind developmental/task-process segmentations. Across six examined interactions, the two representations were empirically non-equivalent: task-stage changes could occur within a continuing Sociodual pathway, while formal pathway breaks could occur within a continuing task context. This distinction persisted under fine-grained re-segmentation and record-format checks and was reproduced in all three prospectively selected unseen records using a fresh model-based Sociodual coding line. Socioduality therefore offers a bounded process-level framework for studying how human and AI contributions become …

Vollständiger Originalartikel ↗

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