Integration access, customer extensions and shared workflow configuration

Purpose

Customers use this module to connect provider accounts, select the accounts that serve application work, and configure supported customer-specific behaviour. The integration gateway records provider calls and supports investigation of unresolved outcomes. Customization contracts and shared action configuration give application owners a common way to expose customer choices.

Boundary

This module owns integration offers, installations, accounts, credentials, routing, gateway records and integration messages. It also owns customization registration and configuration, shared action declarations, reusable recipes, calendars and automation definitions. Security, workspace lifecycle, query infrastructure and general job infrastructure retain their separate ownership. Applications own payment records, source events and hosted action execution; provider adapters own their provider-specific implementation.

Features

Feature	Product group
FEAT-PFM-INT-01	Integration offers and adoption
FEAT-PFM-INT-02	Provider accounts and credentials
FEAT-PFM-INT-03	Gateway calls and settlement
FEAT-PFM-INT-04	Integration messages and subscriptions
FEAT-PFM-INT-05	Customer extensions
FEAT-PFM-INT-06	Workflow configuration and automation

Capabilities

Capability	Outcome	Status	Product intent
CAP-PFM-INT-001	Publish integration releases for eligible customers	draft	proposed
CAP-PFM-INT-002	Explore the integrations available to a workspace	draft	proposed
CAP-PFM-INT-003	Adopt an integration with reviewed access	draft	proposed
CAP-PFM-INT-004	Maintain a verified provider account connection	draft	proposed
CAP-PFM-INT-005	Protect credentials throughout their useful life	draft	proposed
CAP-PFM-INT-006	Recognize integration problems and trace changes	draft	proposed
CAP-PFM-INT-007	Assign provider connections to business needs	draft	proposed
CAP-PFM-INT-008	Explain and select the connection for a call	draft	proposed
CAP-PFM-INT-009	Run provider operations safely through the gateway	draft	proposed
CAP-PFM-INT-010	Determine the result of uncertain or overdue calls	draft	proposed
CAP-PFM-INT-011	Inspect calls and resolve operational problems	draft	proposed
CAP-PFM-INT-012	Exercise a provider capability on a test account	draft	proposed
CAP-PFM-INT-013	Retain and verify incoming provider notifications	draft	proposed
CAP-PFM-INT-014	Deliver subscribed Rhythm changes to integrations	draft	proposed
CAP-PFM-INT-015	Route integration events to their application owners	draft	proposed
CAP-PFM-INT-016	Keep a shared catalogue of customization points and events	draft	proposed
CAP-PFM-INT-017	Apply tested customizations where an application allows them	draft	proposed
CAP-PFM-INT-018	Keep the action builder aligned with deployed applications	draft	proposed
CAP-PFM-INT-019	Reuse workflow recipes and working-time configuration	superseded	proposed
CAP-PFM-INT-020	Publish event-driven automation and follow its work	draft	proposed
CAP-PFM-INT-021	Reuse validated action and workflow recipes	draft	proposed
CAP-PFM-INT-022	Schedule work using customer business calendars	draft	proposed

Journeys

Journey	Experience	Product intent
JNY-PFM-INT-001	Install an integration and recover a failed connection	confirmed
JNY-PFM-INT-002	Move dependent work before retiring an integration	confirmed
JNY-PFM-INT-003	Choose an account and inspect a gateway test call	confirmed
JNY-PFM-INT-004	Resolve a payment after its response is lost	confirmed
JNY-PFM-INT-005	Test and apply a customer pricing rule	proposed
JNY-PFM-INT-006	Publish an automation for a registered business event	confirmed

The six concepts organize the product vocabulary. There are twenty-one active capability outcomes after separating recipes from calendar scheduling, with one superseded combined capability retained for traceability. The coverage catalog maps source declarations; the examination report identifies where those declarations lack complete behavioural proof or connected product surfaces.