Skip to content
2finity.com
2finity.com
2finity.devSign in

CORE layer 10 of 10

Data

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

2finity CORE and the interfaces and participants connected to it
COREWebsiteApplicationsChatAgentsPeopleCompaniesPartnersEnterprise
CORE
The shared operating layer. Ten layers: Identity, Organizations, People, Relationships, Knowledge, Workflows, Commerce, Finance, Communication, Data.
Website (interface)
Public sites and portals that read content and catalog data and submit forms through CORE. Uses the Identity, Knowledge, Commerce and Data layers. Example capabilities: page.get, catalog.list, form.submit.
Applications (interface)
Internal, mobile and dashboard apps: views into CORE with the signed-in identity's permissions. Uses the Identity, Organizations, People, Workflows and Data layers. Example capabilities: customer.get, workflow.start, approval.decide.
Chat (interface)
2finity.chat and other conversational interfaces: language resolved to capabilities, with approval. Uses the Identity, Knowledge, Workflows, Finance and Communication layers. Example capabilities: site.content.update, invoice.create, permission.grant.
Agents (interface)
Actors with their own identity, an owner and scoped permissions; every action leaves an audit event. Uses the Identity, Knowledge, Workflows and Communication layers. Example capabilities: site.publish, deployment.rollback, workflow.start.
People (participant)
Humans in any context: professional, employee, customer or supplier, with one identity throughout. Uses the Identity, People, Relationships and Communication layers. Example capabilities: customer.get, permission.grant, message.send.
Companies (participant)
Organizations that own their data, run their workflows and decide who and what may act inside them. Uses the Organizations, People, Relationships, Commerce and Finance layers. Example capabilities: organization.get, invoice.create, order.update.
Partners (participant)
Other organizations connected by a relationship: suppliers, resellers and agencies see what it grants. Uses the Identity, Relationships, Commerce and Data layers. Example capabilities: catalog.product.get, order.update, permission.grant.
Enterprise (participant)
Large organizations running CORE in an isolated deployment with their own identity provider and policies. Uses the Identity, Organizations, Workflows, Finance and Data layers. Example capabilities: permission.grant, deployment.publish, workflow.start.

Scope

What it holds

What happened, and what do we have?

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.

Model

Example entities

  • Entity type
  • Record
  • Field
  • Event
  • Audit entry
  • Dataset
  • Report
  • Metric

Contract

Capabilities

Every action on this layer is a named capability with a permission check and, where something changes, an event.

  • entity.get

    Named in the layer model; not yet described in the catalogue.

  • entity.list

    Named in the layer model; not yet described in the catalogue.

  • entity.type.define

    Named in the layer model; not yet described in the catalogue.

  • event.emit

    Named in the layer model; not yet described in the catalogue.

  • event.query

    Query events by name, actor, resource and period.

    Member of the organization
  • audit.list

    List audited actions for an organization.

    Privileged role or approval
  • report.run

    Named in the layer model; not yet described in the catalogue.

  • form.submit→ form.submitted

    Record a form submission as an entity and emit an event.

    Public
The full catalogue

Connections

Relationships

The layers Data reads from and writes to most often.

  • 01

    Identity

    Who or what is acting?

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

    Open layer
  • 06

    Workflows

    How does work move?

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

    Open layer
  • 05

    Knowledge

    What do we know and publish?

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

    Open layer

Consumers

How interfaces use it

The interfaces and participants on the CORE graph that read or write this layer, with the capabilities of this layer they name.

  • Website interface

    Public sites and portals that read content and catalog data and submit forms through CORE.

    form.submit

  • Applications interface

    Internal, mobile and dashboard apps: views into CORE with the signed-in identity's permissions.

    Uses the layer; its featured capabilities belong to other layers.

  • Partners participant

    Other organizations connected by a relationship: suppliers, resellers and agencies see what it grants.

    Uses the layer; its featured capabilities belong to other layers.

  • Enterprise participant

    Large organizations running CORE in an isolated deployment with their own identity provider and policies.

    Uses the layer; its featured capabilities belong to other layers.