# Fix (/docs/govern/fix)

Fix is the third move of the Trust Loop. [Understand](/docs/govern/understand)
showed you the reasoning, [Prevent](/docs/govern/prevent) stopped a bad action,
and now Fix is how you correct a decision that was wrong, in the exact context
that produced it. A correction here is not an edit to a log. It is a first-class
event on the run, attributed and kept, that changes what the system does next.

## Correct in context, not in a vacuum [#correct-in-context-not-in-a-vacuum]

A correction lands on the decision itself, against the claims, evidence, and
assumptions that produced it. That context is what makes the fix precise. You are
not retyping an answer; you are overturning a specific claim or replacing a
specific assumption, and the system records exactly what changed and why.

Take the refund run from [Understand](/docs/govern/understand). The agent leaned
on a low-confidence assumption, that the customer tier resolved to standard, and
auto-approved on the back of it. A reviewer who saw that weak link can correct it
directly on the step.

<div className="liquid-glass my-6 p-5">
  <div className="grid grid-cols-1 gap-4 sm:grid-cols-2">
    <TraceStepCard type="logic" title="Branch on customer tier" subtitle="tier == standard . original decision" latency="0.01s" status="error" policies="['assumption: low confidence']" />

    <TraceStepCard type="human" title="Correct customer tier" subtitle="reviewer . tier -> priority" status="ok" policies="['correction', 'carried forward']" />
  </div>
</div>

The reviewer replaced the inferred tier with the confirmed one. The original
decision stays on the record, marked as superseded, and the correction sits
beside it with who made it and when. Nothing is overwritten, because the point of
a system of record is that you can still see what the agent originally believed.

## A fix changes three things [#a-fix-changes-three-things]

A single correction propagates, in order:

1. **The decision.** The outcome is reversed or adjusted now. The refund that was
   auto-approved on a bad assumption is re-routed under the correct tier.
2. **The record.** The correction is appended to the run, attributed to the
   person who made it, with the before and after both visible. The run stays
   auditable, and the audit now includes the human judgment.
3. **The future.** The correction becomes reusable context. The next run that
   hits the same weak assumption starts from the corrected position rather than
   repeating the mistake. That hand-off is [Remember](/docs/govern/remember).

<Callout intent="success" title="A correction is an asset, not a patch">
  Most systems treat a fix as cleanup that disappears once applied. Here a
  correction is durable and reusable. Fixing the same problem twice is a signal
  that the first fix was not carried forward, and on AISquare it is, by default.
</Callout>

## Escalations land here too [#escalations-land-here-too]

A [Prevent](/docs/govern/prevent) policy that escalates rather than denies routes
the decision to a person, and this is where it arrives. The reviewer sees the
full reasoning, makes the call, and that judgment is recorded as a correction on
the run, exactly like any other fix. Escalation and correction are the same loop:
a human decision, attributed and carried forward.

## Why this matters [#why-this-matters]

* **Decisions get better in place.** You fix the cause on the run that produced
  it, not in a downstream patch that loses the context.
* **Human judgment is captured.** The reviewer's call becomes part of the
  permanent record and part of the system's future behaviour. This is the BI
  half of [AI + BI = CI](/docs/collective-intelligence#ai--bi--ci): brain
  intelligence, recorded where the artificial intelligence can reuse it.
* **The fix compounds.** A correction made once is available everywhere the same
  situation recurs, which is the bridge from Fix to
  [Remember](/docs/govern/remember).

## Next steps [#next-steps]

<Cards>
  <Card title="Remember" href="/docs/govern/remember" description="How decisions and corrections compound as reusable enterprise memory." />

  <Card title="Understand" href="/docs/govern/understand" description="Read the reasoning a correction acts on." />

  <Card title="Prevent" href="/docs/govern/prevent" description="Block or escalate an action before it runs." />

  <Card title="Collective Intelligence" href="/docs/collective-intelligence" description="How every governed decision compounds across teams." />
</Cards>