Mappings

A mapping is the comparison between one patent and one product, worked through claim by claim. Patalyze takes each of the patent's claims, breaks it into the individual elements that must all be present for the product to infringe, and judges every element against the product's features, with the evidence behind each call.

This is the conceptual heart of Patalyze. A mapping is essentially a claim chart: the document a patent practitioner builds to argue, element by element, whether a product reads on a claim. It turns a paragraph of dense legal language into a verdict you can scan in seconds and defend line by line.

A mapping at a glance#

Take one patent and one of its independent claims. Patalyze splits the claim into its elements, then marks each one against the product. Read as a claim it is a block of legal text; read as a mapping it is a result you can take in at once.

In a single look: the product clearly has the cathode, the solid electrolyte and the current collector, most likely has the lithium-metal anode and the conductivity figure, and plainly lacks the protective coating. That one missing element holds the claim at 83%, a High read rather than a clean infringement.

When you reach for a mapping#

A mapping is the unit of evidence behind almost every patent question. You build one whenever you need to know how a specific claim lines up against a specific product, whether that product is your own or someone else's.

• Freedom to Operate: before you ship, check your own product against the live patents around it to confirm it is clear to make, use and sell.
• Infringement Detection: show, element by element, that someone else's product reads on a patent you hold.
• Invalidity: map a patent against an earlier product or reference to show its elements were already known.
• Portfolio valuation: see which patents actually read on real products, and how strongly, before you license or buy.

Claim element statuses#

A claim only reads on a product when every one of its elements is present, so the element is the unit of judgement. Patalyze gives each element one of five statuses.

• yes: the product clearly has this element.
• probably-yes: the product most likely has it, but the documents stop short of saying so outright.
• probably-no: the product most likely does not.
• no: the product clearly does not have it.
• omit: the element is set aside and left out of the score.

How a claim is scored#

Once every element has a status, Patalyze rolls them up into a single score for the claim. The score is the share of non-omitted elements judged present, counting both yes and probably-yes.

Treat the score as a measure of how close the read is, not as the verdict on its own. Infringement is all-or-nothing: a claim reads on a product only when every element is present. One missing element breaks the chain, however high the rest score. To keep that distinction visible, Patalyze sorts scores into four risk bands.

• Critical, at 100%, means every element is present (red).
• High, from 81 to 99%, means almost all elements are present (orange).
• Medium, from 61 to 80%, means a majority are present (yellow).
• Low, from 0 to 60%, means few or none are present (gray).

A Critical band on a live claim is the result you came here to find: a patent your product reads on, in force, owned by someone else. The lower bands are the patents you can set aside, at least for now.

The reasoning behind every verdict#

The glance above shows only the statuses. Open the full mapping and each element sits beside the reasoning for its verdict, with links back to the exact feature or document the call rests on.

A feature reference jumps to the matched product feature; a document reference opens the product PDF at the page the evidence came from. That chain, element to evidence, is what makes a mapping something you can trust and defend, rather than a number to take on faith.

How mappings get built#

Mappings appear on their own. When a product with features meets the patents in a research database, Patalyze maps every patent against that product in the background, so each patent-and-product pair already has a mapping by the time you go looking for it.

You stay in control of the result. Create a mapping by hand, override a verdict you disagree with, or omit an element you have ruled out, and the score updates to match. The same edits are open to an AI agent through the Patalyze tools, which can read and adjust mappings without anyone opening the app.

Reading mappings in your tables#

You rarely review mappings one at a time. The per-claim score surfaces in any patent or product table, as a colored cell where a patent and your product intersect. A whole field of comparisons reads at a glance, and the dangerous claims stand out by color.

Click a score and choose Open explanation to drop into the full mapping and walk the evidence for each element in turn.