Patent Drafting

Patent Drafting

Identity

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

• For Creation: Always consult `references/patterns.md`. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
• For Diagnosis: Always consult `references/sharp_edges.md`. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
• For Review: Always consult `references/validations.md`. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Patent Drafting

Patterns

Golden Rules

---

Rule

Claim first, then spec

Reason

Claims define what you protect

---

Rule

One chance for specification

Reason

Can't add new matter later

---

Rule

Antecedent basis

Reason

Every claim term must be introduced

---

Rule

Means-plus-function = narrow

Reason

Tied to spec + equivalents only

---

Rule

Dependent claims = fallback

Reason

If independent fails, dependents may survive

Application Structure

• Title - Concise, descriptive
• Abstract - 150-word summary
• Background - Prior art limitations
• Summary - Invention overview
• Drawings - Figures + reference numbers
• Detailed Description - Enable one of skill
• Claims - Legal scope of protection

Claim Categories

Method

A method of processing data...

System

A system comprising: processor, memory...

Apparatus

An apparatus for measuring...

Crm

A non-transitory computer-readable medium...

Product By Process

A widget produced by the method of claim 1

Transitional Phrases

Comprising

OPEN - Allows additional unlisted elements (preferred)

Consisting Of

CLOSED - Excludes additional elements

Consisting Essentially Of

PARTIALLY OPEN - Rarely used

Patentability Tests

Novelty 102

ALL elements in ONE reference = anticipated

Obviousness 103

Elements known + motivation to combine = obvious

Anti-Patterns

---

Pattern

Too narrow claims

Problem

Easy to design around

Solution

Start broad, add fallbacks

---

Pattern

Missing antecedent

Problem

112(b) rejection

Solution

Track every 'the' reference

---

Pattern

Means-plus-function

Problem

Narrow to spec embodiments

Solution

Use structural language

---

Pattern

No dependent claims

Problem

No fallback if independent fails

Solution

3-5 dependents per independent

---

Pattern

Spec too brief

Problem

Enablement rejection

Solution

Include alternatives and examples

---

Pattern

Jargon without definition

Problem

Indefiniteness

Solution

Define all technical terms

Patent Drafting - Sharp Edges

Means-Plus-Function Invokes 35 USC 112(f)

Id

means-plus-function-trap

Severity

critical

Summary

Claim term 'means for' limits scope to spec embodiments only

Symptoms

• Claim scope unexpectedly narrow
• Competitors avoid infringement with different implementations
• Court limits claim to spec examples

Why

Using "means for [function]" language triggers 112(f) interpretation. The claim term is limited to the corresponding structure in the specification plus equivalents. If you only described one way to do something, that's all your claim covers.

Gotcha

Claim: "means for processing data"

Spec only describes: "Processing module 102 uses algorithm X"

Result: Claim limited to algorithm X and equivalents

• Algorithm Y that achieves same result? Not covered!

Solution

Use structural language instead:

BAD: "means for processing data" GOOD: "a processor configured to execute instructions that cause..."

BAD: "means for storing data" GOOD: "a memory storing instructions that, when executed, cause..."

Include multiple embodiments in spec for each functional term.

Missing Antecedent Basis Causes 112(b) Rejection

Id

antecedent-basis-missing

Severity

high

Summary

'The' references something never introduced

Symptoms

• Office action cites 35 USC 112(b)
• Claim term lacks antecedent basis
• Indefiniteness rejection

Why

When you write "the data" in a claim, there must be an earlier reference to "a data" or "data." Otherwise, the examiner doesn't know what "the data" refers to.

Gotcha

"A method comprising: processing the data..." ← What data?

"A system comprising: wherein the controller performs..." ← What controller?

Solution

Every "the [noun]" must have a prior "a [noun]" or "[noun]":

"A method comprising: receiving a data set; processing the data set..." ← Proper antecedent

For multiple instances: "a first processor... a second processor... wherein the first processor communicates with the second processor"

New Matter Cannot Be Added After Filing

Id

new-matter-added

Severity

critical

Summary

Amendments must be supported by original specification

Symptoms

• Examiner rejects amendment as new matter
• Cannot claim feature not in original spec
• Continuation doesn't help - same spec

Why

35 USC 132 prohibits adding new matter after filing. The specification is frozen at the filing date. If you didn't disclose a feature, you can't claim it - ever. This is why thorough initial disclosure is critical.

Gotcha

Original spec: "The widget processes data using algorithm A"

Later amendment: "...wherein the widget uses machine learning"

Result: REJECTED - ML never disclosed in original application

Solution

At drafting time, include:

• All known embodiments
• Alternative implementations
• Future variations you might want to claim
• "In some embodiments" language for flexibility

Example: "In some embodiments, the processing includes machine learning, neural networks, or statistical methods"

Software Claims Rejected as Abstract Ideas

Id

abstract-idea-101

Severity

high

Summary

Alice/Mayo creates 101 rejection for software patents

Symptoms

• Examiner cites Alice Corp. v. CLS Bank
• Claims characterized as 'abstract idea'
• Told to 'integrate into practical application'

Why

Post-Alice, many software claims are rejected as abstract ideas. The two-step test asks: (1) Is it directed to an abstract idea? (2) If so, does it add "significantly more"? Generic computer implementation doesn't satisfy step 2.

Gotcha

"A method comprising: receiving user input; calculating a result based on the input; displaying the result"

Examiner: "This is the abstract idea of performing calculations"

Solution

Integrate practical application:

1. Claim specific technical improvement: "...thereby reducing memory usage by 40%"

2. Claim unconventional technical steps: "...using a convolutional neural network with architecture X"

3. Claim specific hardware integration: "...wherein the sensor captures real-time data at 1000Hz"

4. Focus on HOW, not WHAT: Don't just claim the goal; claim the novel technical means

Single Embodiment Limits Claim Scope

Id

single-embodiment-spec

Severity

medium

Summary

Specification only describes one way - claims limited

Symptoms

• Examiner narrows claim to match spec
• No support for broader claim language
• Can't claim alternatives not disclosed

Why

Claims are limited by the specification. If you only describe one embodiment, your broad claim language may be construed narrowly. Competitors can use alternative implementations you never disclosed.

Gotcha

Claim: "A method for processing images..." Spec: Only describes processing with algorithm X

Court/examiner: "Processing" means algorithm X because that's all the spec discloses

Solution

Describe multiple embodiments:

"In one embodiment, image processing uses algorithm X. In another embodiment, algorithm Y may be used. In yet another embodiment, machine learning models such as CNNs, transformers, or ensemble methods may be employed."

Use open-ended language: "Processing may include, but is not limited to..."

Patent Drafting - Validations

Means-Plus-Function Language Detected

Id

means-plus-function

Severity

warning

Type

regex

Pattern

• means for \w+
• module for \w+
• mechanism for \w+

Message

Means-plus-function language triggers 112(f) narrow interpretation.

Fix Action

Replace with structural language: 'a processor configured to...'

Applies To

• */claim*.txt
• */patent*.md

Potential Missing Antecedent Basis

Id

missing-antecedent

Severity

warning

Type

regex

Pattern

• the \w+(?!.*(?:a|an) \1)
• said \w+(?!.*(?:a|an) \1)

Message

Check that 'the [noun]' has a prior 'a [noun]' introduction.

Fix Action

Add antecedent: 'a [noun]' before 'the [noun]'

Applies To

• */claim*.txt

Closed Claim Language

Id

consisting-of-closed

Severity

info

Type

regex

Pattern

• consisting of

Message

'Consisting of' is closed transitional phrase - excludes unlisted elements.

Fix Action

Consider 'comprising' for open claim unless closure is intentional

Applies To

• */claim*.txt

No CRM Claim in Software Application

Id

no-crm-claim

Severity

info

Type

regex

Pattern

• method.comprising(?!.non-transitory.*computer-readable)

Message

Consider adding CRM claim for software inventions.

Fix Action

Add: 'A non-transitory computer-readable medium storing instructions...'

Applies To

• */claim*.txt

Generic Computer Implementation

Id

abstract-generic-computer

Severity

warning

Type

regex

Pattern

• a computer.*performing
• a processor.*executing
• generic.*computer

Message

Generic computer implementation may face 101 rejection.

Fix Action

Add specific technical improvement or unconventional implementation

Applies To

• */claim*.txt
• */patent*.md