Intelligence-Authority Separation: Organizational Transfer
The organizational transfer of Intelligence-Authority Separation is not primarily a theory of org charts.
It is a theory of how judgment enters coordinated consequence without collapsing into unchecked action.
The organizational anti-collapse chain is:
analysis
-> recommendation
-> authorization
-> instrument
-> execution
-> audit
The names vary by institution. The invariant is that the organization can still distinguish the function that formed judgment from the function that authorized consequence, the function that executed it, and the function that confirmed what happened.
1. Relation To PDA Organizational Transfer
This is a specialization of PDA Organizational Transfer.
PDA organizational transfer identifies two coordination failures:
- decision drift across time
- authority/locus smearing across structure
IAS specializes the second failure mode. It concerns the smearing of judgment-producing intelligence with permission, mutation, and confirmation.
The organizational problem is not that roles are missing. It is that the role structure does not preserve the distinctions required for accountable consequence.
2. Roles And Responsibilities As Degraded Vocabulary
When corporate populations complain about “roles and responsibilities,” the surface request is often:
Who owns this?
Who decides?
Who executes?
Who is accountable?
Why are many people involved while nothing moves?
Structurally, the complaint often points to intelligence-authority collapse.
The organization has not cleanly separated:
perceive
-> interpret
-> recommend
-> authorize
-> execute
-> verify
-> absorb consequence
People experience this as role ambiguity because the available language names people and boxes. The underlying failure is usually in the transition grammar between knowledge and action.
3. Organizational Functions
An IAS-preserving organization can map each function to an office, person, system, committee, or record type. A small organization may combine functions in one person. The functions still need separate recordable positions.
| IAS function | Organizational expression |
|---|---|
| Judgment | analyst, expert, model, support agent, engineer, physician |
| Evidence record | memo, ticket, chart note, proposal, pull request, case file |
| Authority | approver, manager, risk officer, reviewer, policy owner |
| Instrument / intent | approved order, prescription, contract, deployment request, refund authorization |
| Execution | trader, pharmacist, deployer, support operator, payment processor |
| Confirmation | audit, reconciliation, telemetry, follow-up, accounting, outcome review |
The point is preserved distinction, not maximum separation.
A person may exercise multiple functions. The organizational record must still show which function was being exercised.
4. Collapse Forms
The hard collapse is:
expert judges X
therefore organization does X
The softer form is more common:
expert judges X
manager informally agrees
executor acts
the organization cannot later distinguish judgment, authorization, execution, or confirmation
Common organizational collapses:
| Collapse | Meaning |
|---|---|
| Intelligence without authority | Someone understands the situation and knows the right move, but cannot cause the organization to act |
| Authority without intelligence | Someone has decision rights but lacks direct contact with evidence |
| Execution without authorization | Operators make local moves because waiting is impossible, then authority appears later as blame |
| Responsibility without control | Someone is accountable for an outcome but lacks authority over its causes |
| Consensus as fake authority | Many people are consulted, but no binding decision point exists |
| Escalation as substituted cognition | Ambiguity is pushed upward instead of made legible |
| Review after collapse | Governance appears only after action and becomes blame assignment |
| Audit as punishment | Confirmation exists only as fault-finding, not as closure |
These are not merely cultural defects. They are structural failures in the chain from judgment to consequence.
5. Role Coherence
A role is coherent only when it names a stable position in the intelligence-authority chain.
For example:
- an analyst role forms judgment and evidence
- a reviewer role admits or rejects judgment into authority
- an operator role executes an authorized instrument
- an auditor role confirms or contests consequence
A role becomes incoherent when it silently mixes sensing, recommending, authorizing, executing, and auditing without explicit boundaries.
A responsibility becomes incoherent when it assigns outcome pressure without matching authority over the relevant causes.
This is why many responsibility matrices feel administratively correct but operationally weak. They classify people. The system needs to classify transitions.
6. RACI And Its Limit
RACI-style artifacts are weak repairs for IAS collapse.
They help when the main missing piece is a named owner. They fail when the real missing piece is the authority grammar:
What evidence is admissible?
Who may convert recommendation into authorization?
What instrument carries the authorized consequence?
Who may execute it?
What counts as confirmation?
Who can reopen the decision?
RACI names participation. IAS names consequence-bearing transitions.
The stronger organizational artifact is not just a responsibility grid. It is a judgment-to-consequence chain with authority and evidence at every boundary.
7. Organizational Closure
IAS inherits closure persistence from PDA.
An authority decision remains binding until explicitly reopened. A later local actor may not silently convert prior judgment, exception, or temporary workaround into new policy.
An IAS-preserving organization records:
- what judgment was offered
- what evidence supported it
- what authority admitted or rejected
- what instrument was created
- what execution occurred
- what confirmation showed
- what would reopen the decision
This is how judgment can decentralize without consequence becoming arbitrary.
8. Domains
| Domain | Judgment | Authority | Execution | Confirmation |
|---|---|---|---|---|
| Trading | trader or model identifies opportunity | risk limits, mandate, compliance | order execution | settlement, P&L, risk report |
| Medicine | physician diagnoses and prescribes | prescribing authority, pharmacy checks | medication administration | charting, labs, follow-up |
| Software | engineer proposes change | reviewer, policy, CI gate | deploy system | telemetry, incident review |
| Sales | sales proposes terms | legal or finance approval | contract execution, delivery | accounting, renewal, customer outcome |
| Support | agent diagnoses issue | refund, send, or escalation policy | refund, reply, escalation | audit trail, customer response, reconciliation |
The domains differ. The chain is stable.
9. Summary
Organizational IAS is the discipline of keeping judgment, authorization, execution, and confirmation differentiated under coordination pressure.
Its compressed form:
analysis contributes
authority admits
instrument binds
execution acts
audit confirms
When organizations ask for “roles and responsibilities,” they may be asking for this chain without yet having the vocabulary to name it.