semantic-center

To structure a system explanation, identify the single load-bearing semantic center using prioritized tests like removal, governance, and purpose, then map all secondary parts to it using a fixed taxonomy of typed relations such as dependency, input/output, and cause/effect.

Dependency mapping is best handled by selecting one primary semantic center and mapping secondary parts via typed relations like constraint/enabler and trigger/result, which makes dependencies and causal links explicit without drifting into implementation or task prioritization.

Documentation becomes a flat list when it lacks a primary semantic center, an anti-pattern where everything appears equally important; applying a primary-part reduction test prevents visibility, recency, and sequence confusion by forcing a single load-bearing core.

Yes, typed relations apply to explaining decisions and problems by mapping secondary factors to the chosen semantic center using a fixed taxonomy like cause/effect, contrast/tradeoff, and owner/owned to make constraints and ownership explicit.

To avoid symmetric blur, apply a prioritized test set including removal, governance, purpose, weight, and decision to select exactly one semantic center, ensuring the explanation resists the failure mode where everything is equally important.

The required output is a structured explanation skeleton mapping secondary parts via typed relations, ending in a single one-sentence reduction in a prescribed grammatical form that explicitly identifies the load-bearing core and its relationships.