Keep schema evolution logs minimal (4 fields) and review…

Maintain schema evolution logs with minimum viable entries of four fields - date, schema affected, what changed, and what prompted the change - reviewed weekly, to generate a dataset about cognitive patterns that introspection alone cannot produce.

When This Fires

Setting up a deliberate schema evolution practice
When you want to understand how your thinking changes over time
During epistemic practice design alongside anomaly logs (Keep a separate anomaly log with three fields) and decision records (Record five elements at the moment of every significant…)
When introspection about "how I've grown" produces vague generalities rather than specific patterns

Common Failure Mode

Making entries too detailed: spending 10 minutes on a single log entry. This produces good individual records but kills sustainability. Two minutes maximum per entry. The dataset value comes from consistent, long-term logging — not from elaborate individual entries.

The Protocol

When a schema changes: (1) Log four fields in under 2 minutes: date, which schema, what changed, what prompted the change. (2) Weekly: scan the last 5-7 entries. Ask: patterns in which domains are updating? What types of evidence trigger changes? Any schemas that haven't appeared in the log for months? (3) Monthly: look at the full log. What meta-patterns emerge about your cognitive evolution? (4) The log becomes more valuable over time — 50+ entries reveal patterns that 5 entries can't.