Sequences

Claims to search plan

Turn an application's claims into a search plan that you review and lock before it runs, then rank what the searches find and write the report.

The seven steps

  1. Claims: paste the claims, or read them from a publication XML file or a Word or text file.
  2. Review: the case reads each claim and marks what it recites: SEQ ID NOs, identity thresholds, fragments, CDRs, the changes a claim allows and letters read as any residue. Accept, reject or edit each finding.
  3. Plan: the searches your accepted findings call for, each with its reason. Lock as version 1 records the plan and its SHA-256, and only a locked version runs.
  4. Run: the case checks that the locked version has not changed since you locked it, then runs it.
  5. References: every reference the searches found, under the claim feature whose search found it, ranked by fixed rules.
  6. Report: the plan's searches, your notes and the references you kept, as PDF or Word.
  7. Log: every step. Each event holds the SHA-256 of the event before it, so a changed or deleted event shows, and Verify the log checks this.

When to use it

  • For a search of an application's sequence claims, when you need to show how each search follows from the claims.
  • When a colleague will review the work: hand the case to their account, with its searches and listing.

Example

Claim 1 of US 20260345742-A1, published 2026-11-05, recites giving a peptide with two fragments: XWLXRALIKRIQAZI (SEQ ID NO: 1) or a sequence at least 90% identical to it, and RZLPQLVXRLVLRXS (SEQ ID NO: 2) or a sequence at least 90% identical to it, where X and Z are any amino acid.

Review marks the two SEQ ID NOs, the 90% identity and the letters read as any amino acid. The draft plan's first search gives its reason:

"SEQ ID NOs: 1 to 2, in claim 1: 90% identity or more. Keeps 70% identity or more, since identity counts 3 of the 15 letters of each, X and Z, as differences."

References then reads each X and Z as any amino acid when it checks which matches meet the claim.

Learn more

To try it, read the claims from us12788009b2.xml, the full text of US 12788009-B2 with its 9 claims, in a case's Claims step. There, Use demo data fills the same claims.