← Back to concept explainers

Concept Fable

Separation of duties

Conclusion first:Segregation of Duties (SoD) separates conflicting responsibilities so one person, role, or agent cannot complete a risky transaction end to end without oversight. In enterprise Agent systems, SoD prevents a single agent from requesting, approving, executing, and concealing high-impact actions such as refunds, discounts, payments, deployments, access grants, or record deletion.

Segregation of Duties, SoD · Security/Governance

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

A red seal that one person cannot stamp alone

The rice shop was originally priced, collected payment, shipped, and kept accounts by the shopkeeper alone. The business was small, and it relied on the shopkeeper's reputation.

Later, the rice shop opened a branch and also brought in a quotation puppet and a shipping puppet. The puppets were fast and could complete quotation, discount, contract, and outbound delivery within a quarter of an hour.

Once, a major client requested a temporary discount. To close the deal, the puppet automatically lowered the price, generated a contract, approved shipment, and recorded the exceptional discount as a regular promotion. No one did anything malicious, yet no one stopped the conflict of interest.

The boss first required the puppet to say "I have been careful" at every step. This phrase appeared many times in the records, but the red seal was still stamped through the same single process.

The old internal controller split the red seal into three: the person who quotes cannot approve an excessive discount, the person who approves cannot release the shipment, and the person who ships cannot alter the books. The puppet can prepare materials, but cannot walk the conflict chain alone.

If a task crosses a conflict boundary, the system pauses and finds another role to review it. The reviewer sees the original request, the suggested rationale, the monetary impact, and historical comparisons.

The second major client was pressing hard. The quoting puppet could still draft a proposal quickly, but excess discounts had to be confirmed by the sales manager, and shipment release was handled independently by the warehouse system.

The rice shop did not lose efficiency, because routine small orders flowed automatically; the actions that could truly hurt the books were assigned to different responsible parties. Only then did the boss understand that the greatest risk was not that a particular person was bad, but that a process allowed the same person or the same administrative assistant to be applicant, approver and executor at the same time. Later, an even thornier job arrived. On the surface it looked like just an amplified version of the old problem, but in fact it forced out all the gaps hidden in the process: who takes over first, who can make changes, how to return to the previous step when something goes wrong—places that used to be glossed over by acquaintances' tacit understanding now all had to be made clear. The person in charge did not urge everyone to be more careful; instead, he walked the site again. He had people record every handover, every failure and every remedy, which places were merely slow, which places would harm the outcome, and which places, once wrong, would be hard to recover. After the new rules were rolled out, the first few days were not smooth. Some complained about an extra check, some felt their old experience was being insulted. But when the next anomaly appeared, for the first time everyone could follow the traces to find where the problem had occurred, instead of gathering around the result and guessing at each other.

Reveal

This story is about: separation of duties

Segregation of Duties (SoD) separates conflicting responsibilities so one person, role, or agent cannot complete a risky transaction end to end without oversight. In enterprise Agent systems, SoD prevents a single agent from requesting, approving, executing, and concealing high-impact actions such as refunds, discounts, payments, deployments, access grants, or record deletion.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • Three red seals: separation of duties for request, approval, and execution/bookkeeping
  • The quote puppet completes one chain: Agent over-concentrates high-risk permissions
  • "I have been careful": weak control based only on self-declaration
  • Another role reviews: independent approval and human-machine collaboration controls
  • Routine small orders flow automatically: risk-tiered automation
  • Final insight: enterprise Agents need to improve efficiency, but must not merge mutually balancing responsibilities into a single button

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

approval workflowleast privilegeinternal controlshuman approval
京ICP备2026014272号