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

CORE layer 05 of 10

Knowledge

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

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 do we know and publish?

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.

Model

Example entities

  • Document
  • Page
  • Policy
  • Knowledge article
  • Revision
  • Collection
  • Context
  • Glossary term

Contract

Capabilities

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

  • site.content.update→ site.content.updated

    Propose a content change as a new revision; publishing is a separate step.

    Member of the organization
  • site.publish→ site.published

    Publish pending revisions of a site or page.

    Privileged role or approval
  • page.get

    Read a published page by route or id.

    Public
  • page.create→ page.created

    Create a page from a brief or template as a draft revision.

    Member of the organization
  • document.create

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

  • document.get

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

  • policy.get

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

  • knowledge.search

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

The full catalogue

Connections

Relationships

The layers Knowledge reads from and writes to most often.

  • 06

    Workflows

    How does work move?

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

    Open layer
  • 09

    Communication

    How do we talk?

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

    Open layer
  • 10

    Data

    What happened, and what do we have?

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

    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.

    page.get

  • Chat interface

    2finity.chat and other conversational interfaces: language resolved to capabilities, with approval.

    site.content.update

  • Agents interface

    Actors with their own identity, an owner and scoped permissions; every action leaves an audit event.

    site.publish