> ## Documentation Index > Fetch the complete documentation index at: https://docs.beta.adapter.com/llms.txt > Use this file to discover all available pages before exploring further. # Evidence > All evidence types that Adapter models from your connected data sources Adapter classifies every piece of ingested data as an **evidence type**. Each evidence type has a fixed schema regardless of which provider it came from. Evidence types fall into two categories: * **General** — not tied to a single provider. For example, `email` uses the same schema whether the source is Gmail or Outlook. General types include communication (email, calendar events), files, and assets. * **Provider-scoped** — specific to one integration. Types like `github_issue` or `linear_cycle` represent resources that only exist within that provider. When you query the [Search](/api-reference/knowledge/search) endpoint, each result includes an `evidence_type` field set to one of the values below. ```json All evidence_type values theme={null} [ "article", "asset", "calendar_event", "conversation_message", "document", "drive_file", "email", "file", "github_discussion", "github_issue", "github_push", "github_release", "github_repo", "linear_comment", "linear_cycle", "linear_initiative", "linear_issue", "linear_project", "notion_page", "slack_message" ] ``` ## General | Evidence Type | Description | | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `article` | An external publication — a news article, blog post, press release, or syndicated feed item | | `asset` | A binary media object whose meaning requires analyzing the bytes — images, screenshots, scanned or image-only PDFs. Stored as a blob and analyzed via vision/OCR/EXIF; not text-indexed unless analysis yields text. For text-bearing documents (docx, text PDFs, txt, markdown, csv, html) use evidence\_type='file' instead. When a PDF has both a text layer and visual content, choose by which is the point: extractable text means 'file', pixels mean 'asset' | | `calendar_event` | A scheduled event on a user's calendar. Normalized across Google Calendar, Outlook, and .ics attachments | | `conversation_message` | The provider-neutral chat message — one message in a direct, group, channel, or assistant conversation, normalized across chat apps and message exports. For Slack connector data use evidence\_type='slack\_message' | | `document` | The provider-neutral standalone text document — a page, note, wiki entry, or custom-connector text record whose content is supplied directly (not a file artifact to extract from, and not binary media). The generic sibling of provider-specific document types like notion\_page. For a named file/attachment that yields text use evidence\_type='file'; for binary media analyzed via vision/OCR use evidence\_type='asset' | | `drive_file` | A file stored in a cloud drive. Normalized across Google Drive and OneDrive | | `email` | An individual email in a mailbox. Normalized across Gmail and Outlook | | `file` | A named document or attachment that carries (or yields) text and is indexed as searchable content — docx, text-bearing PDFs, txt, markdown, csv, html. Linked to its parent evidence (e.g. the email it was attached to). When a PDF has both a text layer and visual content, choose by which is the point: extractable text means 'file', pixels mean 'asset' | ## GitHub | Evidence Type | Description | | ------------------- | ------------------------------------------------------------------------------------------- | | `github_discussion` | A GitHub Discussions thread — the forum-style Q\&A and announcement feature on a repository | | `github_issue` | A GitHub issue or pull request. Distinguished by a kind discriminator | | `github_push` | A git push to a repository — one or more commits landed on a branch | | `github_release` | A published release on a GitHub repository, typically tied to a git tag | | `github_repo` | A GitHub repository and its top-level metadata | ## Linear | Evidence Type | Description | | ------------------- | ---------------------------------------------------------------------------------------------- | | `linear_comment` | A comment on a Linear issue — used for discussion, status updates, and decisions | | `linear_cycle` | A Linear cycle — a time-boxed sprint used to plan and track a batch of work | | `linear_initiative` | A Linear initiative — a high-level strategic goal that spans multiple projects | | `linear_issue` | A Linear issue — the core unit of work tracking, with workflow states, priority, and assignees | | `linear_project` | A Linear project — a collection of issues organized around a shared deliverable or milestone | ## Notion | Evidence Type | Description | | ------------- | --------------------------------------------------------------------------------------- | | `notion_page` | A Notion page — can be a standalone document, wiki entry, or a row in a Notion database | ## Slack | Evidence Type | Description | | --------------- | ------------------------------------------------------------------------ | | `slack_message` | A single Slack message — includes channel posts, DMs, and thread replies | ## Experimental **Coming soon.** These evidence types are experimental: the schema is published so you can start sending data, but ingestion, querying, and entity resolution support is limited and the schema may change. | Evidence Type | Description | | ------------- | ------------------------------------------------------------------------------------------------------------------------------ | | `company` | An organization's profile — identity, firmographics, and ownership — as recorded in a source system | | `contact` | A person's professional profile — name, role, contact details, and the company they belong to — as recorded in a source system | | `deal` | A sales opportunity tracked through a pipeline — its value, stage, outcome, and the people and company it involves |