Business content
Business Area → Playbook → Business Flow. A Playbook collects executable, application-independent Business Flows.
Application content
Application → Adapter → Application Flow. An Adapter collects application-specific implementations for one application or product family.
Runtime responsibilities
- Constructor provisions autonomous workers.
- Controller governs qualification, authority, policies, approvals and evidence.
- Conductor executes Business Flows.
- Connector executes Application Flows.
Packages and change
Business Playbook Packages (.bpp) and Application Adapter Packages (.aap) are immutable, versioned distribution artifacts. Each version describes the complete desired collection; deployment compares hashes and versions to avoid unnecessarily redeploying unchanged flows. Rollback restores a retained compatible deployment for new work, not application transactions already completed.
Authoring and operations
Designer owns business drafts and worker definitions; Developer owns application drafts. Drafts are independently testable. Runtime executes deployed immutable versions. Console manages runtime Workers, work, approvals and deployments.
Product direction
Designed Business Flows are the initial path. Dynamically proposed flows are a future direction, subject to approved operations and governance. Confirm availability against the applicable build.