Embodiment Description

Write detailed embodiments for: $ARGUMENTS

Embodiments describe HOW to make and use the invention -- they are the patent equivalent of experiment sections, but describe the invention rather than evaluating it empirically.

Constants

• MIN_EMBODIMENTS = 1, At least one complete embodiment required
• MAX_EMBODIMENTS = 3, Practical limit; more embodiments strengthen enablement
• EMBODIMENT_STYLE = detailed, detailed (full working example) or outline (sketch)
• REFERENCE_NUMERAL_PREFIX = 100, Starting reference numeral for first figure's components

Inputs

1. patent/INVENTION_DISCLOSURE.md, invention decomposition (core/supporting/optional features)
2. patent/CLAIMS.md, drafted claims that the embodiments must support
3. User-provided figures (if any) in any directory
4. patent/figures/numeral_index.md if it exists (from /figure-description)

Workflow

Step 1: Plan Embodiments

For each claim category (method, system, etc.), plan at least one embodiment:

Embodiment	Covers Claims	Type	Key Variations
1	Claims 1, X	Best mode / preferred	[primary implementation]
2	Claims 2, 3	Alternative	[different parameters/materials]
3	Claims 4, 5	Additional alternative	[different configuration]

Step 2: Write Each Embodiment

For each embodiment, write a detailed description following this structure:

Opening paragraph: "In one embodiment, [invention summary with reference to what is being described]."

Component/step-by-step description:

For method embodiments:

• Describe each step in order
• Reference figure numerals: "As shown in FIG. 1, at step 202, the processor 102 receives the input data 104..."
• Include specific parameters, ranges, and conditions
• Describe what happens at each decision point