Aspect toggle
The aspect toggle is the practice of describing the same change two ways, once as an activity ("grilling a steak," "filing taxes") and once as a before-and-after contrast ("raw to cooked," "owed to paid"), and alternating between the two. Each description catches things the other misses: an activity name can sound coherent while hiding what actually changes, and a before-and-after contrast can be precise while sounding nothing like how anyone would describe the activity. When the two disagree about what's happening, the disagreement points at where the description needs more work.
Definition
The methodological alternation between way-naming and difference-specification of the same transition, treating disagreements between them as diagnostic.
Two aspects of the same transition
Every transition can be regarded under two aspects. The way summarizes it by the activity in progress — "grilling a steak," "buying a car." The difference summarizes it by the condition-deltas between starting and resulting states — "raw-to-cooked," "unowned-to-owned-at-specified-price." Both apply to every transition; they describe the same underlying object from different angles, with the analyst picking which aspect to surface based on what the description is for.
The toggle is the discipline of alternating between them on the same transition. Name it as a way, specify it as a difference, then check whether the two descriptions are saying compatible things about the same underlying activity.
How the toggle produces fidelity
Each aspect alone has a characteristic failure mode. Way-naming alone allows hot-air to pass — names that sound coherent but have no specifiable difference-structure underneath them. "Onboarding," "engaging with the product," and "having a great experience" all read as valid way-names until something is asked of the underlying difference-structure, at which point the names dissolve. Difference-specification alone freezes on ideation: a complete condition-delta with no way-name attached is hard to communicate, hard to cluster with adjacent transitions, and hard to deploy in design work.
Alternating between them tests each against the other. A way-name that resists difference-specification flags as hot-air. A difference-specification that doesn't compress into a recognizable way flags as ungrounded analytic detail. The toggle is what produces and maintains scope fidelity at the naming layer — the constraint that a name accurately tracks the structure underneath it.
The activity-condition seam
The most common site where the two aspects disagree is the boundary between activity-naming and condition-naming. A way names an activity ("lift the pancake"); a difference names a condition-pair ("pancake-pan contact broken"). When the analyst names the same step both ways and the descriptions don't line up, the gap is where the fidelity or step-structure needs work — either the activity-name is overreaching its underlying condition-change, or the step is actually multiple sub-steps whose condition-changes the activity-name has bundled together.
Example
A cook breaking down pancake-cooking steps names one step "lift the pancake" (way) and specifies its difference as "{pancake-pan contact = continuous} to {pancake-pan contact = broken}." On comparison, the way-name imports a vertical-motion component the condition-spec doesn't ratify — the spec only requires that contact is broken, not that the pancake is elevated. The disagreement flags that one of the descriptions needs rework: either the way-name overreaches (and "release the pancake" would be more faithful), or the difference-spec under-reaches (and elevation belongs in the condition-change). Which resolution applies depends on what the next sub-transition needs as its starting state.