Map schema dependencies in both directions — most-depended-on schemas need the most review
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.
Why This Is a Rule
Schema portfolios have dependency structures: some schemas are foundational (many others depend on them) and some are terminal (they depend on others but nothing depends on them). The foundational schemas — those appearing most frequently as prerequisites — are the highest-leverage points for review and validation because errors in them cascade through everything that depends on them.
Bidirectional mapping (prerequisites AND dependents) for each schema reveals the architecture. Prerequisites tell you what the schema rests on (if a prerequisite fails, this schema becomes unreliable). Dependents tell you what rests on this schema (if this schema fails, all dependents become unreliable). Schemas with many dependents are load-bearing and need the most careful review (High-dependency schemas need slower revision — each update cascades through all dependents).
Frequency analysis across all mappings identifies the structural hubs: schemas that appear as dependencies for 5+ other schemas are your epistemic infrastructure. These should be reviewed more frequently, tested more rigorously, and revised more carefully than peripheral schemas.
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.