The Law · The Index · The Practice
Read in sequence, or enter at any point. Each document stands alone. Together they form a complete framework for deciding what may safely be delegated to machine intelligence — and what may not.
Names the single governing rule. Defines what delegation must not do. Establishes the three dimensions of readiness.
Operationalises the law into a non-compensatory index. Each dimension must hold independently. Failure in any one fails the whole.
Four grounded examples — scheduling, strategy, defensive automation, and norm enforcement — showing the framework applied to real decisions.
Until recently, this question did not exist. Machines executed instructions. Humans decided. That boundary is gone.
Reasoning itself can now be performed by machines. At speed. At scale. Without fatigue.
This creates a new problem. Delegation is no longer a technical choice. It is a structural one.
History shows that systems do not fail because they adopt new power. They fail because they delegate without a governing rule.
This document names that rule.
A decision may be delegated to machine intelligence if and only if doing so does not degrade the integrity of the system over time.
Progress is temporary. The system decays at a pace that may not be visible until reversal is impossible.
Progress compounds. Scale strengthens the system instead of hollowing it out.
Sometimes a decision should never have been delegated. Sometimes it works at first, then collapses as reliance spreads. Sometimes it succeeds locally while corroding the system quietly.
These failures are not moral. They are structural. The law exists to surface them before delegation becomes irreversible.
Readiness has three independent dimensions. Strength in one does not compensate for weakness in another. If any one fails, delegation fails.
Does delegation remove a real limitation, or merely automate around it? If the underlying constraint remains, delegation only accelerates failure.
Does the decision remain sound as reliance spreads? If behaviour degrades with scale, the system is not ready.
When the machine is wrong, misused, or attacked, does the system recover? If errors compound silently, delegation is unsafe.
The three dimensions are not scored and averaged. They are each independently required. A system scoring perfectly on two dimensions and failing on one is not 67% ready. It is not ready.
When a rule is implicit, delegation defaults to capability. Capability always outruns readiness.
Systems then learn too late. Corrections arrive after damage is done. Control is replaced by reaction.
An explicit law changes this. It allows restraint without weakness. Progress without denial. Leadership without heroics.
The system does not fail loudly. It decays. Judgment erodes. Responsibility diffuses. Recovery becomes impossible. By the time collapse is visible, delegation is already total.
Delegation becomes durable. Human judgment does not disappear — it relocates. From execution to design. From reaction to supervision. From heroics to structure.
This law makes it governable. Progress will continue either way. The only open question is whether it will endure.
The Delegation Readiness Index exists to operationalise The Delegation Law. It provides a clear test for determining whether a decision may be delegated to machine intelligence without degrading the integrity of the system over time.
The index does not measure capability. It measures readiness. These are not the same thing. A system may be highly capable of performing a decision and still not be ready to hold it durably.
Failure in any single dimension results in delegation failure. The multiplication is not mathematical — it is structural. A zero in one column makes the product zero, regardless of the others.
A decision may be delegated to machine intelligence if and only if:
If any dimension fails, delegation is structurally premature — regardless of performance or demand.
DRI is not a benchmark. It is not a maturity model. It is not a safety checklist. It is not a prediction of outcomes. It does not rank systems. It governs decisions.
DRI is applied before reliance becomes normal. It is intended for: system designers, organisational leaders, regulators, boards, and anyone accountable for long-term outcomes.
DRI does not remove responsibility. It makes responsibility explicit.
This section shows how to apply the Delegation Readiness Index to real delegation decisions using four grounded examples. It is designed to be approachable — especially when the decision feels urgent.
1. Structural Alignment: Are we removing the real constraint, or just automating around it?
2. Propagation Stability: As reliance spreads, do outcomes remain sound?
3. System Integrity: If it's wrong, misused, or attacked — can the system recover cleanly?
If any dimension fails, delegation is structurally premature. Strength in one cannot cover weakness in another.
Each example is intentionally short. It does not try to convince you of a worldview. It simply shows how DRI makes the decision decidable.
Notice how often the failure mode is not "the system isn't smart enough," but "the rule is not finished" or "the recovery path is not real."
Each example pressures a different part of the framework:
A small team adopts automated scheduling to reduce manager workload and keep coverage aligned to expected demand. Early results look good. Reliance grows.
What it removes: manual scheduling effort and delays.
What remains: the business rules for coverage are reasonably clear and do not depend on human judgment at the decision point.
As the team grows, edge cases multiply — fatigue, fairness, skill mix, training time, personal constraints. The system optimises "coverage," but important human signals begin to be treated as noise. Over time, people stop raising issues because "the system decided."
Bad schedules often show up late — burnout, morale decay, resignations. Accountability blurs: "Who approved this schedule?" Recovery is possible, but usually after cost has already been paid.
A leadership team wants to reduce bias and speed up decision-making. They propose "data-driven strategy" where the system selects markets, positioning, and priorities.
The real limitation: uncertainty about the future — not lack of information.
The missing prerequisite: a stable rule that defines what "correct strategy" is. Strategy commits the organisation to a chosen future under uncertainty. That commitment requires a human to be responsible for it.
What strategy actually does is not computable. The system cannot hold the accountability that the commitment creates.
Structural Alignment failure halts delegation. The remaining dimensions are not evaluated.
Structural Alignment failure halts delegation.
Human reaction time is insufficient to respond safely. The system is designed to operate in a narrow, well-defined envelope with explicit constraints.
What it removes: the reaction-speed limitation — a genuine structural constraint that humans cannot overcome physically.
What remains human: rule definition, scope, oversight, and accountability. The system executes a fixed rule. It does not invent one.
Scaling increases consistency, not ambiguity. Misuse is constrained by the system's strict operating envelope. The rule does not drift simply because adoption increases.
Actions are logged, attributable, and auditable. Clear disable mechanisms and safe modes exist. Scope is narrow enough that failure does not spill into unrelated domains.
The intention is often understandable: reduce harm, reduce conflict, and keep environments usable. The challenge is that norms are not static — they evolve across communities and time.
The real limitation: ongoing disagreement about values and meaning — not enforcement capacity.
The missing prerequisite: a stable rule that stays legitimate across contexts. Without it, the enforcement system effectively becomes a rule-maker — which is a different, and far more consequential, function than enforcement.
Structural Alignment failure halts delegation. The remaining dimensions are not evaluated.
Structural Alignment failure halts delegation.
When those conditions are missing, the most constructive move is usually not refusal — it is clarity about what must become true to make delegation ready. The framework is not a brake. It is a map.
This framework is written to keep the reader safe to think. It avoids urgency language and avoids framing the reader as "at risk" for asking the question. DRI is a decision aid, not a moral judgment.
Machine intelligence makes delegation inevitable.
The Delegation Law makes it governable.
DRI makes it decidable.