liveBook · Manning

Delegation

Also called delegating

Delegation is the assignment or forwarding of work, responsibility, or authority to another person or component to act on behalf of the delegating party.

How 6 Manning books explain it

Authorization in Action

Delegation is an authorization in which one entity grants another authority to act on its behalf within a defined scope.

How it is used
Enables bounded authority across customer applications, support escalations, supplier relationships, and agent workflows.
How deep it goes
Explains delegation records and runtime checks, with layered Cedar guardrails and permits for agent actions.
Examples
Uses a photo-printing application, a tenant support escalation, supplier credentials, and a document-research subagent to illustrate delegated access.
What you can do after
Apply it via Cedar policies that check a named delegate, allowed actions, resource scope, and expiration.

Read how Authorization in Action explains delegation →

The Joy of JavaScript

A composition style in which an object forwards behavior or property lookup to another object through delegation links rather than copying or class inheritance.

How it is used
Uses delegation to reuse behavior across linked JavaScript domain objects without requiring a class-inheritance design.
How deep it goes
Works through Object.create links, prototype lookup, and initialization; contrasts explicit references without developing that technique further.
Examples
Shows a linked blockchain store and transaction objects, plus implicit and explicit formatter calls.
What you can do after
Build it from scratch with Object.create links and initialization methods, then distinguish prototype delegation from explicit references and mixin composition.

Read how The Joy of JavaScript explains delegation →

Kotlin in Action, 2E

How it is used
Reduces wrapper and accessor boilerplate when behavior should be forwarded to a contained object or helper.
How deep it goes
Explains compiler-generated class forwarding and property delegates through observable-property refactoring, including getValue and setValue conventions.
Examples
Uses a CountingSet wrapper and observable Person age and salary properties to demonstrate selective forwarding.
What you can do after
Apply it via Kotlin’s by syntax and Delegates.observable to customize selected behavior without rewriting routine forwarding code.

Read how Kotlin in Action, 2E explains delegation →

AI Governance

Delegation is the transfer of work or authority from one agent or actor to another.

How it is used
Addresses runtime authorization and accountability when agents delegate work to other agents.
How deep it goes
Explains requester-chain logging and authority narrowing, but does not provide their implementation.
Examples
Uses a clinical workflow involving chart reading, summarization, and patient or emergency-contact messaging.
What you can do after
Operate/configure delegation controls by recording requester chains and restricting downstream authority.

Read how AI Governance explains delegation →

Architecting Autonomous Agentic Systems

The explicit assignment of decision-making power, limits, escalation conditions, and ownership from an enterprise to a system or person.

How it is used
Governs how an enterprise grants agents decision authority while retaining escalation and accountability.
How deep it goes
Defines decision boundaries, escalation, audit trails, and ownership as architectural constraints.
Examples
Uses an agent freezing customer accounts during a 3 a.m. incident and a team–agent contract.
What you can do after
Evaluate readiness to delegate autonomy by identifying authority, limits, escalation, and accountable roles.

Read how Architecting Autonomous Agentic Systems explains delegation →

Vibe Engineering

Delegation is a workflow pattern in which a task is assigned to an autonomous agent that returns an artifact for human review.

How it is used
Assigns a discrete issue to an autonomous agent and routes its pull request to a human reviewer.
How deep it goes
Describes the handoff and its review risk, without detailing the agent’s implementation.
Examples
Names GitHub’s coding agent and Codex as cloud-hosted agents that can return pull requests.
What you can do after
Evaluate delegated work by treating the returned pull request as an artifact requiring review.

Read how Vibe Engineering explains delegation →

Also covered in

What to know first

Related concepts

Questions about delegation

What is delegation?

Delegation is the assignment or forwarding of work, responsibility, or authority to another person or component to act on behalf of the delegating party.

Which Manning books explain delegation?

Authorization in Action, The Joy of JavaScript, Kotlin in Action, 2E, AI Governance, Architecting Autonomous Agentic Systems and Vibe Engineering.

What should I know before learning delegation?

Manning books that teach delegation usually introduce AI agent, attribute, leadership and class first.

What is the difference between delegation and authorization?

Delegation is the assignment or forwarding of work, responsibility, or authority to another person or component to act on behalf of the delegating party. Authorization is the determination of which actions or resources an identity or other entity is permitted to access under defined permissions or policies.

What is delegation also called?

Delegation is also called delegating.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.