Concepts

The Context Layer

How ClariLayer carries selected decisions, definitions, notes, and caveats across AI projects and sessions.

ClariLayer is a personal context layer for the AI tools you already use, delivered over MCP. It keeps selected decisions, definitions, notes, and caveats available across projects and sessions. That might be a launch decision, a project constraint, or an Analytics definition you would otherwise have to explain again in a new chat.

You choose what becomes durable context. Saved entries keep their source and scope, so your agent can recall the relevant context in a later task and you can correct or forget it when it no longer applies. Recall helps continuity; it does not guarantee that every saved statement is correct or that every client will call the tool.

A layer for durable working context

Project instruction files are useful, but they are one file in one client and usually need manual upkeep. ClariLayer gives compatible AI clients a shared place to recall context while you work. A saved entry can carry its source, provenance, applicability, and current trust status instead of becoming an unexplained line in a long prompt.

The basic loop has three parts:

Choose selected work worth carrying forward, either as you work or through a reviewed history import from a supported source.
Recall relevant entries inside your AI client, with source and scope visible.
Correct or forget context when a decision changes or should no longer apply.

Start from selected work

After connection, you can save one confirmed rule or decision directly. Where history support is available, you choose a supported local history source, space, and extraction provider, then review the proposed batch before accepting it. Continuous capture is a separate choice for the sources you select. ClariLayer does not archive raw transcripts; selected source content is processed by the extraction provider you choose.

For Analytics work, existing SQL, dbt models, CLAUDE.md notes, a data dictionary or codebook, and semantic-layer models can seed context. Those are the five Analytics bootstrap source kinds. See bootstrap for their exact contracts and limits.

Analytics reconciliation

General work context is saved with its source and applicability; it is not independently reconciled against an external source. Specialist Analytics context has two live reconcile adapters. For a compatible stored SQL definition, your agent runs the query with its own warehouse access and sends actual_sample result-shape evidence. For a HubSpot CRM contract, it collects bounded property metadata and distributions and sends row-free crm_evidence. ClariLayer compares what the definition declared with that supported evidence, and a mismatch surfaces as a caveat.

In the personal MCP reconcile path, ClariLayer does not receive your source credentials or execute SQL server-side, and it never calls HubSpot — your agent is the connector. The separately gated team connector surface uses only explicitly configured connectors under its own controls. Warehouse actual_sample may include an optional bounded preview with real values, so omit or redact it when result columns and row count are enough. HubSpot crm_evidence is row-free by contract: it contains declared property metadata and aggregate value distributions, never CRM records. Reconcile records a caveat on mismatch or leaves the entry asserted. The stronger verified status remains gated and is not part of the live public result contract. The honest claim is "reconciled and caveat-aware," and Verified vs Asserted explains exactly why.

In-flow, via MCP

ClariLayer lives inside the agent you already use. Claude Code, Cursor, and Codex connect to the production MCP server with a local context key; claude.ai connects to the same service as a custom Connector over OAuth. For general work, recall_context pulls relevant context from the selected authorized space while preserving source and applicability. For supported Analytics or CRM work, get_analysis_context provides the specialist recall path. Recall is a tool your agent decides to call. For local clients, the managed project rule tells the agent to recall ClariLayer context before relevant work.

Build continuity deliberately

Confirmed corrections and new notes persist when you or your agent explicitly save them. Later tasks can recall that context across claude.ai, Claude Code, Cursor, and Codex. Scope and provenance help your agent decide where an entry applies; you remain in control of correction and forgetting.

For teams

The personal context you build can become the foundation for the team story. The Governed Context Edge adds org canon, Diff-to-team, and adjudication in a hand-run private pilot; request access on the For teams page.