What CORE is, and what it is not.

Who or what is acting: humans, agents and service identities, known once and recognized in every context.

Every action in CORE starts with an identity. A person, an agent or a service authenticates once and carries that identity into every organization and role it is connected to. Identity holds credentials, sessions and the links to roles and permissions; it does not hold business data. 2finity Identity is the planned OIDC provider for this layer.

Companies, teams, departments and business units: the boundaries inside which people, data and permissions live.

An organization is the unit of ownership in CORE. It owns entities, defines teams and departments, and sets the boundary that permissions and isolation are enforced against. One identity can belong to many organizations with a different role in each. Networks of organizations connect through relationships, never by sharing a database.

Customers, employees, professionals, suppliers and leads: the people an organization works with, as one record each.

People are the humans an organization knows about, independent of how they arrived. A customer, an employee and a supplier contact are the same kind of record with different relationships attached. When a person also has an identity, the two are linked, so a customer who later joins as an employee is still one person. Leads are people whose relationship is not confirmed yet.

Connections between people, organizations, roles and agents: who is a customer, employee, supplier, partner or owner of whom.

Relationships are first-class records, not foreign keys hidden in a table. Each one names two parties, a type and a validity period, and can carry its own terms. Authorization reads relationships: a person edits a website because a relationship makes them an editor of that organization. The same model links agents to the people and organizations that own them.

Documents, structured knowledge, policies, published content and context: what the organization knows and shows.

Knowledge holds everything an organization has written down: internal documents, policies, product knowledge, website pages and the context agents need to act well. Content is versioned, so a change to a homepage headline is a revision that can be previewed, approved and rolled back. Knowledge is scoped by organization and permission, so an agent only reads what its owner may read.

Tasks, approvals, automations, processes, triggers and state transitions: how work moves and who signs off.

A workflow describes how an entity moves from one state to another and who has to agree along the way. Approvals, scheduled jobs, triggers on events and multi-step processes are all workflows. Agents take part as actors: an agent can start a workflow and propose a step, and a human approval can be required before anything is published or paid. Deployments and rollbacks are workflows over revisions.

Products, services, catalogs, quotes, carts and orders: what an organization sells and how it is bought.

Commerce models the offer and the transaction. Products and services sit in catalogs with prices and variants; quotes, carts and orders record what a person or organization is buying. Because buyers are People and sellers are Organizations, a webshop, a sales agent and a partner portal operate on the same order. Payment and invoicing hand over to Finance.

Invoices, payments, costs and financial records: the money side of every order, contract and relationship.

Finance records what is owed, paid and spent. Invoices reference orders and people, payments settle invoices, costs attach to projects and organizations. Nothing here moves money by itself: a payment provider or bank is an interface that reports into CORE, and a capability like invoice.create is subject to the same identity and permission checks as any other action.

Messages, conversations, notifications and threads between people, agents and organizations.

Communication is where humans and agents talk to each other and to the organization. A conversation can be a support thread, an internal discussion, a chat with an agent or a notification stream. 2finity.chat is one planned interface to this layer; email and messaging integrations are others. Every message is linked to the people, entities and capabilities it refers to, so a chat message that changes a headline is traceable to the revision it produced.

Shared structured entities, events, analytics and operational data: the records and signals every layer produces.

Data is the common ground under the other layers. Every capability invocation emits an event, every entity change is recorded, and custom entity types extend the model without a new backend. Queries, reports and analytics read from here through the same permission checks as everything else. Agents get data through capabilities, not through a database connection.