Decision Authority Clarity
Every consequential decision within the platform shall have an explicit authority.
Decision authority shall be intentionally delegated. It shall never drift.
What must remain true
Every consequential decision within the platform shall have an explicit authority.
Decision authority shall be intentionally delegated.
It shall never be implicit, inferred, or accidentally acquired.
The platform shall distinguish between deterministic execution, probabilistic recommendation, and human judgment.
Why the principle matters
Software is an artifact of a human-authored coordination system.
Every coordination system delegates decisions.
Some decisions are delegated to deterministic execution. Some are delegated to declarative knowledge. Some are delegated to probabilistic reasoning. Some remain intentionally delegated to people.
Healthy coordination depends upon every consequential decision being intentionally delegated to the appropriate authority.
When authority becomes ambiguous, software begins making decisions it was never intended to make.
Decision authority may be delegated. It shall never drift.
Decision Authority Clarity preserves trust by ensuring every consequential decision has an explicit, observable authority.
Observing Decision Authority Clarity
Decision Authority Clarity can be evaluated by examining the observable condition of the coordination system.
Healthy Signals
- Every consequential decision has an explicit authority.
- Deterministic decisions remain deterministic.
- Probabilistic recommendations remain recommendations.
- Human decisions remain human decisions.
- Business policy is explicitly defined rather than inferred.
- Engineers can identify who—or what—is responsible for every consequential outcome.
Degrading Signals
- AI silently acquires business decision authority.
- Runtime components infer business policy.
- Probabilistic recommendations are treated as deterministic facts.
- Decision authority emerges from implementation rather than architecture.
- Engineers cannot explain who ultimately made a consequential decision.
Degrading signals do not necessarily indicate failure.
They indicate that this dimension should be examined before confidence in the platform begins to erode.
Engineering Guidance
When designing or extending the platform:
- Explicitly identify the authority responsible for every consequential decision.
- Delegate decisions to the lowest appropriate authority.
- Separate deterministic execution from probabilistic reasoning.
- Keep business policy declarative rather than embedded in runtime implementation.
- Ensure AI recommendations remain distinguishable from business decisions.
- Never allow implementation convenience to redefine business authority.
Architectural Review Questions
Before approving an implementation, ask:
- What consequential decision is being made?
- Who—or what—is authorized to make it?
- Why is that authority appropriate?
- Is the decision deterministic, probabilistic, or human?
- Could authority be acquired implicitly rather than intentionally delegated?
- Would this implementation make authority clearer or more ambiguous?