Skip to content
Log in
#software testing Dataset Open access

The Cosmological Constructor: A Backward State-Machine Reconstruction from Measured Data / Космологичен конструктор: възстановяване на състоянията назад от измерени данни

Станислав Панайотов
Aug 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

English Dataset and software · bilingual Bulgarian/English release The Cosmological Constructor is an audit-ready dataset and software release centred on append-only, typed scientific memory. The historical FITS files are never used as parents of the new chain and are never rewritten. Their contents are migrated into active semantic memory, while byte-exact snapshots remain available only as immutable provenance evidence. The source history contains 120 append-only FITS states with 274,180 table-row occurrences across 37 table schemas. The active migration stores 94,229 unique typed row values as standard SEMANTIC_OBJECTS. Identical typed values are stored once, but every original occurrence remains addressable by its exact [source sequence, HDU index, row index] position. ASCII, logical and integer cells are explicitly typed; floating-point cells retain their original IEEE-754 bit patterns. No averaging, sampling, binning or numerical rounding is introduced by the migration. The canonical FITS memory consists of nine SHA-256-linked commits. Commits 000002 and 000006 preserve the 120 historical files as byte-exact provenance snapshots. Commits 000007 and 000008 contain the active typed-value migration. The complete typed memory contains 47 action records, 218 layered-memory records, 94,385 semantic objects, 39 conclusions, 102 evidence paths, four cycle summaries and 449 lineage edges. Integrity and reproducibility all 120 source files pass FITS CHECKSUM/DATASUM and source-chain validation; all 274,180 source occurrences match the active typed representation; typed-value verdict: ALL_TYPED_VALUES_AND_OCCURRENCES_EXACT; file-chain verdict: CHAIN_INTEGRITY_OK; JSONL-to-FITS verdict: FULL_JSONL_FITS_OBJECT_EQUIVALENCE_OK; repeating either migration is idempotent and creates no additional commit; the focused FITS, universal-ingest, constant-frame-rate A/V and variable-frame-rate A/V tests pass; all eight runtime modules complete without exceptions, and repeated runtime evidence is byte-identical. Scientific and epistemic scope This revision changes storage, migration, consistency and provenance enforcement; it does not change the physical model, scientific equations, declared thresholds or numerical-precision rules. The machine contract remains fail-closed and additive. Results produced in the supplied runtime are labelled SELF_VALIDATED, INTERNAL_SELF_VALIDATED or INTERNAL_HELDOUT_SELF_VALIDATED. No result is presented as externally VALIDATED; that status requires a genuinely independent source and execution. Package contents 01_CURRENT_SOURCE/ — executable source, migration tools and focused tests; 02_DATA_INPUT/ — frozen, explicitly identified runtime input; 03_MEMORY/ — action ledger, layered semantic memory, cycle history and the nine-commit typed FITS chain; 04_RUNTIME_EVIDENCE/ — deterministic reports and auxiliary ledgers; 09_PROVENANCE_EVIDENCE/ — integrity report and quarantined/superseded artifacts; the release manifest and SHA256SUMS.txt — canonical inventory, sizes and hashes. Verify the downloaded release with sha256sum -c SHA256SUMS.txt. Python requires NumPy, Astropy and mpmath; the audio/video focused tests additionally require FFmpeg. Source-specific provenance and licensing notes remain part of the release documentation. Български Данни и софтуер · двуезично издание на български и английски Космологичният конструктор е одитируемо издание на данни и софтуер, изградено около append-only типизирана научна памет. Историческите FITS файлове никога не са родители на новата верига и никога не се презаписват. Съдържанието им е мигрирано в активната семантична памет, а byte-exact snapshots са запазени единствено като неизменимо доказателство за произхода. Изходната история съдържа 120 append-only FITS състояния с 274 180 срещания на таблични редове в 37 таблични схеми. Активната миграция съхранява 94 229 уникални типизирани стойности на редове като стандартни SEMANTIC_OBJECTS. Еднаквите типизирани стойности се пазят веднъж, но всяко първоначално срещане остава адресируемо чрез точната позиция [пореден номер на източника, HDU индекс, индекс на реда]. ASCII, логическите и целочислените клетки са изрично типизирани; клетките с плаваща запетая пазят първоначалните си IEEE-754 битове. Миграцията не въвежда усредняване, sampling, binning или числово закръгляне. Каноничната FITS памет се състои от девет SHA-256-свързани commits. Commits 000002 и 000006 пазят 120-те исторически файла като byte-exact provenance snapshots. Commits 000007 и 000008 съдържат активната миграция на типизираните стойности. Пълната типизирана памет съдържа 47 action записа, 218 layered-memory записа, 94 385 семантични обекта, 39 заключения, 102 доказателствени пътя, четири cycle summaries и 449 lineage връзки. Цялост и възпроизводимост всичките 120 изходни файла преминават FITS CHECKSUM/DATASUM и проверката на изходната верига; всичките 274 180 изходни срещания съвпадат с активното типизирано представяне; присъда за типизираните стойности: ALL_TYPED_VALUES_AND_OCCURRENCES_EXACT; присъда за файловата верига: CHAIN_INTEGRITY_OK; присъда за JSONL-to-FITS: FULL_JSONL_FITS_OBJECT_EQUIVALENCE_OK; повторното изпълнение на всяка миграция е идемпотентно и не създава допълнителен commit; focused тестовете за FITS, universal ingest, constant-frame-rate A/V и variable-frame-rate A/V преминават; всичките осем runtime модула завършват без изключения, а повторните runtime evidence файлове са byte-identical. Научен и епистемичен обхват Тази ревизия променя съхранението, миграцията, консистентността и контрола на произхода; тя не променя физическия модел, научните уравнения, обявените прагове или правилата за числова точност. Машинният договор остава fail-closed и additive. Резултатите от приложения runtime са означени като SELF_VALIDATED, INTERNAL_SELF_VALIDATED или INTERNAL_HELDOUT_SELF_VALIDATED. Нито един резултат не е представен като външно VALIDATED; този статус изисква действително независим източник и независимо изпълнение. Съдържание на пакета 01_CURRENT_SOURCE/ — изпълним source, инструменти за миграция и focused тестове; 02_DATA_INPUT/ — замразен и еднозначно идентифициран runtime вход; 03_MEMORY/ — action ledger, layered semantic memory, cycle history и деветкомитова typed FITS верига; 04_RUNTIME_EVIDENCE/ — детерминистични отчети и помощни ledgers; 09_PROVENANCE_EVIDENCE/ — integrity report и карантинни/заменени артефакти; manifest файлът на изданието и SHA256SUMS.txt — каноничен опис, размери и хешове. Проверката на сваленото издание се изпълнява с sha256sum -c SHA256SUMS.txt. Python средата изисква NumPy, Astropy и mpmath; focused тестовете за аудио и видео изискват допълнително FFmpeg. Бележките за произхода и лицензите на отделните източници остават част от документацията на изданието.

DOI
View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

Agile - denoting "the quality of being agile, readiness for motion, nimbleness, activity, dexterity in motion" - software development methods are attempting to offer an answer to the eager business community asking for lighter weight along with faster and nimbler software development processes. This is especially the case with the rapidly growing and volatile Internet software industry as well as for the emerging mobile application environment. The new agile methods have evoked substantial amount of literature and debates. However, academic research on the subject is still scarce, as most of existing publications are written by practitioners or consultants. The aim of this publication is to begin filling this gap by systematically reviewing the existing literature on agile software development methodologies. This publication has three purposes. First, it proposes a definition and a classification of agile software development approaches. Second, it analyses ten software development methods that can be characterized as being "agile" against the defined criterion. Third, it compares these methods and highlights their similarities and differences. Based on this analysis, future research needs are identified and discussed.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 728 citations · ⚡54
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

Context: Software startups are newly created companies with no operating history and fast in producing cutting-edge technologies. These companies develop software under highly uncertain conditions, tackling fast-growing markets under severe lack of resources. Therefore, software startups present a unique combination of characteristics which pose several challenges to software development activities. Objective: This study aims to structure and analyze the literature on software development in startup companies, determining thereby the potential for technology transfer and identifying software development work practices reported by practitioners and researchers. Method: We conducted a systematic mapping study, developing a classification schema, ranking the selected primary studies according their rigor and relevance, and analyzing reported software development work practices in startups. Results: A total of 43 primary studies were identified and mapped, synthesizing the available evidence on software development in startups. Only 16 studies are entirely dedicated to software development in startups, of which 10 result in a weak contribution (advice and implications (6); lesson learned (3); tool (1)). Nineteen studies focus on managerial and organizational factors. Moreover, only 9 studies exhibit high scientific rigor and relevance. From the reviewed primary studies, 213 software engineering work practices were extracted, categorized and analyzed. Conclusion: This mapping study provides the first systematic exploration of the state-of-art on software startup research. The existing body of knowledge is limited to a few high quality studies. Furthermore, 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 Open access Jul 2017

What happens when software developers are (un)happy

The growing literature on affect among software developers mostly reports on the linkage between happiness, software quality, and developer productivity. Understanding happiness and unhappiness in all its components -- positive and negative emotions and moods -- is an attractive and important endeavor. Scholars in industrial and organizational psychology have suggested that understanding happiness and unhappiness could lead to cost-effective ways of enhancing working conditions, job performance, and to limiting the occurrence of psychological disorders. Our comprehension of the consequences of (un)happiness among developers is still too shallow, being mainly expressed in terms of development productivity and software quality. In this paper, we study what happens when developers are happy and unhappy while developing software. Qualitative data analysis of responses given by 317 questionnaire participants identified 42 consequences of unhappiness and 32 of happiness. We found consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts. Our classification scheme, available as open data enables new happiness research opportunities of cause-effect type, and it can act as a guideline for practitioners for identifying damaging effects of unhappiness and for fostering happiness on the job.

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

Mobile phones have been closed environments until recent years. The change brought by open platform technologies such as the Symbian operating system and Java technologies has opened up a significant business opportunity for anyone to develop application software such as games for mobile terminals. However, developing mobile applications is currently a challenging task due to the specific demands and technical constraints of mobile development. Furthermore, at the moment very little is known about the suitability of the different development processes for mobile application development. Due to these issues, we have developed an agile development approach called Mobile-D. The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed.

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

Related blog posts

MIT News · Artificial Intelligence Aug 17, 2026

Q&A: Rethinking how innovation happens

In his latest book, Professor Eugene Fitzgerald examines the forces that turn breakthroughs into value — and why innovation resists simple formulas.