# Capability Delivery & Operations — Capability Productization Cycle

Canonical page: https://apiopscycles.com/cycles/capability-productization-cycle/stations/api-delivery

Language: en

Entity ID: api-delivery

Cycle: [Capability Productization Cycle](https://apiopscycles.com/cycles/capability-productization-cycle.md)

Read [shared station guidance](https://apiopscycles.com/stations/api-delivery.md) first. The sections below supplement or replace the corresponding shared sections for this cycle. Sections not repeated here retain the shared guidance.

## Journey entry criteria

- The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders. — The chosen API architecture and platform patterns have been validated with the relevant architecture, security, and platform stakeholders. (ID: architecture-patterns-validated)
- The selected interface provides an appropriate abstraction for consumers. — The API is intended to shield consumers from backend complexity and inconsistencies. (ID: hide-backend-discrepancies)
- The interface design and exposed capabilities trace back to business value and consumer needs. — The API design and exposed capabilities clearly trace back to business value and user needs. (ID: design-reflects-business-value)
- The interface design follows agreed design standards and conventions. — The API design follows our shared API product and design conventions. (ID: api-consistency)

## Journey exit criteria

- The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders. — The chosen API architecture and platform patterns have been validated with the relevant architecture, security, and platform stakeholders. (ID: architecture-patterns-validated)
- The selected interface provides an appropriate abstraction for consumers. — The API is intended to shield consumers from backend complexity and inconsistencies. (ID: hide-backend-discrepancies)
- The interface design and exposed capabilities trace back to business value and consumer needs. — The API design and exposed capabilities clearly trace back to business value and user needs. (ID: design-reflects-business-value)
- The interface design follows agreed design standards and conventions. — The API design follows our shared API product and design conventions. (ID: api-consistency)

## Description

Deliver and operate the reusable capability using implementation-style-appropriate engineering, testing, security, release, support, and operational ownership practices.

## Role participation and responsibilities

- [Delivery Engineer](https://apiopscycles.com/roles/api-engineer.md) (lead): Owns implementation, automation, testing, and release flow concerns needed to deliver the capability, API, or automation reliably.; suggested-answer-owner: [Capability Readiness & Operations Canvas](https://apiopscycles.com/resources/capability-readiness-operations-canvas.md)
- [Platform Architect](https://apiopscycles.com/roles/platform-architect.md) (core): Guides platform, integration, scalability, and architecture decisions that shape how the capability or API is built and operated.
- [Security Specialist](https://apiopscycles.com/roles/security-specialist.md) (core): Ensures security risks, controls, and trust boundaries are addressed throughout the API lifecycle.
- [Support and Operations Owner](https://apiopscycles.com/roles/operations-specialist.md) (core): Represents runtime support, incident handling, observability, and operational readiness for the capability, API, or automation.
- [API Designer](https://apiopscycles.com/roles/api-designer.md) (consulted): Shapes the interface contract, interaction model, consistency, and usability of the exposed capabilities.
- [Capability Owner](https://apiopscycles.com/roles/capability-owner.md) (consulted): Owns the capability vision, value, priorities, lifecycle, and reuse across consumers.
- [Compliance and Legal Specialist](https://apiopscycles.com/roles/compliance-specialist.md) (consulted): Clarifies legal, privacy, regulatory, and contractual requirements that affect the capability, API, interface, or automation.

## Resources

- [Capability Readiness & Operations Canvas](https://apiopscycles.com/resources/capability-readiness-operations-canvas.md)