Design Pattern · September 2026
Liability Decomposition map
Separate who creates, controls, authorizes, owns, transfers, and finances risk at each stage.
Under the pillar Unbundling Work, Credentials, and Liability
Inputs
Workflow stages, authorities, contracts, supervision, indemnities, coverage, incidents, and evidence.
Method
Map cause, prevention, authorization, execution, communication, supervision, legal accountability, contractual duty, indemnity, and possible financial response.
Output
A stage by stage risk and responsibility map with unresolved questions.
Boundary
Technical architecture does not establish legal liability, coverage, or insurability.
Stop
Reject a recomposition when no party clearly owns a consequential failure or lacks control needed to carry that responsibility.
Put this to work
Liability Decomposition map application record
Apply Liability Decomposition map to a real piece of work and record what happened.
- For
- Operators redesigning a team, service, or AI workforce.
- What you keep
- A liability decomposition map application record you can review, revise, and send.
- What counts as sound
- Names a real setting
- Shows the work before and after
- Records exceptions
- Uses an observable result
- Ends with keep, revise, or stop
Do not infer that a task can move merely because it can be described.
Nothing entered here is stored or sent. Review the prompt before sharing confidential, personal, patient, or privileged information.
Review the prompt
You can leave any field blank. The prompt will mark it as not provided.
If the record survives your review, send the question, evidence, unknowns, and requested next step.