Skip to content
#software testing Open access

THE RESEARCH HEART: A LONGITUDINAL WITNESSING, COUNTER-EVIDENCE, AND RECOGNITION FRAMEWORK FOR LIVING OPEN RESEARCH

Oct 2026 · Figshare
scientometrics and bibliometrics research

Abstract

THE RESEARCH HEART: A LONGITUDINAL WITNESSING, COUNTER-EVIDENCE, AND RECOGNITION FRAMEWORK FOR LIVING OPEN RESEARCHThe Research Heart proposes a longitudinal framework for understanding research not only as a collection of static outputs, but as a living system that continues to interact with people, institutions, scholarly infrastructures, and evidence after publication.Conventional research evaluation emphasizes publications, citations, datasets, software, and other scholarly outputs. These remain essential. However, they do not fully describe what happens when research encounters the world.The Research Heart introduces Witness Events as a structured layer for recording observable interactions with research, including acknowledgment, institutional routing, substantive engagement, critical responses, counter-evidence, referrals, infrastructure-level recognition, ethical boundaries, and other verifiable responses.The framework introduces a Witness Ring, a Research Metabolism Profile, and a Research EKG for representing the temporal rhythm and development of research interaction. Rather than reducing engagement to a popularity score, these concepts preserve the type, timing, provenance, and methodological significance of interactions.A central component is the Counter-Evidence Loop:CRITICAL WITNESS → TESTED → CONFIRMED / REJECTED / PARTIALLY CONFIRMED → REVISED → LEARNThis structure deliberately avoids assuming that either the original research claim or the criticism is correct. Evidence determines the outcome. Revision is preserved as part of the research history rather than treated as failure.The framework also introduces Boundary Witnesses, recognizing that an explicit request to discontinue communication is itself an observable event and must be respected. The methodological sequence is therefore:OBSERVE → RECORD → PUBLISH → NOTIFY → ACKNOWLEDGE → RESPOND → VERIFY → COMPARE → LEARNThe Research Heart further develops the concept of Narrative Provenance, through which accumulated Witness Events can be transformed into longitudinal research histories while preserving the underlying evidence.The framework does not replace peer review, citation analysis, bibliometrics, altmetrics, authorship, or established research evaluation systems. Instead, it proposes a complementary dimension:observable research interaction.A publication tells us that research was released.A citation tells us that research was reused or referenced.A witness record tells us what happened when research encountered the world.The framework is governed by explicit epistemic and ethical principles:No award implies endorsement.No silence implies rejection.No criticism implies error.No boundary is a failure.No revision is concealed.The Research Heart therefore treats research communication, institutional interaction, counter-evidence, ethical boundaries, provenance, and learning as potentially connected components of a living longitudinal research system.Its central proposition is:A research system becomes longitudinally observable when its interactions with the world are preserved as part of its provenance.The ultimate objective is not to prove that research is alive, but to develop an infrastructure capable of showing how research lives, changes, responds, and learns through time.The heart beats. The witnesses leave traces. The research learns.Primary themes: Living Open Research; Research Provenance; Institutional Observation; Witness Events; Counter-Evidence; Research Evaluation; Open Science; Research Ethics; Digital Evidence; Citizen Auditing; AI Accountability; Scholarly Communication; Longitudinal Research.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.