Docs

ClariLayer is a personal context layer for your AI coding agent, delivered over MCP. Connect it once to Claude Code, Cursor, Codex, or claude.ai, and your agent stops re-explaining your data every session: it can recall the definitions, joins, schema notes, and gotchas you have saved, then reconcile supported SQL definitions against warehouse evidence and HubSpot CRM contracts against row-free CRM evidence.

Start here

• Quickstart connects a CLI agent with a context key or production claude.ai over OAuth, then confirms the connection so your agent can recall your context.
• The Context Layer explains the mental model: why a personal, reconciled, in-flow context layer beats a hand-typed CLAUDE.md.
• Verified vs Asserted explains the trust-status model — asserted and caveat are live, while the stronger verified status is gated and not part of the public result contract.

The four verbs

After you connect, your agent has four headline, everyday verbs:

• bootstrap bulk-ingests SQL, dbt models, CLAUDE.md notes, a data dictionary / codebook, and semantic-layer models so you do not start from an empty store.
• recall pulls the most relevant saved context for the current task, in-flow (get_analysis_context).
• remember saves a definition, schema note, join, or gotcha so your agent retains it across sessions.
• reconcile checks a compatible stored SQL definition against warehouse actual_sample evidence or a HubSpot CRM contract against row-free crm_evidence; a mismatch is flagged as a caveat.

Going deeper

• AI Agent Context Guide walks through the recall-first working loop in practice.
• The completion loop uses context_checkpoint to persist the agent's bounded managed-protocol declaration and validate its referenced ClariLayer objects. It does not independently prove that an entry changed, external code deployed, or a source result is correct.
• SaaS Metrics Definition Library is a reference for the metric definitions teams argue about most: ARR, MRR, NRR, churn, and pipeline coverage.

For teams

ClariLayer starts as your personal context layer. As teams adopt it, the personal context analysts build merges into shared, owned, governed metric context — ownership, approval, and one right definition. That team strand is kept and reachable, but secondary to the single-player wedge:

• For teams covers where ClariLayer goes as teams adopt it: personal context layers joined by a governed Context Edge — propose your definition up, adopt the team's canon down, with agency.
• API v1 overview documents the read-only Contract API an external workflow or BI tool can use to read a governed metric's canonical context.