# Remember (/docs/govern/remember)

Remember is the fourth move of the Trust Loop, and the one that makes the first
three compound. [Understand](/docs/govern/understand) captured the reasoning,
[Prevent](/docs/govern/prevent) recorded the verdicts, and [Fix](/docs/govern/fix)
attached the corrections. Remember persists all of it as enterprise memory, so
the next run does not start from zero. Without this step, governance is a logbook.
With it, governance is something the system learns from.

## Decisions accumulate on a graph [#decisions-accumulate-on-a-graph]

Every governed decision, with its claims, evidence, policy verdicts, and any
human corrections, is written to a shared reasoning and memory graph. It is not a
flat log of past runs. It is queryable context: a later run can read the prior
decision that matches its situation and start ahead of where the earlier one did.

Carrying the refund agent forward, the assumption a reviewer corrected in
[Fix](/docs/govern/fix), that the customer tier was inferred rather than
confirmed, is now memory. The next run on that customer reads it before it
reasons.

<div className="liquid-glass my-6 p-5">
  <div className="grid grid-cols-1 gap-4 sm:grid-cols-2">
    <TraceStepCard type="memory" title="Recall prior decision" subtitle="episodic memory . graph read" latency="0.12s" tokens="318" cost="$0.001" status="ok" policies="['#memory', 'prior correction']" />

    <TraceStepCard type="logic" title="Branch on customer tier" subtitle="tier == priority . from memory" latency="0.01s" status="ok" policies="['no assumption needed']" />
  </div>
</div>

The second run reads the correction and branches on the confirmed priority tier
straight away. The weak assumption never recurs, not because the prompt changed,
but because the decision that fixed it is part of the record the agent now draws
on. A memory read is a step like any other: it shows up on the trace, with its
own latency and cost, so you can always see what the agent recalled and where it
came from.

## What gets remembered [#what-gets-remembered]

Memory is not the raw transcript. It is the governed, structured outcome of each
run:

* **Decisions.** The claims an agent acted on and the evidence behind them.
* **Verdicts.** Which policies fired and how, so a precedent carries its
  governance with it.
* **Corrections.** Every human fix and escalation, attributed, so judgment made
  once is available everywhere.
* **Outcomes.** What actually happened after the decision, which is what lets the
  graph distinguish a good call from a lucky one.

<Callout intent="note" title="Memory is governed, and scoped">
  Everything in memory has already been through ingest, so detected PII / PHI / PCI
  was screened before anything was persisted (redacted when your data policy is
  set to mask), and the graph is scoped to your
  workspace. Remembering more does not mean retaining more sensitive data; the same
  [connection-time](/docs/govern/connect-your-agents) protections apply to what is
  recalled.
</Callout>

## Logging becomes learning [#logging-becomes-learning]

This is the move that changes the economics of running agents. When decisions are
remembered:

* **Corrections do not have to be repeated.** A fix made once is reused
  automatically, so the same mistake is caught earlier, or avoided entirely, on
  every later run.
* **Precedent accrues.** Similar decisions resolve consistently because the agent
  can see how the matching case was handled before.
* **Each run starts ahead.** The system gets more reliable the more it is used,
  rather than relearning the same lessons.

## Where memory lands: Collective Intelligence [#where-memory-lands-collective-intelligence]

Remember closes the Trust Loop for a single agent. The same graph spans every
agent and every team, which is where it stops being one agent getting better and
becomes an organisation getting better. Each team gets the benefit of every
governed decision that came before it. That compounding layer is
[Collective Intelligence](/docs/collective-intelligence): every capability
writes into it, every capability is powered by it, and it is the intelligence
behind the [Studios](/docs/studios/overview) your customers ship.

## Next steps [#next-steps]

<Cards>
  <Card title="Collective Intelligence" href="/docs/collective-intelligence" description="How governed decisions compound across every agent and team." />

  <Card title="Studios" href="/docs/studios/overview" description="Ship products on top of governed intelligence." />

  <Card title="Understand" href="/docs/govern/understand" description="Where the loop begins: the reasoning behind a decision." />

  <Card title="Connect your agents" href="/docs/govern/connect-your-agents" description="Bring an agent from any framework. It keeps running as-is." />
</Cards>