What does it mean that schema construction is the core skill of this curriculum?

Everything that follows builds on your ability to create inspect and improve schemas.

Example: A software architect joins a new company and inherits a codebase with no documentation, inconsistent naming, and tribal knowledge spread across a dozen engineers' heads. She does not start by writing code. She starts by constructing a schema: entity types, relationship maps, data flow diagrams, naming conventions. Her colleagues call this 'onboarding.' She calls it what it is — schema construction. Within two weeks, she can navigate the system faster than engineers who have been there for years. Not because she knows more facts. Because she has a better organizational structure for the facts she does know. Every subsequent decision she makes — refactoring, feature design, debugging — operates through that schema. The schema is not a byproduct of understanding. It is the mechanism of understanding.

Try this: Review the schemas you have built or encountered across Phase 11. Choose three — one you constructed from scratch, one you inherited and inspected, and one you discovered was flawed. For each, write a one-paragraph retrospective: What did it organize? What did it reveal that was previously invisible? What would you change now? Then write a single paragraph answering: What is your current process for constructing a new schema? Can you articulate it as a repeatable method? If not, draft one. This is your Schema Construction Protocol v1.0.