Research program
Unbundling Work, Credentials, and Liability
A job title bundles work, authority, trust, evidence, and liability. Open the bundle before deciding what should move and what must stay with a person.
Which parts of consequential work need this person's capability, credential, authority, presence, or liability bearing responsibility?
The job title is not the work
A title records an institutional arrangement. It does not show the tasks, decisions, handoffs, evidence, exceptions, or outcomes inside it. Those parts may have been bundled because of regulation, old software, labor scarcity, reimbursement, or habit.
Begin with observed work. Record what happens, how often, what enters, what leaves, who decides, what can go wrong, and who answers for it.
Credentials carry several things
A professional credential can stand for training, tested competence, legal scope, institutional privilege, trust, supervision, accountability, and liability. These are related, but they are not interchangeable.
A machine may be capable of preparing a recommendation and still lack authority to issue it. A person may hold authority while adding little value to routine preparation. The design must state both facts.
Use the minimum necessary exposure
Count credentialed touches and minutes per accepted outcome. Then ask which touch uses judgment or authority and which merely repairs missing information, repeats documentation, or moves a packet.
The objective is not fewer professional minutes at any cost. It is the least credential, authority, and liability exposure consistent with a safe result and clear accountability.
Find where liability lives
For each stage, name who can cause harm, prevent harm, authorize action, execute it, supervise it, communicate it, and pay after failure. Those may be different parties.
Risk creation, risk control, risk ownership, risk transfer, and risk financing need separate fields. Moving work without moving control can leave a person responsible for an outcome they can no longer influence.
Ask why the work exists
Some work produces the outcome. Some protects safety. Some exists because a payer, regulator, contract, vendor, department, or missing information imposes it. One party may require the work while another pays and a third waits.
Before automating a burden, identify its cause. The right answer may be to retain it, assist it, redesign the exchange, change a rule, renegotiate a contract, consolidate a handoff, or remove the requirement.
Count work wherever it moves
A local labor saving can move effort to another employee, a more expensive professional, a vendor, a patient, or a caregiver. It can also return later as review, exception handling, or correction.
Keep a transfer ledger. A redesign is not better when it saves twenty staff minutes by adding forty minutes of phone calls, forms, portal work, or record gathering for a family.
Know when the bundle should remain
Keep work bundled when the judgment is tacit, the physical act and decision are inseparable, law requires one accountable professional, trust depends on direct participation, or decomposition creates more ambiguity and risk than it removes.
Technical separability is not enough. The legal, clinical, operating, economic, and human case must also hold.
Disposition review
Choose the disposition from evidence, not enthusiasm for automation.
| Disposition | Use when | Evidence needed |
|---|---|---|
| Retain with a person | Judgment, authority, trust, presence, or learning changes the result | Outcome and capability evidence |
| Assist | Preparation can move while a person keeps the decision | Review burden and error record |
| Automate | Work is bounded, observable, reversible, and testable | Accepted outcomes under live conditions |
| Redesign or remove | The burden comes from an avoidable rule or broken exchange | Cause, authority, and system effect |
| Keep bundled | Separation creates legal, safety, or accountability gaps | Qualified review and failure analysis |
Research notes
An AI credential
Represent trust as evidence about a narrow capability, approved sources, authority, incidents, and recertification. An AI credential is a task specific operating record that can be narrowed, suspended, or renewed as evidence changes. It is not a professional license or legal credential.
Burden Payer and Burden Imposer matrix
Show who requires work, who performs it, who pays, who benefits, who waits, and who can change it. The matrix exposes cost shifting and the party able to remove the cause, but it does not settle the policy choice, because different parties may have sound reasons for the same work.
Credential Exposure profile
This note gives a way to measure how much credentialed time, authority and liability a workflow uses per accepted outcome, before and after a redesign. Lower exposure is not automatically better, so the redesign stops when accepted outcomes, responsibility, trust or capability formation worsen. Count where credentialed time, authority, supervision, and liability enter one accepted outcome.
Credentials as insurance
Training, credential, licence, supervision, and liability cover exist as a stack because each layer is insufficient alone. An AI worker arrives with none of them.
Liability Decomposition map
Separate who creates, controls, authorizes, owns, transfers, and finances risk at each stage. The map gives a stage by stage view of risk and responsibility with unresolved questions, and a recomposition is rejected when no party clearly owns a consequential failure. Technical architecture does not establish legal liability.
The title trap
A role name hides the scope, authority, evidence, exceptions, and outcomes that determine whether work can move. Comparing the formal description with actual tasks and decisions yields a role decomposition into distinct work units. A title can stay useful for employment, identity, and accountability even when it is a poor automation unit.
Work Origin and Incentive map
Find whether work serves the outcome or was created by a rule, incentive, boundary, or information failure. Each burden is classified and given a disposition of retain, assist, automate, redesign, renegotiate, or remove. Institutional friction can be protective, so classification does not prove a burden is waste.