For each schema, list its key assumptions…

When This Fires

• When documenting a new schema and wanting to future-proof it against environmental change
• During assumption registers (Track assumptions in a five-field register) when linking assumptions to monitoring
• When a schema's assumptions haven't been checked in months
• After an environmental shift that may have invalidated multiple schemas

Common Failure Mode

Listing assumptions without specifying observable indicators: "This schema assumes the market is growing." How would you know if it stopped growing? Without an observable indicator, you can't monitor the assumption — you'll only discover it broke after the schema fails. Every assumption needs a paired indicator.

The Protocol

For each schema: (1) List its 2-3 key environmental assumptions — the conditions it depends on. (2) For each assumption, specify an observable indicator of violation: "Assumption [X] would no longer hold if I observed [specific, monitorable event]." (3) Add these indicators to your monitoring: check them during scheduled reviews (Match review frequency to volatility) or set up automated alerts where possible. (4) When an indicator fires → the assumption may have broken. Investigate immediately and review the schema.