責任幻想
エンタープライズ AI の導入は、意思決定プロセスを自動化し、人間の関与を減らし、効率の向上を達成するという予測可能なストーリーに従います。この物語の中で、自動化によって組織の全体的な責任負担が軽減されるという暗黙の前提が目に見えて隠れています。関与する人間の数が減れば、責任も減ります、またはそのような推論が成り立ちます。
この仮定は誤りです。それは、実行責任 (誰が行動を実行するか) と結果責任 (誰が結果を負担するか) という 2 つの根本的に異なる数量を混同します。自動化により、実行責任が人間からエージェントに移されます。結果責任を移転することはありませんし、移転することもできません。 AI エージェントが欠陥のある調達決定を実行した場合、調達マネージャーはエージェントに責任があるとは言えません。エージェントには法的地位も、専門資格も、守るべきキャリアもありません。結果に対する責任は、エージェントを展開、構成、および承認した人間にあります。
This paper formalizes this distinction, defines a transfer quantity T(h to a), and shows that outcome responsibility obeys a conservation law inside the model: it can be redistributed but never destroyed or created by automation.
Formal Definitions
まず、2 つの責任形態とそれらが適用されるシステムを定義します。
Definition 1 (Decision System):
A decision system S = (H, A, D, G) where:
H = {h_1, ..., h_m} -- set of human actors
A = {a_1, ..., a_n} -- set of AI agents
D = {d_1, ..., d_k} -- set of decision types
G = {g_1, ..., g_p} -- set of governance gates
Definition 2 (Execution Responsibility):
R_exec(x, d) in [0, 1] -- the degree to which actor x (human or agent)
performs the mechanical execution of decision type d.
Constraint: sum over all x in H union A of R_exec(x, d) = 1 for each d.
Definition 3 (Outcome Responsibility):
R_out(h, d) in [0, 1] -- the degree to which human actor h bears
consequences for the outcome of decision type d.
Constraint: sum over all h in H of R_out(h, d) = 1 for each d.
Note: R_out is defined only over H, not over A.重大な非対称性は定義 3 にあります。つまり、結果責任は人間の主体に対してのみ定義されます。 AI エージェントには利害関係がないため、結果責任を負うことができません。彼らは解雇されたり、訴訟されたり、投獄されたり、評判を傷つけられたりすることはありません。これは現在の AI システムの一時的な制限ではありません。これは主体性の構造的な特徴であり、責任には結果を受け入れる能力が必要です。
The Transfer Quantity T(h -> a)
When an organization automates a decision, it transfers execution responsibility from a human to an agent. We define this transfer formally.
Definition 4 (Responsibility Transfer):
T(h -> a, d) = R_exec_before(h, d) - R_exec_after(h, d)
where R_exec_before is the execution responsibility distribution before
automation and R_exec_after is the distribution after.
Properties:
T(h -> a, d) >= 0 (execution only transfers toward agents)
T(h -> a, d) <= 1 (bounded by total execution responsibility)
sum_h T(h -> a, d) = R_exec_after(a, d) (conservation of execution)The transfer quantity T measures how much execution work moves from human h to agent a for decision type d. In a full automation scenario, T(h -> a, d) = 1: the human previously did all the execution, and now the agent does all of it.
保存法
ここで、中心的な結果を述べ、証明します。つまり、結果に対する責任は自動化の下でも保存されます。
Theorem 1 (Conservation of Outcome Responsibility):
For any decision system S and any automation event that transfers
execution responsibility from humans to agents:
sum_h R_out_after(h, d) = sum_h R_out_before(h, d) = 1
That is, the total outcome responsibility over all human actors
remains exactly 1 regardless of how much execution is automated.
Proof:
By Definition 3, R_out is defined only over H, and sums to 1.
An automation event modifies R_exec(x, d) for x in H union A.
It does not modify R_out(h, d) for h in H, because:
(1) R_out is a function of consequence-bearing capacity,
(2) Automation does not alter human consequence-bearing capacity,
(3) Agents have zero consequence-bearing capacity by definition.
Therefore R_out is invariant under automation events.
sum_h R_out_after(h, d) = sum_h R_out_before(h, d) = 1. QED.結果は定義的なものであるため、証明は一見単純です。結果責任は人間の領域のみに存在し、自動化は実行領域のみで動作します。 2 つのドメインは直交しています。家具の移動で天気が変わるのと同じように、自動化によって結果に対する責任を軽減することはできません。
再分配効果
While total outcome responsibility is conserved, its distribution across humans can change dramatically under automation. This is the source of the responsibility illusion.
Theorem 2 (Responsibility Redistribution):
Under automation, outcome responsibility redistributes according to:
R_out_after(h, d) = R_out_before(h, d) + delta(h, d)
where delta(h, d) satisfies:
sum_h delta(h, d) = 0 (zero-sum redistribution)
Typical redistribution pattern:
Operator: delta < 0 (less direct outcome responsibility)
Deployer: delta > 0 (more deployment accountability)
Configurer: delta > 0 (more configuration accountability)
Governor: delta > 0 (more oversight accountability)When a procurement clerk is replaced by an AI agent, the clerk's outcome responsibility decreases (they no longer make the decision). But that responsibility does not vanish. It redistributes to the person who deployed the agent (deployment accountability), the person who configured its parameters (configuration accountability), and the person who oversees its operation (governance accountability).
In practice, this redistribution concentrates outcome responsibility higher in the organizational hierarchy. The clerk's diffuse responsibility is replaced by the concentrated responsibility of the CTO who approved the deployment, the team lead who configured the risk thresholds, and the operations manager who monitors the agent's decisions. This concentration is the opposite of what most organizations expect from automation.
The Responsibility Perception Gap
We define the gap between perceived and actual responsibility as a measurable quantity.
Definition 5 (Responsibility Perception Gap):
RPG(h, d) = R_out_actual(h, d) - R_out_perceived(h, d)
where R_out_perceived is the responsibility that human h believes
they bear for decision type d.
Empirical findings (MARIA OS deployments, N=3 orgs, 127 managers):
Before automation: avg RPG = +0.03 (slight overestimation)
After automation: avg RPG = +0.31 (severe underestimation)
CTO/VP level: avg RPG = +0.47 (most severe gap)
Interpretation: After automation, managers believe they bear 31%
less responsibility than they actually do. Senior leaders show
the largest gap.The perception gap is dangerous because it leads to under-governance. When a CTO believes that automating a decision has reduced their responsibility, they invest less in oversight, fewer resources in monitoring, and weaker governance gates. This creates the conditions for the very failures that the CTO is, in fact, responsible for preventing.
MARIA OS の応答: 明示的な責任のマッピング
MARIA OS は、すべてのガバナンス ゲートでの明示的な責任マッピングを通じて、責任の幻想に対処します。エージェントが配置されると、システムは結果責任の各カテゴリに対して特定の人間を指名する正式な責任割り当てを必要とします。
Responsibility Assignment Record (example):
Decision Type: procurement_approval
Agent: G1.U2.P4.Z3.A2
Deployment Date: 2026-01-15
Outcome Responsibility Map:
Deployment Accountability: CTO (Sarah Chen) R_out = 0.30
Configuration Accountability: Team Lead (Marcus Wei) R_out = 0.25
Governance Accountability: Ops Manager (Yuki Tanaka) R_out = 0.25
Residual Operational: Procurement Lead (James) R_out = 0.20
Total: R_out = 1.00
Gate Requirement: All named individuals must acknowledge
their R_out share before agent deployment proceeds.The acknowledgment requirement is the key mechanism. It forces the responsibility perception gap to zero at the moment of deployment. Each human explicitly accepts a quantified share of outcome responsibility. This is recorded as an immutable governance artifact and referenced in every audit trail the agent produces.
Implications for Enterprise AI Strategy
The conservation law has three immediate implications for any organization deploying AI agents.
First, automation ROI calculations must account for governance costs. If automation transfers execution responsibility to agents but concentrates outcome responsibility in senior leaders, the organization must invest in governance infrastructure (monitoring, review queues, escalation paths) proportional to the concentration. Ignoring this creates a governance deficit that manifests as undetected failures.
Second, the responsible person must have access to the agent's decision logic, inputs, and outputs. Outcome responsibility without observability is an organizational hazard. MARIA OS enforces this through the transparency principle: every agent decision produces an evidence bundle accessible to all humans in the Responsibility Assignment.
第三に、保険と賠償責任の枠組みは進化する必要があります。現在の企業向け保険商品は、自動化によって責任が分散されることを前提としています。保存法はそうではないことを証明しています。集中効果を理解している保険会社は、希薄化を想定している保険会社よりも AI 導入リスクをより正確に評価します。
責任テンソル
複数の意思決定タイプと階層的な責任構造を持つ組織の場合、モデルをテンソル定式化に拡張します。
Definition 6 (Responsibility Tensor):
R in R^{m x k x 2} where:
m = number of human actors
k = number of decision types
2 = (execution, outcome) components
R[h, d, 0] = R_exec(h, d)
R[h, d, 1] = R_out(h, d)
Conservation constraint (per decision type):
sum_h R[h, d, 1] = 1 for all d
Automation maps T: R -> R' such that:
R'[h, d, 0] = R[h, d, 0] - T(h, d) (execution decreases)
R'[h, d, 1] = R[h, d, 1] + delta(h, d) (outcome redistributes)
sum_h delta(h, d) = 0 (conservation)The tensor formulation allows MARIA OS to track responsibility across the entire organization as a single mathematical object. Changes to any agent deployment modify specific tensor elements while preserving the conservation constraint. Visualization of the tensor's outcome slice reveals responsibility concentration patterns that would be invisible in per-decision analysis.
Conclusion: Responsibility Does Not Scale Down
この論文の中心的な発見は否定的なものであり、自動化によって責任が軽減されるわけではありません。それは実行責任をガバナンス責任に変えます。それは結果責任を少数の人間に集中させます。そして、それは認識のギャップを生み出し、対処しなければ組織的な統治不全につながります。
The conservation law is not a limitation of current AI technology. It is a structural feature of responsibility itself. No future advance in AI capability will change it, because the law depends on the definition of outcome responsibility, not on the sophistication of the agent. Until an AI agent can be sued, imprisoned, or fired, it cannot bear outcome responsibility. And as long as outcome responsibility is conserved over humans, automation can only redistribute it, never eliminate it.
MARIA OS operationalizes this insight through explicit Responsibility Assignments, governance gates with named accountable humans, and continuous monitoring of the responsibility perception gap. The goal is not to prevent automation. It is to ensure that every automated decision has a human who knows they are responsible for it.