> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensorpro.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Data model

> Record types and the core objects EDN stores.

This page stays high level. For exact request and response fields, use the
[API Reference](/api-reference/health-check), which is generated from the
OpenAPI specification.

## Record types

Every memory record has a type that describes what kind of thing it is.

| Record type  | Meaning                |
| ------------ | ---------------------- |
| `FACTUAL`    | A fact                 |
| `PREFERENCE` | A user preference      |
| `STYLE`      | A style or tone signal |

Each record also carries a provenance class, which records its origin and
governs how it is used. See [Core concepts](/developer/core-concepts) for the
full set of provenance classes.

## Core objects

<CardGroup cols={2}>
  <Card title="Memory record" icon="database">
    The unit of memory. Carries its record type, provenance, domain, a content
    summary, and an embedding, along with lifecycle fields such as whether it is
    active and which record it supersedes.
  </Card>

  <Card title="Session" icon="comments">
    A conversation. Tracks its title, message count, and whether it is active or
    archived, and can be associated with a project.
  </Card>

  <Card title="Project" icon="folder">
    A named workspace that groups sessions and sources, and can carry its own
    custom instructions.
  </Card>

  <Card title="Instructions" icon="sliders">
    Per-user global instructions such as display name, language, response style,
    domain, and custom instructions.
  </Card>

  <Card title="Project source" icon="file-lines">
    An ingested document registered to a project, with a title, source type,
    ingest status, and chunk count.
  </Card>

  <Card title="Conversation message" icon="message">
    A single message in a session. Conversation messages are chat history and
    are never eligible for retrieval into the SIP.
  </Card>
</CardGroup>

<Note>
  Field lists above name only the top-level attributes that matter for using the
  API. The authoritative schema for every object lives in the
  [API Reference](/api-reference/health-check).
</Note>