Principlev1

Review high-dependency schemas more slowly and deliberately

Review high-dependency schemas more slowly and deliberately than peripheral schemas, because revising foundational schemas requires updating all dependent schemas in a cascading revision process.

Why This Is a Principle

Derives from Schemas as Knowledge Organization Structures (schemas organize knowledge), Expertise as Domain-Specific Schema Organization (domain-specific expertise), and Hierarchical Chunking Expands Capacity (hierarchical organization with subsystems). Core schemas have high revision costs due to dependency chains, justifying higher evidential thresholds.

Source Lessons

L-0313

Evolution pace varies by domain

Some schemas need rapid evolution while others remain stable for years. The velocity at which a schema should change is not uniform — it depends on the domain. A schema governing JavaScript frameworks must update quarterly; a schema governing basic arithmetic can remain static for a lifetime. Treating all schemas with the same update cadence is a structural error: you will either exhaust yourself revising stable knowledge or cling to outdated models in fast-moving domains.

Connections

Derived From (3)

AxiomSchemas as Knowledge Organization Structures AxiomExpertise as Domain-Specific Schema Organization AxiomHierarchical Chunking Expands Capacity

Back to Concepts