# Business Entities overview
Each Business Entity maps to one datasource manifest under a Connected System. Enterprise Knowledge, governed capabilities, sync, and certification are declared per entity.
Who this is for
Integrators modeling business vocabulary, policies, data flow (CIP), sync, and AI contract exposure for one datasourceKey.
Prerequisites
- Connected System scaffolded with authentication configured
- Entity basics, types, and resource type understood for your domain
Where it lives
integration/<systemKey>/
<systemKey>-datasource-<name>.json # one Business Entity per file
Dataplane UI: Connected Systems → select system → Business Entities → select entity → tabs (Business Vocabulary, Data Flow, …).
Configure pages (datasource manifest)
| Topic | Configure page | Manifest keys |
|---|---|---|
| Identity | Entity basics | datasource.basics, datasource.entityType, datasource.resourceType |
| Business language | Configure business vocabulary | datasource.fieldMappings |
| Metadata / identity | Configure metadata and identity | datasource.metadata, datasource.identity |
| CIP execution | Configure data flow | datasource.execution |
| AI contract | Configure AI contract | datasource.capabilities, datasource.exposedAttributes |
| Operations | Configure OpenAPI and MCP operations | datasource.openapiOperations, datasource.mcpOperations |
| Entity config | Configure entity configuration | datasource.configuration |
| Sync | Configure sync | datasource.sync |
| Governance | Configure business policies | datasource.dimensions, datasource.abac, datasource.foreignKeys, datasource.protection |
| Quality | Configure data quality | datasource.dataQuality |
| Test payload | Configure validation and test payload | datasource.validation, datasource.testPayload |
Entity-type walkthroughs: Entity type guides.
How to set
- Pick an entity type guide matching your use case (record storage, document storage, vector store, static, records search).
- Set root identity:
key,displayName,systemKey,entityType,resourceType. - Configure business vocabulary and business policies.
- Add CIP operations and test payload before E2E.
- Validate:
aifabrix datasource validate <datasourceKey>andaifabrix validate <systemKey>.
Golden manifest patterns: help topic goldenExample — index on UI terminology map.
Limits
Some entity types and resource types require platform catalog registration before upload. Validation errors name the missing catalog row.