Skip to content
#software testing Open access

Execution Governance 4.0: From Authorization-Bound Execution to Governed Effect Fabrics

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

Abstract

Execution Governance 4.0 (EG4) extends Execution Governance from authorization-bound execution at an individual effect boundary to the preservation of current, non-expanding, revocable, and independently verifiable authority across a distributed Governed Effect Fabric. EG4 addresses a structural problem in increasingly autonomous and distributed systems: local authentication, authorization, policy compliance, valid credentials, or individually permitted actions do not necessarily establish that the final consequential effect still possesses a coherent and current authority path after authority has been delegated, translated, cached, re-expressed, revoked, or carried across agents, protocols, organizations, versions, services, and physical control points. EG4 does not replace the Six Conditions or the EG3 authorization-bound commitment invariant, and it introduces no seventh live normative condition. Instead, it composes over EG3 with a fabric-level engineering predicate, Fabric Integrity, comprising six properties: Current Authority Path Semantic Non-Expansion Revocation Closure Runtime Continuity Commit-Surface Completeness Witnessed Closure Four primary governance objects structure the architecture: the Governance Contract, Authority Graph, Runtime Witness, and Commit Evidence Package (CEP). Together, they provide a profile-defined way to preserve authority semantics and currentness across heterogeneous execution boundaries while making stale authority, semantic expansion, unresolved conflict, material runtime drift, or unmediated commit paths detectable and capable of failing closed or triggering re-authorization. The central architectural proposition is: “Authority must survive translation without expansion.” EG4 is deliberately broader than AI. The governed object is the consequential external effect, not a model, prompt, reasoning trace, or software agent as such. The architecture is therefore applicable to autonomous workflows, AI agents, programmable finance, software-controlled infrastructure, robotics, IoT, industrial control, and other cyber-physical systems in which distributed capabilities can create real-world consequences. Version 0.3.8 is an evidence-synchronized, prior-art-hardened research-architecture release. It preserves the EG4 architecture semantics established in the earlier v0.3.6 series while incorporating a stronger cumulative evidence programme. The bounded EG4 common core carrying Semantic Non-Expansion, Revocation and live-current-state obligations was externally reproduced on three tester-controlled heterogeneous edge platforms: NVIDIA Jetson Orin Nano (ARM64, Ubuntu 24.04 / ROS 2 Jazzy), Orange Pi 5B (ARM64, Ubuntu 22.04 / ROS 2 Humble), and Raspberry Pi Zero 2 W (32-bit ARMv7, Raspbian Bookworm constrained profile). Across the common tested core, the evidence sets produced materially identical normalized outcomes, including Gate3B TLC PASS (195 generated states, 66 distinct states, depth 8), six intended guard-ablation counterexamples, 37/37 reference-evaluator tests, 32/32 falsification vectors, Gate4A 15/15, and Gate4C 16/16 with dynamic revocation blocked as expected. The release also incorporates ERP-1D v0.1.2, in which one eligible Gate4C release was carried through an authenticated ESP32-S3 enforcement endpoint to a board-local RGB-LED physical effect. All 10 pre-registered HIL vectors passed and the endpoint actuation counter advanced exactly once. The nominal eligible vector produced one visually observed effect, while authority failure, dynamic revocation, exact-effect mutation, independent safety veto, HMAC tamper, replay, expiry, wrong-session, and wrong-target vectors produced no additional actuation. EG4 also provides a machine-readable research seam comprising a candidate EG4-Core v0.1 semantic kernel, Minimal Digital Fabric Profile v0.1, profile-bounded JSON Schemas, a bounded executable counterexample model, an author-controlled reference implementation, conformance tests, an OpenAPI surface, and a version-pinned research endpoint. The prior-art boundary is intentionally conservative. EG4 does not claim invention of authentication, delegation, authorization evidence, authority provenance graphs, governance contracts, complete mediation, least privilege, revocation, semantic interoperability, cryptographic receipts, runtime authorization, or conformance testing in isolation. Related standards and research—including MCP, A2A, WIMSE, OAuth Rich Authorization Requests, Transaction Tokens, SCITT, Microsoft Agent Hooks, Execution-Time Authorization, Proof of Execution, LATTICE, AID-Guard, Quipu and related work—are treated as substrates, adjacent architectures, or prior-art pressure rather than as endorsements of EG. The strongest defensible EG4 claim is therefore not that every component mechanism is new. It is the effect-fabric composition of current rooted authority, semantic non-expansion, descendant revocation closure, runtime continuity, declared commit-surface mediation, exact-effect commitment, and independently checkable closure across heterogeneous consequential action chains. Evidence and maturity boundary: EG4 v0.3.8 is a publication-ready independent research and pre-standardization architecture. The reported results are bounded research evidence. They do not constitute full formal verification of EG4, an independent reimplementation from specification, universal interoperability proof, open-world commit-surface completeness, accredited laboratory validation, functional-safety certification, production assurance, legal authorization, compliance determination, or institutional endorsement.

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

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.

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.

Microsoft Research Blog Aug 12, 2026

MindTopo reveals VLMs’ spatial reasoning abilities

A path, a fence, a knot. MindTopo sets a new benchmark for testing how AI understands topological relationships and highlights new opportunities to strengthen spatial reasoning and planning. The post MindTopo reveals VLMs’ spatial reasoning abilities appeared first on Microsoft Research.

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