Docs

Connect Claude Code, Cursor, Codex, or claude.ai. Save one confirmed decision from your work, then ask your AI to recall it in a later project or session.

Start here

Choose your client and start setup. Start free. No credit card. Pricing.

The Quickstart keeps connection, one saved decision or rule, and agent recall together. Connecting MCP is separate from optional history import or ongoing capture: you choose the source, space, provider, and what to accept.

• The Context Layer explains how saved context travels between tasks.
• Verified vs Asserted explains the live asserted and caveat statuses; verified is not live.

The four verbs

ClariLayer documents four verbs. recall and remember are the everyday continuity loop. bootstrap and reconcile cover structured Analytics context and its supported evidence paths.

• recall pulls relevant saved decisions, definitions, notes, and caveats for the current task. General work uses recall_context; supported Analytics or CRM work also uses get_analysis_context when relevant.
• remember saves a confirmed decision, constraint, definition, or correction for later sessions. It is an explicit agent-triggered write.
• bootstrap seeds Analytics context from SQL, dbt models, CLAUDE.md notes, a data dictionary or codebook, and semantic-layer models.
• reconcile checks a compatible Analytics SQL definition against warehouse actual_sample evidence or a HubSpot CRM contract against row-free crm_evidence; a mismatch is flagged as a caveat.

Saved context keeps its source and applicability visible. Correct, replace, supersede, or forget an entry when the work changes. General work memory is not independently reconciled; the asserted and caveat model applies to the supported Analytics evidence paths described above.

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

The Governed Context Edge supports shared team canon, governed write and explicit adoption. It is available as a hand-run private pilot:

• 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.