Oct 2026· Zenodo (CERN European Organization for Nuclear Research)· 2 citations· 3 references
Abstract
12-slide enterprise architecture deck: Constitutional Core; Bifurcated Governance (probabilistic proposers operate inside a deterministic cage that validates every proposal against invariant contracts before execution); Deterministic Mesh; Four Horsemen benchmark fleet; SDR-1 substrate determinism receipts (checksum 0xc5f88dcf); October roadmap; adversarial-suite risk matrix. Release lineage: deck created September 2026; first public release October 6, 2026 (GitHub, eve of the 60-day Horsemen battery kickoff); this Zenodo DOI stamps the same bytes on October 11, 2026. The October 6 publication edit pass is disclosed on the record: (1) internal watermarks replaced with PUBLIC EDITION markings; (2) the SDR-1 injection claim reworded to receipt-anchored wording so deck precision matches ledger precision; (3) AI-assisted research disclosure + public ledger link added to the closing slide; (4) prototype disclaimer retained. No content changes since. Patent-safe statement: all architecture content is covered by filed provisional applications (64/157,915; 64/119,191; 64/114,746; 64/145,825). No unfiled method material is disclosed; the DCAI-EVT taxonomy and five-step finality method remain drawer-bound pending the follow-on provisional. Dual Mesh Benchmark: NOT MEASURED in this artifact. No comparative mesh, latency, learning, or healing performance claim is made. SDR-1 receipts and SIM-B 100% parity (Sept 29, 2026) are cited as scoped prior results, not re-measured here. AI assistance: deck drafting and assembly were AI-assisted under human direction; the disclosure block on the closing slide is part of the artifact itself. All benchmark data shown is receipted from the public append-only ledger. Research home: DCAI community; portal: DSOS Science; public append-only ledger: four-horsemen. This software is a prototype and is provided for educational and research purposes only. It is not intended for production use, commercial deployment, or safety-critical environments. All systems are experimental and may contain defects on them.
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.· arXiv.org· 727 citations· ⚡54
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.· Empirical Software Engineeri...· 401 citations· ⚡48
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.· Information and Software Tec...· 394 citations· ⚡54
It is proved that any global minimizer of the trajectory balance objective can define a policy that samples exactly from the target distribution, and empirically demonstrate the benefits of the trajectories balance objective for GFlowNet convergence, diversity of generated samples, and robustness to long action sequenc...
Esmeralda S. Whitammer, Moksh Jain, Emmanuel Bengio et al.· Neural Information Processin...· 302 citations· ⚡60