Keep a separate anomaly log with three fields

When This Fires

• Setting up an epistemic practice for tracking prediction accuracy
• When anomalies are currently scattered across various notes and journals
• After establishing schemas that generate regular predictions
• Complements Accumulate anomalies on a running list — trigger schema… (anomaly accumulation with threshold) by providing the logging structure

Common Failure Mode

Logging anomalies without the schema field: "Expected the meeting to go well, it didn't." Which schema predicted "meeting goes well"? Was it your model of this particular client? Your model of meeting structure? Your model of the topic's difficulty? Without tracing to a schema, the anomaly improves nothing specific.

The Protocol

Create a dedicated anomaly log (separate document, note, or database): (1) For each anomaly, record three fields: Expected: "Schema [X] predicted [specific prediction]." Actual: "What actually happened was [specific outcome]." Schema: "The failing schema is [name or statement of the specific model that generated the prediction]." (2) Review the log periodically (monthly) to detect per-schema accumulation (Accumulate anomalies on a running list — trigger schema…) and cross-schema patterns (Analyze validation records as a set — recurring failure…). The log's value compounds over time as the entry count grows.