Business Projects and Business Catalogs describe business work
Business Projects and Business Catalogs organize reusable Business Flows, Capabilities, published Operation usage, and supporting business content around recognizable responsibilities and processes. Business Flows stay at the business level, using Application nodes for stable published Operations and Agent Tasks for bounded reasoning without embedding vendor endpoints, credentials, Routes, or backend mechanics.
Application Projects and the Application Catalog implement the application boundary
Application Projects and the Application Catalog contain application-specific implementation for the systems customers actually run. They can provide Application Flows, Operations, mappings, schemas, Camel/Kaoto Routes, and implementation metadata behind governed published Operation contracts while environment-specific endpoints, credentials, secrets, and operational bindings remain outside the distributable package.
Why keep the layers separate?
If business-process meaning is embedded directly inside every application integration, the same business responsibility gets redefined whenever implementation changes. Separating the layers lets business process intent stay stable while application implementation evolves independently. Autonomy governs installation, binding, execution, evidence, and lifecycle across both.