Decision authority under action becomes critical the moment execution begins. Execution introduces motion, and motion introduces risk. Once systems are moving, decisions no longer operate as abstract choices; they become system-altering events.
Within FM Mastery Q5, decision authority is treated as a governance control, not a leadership concept. This post defines decision authority structurally and explains why authority ambiguity becomes a primary execution risk once execution is active.
Within Q5, decision authority under action exists to ensure that execution remains governed by defined permissions rather than momentum, urgency, or proximity to activity.
Decision Authority Under Action as a System Property
In Q5, decision authority is the system-defined right to alter execution state while execution is active.
Decision authority is not:
• A role title
• A personal attribute
• A function of experience or confidence
• A proxy for speed, ownership, or proximity to action
Decision authority exists as a structural permission boundary. It determines which decisions are valid within an executing system and which are not, independent of outcome quality.
At the system level, authority is binary. A decision is either authorized or unauthorized.
In practice, decision authority under action determines whether execution changes are structurally valid or constitute unauthorized state transitions.
How Authority Changes Under Execution
Before execution begins, decisions shape intent. Once execution is underway, decisions shape system trajectory.
Under active execution:
• Decisions can alter capacity utilization
• Decisions can affect reversibility
• Decisions can convert throughput into burn
• Decisions can lock the system into irreversible states
Because of this, authority under execution is more constrained than authority during planning.
Q5 explicitly separates decision existence from decision legitimacy. A decision may be possible to make, yet invalid to execute.
Authority Ambiguity as an Execution Risk
Authority ambiguity exists when it is unclear which decisions are permitted to alter execution while systems are active.
This ambiguity creates risk faster than most execution errors because:
• Conflicting decisions can be applied simultaneously
• Overrides can bypass capacity and reversibility constraints
• Execution can continue without a single controlling reference
• Responsibility diffuses without halting motion
Within Q5, authority ambiguity is treated as a system failure mode, not a coordination issue.
Outcome Success Does Not Legitimize Authority Breach
In Q5, outcomes do not retroactively validate decisions.
A decision made without authority remains a governance violation even if:
• Output increases
• Short-term results appear positive
• No immediate damage is observed
This principle exists because unauthorized decisions can:
• Consume future capacity invisibly
• Reduce reversibility without detection
• Establish precedent for further authority erosion
Governance is concerned with system integrity, not result justification.
Authority, Capacity, and Reversibility
Decision authority functions as a gate protecting previously defined constraints:
• Q5.1 — Execution Capacity defined execution capacity as a fixed system limit
• Q5.2 — Defining Full Capacity defined full capacity as utilization without violation
• Q5.7 — Throughput vs Burn defined burn as execution beyond capacity
• Q5.8 — Reversibility Standards defined reversibility as a binary safety condition
Q5.10 defines who is permitted to alter execution in relation to these constraints while systems are moving.
Authority does not expand capacity.
Authority does not restore reversibility.
Authority determines whether execution may be altered at all.
Decision Authority as an Execution Gate
In Q5, execution continuity is conditional on authority integrity.
• Authorized decisions preserve governance alignment
• Unauthorized decisions introduce uncontrolled state changes
• Accumulated authority breaches destabilize execution even if output persists
For this reason, decision authority functions as a gating condition. When authority integrity fails, execution may continue mechanically, but it is no longer governed.
Bottom Line
Decision authority under action is not about making better choices.
It is about preventing unauthorized choices from redefining the system mid-execution.
Q5.10 exists to ensure that execution remains controlled by defined authority rather than momentum, urgency, or proximity to action.
Related structural concept:
Decision-making (systems context)
Part of the FM Mastery framework.
View all Q5 — Execution Readiness & Capacity Governance posts
