harvest & propose

remember saves one fact at a time. When a working session has produced several durable facts — a definition you nailed down, a join you figured out, a gotcha you hit — you don't have to save them one by one. You can ask your agent to harvest them: it distills the conversation into a handful of candidate facts and stages them in your Context Inbox, where you accept or reject each.

This is a workflow, not a separate magic mode. It is built on two tools — propose (suggest one entry for review) and propose_batch (suggest several in one call) — and it is governed by three guardrails that keep it honest.

The guardrails (read these first)

• Explicit request only. Harvesting never happens in the background or "continuously." Your agent only does it when you ask — "save the durable facts from this conversation." There is no ambient capture.
• You approve everything. Nothing harvested is saved or recalled until you accept it in the Inbox. A proposal is a suggestion, not a write. Reject the ones you don't want.
• The transcript is never sent. ClariLayer never receives your conversation. Your agent reads the session locally and sends only the distilled candidate facts it proposes — the same files-not-data posture as bootstrap.

How to use it

Ask your agent, in your own words, to capture what the session produced. For example:

"We just worked out the MRR definition and the refunds caveat — save the durable facts from this conversation to ClariLayer for me to review."

Your agent will recall what's already saved (to avoid duplicates), distill the session into a small set of candidates (typically a handful, not dozens), and stage them in one propose_batch call. Each candidate carries a short rationale and provenance agent — so when you review it, it's clear the fact was suggested by your agent, not authored by you and not checked against your warehouse.

Review in the Inbox

Open your Context Inbox (the console link your agent returns) and step through the proposals:

• Accept a candidate and it becomes a normal saved entry — recallable from then on, with provenance agent.
• Reject the ones that aren't durable or aren't right. Nothing rejected is ever saved.

Accepted facts behave exactly like anything you remember yourself, with one honesty caveat: their provenance stays agent, and like every v1 entry they are asserted, never "verified." Knowing a fact came from your agent is not the same as checking it against your data — run reconcile if you want it grounded against your warehouse.

propose vs propose_batch

• propose — stage a single candidate entry for review. Useful when your agent surfaces one fact worth keeping.
• propose_batch — stage several candidates (bounded — up to ~25) in one call. This is the path harvest uses, and the right tool any time there's more than one thing to capture.

Both land in the Inbox; neither auto-saves. They are included in the free tier — the same tier as recall, remember, bootstrap, and reconcile.