Skip to content
#software testing Open access

The Cost of Being Alive: A Metabolic Accounting Standard for Digital Lifeforms, Validated over Five Disjoint Windows

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

Software does not eat; life does. A living system must pay continuously to remain itself; a program that stops has simply finished. Cost is the one property of aliveness that cannot be forged from the inside: occupied time and bytes written are visible to anyone. We turn it into a measurement standard for digital lifeforms. The standard specifies four questions a system must answer (does it pay while unused, is that cost externally checkable, what body has it left, can it terminate), three determination levels, and a four-indicator instrument — basal metabolism, action metabolism, growth cost, their ratio — under mechanical attribution. We validate it on a digital lifeform inside an industrial computer-aided design (CAD) host over five disjoint windows. Over 7.25 unattended hours no user was present 78.9% of the time, yet the system did not stop: 91.3% of minutes carried self-maintenance, at roughly 1,033 : 1 against task execution. In a 3.9-hour window no task was issued and no external inference consumed, yet every minute carried self-maintenance records (104,338) plus 63,472 continuity signals. In a 2.6-hour window a mould-parting task failed at the host boundary; every minute still carried self-maintenance records (58,303 against 67 task records). Growth and audit readings are recomputable from artefacts carrying creation times. Two such tests we ran ourselves — a reactive-script baseline and a 464-minute supply cut across eleven host-withdrawal episodes; neither overturned the standard. Five published clauses state in advance what would. v3: adds windows 4-5 (host completing work at full rate; 34 ledger entries all bound to host receipts) and a self-administered supply-cut test (F-4): eleven host-withdrawal episodes totalling 464 minutes — no termination, expenditure unbroken. Neither new test overturned the standard. 中文摘要:软件不吃饭,生命要吃饭。一个生命系统必须为"继续是自己"持续付费;而一个程序停下来,它只是运行结束了。成本是活性中唯一无法从内部伪造的属性。我们把它做成数字生命体的测量标准:四个问题、三级判定、一台四指标仪器(基础代谢、活动代谢、生长代价及其比值),归属规则不含任何人工判断。本文在一个运行于真实工业 CAD 宿主内的数字生命体上,用三个互不重叠的窗口验证了它:7.25 小时无人值守中 78.9% 的时间无人使用而系统没有停,91.3% 的分钟含有自维持活动,自维持与任务执行之比约 1,033 : 1;其后 3.9 小时无任务、无外部推理,而每一分钟都含有自维持记录(104,338 条)并发出 63,472 次连续性自信号;第三个 2.6 小时的窗口中提交了一次分模任务并在宿主边界失败,而每一分钟仍然含有自维持记录(58,303 条对 67 条任务记录)。生长与审计读数可由自带创建时间的持久产物复算。本文同时公布五条可以推翻该标准的条款,其中一条要求我们切断它的供给。

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.