Document what the old belief was protecting — the lost…
For each evolved schema, document not just old and new versions but also what the old belief was protecting or enabling, because identifying the lost function reveals emotional costs of revision and increases honesty about unrevised beliefs.
When This Fires
- During schema evolution logging (Log schema changes with 4 fields) as an additional field
- When a schema revision feels emotionally costly despite being epistemically clear
- When a belief you know is wrong persists despite evidence against it
- During any deep self-reflection about why certain beliefs resist change
Common Failure Mode
Documenting only the epistemic change: "Old: X was true. New: Y is true." This misses the functional dimension entirely. The full entry: "Old: X was true. New: Y is true. What X was protecting: [specific psychological function the old belief served]." Without the protection field, you have a record of what changed but not why it was hard to change or why similar beliefs might resist change in the future.
The Protocol
For each schema evolution entry, add a fifth field: (1) Date, old belief, triggering evidence, new belief (Log schema changes with 4 fields). (2) What the old belief was protecting or enabling: "The old belief [protected me from / enabled me to / saved me from having to] [specific function]." (3) Read the protection field honestly. Is the lost function still needed? If yes → you may need to find an alternative way to serve that function under the new schema. If no → the revision is cleaner than expected. The protection field makes the emotional cost visible, which makes both revision and non-revision more honest.