Vendor-neutral
Describe what a business capability means without embedding SAP, Oracle, Salesforce, ServiceNow, or any other application into the definition.
ABCSDraft 0.1ABCS is an open, vendor-neutral specification for describing business capabilities so humans, agents, applications, and automation platforms can discover and execute business operations consistently.
Business intent should not be tied to a particular application vendor. ABCS defines stable, application-neutral capability identities that implementations can map to any suitable system.
Describe what a business capability means without embedding SAP, Oracle, Salesforce, ServiceNow, or any other application into the definition.
Use predictable identifiers, contracts, relationships, and semantics that agents and automation runtimes can discover programmatically.
A single canonical capability can have multiple implementations across applications, environments, protocols, and technologies.
ABCS Draft 0.1 uses a domain.resource.operation convention. Definitions carry version metadata while canonical identifiers remain stable across compatible revisions.
procurement.purchase-order.get procurement.purchase-order.search procurement.purchase-order.create procurement.purchase-order.approve procurement.receipt.create procurement.supplier.get
ABCS describes domains, resources, capabilities, contracts, processes, policies, events, and relationships in application-neutral terms.
Sirvisetti Autonomy implements ABCS through governed Processes, Actions, Policies, Adapters, Packs, Agent and Chatbot experiences. Other implementations are welcome.
Draft 0.1 intentionally starts small. The initial Procurement domain validates the naming model, contracts, relationships, and implementation mapping before ABCS expands into additional business domains.
ABCS is published so software vendors, partners, customers, standards communities, and agent platforms can implement the capability model independently. Draft 0.1 is deliberately small and open to practical feedback.