liveBook · Manning

Capability

Also called functionality, ability

A capability is an ability or defined authority that enables an entity to perform an action, provide a function, or achieve an outcome.

How 9 Manning books explain it

Architecture Modernization: Socio-technical alignment of software, strategy, and structure

A capability is an organizational ability to perform a business function or produce a business outcome.

How it is used
Frames decisions about domain boundaries, long-lived team ownership, and where modernization investment belongs.
How deep it goes
Develops the concept through mapping and organizational examples, without prescribing a fixed capability taxonomy or technical implementation.
Examples
Uses broadband self-fulfillment and cruise booking fulfillment to show capabilities informing boundaries and team organization.
What you can do after
Practice/perform capability mapping to propose boundaries, then evaluate them against team dependencies and investment priorities.

Read how Architecture Modernization: Socio-technical alignment of software, strategy, and structure explains capability →

BDD in Action, Second Edition

A capability is an ability that enables users or stakeholders to achieve a goal or fulfill a task independently of a particular implementation.

How it is used
Connects business goals to the features selected to give users or stakeholders a useful ability.
How deep it goes
Defines an implementation-independent ability and traces it through feature discovery, examples, and specification organization without prescribing one implementation.
Examples
Uses commuter journey planning, disruption handling, frequent-flyer renewal, and a capability-organized feature-file tree.
What you can do after
Practice/perform capability discovery, select supporting features, and organize feature files around the abilities an application provides.

Read how BDD in Action, Second Edition explains capability →

The Design of Web APIs, Second Edition

An API capability is a function or set of functions that an API exposes to satisfy a user need.

How it is used
Translates user needs into use cases and reusable operations before programming-interface design.
How deep it goes
Works through a two-pass canvas for users, steps, inputs, outcomes, failures, and operations; defers endpoint design.
Examples
Uses social-network messaging, photo uploads, account closure, and account-title updates to distinguish shared and dedicated operations.
What you can do after
Practice/perform capability identification with the API Capabilities Canvas, then check proposed operations against stakeholder needs.

Read how The Design of Web APIs, Second Edition explains capability →

Platform Engineering on Kubernetes

A platform capability is a platform-provided function that abstracts infrastructure or operational complexity behind a simpler developer-facing interface.

How it is used
Abstracts infrastructure concerns into shared APIs that application teams use while delivering distributed software.
How deep it goes
Explains API separation, team responsibilities, versioning, and environment consistency, but defers observability, metrics, logs, and service meshes.
Examples
Uses the Conference application, HTTP/gRPC interfaces, Dapr, shared infrastructure services, and feature flags as concrete examples.
What you can do after
Apply it via standard APIs to reduce application dependencies and consume infrastructure capabilities across environments.

Read how Platform Engineering on Kubernetes explains capability →

Effective Platform Engineering

A platform capability is a discrete function or service provided by an engineering platform to support software engineering work.

How it is used
Deploys reusable platform services to support multiple development teams instead of completing isolated infrastructure requests.
How deep it goes
Connects capabilities to discovery, qualification, cognitive-load measurement, observability, and platform pipelines, but defers detailed implementation.
Examples
Uses developer portals, centralized documentation, distributed tracing, service meshes, Kubernetes workloads, and domain-specific infrastructure pipelines.
What you can do after
Build and evaluate shared platform services by linking recurring developer problems to capabilities, expected effects, and implementation effort.

Read how Effective Platform Engineering explains capability →

Server-Side WebAssembly

A capability is an explicit, constrained authority that permits code to access a particular resource or operation.

How it is used
Controls how sandboxed Wasm components interact with host operating-system resources.
How deep it goes
Explains sandbox boundaries and demonstrates capability selection through WASI configuration, stopping short of a broader permission model.
Examples
Uses a greeting component that prints through WASI while disabling HTTP access.
What you can do after
Operate/configure Wasmtime and WASI hosts to grant standard output while withholding unused capabilities.

Read how Server-Side WebAssembly explains capability →

Architecting for Autonomy

An organizational ability defined by an intended outcome, permitted authority, and operational boundaries.

How it is used
Defines bounded enterprise abilities that agents can execute within explicit outcomes, authority limits, and escalation paths.
How deep it goes
Explains capability boundaries through outcomes, decision surfaces, triggers, ownership, migration, and wrapper constraints, stopping short of implementation detail.
Examples
Uses fraud containment, SaaS non-conformance investigation, and legacy approval controls to make capability boundaries concrete.
What you can do after
Apply it via bounded wrappers, explicit escalation triggers, accountable ownership, and controlled delegation of agent authority.

Read how Architecting for Autonomy explains capability →

Effective Behavior-Driven Development

The set of capabilities and behaviors that a software system provides.

How it is used
Organizes living documentation around distinct business functionality rather than delivery-story order.
How deep it goes
Defines functionality as business-facing and contrasts fine-grained component rules with multi-behavior stakeholder journeys, without prescribing a fixed feature size.
Examples
Uses blocklisting rules and online pizza ordering journeys to contrast narrow behaviors with larger customer activities.
What you can do after
Evaluate whether to group documentation by stable business functionality or by incremental delivery stories.

Read how Effective Behavior-Driven Development explains capability →

How Large Language Models Work

A capability is an ability or functional competence that a system can demonstrate.

How it is used
Frames LLM use around demonstrated abilities and reliability rather than broad claims about intelligence.
How deep it goes
Defines capability and surveys applications, while stopping short of detailed mechanisms or formal measurement.
Examples
Uses translation, transcription, document reading, search, and media generation as concrete capability examples.
What you can do after
Evaluate/understand LLM applications by separating what a model can produce from how reliably it produces it.

Read how How Large Language Models Work explains capability →

Also covered in

What to know first

Related concepts

Questions about capability

What is capability?

A capability is an ability or defined authority that enables an entity to perform an action, provide a function, or achieve an outcome.

Which Manning books explain capability?

Architecture Modernization: Socio-technical alignment of software, strategy, and structure, BDD in Action, Second Edition, The Design of Web APIs, Second Edition, Platform Engineering on Kubernetes, Effective Platform Engineering, Server-Side WebAssembly, Architecting for Autonomy, Effective Behavior-Driven Development and 1 more.

What should I know before learning capability?

Manning books that teach capability usually introduce language model, contract, foundation model and communication first.

What is the difference between capability and performance?

A capability is an ability or defined authority that enables an entity to perform an action, provide a function, or achieve an outcome. Performance is a measure of how effectively a person, process, model, or system achieves its objectives, including qualities such as output quality, speed, and resource efficiency.

What kinds of capability are there?

Kinds of capability include decision making and communication.

What is capability also called?

Capability is also called functionality or ability.

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.