Business Objects
A Business Object defines canonical business information used by capabilities. It is application-neutral and is not an execution primitive.
Definition model
A canonical Business Object may define its identifier, business definition, JSON Schema, business keys and key scope, typed relationships, lifecycle/state dimensions, related capabilities, version and provenance.
Business keys, not artificial global IDs
ABCS distinguishes the identity of an object type from the identity of a business record. An individual Purchase Order, Invoice, Shipment or Project may be identified by a real business number scoped to the relevant organization rather than an artificial global UUID.
Reusable business primitives
Draft 0.2 includes reusable Party, Identifier, Address, Monetary Amount, Quantity and Business Object Reference schemas so domains do not independently redefine shared business semantics.
Party and contextual roles
A Party may be an organization or person. Supplier, Customer, Buyer, Seller, Payer, Payee and Carrier are contextual business roles. The same organization can participate in different domains without becoming unrelated identities.
Multidimensional state
Complex business objects should not collapse independent state dimensions into one giant status value. Purchase Orders distinguish lifecycle, approval, fulfillment and invoicing; Customer Cases distinguish lifecycle and assignment; Invoices distinguish lifecycle, approval and settlement.
Closed canonical schemas
Draft 0.2 canonical schemas are deliberately strict. Vendor-specific application fields, routing metadata and implementation details do not belong in canonical payloads.