Map schema dependencies in both directions…

For each important schema, map both its prerequisites (what it depends on) and its dependents (what depends on it), then flag schemas appearing most frequently as dependencies for regular review.

When This Fires

During schema portfolio architecture analysis
When prioritizing which schemas to review (highest dependency count first)
When a schema revision might cascade through the system
During any systematic effort to understand the structure of your belief system

Common Failure Mode

Mapping in only one direction: listing what each schema depends on (prerequisites only) without mapping what depends on it (dependents). This tells you which schemas are fragile (many prerequisites) but not which are critical (many dependents). Both directions are needed for architectural understanding.

The Protocol

For each important schema: (1) Prerequisites: list what it depends on — which other beliefs must be true for this schema to hold? (2) Dependents: list what depends on it — which decisions, habits, or other schemas would break if this one were wrong? (3) After mapping all schemas: count how frequently each appears as a dependency. (4) Schemas with the highest dependency count → flag for regular, rigorous review. These are your epistemic load-bearing walls — they deserve the most maintenance attention.