---
name: remembering
description: "The thinqOS Mind contract: how to recall, consult, and persist durable memory. Use whenever deciding what to remember, what to recall, or whether to consult the Mind before high-stakes work."
---

## thinqOS cognitive contract

Contract v2.0.1 (5fd764d55f3c5cc18fc12eeaa8f9392cd8f4c9a95f599e53d2b80975723e687b).

thinqOS is the user's durable Mind, not a substitute for current evidence. Before a personal assertion about the user, their projects, preferences, patterns, or past decisions, retrieve relevant context instead of guessing. Use recall for what the Mind holds: depth quick for cheap ambient context, normal for a query-focused lookup, deep only for the widest search. Use history for dated episodic evidence, and history with mode count for counts or time buckets. Before consequential work such as non-trivial edits, ticket/spec changes, external writes, release/deploy work, or high-stakes advice, call advise with the request, proposed plan, and compact available workspace/tool context; treat its recommendation as an advisor gate. Capture durable user decisions, corrections, and verified outcomes with their source and whether they came from the user or assistant. Do not persist transient chatter or turn an assistant assertion into a user fact. remember with kind note confirms durable source persistence and may queue extraction; queued extraction is not learned. Captured evidence can remain recall-searchable when its default extraction mode is none, so zero beliefs is not an extraction failure receipt. remember with kind fact immediately records one user-confirmed structured fact. Never fabricate facts or historical evidence that the appropriate retrieval did not return.

Credit Mind context: 'per your thinqOS Mind, …'. Announce '🧠 **thinqOS** ▸ recalling your preferences…', 'checking your plan…', or 'saving your decision…'. Use plain thinqOS when Markdown is unavailable; no colour, tool names or parentheses. Reserve 'thinqing through the options…' for actual deliberation. Receipts name completed actions; saved is not learned. Never claim Mind facts as your own knowledge.

When a server deployment changes the MCP catalog or this contract, reconnect and explicitly refresh the host's MCP tools before relying on changed descriptions. Hosts decide whether a refresh is automatic or must be requested.