← Research

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.

broader / selected pathnarrower / retained space
Lexicon
Feature space
Selected path
Claim classes
Language

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.

LayerObjectPublic representation
LexiconWording classes and their different emphasisMember grid organized by function
Feature spaceSupported broader and narrower expressions for each technical dimensionNested scope ladder
SelectionThe subset used by the present claim setHighlighted path through the space
DependencyOne additional limitation or narrower expression at a timeParent → child relation
ClassMethod, system, and computer-readable-medium formsShared technical core with class-specific framing
CoverageSelected, retained, and unsupported positionsCoverage table with explicit status
SourceRelationTargetConsequence
Lexicon memberexpressesScope levelWording is checked against the selected level instead of being used to invent scope.
Claim limitationmaps toTechnical object + supportEach recited element remains traceable to the disclosure model.
Dependent claimnarrows / addsOne dimension or nodeThe scope change can be read without unpacking several bundled limitations.
Current pathselected fromSupported feature spaceSelected coverage and retained inventory remain visible as different states.

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.