Skip to content
#software testing Open access

Sovereign Cyber-Physical Hypervisor Platform: Hardened Asymmetric Multiprocessing Co-Design Matrix Framework

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

Abstract

Sovereign Cyber-Physical Hypervisor Platform: Hardened Asymmetric Multiprocessing Co-Design Matrix Framework (v1 / REV14-FROZEN) This repository contains the absolute, production-frozen version 1 (v1) parent codebase for the Sovereign Cyber-Physical Hypervisor, implemented in strict compliance with the SEC-AMP-TRILOGY-SECURE-REV14-FROZEN master specification. The framework is engineered to enforce pure silicon determinism, absolute data integrity, and complete fault isolation across heterogeneous dual-core Asymmetric Multiprocessing (AMP) infrastructures. It targets mission-critical deployment environments prone to physical vulnerability vectors such as Electromagnetic Fault Injection (EMFI) and electrical voltage transients. This frozen v1 release establishes the uncompromised architectural foundation that will be continued under version 2 (v2) to support downstream child project integration layers. The platform splits execution domains between a high-overhead, non-deterministic primary Application Core (480 MHz ARM Cortex-M7 domain running Linux/RTOS abstractions for optical telemetry and SCADA logging) and an ultra-fast, strictly deterministic Sentinel Core (240 MHz bare-metal ARM Cortex-M4 domain handling real-time control loops and critical fluid line actuation). Key Microarchitectural Hardening Invariants:1. Strict Parallel Harvard Segregation: Instruction text and case targets execute natively inside zero-wait-state Instruction Tightly-Coupled Memory (ITCM) over the I-Code bus, while all static lookup tables, function pointer arrays, mutable tracking matrices, and buffers live strictly within Data Tightly-Coupled Memory (DTCM) to eliminate crossbar cross-contamination.2. Pure Arithmetic Determinism: Enforces strict compile-time soft-float constraints (#pragma GCC poison float double) combined with explicit linker-stage symbol exclusions (*(__aeabi_f*)) to completely paralyze software float-emulation timing jitter loops.3. Asymmetric Mailbox Protection: Communication interfaces are physically air-gapped using separate unidirectional APB peripheral bus structures. Slave Interface A (Application side) is bound to Shareable Normal Non-Cacheable Memory (TEX=001, C=0, B=0, XN=1) to prevent speculative prefetches, while Slave Interface B (Sentinel side) is mapped strictly to Strongly-Ordered Memory (TEX=000, C=0, B=0) to ensure un-buffered immediate register retirement.4. Word-Driven Stride Packings: Telemetry serialization utilizes strict 32-bit word-aligned strides to satisfy peripheral bus alignment restrictions, backed by an atomic four-step read-after-write pipeline register interlock (Atomic Write -> Compiler Fence -> Dummy Read -> Assembly DSB SY/ISB SY Barrier) to eliminate cross-boundary data tearing.5. Branchless Math Engine: Features an un-preemptible supervisor loop running a 7th-order fixed-point Taylor expansion Arrhenius decay engine. Upper and lower saturation clamping limits are resolved via portable, branchless unsigned relational bitmask selections to maintain single-clock execution profiles.6. Automated Disassembly Audit Gating: Includes a target-prefixed automated continuous integration parser (verify_pipeline.py) that evaluates post-link object text segments to mathematically prove the complete absence of non-deterministic conditional branch opcodes (bne, beq, cbz, cbnz) inside verified runtime code boundaries, while accepting deterministic IT blocks. The repository zip payload contains the full, production-tested 15-file blueprint manifest, including the global technical constitution (master_specification.md), the race-condition isolated Makefile build matrix, the target GNU Linker Script (sentinel_flash.ld), and the complete, verified C/Assembly source environments. --- 📋 SUBMISSION METADATA DIRECTIVES [Deposit Parameters]* Version Tag: v1.0.0-frozen* Upload Type: Software* Access Right: Open Access* License: Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0) [Target Keywords]Bare-Metal Hypervisor, Asymmetric Multiprocessing (AMP), MISRA-C:2012, Cyber-Physical Systems (CPS), Deterministic Execution, Fault-Injection Mitigation, Tightly-Coupled Memory (TCM), High-Assurance Firmware, Harvard Bus Matrix Isolation, Silicon-Determinism. [Target Curation Communities]1. Cyber-Physical Systems Security2. Open-Source Hardware/Software Co-Design3. High-Assurance Firmware --- Licensing & Open-Science Compliance:This archive is published under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License (CC BY-NC-SA 4.0). Any derivative works, downstream sub-systems, or secondary version 2 (v2) child projects must inherit these identical legal protection attributes and attribute this parent platform record accordingly. Code Verification Token: [ysD9J5, 0.1.1].

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.