Core concepts

ABCS keeps the semantic model intentionally small so it remains useful to business systems, developers, and autonomous agents.

Concept	Purpose
Domain	A coherent area of business responsibility, such as Procurement, Finance, Sales, Service, HR, or IT.
Resource	A business object or subject acted upon, such as Purchase Order, Supplier, Customer, Invoice, or Case.
Capability	An application-neutral business operation with a stable identity and defined semantics.
Contract	Machine-readable input and output expectations for a capability.
Process	An orchestration of capabilities and human/system steps toward a business outcome.
Policy	A decision or constraint that governs when or how a capability or process may operate.
Event	A business-significant occurrence associated with a domain or resource.
Relationship	A typed link between capabilities, resources, processes, policies, or events.

Capability vs. implementation

ABCS capability
procurement.purchase-order.get
          │
          ├── SAP S/4HANA implementation
          ├── Oracle E-Business Suite implementation
          ├── Microsoft Dynamics implementation
          └── custom implementation

The canonical capability is stable. Implementations may vary by application, protocol, environment, and technology.

What ABCS does not standardize

Draft 0.1 does not prescribe a workflow engine, agent framework, integration runtime, user interface, authentication product, database, message broker, or application vendor.