Skip to main content

​
Shapes of data

The Context Registry organizes information in two layers: An entity type is a category of record in your workspace. A context type is a schema for structured data — fields, validation, and prompts that guide how information is captured or extracted. Every entity type gets a primary context type when you create it. You can add more context types later as the entity accumulates different kinds of information.
Diagram placeholder Simple illustration: one entity type box (“People”) with three nested context type boxes (“Contact info”, “Work history”, “Notes”). User-facing labels only.

​
Entity types

An entity type defines a kind of record your organization works with. When you create one, you give it:
  • A display name your team recognizes in lists and settings (e.g. “Formulas”, “Locations”, “Candidates”).
  • An optional description of what the type represents.
  • A primary context type — the main data shape for new instances of this type.
The system generates an internal type code from the display name. You do not need to manage codes manually; focus on names your team will understand.

​
Common entity types

Many workspaces start from familiar categories. Yours may include:
Use Case Brainstorm agent in Evolve can suggest entity types that match your industry before you create them here.

​
Create an entity type

  1. Open Intelligent Registries → Context types (or Entity Manager → create flow).
  2. Switch the list view to Entity types if needed.
  3. Click Create entity type.
  4. Enter display name and description.
  5. Save — a primary context type is created with the entity.
Screenshot placeholder Create entity type dialog with display name field and expanded “What is an entity type?” help panel.
Before naming a type, ask: What real-world thing does this represent? Will my team recognize this name? Is it distinct from types we already have?

​
Context types

A context type defines how data is structured and how the system helps capture it:
  • Field definitions (the shape of the data).
  • Prompts that guide assisted extraction when someone adds context in conversation.
  • Whether the type applies to a specific entity type or broadly across your facility.
Context types can be:
  • Entity-bound — tied to one entity type (e.g. “Contact Information” on People).
  • Facility-wide — shared shapes not tied to a single entity category.

​
Primary vs. additional context

You will see a Primary badge on the main context type in entity type detail views.
Screenshot placeholder Context types list (/cir/context-types) or entity type detail showing linked context types with Primary badge on one row.

​
Create a context type

  1. Open Context types from the Intelligent Registries Context group.
  2. Click Create context type.
  3. Name the shape and describe what data it holds.
  4. Optionally link it to an entity type, or leave it facility-wide.
  5. Configure the schema (often with assisted generation from a description).
Screenshot placeholder Create context type dialog with entity type linker dropdown and schema preview.
Video placeholder (Screen Studio) Short clip: create entity type → see primary context appear → add a second context type linked to the same entity.

​
Subscriptions

Your workspace subscribes to entity types and context types that are active for your organization. Only subscribed types appear in Entity Manager, page builders, and track entity pickers. If a type is missing from a dropdown, confirm it is subscribed and active for your facility.

​
How Tracks use entity types

When you create a track, you choose an entity type — that decision controls what kind of instance you can add later (a person, a file, an idea, etc.). Those options come directly from entity types defined here. Changes to context on those instances are recorded on the Intelligence Timeline for your organization. Next: Intelligence Timeline — how context history flows and accumulates.