What is Korzybski general semantics?

Example: Your team's architecture diagram shows three microservices communicating through a message queue. In production, there's a fourth service nobody documented, the queue has a retry loop that creates duplicate messages, and one service bypasses the queue entirely during peak load. The diagram isn't wrong — it's a schema. It captures structure that was true at one point. But the system kept evolving while the diagram stayed frozen. Every decision made from the diagram alone is a decision made from an incomplete map.

This concept is part of Schema Foundations in the How to Think curriculum, which builds the epistemic infrastructure for schema foundations.