Skip to main content
Clarifeye captures business knowledge in a structured form and exposes it to AI. Once you know these concepts, the rest of the docs read quickly.

​
Organization and knowledge store

Clarifeye has two layers. Organization is your company’s top-level account. Billing, plan, org-wide settings (SSO, security), shared organization context, and interview templates live here, so finance and admin only manage one contract. See Organization settings. Knowledge store is the working unit inside an organization: one self-contained body of expertise for a team, product, or use case. An organization can hold several. Permissions are scoped to a knowledge store rather than the organization, so the same person can be a contributor in one store and a user in another, while billing rolls up to a single invoice.

​
The three areas of a knowledge store

Every knowledge store is organized the same way, following the lifecycle of the knowledge inside it.

​
Clara

Clara is Clarifeye’s agent. She runs your interviews and adapts to whoever she’s talking to, analyzes what comes in, and works with you to consolidate it into artifacts. Clara does the analysis and the mechanical edits, you stay in control of every change.

​
Artifacts

Artifacts are the consolidated, trusted representation of your expertise. A knowledge store contains a small set:
  • Brief: a structured document presenting the key elements of the domain expertise.
  • Playbooks: multi-step descriptions of how an expert approaches a specific kind of query or task.
  • Mental map: the domain’s ontology, with a glossary of domain terms and the domains, classes, and relations that group concepts and link them together.
  • Corpus description: what source material the store draws on, how it’s organized, and how to navigate it.
  • General knowledge: task-level context that doesn’t live in any one document, the conventions and assumptions an expert just knows.
See Artifacts.

​
Sources

Sources are the raw material the store draws on, alongside interviews. They can be uploaded documents (PDF, docs, slides, spreadsheets) or connected sources pulled from Google Drive, SharePoint, and other connectors. See Sources.

​
Interviews

Interviews are the primary way knowledge is captured. You create an interview for a topic and assign it to the teammate who holds that knowledge. Clara conducts it asynchronously and in the contributor’s own language. See Interviews.

​
Signals

A signal is anything that should update the knowledge store: a correction, a gap, a piece of drift, or new context. Signals can come from anywhere people use the knowledge (an AI client, a task, or a manual note) and are centralized in one place so nothing is lost. Clara helps turn them into concrete updates, sometimes triggering a new interview. See Signals.

​
The Clarifeye skill and how AI consumes a store

Your team installs the Clarifeye skill in their AI client. The skill teaches the client how to work with Clarifeye, then uses the Model Context Protocol (MCP) to discover knowledge stores, inspect their knowledge, run retrieval, and raise signals. Each knowledge store behaves like a skill the client can draw on, faithful to what was captured. See Connect to AI clients.

​
Task

A task applies a knowledge store to real work at a point in time, like filling an RFP or drafting an answer that follows your process. Where Work with Clara changes the knowledge, Task uses it as it stands today. See Task.