Zusammenfassung
Compliance in AI deployments is usually applied afterwards, through prompt engineering, rather than built into the foundation. This architecture encodes regulatory, governance and ESG requirements as an objective-under-constraints problem, so every specialised agent operates within legally admissible and auditable bounds before any domain work begins.
Introduction
Contemporary consumer-facing artificial intelligence deployments are dominated by large language models (LLMs) and related generative architectures, typically accessed through proprietary API endpoints.(Stanford HAI 2025; OpenAI 2025) In such systems, the generated output itself constitutes the primary product.(Stanford HAI 2025)
Internal optimisation targets coherence, syntactic precision, and surface-level factuality, achieved through prompt engineering, instruction tuning, retrieval-augmented generation (RAG) pipelines, and post-processing moderation.(Schulhoff et al. 2024; Longpre et al. 2023; Ouyang et al. 2022; Lewis et al. 2020; OpenAI 2024) These mechanisms are effective in improving immediate relevance and reliability, particularly where the value of the system is measured by the quality of a single response.(Lewis et al. 2020; Ouyang et al. 2022)
Such output-centric architectures exhibit structural limitations in enterprise-scale, multi-agent systems operating in regulated domains.(National Institute of Standards and Technology 2023)
In consumer deployments, compliance, ethical alignment, and environmental, social, and governance (ESG) considerations are typically applied as non-binding guidelines or post hoc filters rather than embedded constraints.(National Institute of Standards and Technology 2023)
Provider control is exercised primarily through model training choices and prompt manipulation, which provides no systemic assurance that outputs, or the intermediate reasoning steps producing them, comply with procedural, legal, or evidentiary requirements.(European Parliament and Council of the European Union 2024; National Institute of Standards and Technology 2023)
From the provider’s perspective, this optimisation objective can be formalised as the constrained problem in Equation Eq. 1, where the aim is to maximise perceived output quality within bounded constraints on compliance, factual accuracy, user-perceived helpfulness, stylistic acceptability, safety, and latency.
Here, denotes the output text sequence generated by the model in response to the input prompt , with representing the model parameters. The scalar utility function estimates the perceived output quality from the end-user’s perspective. The constraint enforces compliance with provider policies and applicable legal frameworks. Factual correctness is measured by relative to a knowledge base , bounded below by a threshold . Contextual alignment with inferred user intent is expressed as with threshold , while ensures stylistic and rhetorical acceptability above threshold . Safety and reputational risk minimisation are modelled through with threshold , and denotes the total generation latency, constrained by .
Enterprise-grade AI, by contrast, functions as a delegated agent on behalf of an organisation, whether corporate, governmental, medical, or otherwise, and must operate within a normative framework.(Chopra et al. 2018; Wooldridge 2009) In such contexts, accuracy of output is necessary but insufficient for admissibility.(European Parliament and Council of the European Union 2024) All actions and decisions must be bounded by a formally defined objective-under-constraints environment in which compliance, ESG adherence, and procedural validity are structural guarantees rather than aspirational properties.(National Institute of Standards and Technology 2023; European Parliament and Council of the European Union 2024) This mirrors the legal and contractual obligations of human actors, whose conduct is constrained by performance requirements as well as enforceable compliance obligations.(National Institute of Standards and Technology 2023)
Within this frame, generative models, including LLMs, are best understood as modular components within a larger multi-agent architecture, rather than as the defining element of the system.(Wooldridge 2009) The proposed approach comprises two co-dependent layers: a modular, role-specific multi-agent system capable of both persistent and ad hoc committee formation for continuous and event-driven tasks; and a distributed ledger infrastructure, incorporating a directed acyclic graph (DAG) verification layer to deliver low-latency, tamper-evident auditability.(Chopra et al. 2018; Yaga et al. 2018; Baird 2016a) This design is deliberately deployment- and vendor-agnostic, enabling heterogeneous AI modules, generative or otherwise, to be integrated without compromising compliance or scalability.(National Institute of Standards and Technology 2023; Yaga et al. 2018)
Related Work and Research Gap
Multi-Agent Architectures in AI Systems
Multi-agent systems (MAS) have a long history in distributed problem solving, coordination, and planning, with established mechanisms for task allocation and cooperation such as the Contract Net Protocol and cooperative planning pipelines.(Smith 1980; Torreño et al. 2017) Classical accounts describe autonomous, locally rational agents that coordinate through negotiation, commitments, or shared plans to achieve global objectives in heterogeneous environments.(Jennings et al. 1998; Wooldridge 2009) This tradition forms the basis of many contemporary frameworks, which adopt the decomposition of complex objectives into role-specific competencies, local decision making, and explicit protocols for inter-agent communication.(Jennings et al. 1998; Torreño et al. 2017)
Recent advances in large language models (LLMs) have prompted renewed interest in agentic architectures that use LLMs as planning, communication, and tool-use primitives. These support conversational teams and orchestration layers, as shown by frameworks such as AutoGen, which enable conversation-programmed teams of specialised agents, and by role-playing and workflow-based approaches (e.g., CAMEL, MetaGPT), which demonstrate how division of labour and inter-agent critique can improve performance on open-ended tasks.(Wu et al. 2023; Li et al. 2023; Hong et al. 2023) Methodologically related patterns like ReAct integrate chain-of-thought reasoning with action selection, reinforcing tool-using agent designs.(Yao et al. 2023)
Beyond research prototypes, developer toolchains provide agent modules for domain-specific pipelines. For example, LangChain-based agents have been applied in data- and tool-integrating systems such as bilingual real-estate advisory assistants, illustrating the accessibility, but also the variability, of engineering practices in current agent stacks.(Haurum et al. 2024)
Most of these systems are assessed primarily on functional metrics such as task success, sample efficiency, or benchmark scores, with embedded compliance properties rarely enforced at the orchestration layer. This gap is reflected in the creation of dedicated safety and trustworthiness benchmarks for LLM agents, which document frequent policy violations and limited risk-awareness even when task outcomes meet performance targets.(Yuan et al. 2024; Levy et al. 2024) Surveys of LLM-based MAS and of LLM security and privacy similarly characterise the field as performance-driven, with governance and assurance positioned as peripheral rather than architectural concerns.(Li et al. 2024; Yao et al. 2024) These findings motivate the design of architectures in which compliance, procedural validity, and auditability are encoded as binding constraints on inter-agent coordination, rather than implemented through external monitoring after deployment.
Compliance-by-Design in AI
Compliance-by-design, also referred to as regulation-by-design, is embedded in European data protection law through the principle of data protection by design and by default (DPbDD), which requires ex ante technical and organisational measures by controllers (Article 25 GDPR) and is elaborated in the European Data Protection Board’s Guidelines 4/2019.(European Parliament and Council of the European Union 2016; European Data Protection Board 2020) Contemporary AI governance frameworks extend this preventive approach: the EU Artificial Intelligence Act adopts a risk-based regime in which classification and obligations depend on risk level (notably Article 6 and Annex III for high-risk applications), while the NIST AI Risk Management Framework (AI RMF 1.0) structures governance, mapping, measurement, and management functions across the AI lifecycle.(European Parliament and Council of the European Union 2024; National Institute of Standards and Technology 2023)
For high-risk AI systems, the AI Act sets both design-time and run-time requirements that operationalise compliance-by-design. These include a documented, lifecycle risk management system (Article 9); data and data governance controls for training, validation, and testing datasets (Article 10); technical documentation demonstrating conformity (Article 11); logging capabilities for traceability and supervision (Article 12); transparency obligations toward deployers (Article 13); human oversight mechanisms (Article 14); and thresholds for accuracy, robustness, and cybersecurity (Article 15).(European Parliament and Council of the European Union 2024) Conformity is reinforced through conformity assessment procedures (Article 43), post-market monitoring and incident reporting (Articles 72–73), and registration in an EU database for traceability (Articles 49, 71). Together, these measures embed auditability into orchestration rather than treating it as an external control.(European Parliament and Council of the European Union 2024) Complementary standards such as ISO/IEC 42001:2023 (AI management systems) and ISO/IEC 23894:2023 (AI risk management guidance) codify organisational processes that support such embedding at scale.(International Organization for Standardization and International Electrotechnical Commission 2023b, 2023a)
In practice many implementations remain model-centric: compliance mechanisms are attached to single-model pipelines via pre-deployment documentation and post hoc audits, rather than enforced as binding constraints across system orchestration.(Raji et al. 2020; Costanza-Chock et al. 2022) Reporting artefacts such as model cards and datasheets for datasets improve transparency but do not, on their own, guarantee procedural validity under operational conditions or cross-component accountability in complex deployments.(Mitchell et al. 2019; Gebru et al. 2021) Distributed, multi-agent ecosystems amplify these gaps because compliance must propagate consistently across inter-agent communication, task delegation, and decision rights. Current surveys and risk frameworks describe assurance in such contexts as an unresolved socio-technical challenge, reinforcing the need to integrate governance and oversight into orchestration logic rather than relying solely on downstream monitoring.(Yao et al. 2024; National Institute of Standards and Technology 2023)
Distributed Ledger Technology for Verification
Distributed ledger technology (DLT) is widely used to secure data integrity, provenance, and auditability by maintaining append-only, tamper-evident records in adversarial settings.(Yaga et al. 2018; Nakamoto 2008) These guarantees are realised through hash-chaining and authenticated data structures, such as Merkle trees, which enable efficient inclusion and append-only proofs, as demonstrated in transparency-log systems for public auditing.(Laurie et al. 2021; Crosby and Wallach 2009; Tomescu et al. 2019) Enterprise-grade, permissioned platforms such as Hyperledger Fabric extend these primitives with identity management, endorsement policies, and configurable consensus, providing fine-grained access control and verifiable transaction histories.(Androulaki et al. 2018)
Conventional blockchains impose a linear order of blocks, simplifying verification but constraining throughput and latency.(Yaga et al. 2018; Nakamoto 2008) Directed acyclic graph (DAG) ledgers generalise this structure to blockDAGs or transaction DAGs, enabling higher concurrency and, in practice, improved throughput–latency trade-offs.(Silvano and Marcelino 2020; Baird 2016b; Sompolinsky et al. 2021) Peer-reviewed analyses of DAG-based designs—including IOTA’s Tangle, Hashgraph, and GHOSTDAG/PHANTOM—formalise consensus and irreversibility properties while identifying performance regimes relevant to near-real-time verification.(Silvano and Marcelino 2020; Baird 2016b; Sompolinsky et al. 2021)
In AI contexts, DLT has been applied to safeguard dataset lineage, access logs, and model or update provenance, as well as to provide auditable coordination in federated learning (FL) settings.(Kuo et al. 2020; Qu et al. 2022; Özdayi et al. 2020) These applications create tamper-evident trails for coarse-grained artefacts, such as data snapshots, gradient or model updates, and access events. They do not, however, address the fine-grained, low-latency verification of inter-agent messages and decisions required for distributed multi-agent orchestration. Recent work on verifiable ledger databases, such as GlassDB, shows how transparency-log abstractions can deliver efficient inclusion and append-only proofs within transactional workloads, supporting low-latency, tamper-evident verification layers beneath higher-level applications.(Yue et al. 2023)
The literature positions DLT as a robust substrate for evidentiary integrity and for public or consortium-scale auditability, with DAG-based ledgers particularly suited to high event-rate verification. What remains underexplored is the explicit instrumentation of agent-to-agent coordination and delegation decisions with these verifiability guarantees at the orchestration layer of multi-agent AI systems, extending beyond static data and FL update logging.(Qu et al. 2022; Kuo et al. 2020)
ESG Integration in Digital Architectures
ESG requirements in digital infrastructures have been institutionalised primarily through disclosure regimes and reporting standards rather than through runtime control of systems. In the EU, the Corporate Sustainability Reporting Directive (CSRD) mandates comprehensive sustainability disclosures, operationalised via the European Sustainability Reporting Standards (ESRS), which specify topic-level reporting (e.g., ESRS E1 on climate) and alignment with established greenhouse gas (GHG) accounting practices.(European Parliament and Council 2022; European Commission 2023; EFRAG 2023) In parallel, AI governance proposals emphasise sustainability as a design value, yet the technical literature consistently reports that energy and carbon metrics are underreported or appended post hoc, rather than embedded as binding operational constraints.(Schwartz et al. 2020; Strubell et al. 2019; Henderson et al. 2020)
For AI workloads, environmental impacts vary by model class, training versus inference phase, facility efficiency, hardware choice, geography, and time-varying grid carbon intensity.(Patterson et al. 2021; Dodge et al. 2022) Empirical studies on frontier-scale models, such as BLOOM 176B, show that adopting a full life-cycle perspective materially alters footprint estimates compared to training-only views, underscoring the importance of inventory boundaries for any architecture-level constraint.(Luccioni et al. 2023) These findings strengthen calls to treat emissions and efficiency as first-class performance criteria rather than externalities assessed after deployment.(Schwartz et al. 2020)
Standardised metrics already translate facility- and product-level sustainability attributes into machine-readable constraints. For data centres, the ISO/IEC 30134 series defines key performance indicators such as Power Usage Effectiveness (PUE), Energy Reuse Factor (ERF), and Carbon Usage Effectiveness (CUE), enabling comparison and thresholding of energy efficiency, energy reuse, and operational intensity during use-phase operations.(ISO/IEC 2016, 2021, 2022) At product and organisational levels, ISO 14067 specifies principles for quantifying a product carbon footprint, while the Greenhouse Gas Protocol’s Corporate Standard governs Scope 1–3 accounting, providing a bridge between operational telemetry and corporate reporting baselines.(ISO 2018; World Resources Institute and World Business Council for Sustainable Development 2015) ESRS E1 requires disclosure of Scope 1 and Scope 2 emissions and material Scope 3 categories, with guidance to draw on the GHG Protocol (including Scope 2 Guidance) and to include upstream services such as cloud computing and data centre usage under Scope 3, linking digital procurement to reportable inventories.(EFRAG 2023)
In most AI systems, environmental metrics are recorded for transparency or for post-deployment optimisation (e.g., shifting regions or times to lower marginal grid intensity) rather than enforced as ex ante constraints at the orchestration layer.(Dodge et al. 2022; Henderson et al. 2020) A compliance-first multi-agent architecture can reverse this pattern by: (i) parameterising tasks with explicit environmental budgets, such as caps on energy use or CUE-derived ; (ii) binding scheduler decisions to standards-aligned telemetry, including PUE, ERF, CUE, and ISO 14067-compliant product footprints; and (iii) recording allocations and outcomes for auditability and ESRS-aligned reporting. In such a model, ESG becomes a set of machine-enforceable constraints shaping planning, placement, and execution pathways in real time.(Schwartz et al. 2020; ISO/IEC 2022; EFRAG 2023)
Identified Research Gap
Across the surveyed strands of multi-agent orchestration, compliance-by-design, ledger-based verification, and ESG governance, the literature shows substantial progress in isolation. What is missing is an integrated reference architecture that (i) encodes regulatory and assurance obligations as binding orchestration constraints for multi-agent coordination, (ii) instruments agent-to-agent interactions with tamper-evident, low-latency verification, and (iii) operationalises ESG targets as run-time budget constraints rather than retrospective disclosures.
First, contemporary LLM-based multi-agent systems and orchestration frameworks emphasise task performance, division of labour, and communication protocols, while governance and assurance remain secondary concerns or external monitoring functions.(Li et al. 2024; Yao et al. 2024) Surveys of LLM security and privacy report persistent gaps in policy adherence, traceability, and cross-component accountability in agentic settings, indicating the absence of orchestration-layer guarantees.(Yao et al. 2024)
Second, compliance frameworks codify obligations such as lifecycle risk management, logging, technical documentation, and human oversight, yet they do not specify how such requirements can be expressed as machine-enforceable constraints governing inter-agent delegation, voting, and escalation within MAS.(European Parliament and Council of the European Union 2024; National Institute of Standards and Technology 2023) This leaves a design space between policy intent and system realisation, where orchestration semantics rarely bind compliance artefacts, including risk registers, logs, and conformity documentation, to the decision rights and protocols of interacting agents.(National Institute of Standards and Technology 2023)
Third, distributed ledgers provide tamper-evident auditability, DAG-based designs improve throughput and latency characteristics, and verifiable ledgers offer efficient inclusion proofs. Existing AI integrations, however, focus on dataset or model provenance and federated learning update trails rather than on fine-grained verification of agent-to-agent messages and decisions in real time.(Silvano and Marcelino 2020; Baird 2016b; Sompolinsky et al. 2021; Yue et al. 2023; Qu et al. 2022) As a result, evidentiary integrity is typically attached to coarse events, such as data access or model versioning, rather than to the internal coordination steps that determine enterprise actions.(Qu et al. 2022; Yue et al. 2023)
Finally, ESG standards and reporting regimes define metrics and disclosures, such as CUE for data centres and ESRS E1 for Scope 1–3, yet they are rarely embedded into schedulers, planners, or resource allocators as enforceable budgets or thresholds that shape agent behaviour at run time.(ISO/IEC 2022; EFRAG 2023) The prevailing pattern is post-deployment measurement and reporting, not ex ante constraint satisfaction within the operational fabric of AI systems.(EFRAG 2023)
The gap is the absence of an enterprise-grade, domain- and vendor-agnostic orchestration layer for multi-agent AI that encodes compliance obligations and ESG constraints as structural properties, and couples these with DAG-backed, tamper-evident verification of inter-agent coordination to achieve admissible, auditable operations at scale.
Objective and Contribution
The objective of this work is to define and operationalise a compliance-first architecture for enterprise multi-agent AI in which regulatory, governance, and ESG obligations function as binding orchestration primitives. The architecture is domain-, deployment-, and vendor-agnostic, positioning generative models as interchangeable components within a governed multi-agent fabric. A role-specific agent layer supports both persistent and ad hoc committees, while a verification-and-governance layer enforces policies, captures evidence, and integrates a directed acyclic graph (DAG) verification substrate for tamper-evident, low-latency auditability. ESG requirements are embedded as run-time budgets, with scheduling and placement decisions bound to standards-aligned telemetry and recorded for auditability. The design preserves operational neutrality across cloud, on-premise, and edge deployments, and incorporates assurance mechanisms for human oversight, incident response, and procedural validity.
The contributions of this work are, first, a reference architecture and orchestration semantics that bind decision rights, escalation paths, and separation-of-duties to machine-enforceable constraints. Second, a DAG-based verification layer that records inter-agent coordination at message level with inclusion proofs and evidentiary retention policies. Third, an ESG-aware scheduler that treats environmental targets as binding optimisation constraints, exposing trade-offs between utility, latency, and resource impact. Fourth, a deployment blueprint and threat model addressing trust zones, policy evasion, and evidence manipulation. Finally, the paper outlines cross-domain applicability through healthcare triage, public procurement, and incident management scenarios, and identifies open research directions in formal policy verification, cross-organisation committee incentives, and performance–auditability trade-offs at scale.
Research
Organisations can be broadly classified into two categories: profit-oriented and mission-oriented. Profit-oriented entities focus on maximising financial performance, while mission-oriented entities, such as governmental bodies, healthcare providers, educational institutions, and non-governmental organisations, prioritise service delivery, public welfare, or other non-financial mandates. Despite these differences, both operate under bounded resources and are subject to regulatory, governance, and operational constraints. This organisational taxonomy provides a useful lens for framing optimisation problems in enterprise AI design.
In its most general form, the operational objective of an organisation can be expressed as the joint maximisation of utility and viability, where viability is understood as the sustained capacity of the organisation to operate, adapt, and meet its objectives under changing internal and external conditions, as shown in Equation Eq. 2:
When applied to profit-oriented organisations, this formulation specialises to Equation Eq. 3:
For mission-oriented organisations, the same structure yields Equation Eq. 4:
This distinction matters because the underlying objectives shape both the optimisation target and the permissible coordination and competition patterns among agents. Profit-oriented entities often operate in competitive markets where strategic advantage depends on outperforming or displacing rivals, aligning with adversarial or non-cooperative game-theoretic models. Mission-oriented organisations, by contrast, frequently operate in settings where cooperation and information sharing improve collective outcomes, such as public health, safety, or environmental protection. In these domains, cooperative game theory and equilibrium concepts such as the Nash equilibrium can support joint optimisation rather than zero-sum competition. In profit-driven AI systems, the practical relevance of such equilibria is diminished, as design incentives typically favour unilateral maximisation over collaborative stability. Within this taxonomy, enterprise AI orchestration in regulated multi-agent environments can be seen as a domain-specific instance of the general organisational formulations in Equations Eq. 2–Eq. 4. Regardless of whether the organisation is profit- or mission-oriented, the orchestration problem differs fundamentally from the consumer-facing formulation in Equation Eq. 1. Rather than optimising the quality of a single model output, the aim is to maximise organisational utility while meeting a set of normative, procedural, evidentiary, ESG, and safety constraints that bind all agents in the system. This enterprise-specific objective is formalised in Equation Eq. 5:
Here, denotes an orchestration policy mapping goals to coordinated agent actions, with representing system-wide parameters and configuration. The function captures organisational utility, including task success, resource efficiency, and mission alignment. Each constraint returns if and only if it is satisfied, meaning that equations of the form represent requirements that must be met for the policy to be admissible. enforces legal and regulatory compliance; ensures procedural validity, including separation-of-duties and escalation rules; measures ESG performance against a minimum threshold ; guarantees evidentiary completeness and auditability; enforces operational safety and risk minimisation with threshold ; is the end-to-end execution latency, bounded by ; and covers any additional enterprise policies, strategic objectives, or operational constraints. The organisational taxonomy outlined above defines the admissible objectives and constraints and also influences the strategic interactions embedded in the orchestration layer. Real-world organisations rarely operate in a state of pure competition or pure cooperation. Mission-oriented hospitals may compete for funding, talent, or innovation leadership, while profit-oriented enterprises may cooperate in areas such as industry safety standards, shared infrastructure, or joint lobbying.
To capture this variability, we introduce a tunable cooperation–competition continuum as a first-class orchestration parameter, formalised in Equation Eq. 6. Let denote the degree of cooperative strategic alignment across the multi-agent system:
This formulation supports orchestration policies ranging from purely competitive () to purely cooperative (), with intermediate values representing blended strategies. For example, a public administration without a competitive mandate may operate with close to , while a mission-oriented hospital could set to reflect cooperative public health coordination alongside selective competition for scarce resources. A profit-oriented enterprise might operate near but temporarily increase it in contexts where cooperation improves expected payoffs. Embedding at the orchestration level makes the cooperative–competitive balance an explicit, governed parameter rather than an emergent property of ad hoc agent design. It also enables scenario planning in which the system can simulate or execute strategic shifts. For instance, an organisation could operate with in a stable supply chain, but reduce it to when market volatility calls for stronger competitive positioning. This capability provides strategic agility and preserves an auditable record of the decision logic behind changes in inter-agent interaction patterns.
Building on the cooperation–competition continuum, we extend the framework to allow to vary with context rather than remain fixed across all scenarios. Organisations may define a baseline profile, for example to reflect a 30% cooperative and 70% competitive stance, while retaining the ability to override this default when circumstances change. In a stable market, the baseline may be sufficient. During a critical competitive challenge the system could shift to for a fully competitive posture. In a joint-response emergency the system could move to to maximise coordination and shared resource use.
The adaptive parameter is expressed as a context-driven function in Equation Eq. 7, which extends the formulation in Equation Eq. 6:
This adaptive formulation keeps multi-agent reasoning and decision outputs aligned with situational demands, echoing patterns seen in social and biological systems. In nature, cooperation is often extended to in-group members, while competition or defensive actions are directed toward external threats. Protecting community members is a cooperative imperative, whereas repelling an intruder may require aggressive and competitive tactics. In organisational terms, applying a collaborative strategy to a hostile market entrant risks undermining viability, while treating a trusted supply chain partner as an adversary can erode long-term utility. The proposed approach enables this flexibility without presupposing a single correct posture or enforcing a fixed set of cooperative or competitive behaviours. It leaves the choice to the orchestration logic and the governing policies, which can interpret the operational context in real time and select the most suitable balance. This preserves adaptability as a design property, allowing the system to respond to complex or ambiguous situations without being constrained by rigid strategic assumptions.
Orchestration Architecture with Context-Adaptive Strategic Parameters
We extend the enterprise orchestration formulation in Equation Eq. 5 by embedding the cooperation–competition continuum from Equation Eq. 6 together with its context-driven adaptation from Equation Eq. 7. The resulting objective is given in Equation Eq. 8, where the cooperation weight varies over time in response to observed conditions:
Here, is obtained from the prevailing situational context through the mapping , where denotes the organisation’s governing policies and contains system-level parameters and thresholds. Values of close to one direct orchestration towards cooperative modes, with emphasis on resource pooling, mutual aid, and joint optimisation. Values near zero shift the balance toward competitive modes, prioritising market capture, strategic positioning, or adversarial advantage. Intermediate values produce blended regimes in which cooperation and competition are weighted according to the current context.
The mapping supports strategic shifts in response to market signals, environmental changes, or operational events. A dedicated Context Monitor ingests telemetry, market indicators, ESG metrics, and incident data to update . Each update is checked by the Policy Store and Rule Engine, transformed into enforceable constraints by the Constraint Compiler, and passed through the Compliance Verification stage. Pre-execution outputs may be reviewed with human oversight before passing the Execution Gate.
Chain-of-Thought scopes, variable states, and decision records are notarised in the DAG Verification Layer alongside event logs and inclusion proofs. This ensures that policy compliance, reproducibility, and auditability are preserved. The Audit Layer offers retrieval and simulation capabilities through a dedicated query API. The layered orchestration architecture in Figure 1 integrates these elements.
While existing multi-agent orchestration frameworks tend to address coordination, optimisation, or compliance as separate concerns, few combine them in a single architecture that treats the cooperation–competition balance as a governed, context-adaptive parameter. The design in Figure 1 embeds directly into the decision loop, applies compliance checks before execution, and records all strategic changes with verifiable provenance. This integration closes two persistent gaps in the literature. The first is the absence of a mechanism for adjusting inter-agent posture along a continuum from fully cooperative to fully competitive in response to contextual triggers. The second is the lack of a transparent link between those triggers, the orchestration decisions they influence, and their eventual operational outcomes. Addressing both allows enterprise-scale multi-agent systems to remain strategically agile while demonstrably aligned with long-term viability objectives.
A Directed Acyclic Graph (DAG) is adopted as the notarisation substrate to avoid the latency bottlenecks inherent in block-generation intervals of conventional blockchains. For audit logs that are technical rather than financial, the confirmation delays and transaction fees typical of Layer 1 financial ledgers are poorly aligned with operational requirements. In the proposed model, events are minted into a Layer 2 DAG with negligible or zero transaction costs, allowing high-frequency, low-latency notarisation of decisions, constraint checks, and contextual triggers. Where minting costs are non-zero, a game-theoretic incentive design can be applied to favour comprehensive notarisation while retaining the ability to omit non-critical events. Let be the set of events, the minting cost of event , and its expected verification or audit value. The resulting notarisation preference function is given in Equation Eq. 9:
In a dedicated DAG system, the vectorisation of smart contracts and stored hashes is proposed to enable AI agents to parse and reason over notarised content with greater efficiency and security. Representing contract logic and state proofs as vectorised structures allows faster retrieval and interpretation while ensuring compatibility with embedding-based reasoning systems. This can reduce parsing overhead and lower the risk of errors arising from ambiguous or inconsistent contract encoding. The feasibility of this approach, along with its performance trade-offs and security implications, must be validated through rigorous testing in realistic deployment environments. We regard this as a priority direction for future research, with the potential to strengthen the integration between notarisation layers and AI orchestration systems.
Human Oversight as a Governance Primitive
Human oversight is embedded in the orchestration framework as a governance primitive, spanning the full operational lifecycle from policy definition to post-execution audit. In the proposed architecture, human actors interact with the system at points chosen for their alignment with governance objectives and risk profiles.
At the policy and strategy level, human decision-makers establish baseline rules, operational constraints, and strategic priorities, including the cooperation–competition balance parameter . While may be dynamically adjusted by the system in response to situational data , human operators retain the authority to refine or override these values when contextual insight exceeds the agents’ situational model. In volatile markets or emergent public health crises, for instance, a human may recalibrate the cooperative–competitive weighting on the basis of information not yet incorporated into the system state.
At the pre-execution stage, humans participate in compliance validation for high-impact or high-risk actions. This may involve reviewing an output draft from the orchestration layer, with compliance agents—human or AI—verifying adherence to regulatory, procedural, and ESG constraints before execution. Human reviewers act as an adaptive safeguard, addressing edge cases, interpretative ambiguities, or ethical considerations that fall outside the scope of formalised constraints.
At the audit and review stage, human oversight complements AI-based auditing. Post-execution logs notarised in the DAG layer are accessible for forensic review, simulation replay, and regulatory reporting. High-volume routine verification may be handled algorithmically, whereas exceptional cases, disputed actions, or policy updates can trigger human-led audits. This dual-mode design combines the speed and coverage of automated verification with the interpretability and accountability of human review.
Integrating human oversight at multiple stages allows the system to incorporate human intuition, ethical reasoning, and domain expertise without diminishing the autonomy and scalability of the multi-agent fabric. Oversight frequency and depth can be adapted through scenario policies, increasing human involvement during periods of regulatory uncertainty or heightened reputational risk. By formalising oversight within the orchestration semantics rather than treating it as an ad hoc intervention, the architecture ensures that human judgement remains a governed, auditable, and strategically aligned element of system operation.
Discussion and Theoretical Implications
The proposed architecture integrates a multi-agent orchestration framework with a context-adaptive cooperation–competition continuum, notarisation through a Layer 2 DAG, and governed human oversight. While these components have each been examined in prior work, their combination into a unified, policy-driven enterprise AI system represents a shift in both theoretical framing and operational design.
From a theoretical perspective, the cooperation–competition parameter moves beyond static game-theoretic formulations toward a dynamic, context-aware representation. This formulation recognises that organisational strategy is not fixed along the competitive–cooperative axis, but evolves in response to market dynamics, environmental triggers, and internal strategic priorities. Embedding as a tunable orchestration parameter brings the model closer to observed organisational behaviour in both profit-oriented and mission-oriented contexts. The continuum also creates a formal bridge between strategic management theory and multi-agent system design, supporting scenario modelling in which competitive advantage and cooperative stability are jointly optimised.
The use of a Layer 2 DAG as the notarisation substrate introduces additional theoretical considerations. It reframes distributed ledger technology in AI governance from a financial transaction ledger to a high-frequency, low-latency record of decision processes and constraint evaluations. This shift positions the ledger as a strategic memory that enables replay, forensic analysis, and policy refinement without the performance costs of Layer 1 blockchains. The game-theoretic cost–value function for notarisation in Equation Eq. 9 formalises the trade-off between completeness and operational expenditure, allowing preferred behaviours to be embedded directly into the economic logic of the logging mechanism.
Embedding human oversight across multiple orchestration stages also carries theoretical significance. By defining human interaction points at policy formulation, pre-execution validation, and post-execution audit, the architecture treats oversight as a structural governance mechanism rather than a reactive safeguard. This ensures that human intervention is both traceable and integrated with operational constraints, supporting a hybrid governance model in which ethical reasoning and domain expertise complement algorithmic scale and consistency.
Taken together, the architecture operationalises concepts that have often been addressed separately in AI research: strategic adaptability, distributed trust infrastructure, and governed human–AI collaboration. The theoretical contribution lies in positioning these elements as interdependent components of an enterprise-grade, multi-agent AI system. This perspective offers new avenues for research on adaptive game-theoretic strategies, ledger-augmented governance mechanisms, and empirical studies of human oversight in complex socio-technical environments.
Limitations and Future Research
The proposed architecture offers a coherent framework for enterprise-grade multi-agent AI orchestration, yet several limitations remain that merit further investigation.
The cooperation–competition continuum parameter is theoretically well-founded but has not been empirically validated across heterogeneous organisational settings. Robust calibration of will require longitudinal studies and controlled simulation experiments to test its stability, responsiveness, and resilience to strategic manipulation. The behavioural effects of abrupt adjustments in high-stakes domains such as emergency healthcare or volatile financial markets remain largely unexplored.
The Layer 2 DAG notarisation mechanism addresses latency and transaction cost constraints, but introduces its own operational trade-offs. The cost–value formulation in Equation Eq. 9 presumes accurate estimation of and a stable cost-sensitivity parameter . In practice, both are likely to vary with shifting priorities, governance changes, and external pressures. Future work should examine adaptive strategies for tuning , as well as the implications of partial notarisation on the completeness and reliability of forensic records. The proposal to vectorise smart contracts and hashed proofs for AI-native access also requires targeted benchmarking to assess retrieval speed, parsing accuracy, and security performance under realistic deployment loads.
Human oversight, although structurally embedded at multiple orchestration stages, has not yet been assessed in terms of cognitive demand and process latency. Without careful design, oversight points could become operational bottlenecks when the complexity or frequency of agent actions exceeds feasible review capacity. A promising direction is the development of hybrid audit workflows that combine AI-assisted triage with selective human review, preserving both scalability and accountability.
Interoperability with existing enterprise systems and regulatory environments is another open challenge. Cross-layer anchoring strategies, jurisdiction-specific compliance rules, and sector-calibrated ESG thresholds will likely require domain-specific tailoring. These factors are critical for adoption in regulated industries and for ensuring cross-border operational validity.