# Corrections land in files same-day

A correction or agreed behavior is written into the standing files the day it is agreed, or the other chats will never know it happened.

From the [Tips & tricks](../index.md#tips) section of [The Muse Field Guide](../index.md).

## The move

A correction, a preference, or an agreed behavior is written into the standing files or memory the day it is agreed. A promise that lives only in one chat's transcript does not exist for the other chats.

## When to use it

After every correction, ruling, or "from now on" agreement. This is the mechanism underneath every other practice in this inventory.

## Steps

1. Identify which file the lesson belongs in: persona, user facts, operating rules, or memory.
2. Make the edit the same day, with the incident cited.
3. Propagate to live chats when the rule cannot wait for their next start.
4. Verify later by conduct, not by the edit alone.

## The gotcha

Chats snapshot their instructions at the start; an old chat runs an old copy. The standing files are the only place a lesson becomes permanent, and delivery receipts prove the file moved, not that behavior changed.

## Where this came from

On October 20, 2026, a standing-rules note was propagated to 29 chats in five minutes, with the caveat recorded alongside: receipts prove delivery, not behavior change; behavior is proven later, by conduct.

Deep dive: [Practices and tips: the resource core](../deep-dives/practices.md)

Related resources: [Standing files as configuration](standing-files-as-configuration.md), [Steal this setup: standing files](standing-files-starter-kit.md)

Canonical page: https://www.niclydon.io/muse/items/corrections-land-same-day.html