Claim Strategy
Claim strategy separates four objects that drafting often collapses: the supported feature space, the path selected for one claim set, the claim classes that express it, and the language used at each level of scope.
Did the scope change, or did only the wording change?
Receiving, obtaining, and accessing can emphasize different ingress conditions; replacing one with another does not by itself move from a species to a supported genus.
What is in the disclosure but outside the current claim path?
A disclosure can contain supported alternatives, axes, and narrower species not selected in the present set. Speculative material is kept separate from supported inventory.
Can each dependent claim be explained as one change?
A dependent path is easier to inspect when it adds one supported node, narrows one dimension, or opens one supported species at a time.
Lexicon view
Terms grouped by the function they perform in a claim, not by superficial synonymy.
Feature-space view
Each concept shown with scope, support, and available alternative expressions.
Selection view
The current claim path distinguished from retained and unsupported positions.
Mapping audit
Each limitation linked back to a technical object and support record.