Skip to content
#software testing Open access

DS-EV: Battery Intelligence, Energy Recovery & Safety Governance

Oct 2026 · Zenodo (CERN European Organization for Nuclear Research)
Advanced Battery Technologies Research Electric and Hybrid Vehicle Technologies

Abstract

DS-EV v9.0.0 — BEDROCK REFORGED: ENERGY CONTINUITY Preserve the mathematics. Govern the evidence. Reconcile the energy. Overview DS-EV v9.0.0 represents a major engineering milestone: the culmination of the BEDROCK hardening campaign and the introduction of Energy Continuity. The philosophy behind this release is simple: hardening software is not about adding complexity. It is about strengthening the guarantees an application must uphold. Beginning with fifteen identified BEDROCK findings, we reinforced state integrity, numerical validation, trusted learning, rollback authorization, battery-energy accounting, and software update safeguards. Rather than replace existing architecture, we hardened its responsibilities while preserving the mathematical foundation. That preparation made the next capability possible. Energy Continuity introduces an optional, passive C++17 accounting layer for explicitly modeled physical energy transfers between batteries, power electronics, motors, vehicle motion, and dissipative sinks. It distinguishes measured, calculated, estimated, and simulated evidence; detects accounting discrepancies; and avoids presenting unexplained residuals as legitimate energy losses. This release remains research-stage software. Simulation results do not establish physical vehicle performance, hardware safety, or automotive certification. Engineering History — Pull Requests The following merged PRs document the work performed since v8.0.1, in chronological order. PR #39 — State Integrity Foundations [Review PR #39](https://github.com/dfeen87/DS-EV/pull/39) Resolved PB-01 through PB-03 by strengthening transactional state updates, coupling integrity, multicell validation, and short-interval rejection. Failed operations now preserve previously committed state within the tested contracts. PR #40 — Safety Limits and Hardware Clock Evidence [Review PR #40](https://github.com/dfeen87/DS-EV/pull/40) Strengthened directional state-of-charge and temperature checks while enforcing finite, valid hardware timestamps and evidence freshness. PR #41 — WNN Integration Corrections [Review PR #41](https://github.com/dfeen87/DS-EV/pull/41) Improved diagnostic visibility, Python warning-state exposure, initialization validation, and handling of integration edge cases. PR #42 — Diagnostic and Python CI Follow-Ups [Review PR #42](https://github.com/dfeen87/DS-EV/pull/42) Corrected advisory reporting, strengthened safety-monitor assertions, and established dedicated Python extension build-and-test coverage. PR #43 — DS-EV Repository Identity [Review PR #43](https://github.com/dfeen87/DS-EV/pull/43) Unified repository identity and documentation references under DS-EV without unnecessarily changing underlying software architecture. PR #44 — Fail-Closed Software Updater [Review PR #44](https://github.com/dfeen87/DS-EV/pull/44) Reworked the updater around authenticated payloads, SHA-256 verification, protected backups, staged validation, explicit failure handling, and verified recovery. PR #45 — Trusted Legacy Migration [Review PR #45](https://github.com/dfeen87/DS-EV/pull/45) Introduced a controlled, administrator-initiated maintenance migration for legacy installations that cannot satisfy newer updater trust requirements. PR #46 — Validation Report Accuracy [Review PR #46](https://github.com/dfeen87/DS-EV/pull/46) Corrected historical Python test reporting to distinguish passing tests from optional extension skips. PR #47 — Research Software Citation [Review PR #47](https://github.com/dfeen87/DS-EV/pull/47) Added CITATION.cff, enabling structured attribution and citation of the research software. PR #48 — README and Evidence Alignment [Review PR #48](https://github.com/dfeen87/DS-EV/pull/48) Aligned public documentation with demonstrated software capabilities, reproducible tests, known limitations, and simulation-only scope. PR #50 — Numerical and Middleware Integrity [Review PR #50](https://github.com/dfeen87/DS-EV/pull/50) Addressed PB-13 through PB-15: finite-energy accounting, coherent configuration and reinitialization, and invalid fallback evidence. Strengthened rejection without partial state mutation. PR #51 — Learning, Rollback, Audit and Recovery [Review PR #51](https://github.com/dfeen87/DS-EV/pull/51) Resolved PB-09 through PB-12 by reinforcing rollback authorization, trust-policy validation, committed-history integrity, audit representations, and accepted regenerative-energy accounting. PR #52 — BEDROCK REFORGED: ENERGY CONTINUITY [Review PR #52](https://github.com/dfeen87/DS-EV/pull/52) Introduced the Energy Continuity engine, bounded physical-transfer records, explicit conservation boundaries, compensated numerical reconciliation, passive BMS/recovery observers, and deterministic simulations. Also aligned overall version metadata to v9.0.0 and corrected nonfinite raw trust-evidence acceptance in the Python AILEE integration. PR #53 — Independent Cross-Boundary & Multi-Interval Validation [Review PR #53](https://github.com/dfeen87/DS-EV/pull/53) Extended the Energy Continuity verification campaign with a dedicated C++ simulation suite examining battery, inverter, motor, and kinetic-energy boundaries. The independent tests challenged conservation residuals, explicit thermal losses, missing energy transfers, duplicate charging contributions, replay protection, session resets, and floating-point edge cases involving subnormal values, 2⁵³, and 10²⁰-joule inventories. The campaign reproduced deliberate inverter and motor imbalances of +5 J and −20 J, respectively, while correctly balancing supported complete examples. It also confirmed an important documented limitation: individual intervals can reconcile successfully even when consecutive storage endpoints disagree. Cross-event continuity remains the integrator's responsibility. Hosted GitHub Actions passed both jobs, including the expanded 23/23 CTest suite and Python regression run (202 passed, one optional extension skip). No production Energy Continuity changes were introduced. The additional findings and reproduction evidence are documented in docs/SIMULATION_VALIDATION_9.0.0.md. Validation and Release Boundaries The release includes regression testing, deterministic energy simulations, numerical adversarial tests, and CI verification. The original four-step Energy Continuity simulation demonstrated zero-joule residuals with 8,000 joules of explicitly modeled dissipation. Additional tests examine cancellation, overflow, rejected evidence, and duplicate accounting. Final test totals, Git statistics, and independent validation conclusions will be updated after PR #53 is reviewed. Energy Continuity is passive and does not assume actuator authority. Its results depend on the completeness, provenance, independence, and physical validity of supplied evidence. Acknowledgments DS-EV is an independently maintained research and engineering project developed by Don Michael Feeney Jr. Special appreciation goes to the AI-assisted engineering tools that contributed throughout this release: ChatGPT (Lex), developed by OpenAI, for architectural discussion, engineering planning, technical interpretation, code-review assistance, and helping translate complex findings into clear documentation. OpenAI Codex, including its SOL coding workflows, for implementation assistance, regression development, numerical hardening, and substantial work across the BEDROCK and Energy Continuity campaigns. Google Jules, for targeted code remediation, independent simulation development, regression testing, and additional engineering review. These tools supported the development process; engineering direction, integration decisions, and release responsibility remain with the project maintainer. Their contributions also illustrate the value of combining human engineering judgment with specialized AI tools while preserving verification, accountability, and clear limitations. Thank you to everyone exploring, testing, studying, and building upon this open-source work. Because sometimes the greatest engineering advancement isn't adding another layer. It's building a foundation strong enough that the next layer finally makes sense. DS-EV v9.0.0 — BEDROCK REFORGED: ENERGY CONTINUITY Preserve the mathematics. Govern the evidence. Reconcile the energy.

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

Microsoft Research Blog Oct 12, 2026

Simulating student learning for better AI tutoring

StudentSim is a research system for evaluating and improving AI tutoring tools before they are tested with learners. It models how individuals may engage with tutors, giving feedback to improve tutor performance across subjects like chess, writing, and mathematics. The post Simulating student learning for better AI tutoring appeared first on Microsoft Research.

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.

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