Research pillar · Unbundling Work

Unbundling Work, Credentials, and Liability

A job title bundles tasks, authority, evidence, credentials, and liability that should be examined separately before work is reassigned.

The question

Which parts of a role require the credentialed person, and which parts merely arrived with the title?

Active · since 2026 · Unbundling Work

Open the bundle

List the tasks actually performed, their frequency, inputs, outputs, decisions, required authority, evidence, failure cost, and the person who remains accountable.

Move work only after the bundle is understood.

Treat credentials precisely

A credential can signal knowledge, legal authority, supervision, insurance, institutional trust, or all five. The reason matters when deciding what can move.

Put liability where control sits

Someone held responsible for an outcome needs the information, authority, and intervention path needed to influence it. Recomposition fails when accountability stays while control moves elsewhere.

Test incentives and transition

A sound future-state design can still fail during the move. Measure displaced effort, new review burden, gaming, deskilling, concentration, and who bears the temporary risk.

Preserve the scarce human work

Keep judgment under uncertainty, accountable decisions, trust, negotiation, care, and legitimate authority with people where evidence shows they remain necessary.

Put this to work

Credential and liability map

Use the question “Which parts of a role require the credentialed person, and which parts merely arrived with the title?” on a real case and produce a record another person can challenge.

For: Operators redesigning a team, service, or AI workforce.
What you keep: A credential and liability map you can review, revise, and send.
What counts as sound: Keeps authority and accountability explicit
Preserves scarce human judgment
Names machine boundaries
Counts review and exception work
Defines proof of a better outcome

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.

The caseName the organization, setting, product, or piece of work without including confidential information.The decisionWhat must someone decide, and who owns that decision?Evidence in handList records, observations, measurements, rights, or prior work that can be checked.What is still unknownName missing evidence, disputed assumptions, and practical constraints.Work as it happensList the recurring tasks, decisions, handoffs, exceptions, and proof of completion.

Review the prompt

Credential and liability map 1.0

PURPOSE
Use the question “Which parts of a role require the credentialed person, and which parts merely arrived with the title?” on a real case and produce a record another person can challenge.

CONTEXT
The case: Not provided
The decision: Not provided
Evidence in hand: Not provided
What is still unknown: Not provided
Work as it happens: Not provided

METHOD
1. Start with the outcome, not the job title.
2. List tasks, decisions, inputs, outputs, and exceptions.
3. Mark required credentials and legal authority.
4. Assign work by risk, observability, and judgment.
5. Test the whole operation, including review burden and recovery.

TASK
Use the method below to produce a Credential and liability map.

RULES
Separate facts, inferences, assumptions, estimates, hypotheses, and unknowns. Do not invent evidence, performance, rights, customers, economics, or regulatory standing. Quote or link the source for material facts. State uncertainty. Name what would disprove the conclusion. End with the smallest credible test, an owner, a decision date, and a stop condition.

A SOUND ANSWER
- Keeps authority and accountability explicit
- Preserves scarce human judgment
- Names machine boundaries
- Counts review and exception work
- Defines proof of a better outcome

CAUTION
Do not infer that a task can move merely because it can be described.

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.

Send us the result Intellectual Frontiers on LinkedIn

Notes under this pillar

Design Patterns

An AI credential
If a title cannot be trusted and a licence does not exist, the substitute is a trust contract: what the worker can do, on what data, with what escalation, and what it leaves behind.
September 2026

Operating Theorys

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.
September 2026

Related records

Zero Neo