Skip to content
#software testing Open access

spark-membrane: a fail-closed console that orchestrates pinned OES repositories without merging them

Oct 2026 · Zenodo (CERN European Organization for Nuclear Research) · 1 citation · 4 references

Abstract

spark-membrane is an offline, standard-library Python console that audits SYNTHETIC native 32-channel frames against the existing Spark AI NLP OES repositories, pinned by commit SHA and never copied or merged. Small labelled reference re-implementations are tested against outputs of the pinned upstream code. Read first. On the locked NASA SMAP/MSL protocol, OES32 did not meet its pre-stated success criterion (oes-resilience v0.5.0). On the oes-telemetry-bench synthetic held-out set, max-abs matched OES32 (6/7) with fewer false alarms (11.54/h vs 23.08/h). The multi-quantum-oes stress evaluation found no demonstrated advantage. oes32-hls synthesis and the qldpc_decoder_cpp kernel are UNRUN. In its own seed-42 demo the gate accepts a slow drift that only the advisory EWMA/CUSUM detect. What it does. A T=0 audit accepts a frame only if the protocol hash, the normative residual, the oes32_engine Profile A sidecar and the weighted score all pass. Max-abs, EWMA and CUSUM are advisory; EWMA and CUSUM are calibrated on a separate event-free stream and restart after alarms. The two OES-32 formulas are never blended. The console names the failing engine and index and reports engine disagreement (7 of 40 frames for seed 42). A seeded, protocol-capped one-index explorer (new code, inspired by an external dual-engine idea) reports REPAIRED_IN_SIM or LATCH_HELD in simulation only. A capability gate admits nothing on role policy alone and verifies Ed25519 capabilities with an optional extra. Runs are hash-chained (measurement-trail format), rendered as an evidence passport, and passed through a claims gate. v0.2.0. Hardening after an internal audit: the claims gate normalises Unicode and refuses paraphrased, look-alike, zero-width and line-split overclaims, binds labels and sources; the trail rejects backwards timestamps and non-integer fields and is anchored (record count and head) so truncation is detected; every trail payload digest is recomputed from the published files; and the capability gate rejects small-order and non-canonical Ed25519 keys and signature R values (the same fix was made upstream in oes32-membrane-shield). Seed-42 verdict counts are unchanged. Limits. Everything is SYNTHETIC classical simulation, and every threshold is an UNCALIBRATED placeholder (docs/PROTOCOL.md). Not a medical device, not control software, not sensor fusion; no field-performance or superiority claims; it makes no quantum, QEC, consciousness, medical or gravity claims.

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.