dsh-aris-panel 0.1.0

package/skills/shared-references/output-versioning.md

@@ -0,0 +1,111 @@
+# Output Versioning Protocol
+
+When writing any output file that would overwrite an existing file, use timestamped filename + fixed-name latest copy:
+
+1. Write output to timestamped file: `{FILENAME}_{YYYYMMDD_HHmmss}.md` (or `.json`, `.tex` as appropriate)
+   - Timestamp precision to seconds to reduce collisions. In the rare case of sub-second conflicts, append `_2`, `_3` etc.
+   - Place the timestamped file in the same directory as the fixed-name file
+2. Copy the same content to the fixed-name file: `{FILENAME}.md` (overwrites the previous latest copy)
+3. Downstream skills always read the fixed-name file — they do not need to know about timestamps
+
+## Directory Structure
+
+All ARIS output files are organized by workflow stage:
+
+```
+project/
+├── CLAUDE.md                              # Dashboard (root — read by all stages)
+├── findings.md                            # Cross-stage discovery log (root — append-only)
+├── MANIFEST.md                            # Output tracking manifest (root)
+│
+├── idea-stage/                            # W1: Idea Discovery
+│   ├── IDEA_REPORT.md                     # Latest copy
+│   ├── IDEA_REPORT_20250615_143022.md     # Timestamped version
+│   ├── IDEA_CANDIDATES.md
+│   ├── REF_PAPER_SUMMARY.md
+│   └── docs/
+│       └── research_contract.md
+│
+├── refine-logs/                           # W1.5: Experiment Planning & Refinement
+│   ├── EXPERIMENT_PLAN.md
+│   ├── EXPERIMENT_TRACKER.md
+│   ├── EXPERIMENT_RESULTS.md
+│   ├── FINAL_PROPOSAL.md
+│   ├── PIPELINE_SUMMARY.md
+│   ├── REFINE_STATE.json
+│   ├── REVIEW_SUMMARY.md
+│   ├── REFINEMENT_REPORT.md
+│   └── round_N_*.md
+│
+├── review-stage/                          # W2: Auto Review
+│   ├── AUTO_REVIEW.md
+│   └── REVIEW_STATE.json
+│
+├── paper/                                 # W3: Paper Writing
+│   ├── main.tex
+│   └── roundN/
+│
+└── research-wiki/                         # Persistent knowledge base
+```
+
+## What to Timestamp
+
+Files that get overwritten on re-runs:
+- `IDEA_REPORT.md`, `IDEA_CANDIDATES.md`, `REF_PAPER_SUMMARY.md`
+- `EXPERIMENT_PLAN.md`, `EXPERIMENT_TRACKER.md`, `EXPERIMENT_RESULTS.md`
+- `FINAL_PROPOSAL.md`, `PIPELINE_SUMMARY.md`
+- `AUTO_REVIEW.md` (when starting a new review loop, not within a loop)
+- `paper/main.tex`
+- State files: `REFINE_STATE.json`, `REVIEW_STATE.json`
+
+## What NOT to Timestamp
+
+- **Append-only files**: `findings.md`, `research-wiki/log.md` — these accumulate entries, not overwrite
+- **Per-round files**: `refine-logs/round_N_*.md` — already versioned by round number
+- **Dashboard**: `CLAUDE.md` — single source of truth, always latest
+- **MANIFEST.md** — append-only tracking file
+
+Never delete timestamped files. They are the permanent history.
+
+## Path Fallback Rule (Backward Compatibility)
+
+Skills that **read** stage-scoped files must fall back to the old root-level location for projects created before this layout was introduced:
+
+```
+# For idea-stage files:
+Read from idea-stage/IDEA_REPORT.md
+If not found → fall back to ./IDEA_REPORT.md
+
+Read from idea-stage/IDEA_CANDIDATES.md
+If not found → fall back to ./IDEA_CANDIDATES.md
+
+# For review-stage files:
+Read from review-stage/AUTO_REVIEW.md
+If not found → fall back to ./AUTO_REVIEW.md
+
+Read from review-stage/REVIEW_STATE.json
+If not found → fall back to ./REVIEW_STATE.json
+```
+
+Skills that **write** always use the stage-scoped path (never write to root). This ensures new runs migrate output forward while old projects continue to work.
+
+## Migration for Existing Projects
+
+If you find root-level files (`IDEA_REPORT.md`, `AUTO_REVIEW.md`, etc.) and the stage directories do not yet exist, you may optionally offer to migrate:
+
+```
+📁 Found legacy root-level files. Migrate to stage directories?
+  mv IDEA_REPORT.md idea-stage/IDEA_REPORT.md
+  mv AUTO_REVIEW.md review-stage/AUTO_REVIEW.md
+  (etc.)
+Only do this if the user confirms — do not auto-migrate silently.
+```
+
+## Stale State Detection
+
+Before reading a state file (`REFINE_STATE.json`, `REVIEW_STATE.json`, `DSE_STATE.json`):
+1. Check the file's last modified time via `ls -la` or `stat`
+2. Default staleness threshold: **24 hours** (individual skills may override — e.g., `auto-review-loop` uses 24h, `research-refine` uses 24h). If a skill defines its own threshold, that takes precedence.
+3. If older than the threshold, warn the user:
+   "⚠️ State file {filename} is {N} hours/days old. It may be from a previous research direction. Continue with this state, or start fresh?"
+4. If the user chooses to start fresh, write a timestamped archive copy and proceed without the old state

package/skills/shared-references/patent-format-cn.md

@@ -0,0 +1,199 @@
+# CNIPA Patent Format Guide (中国专利格式指南)
+
+Use this reference when drafting Chinese patent applications for filing with CNIPA (国家知识产权局).
+
+## When to Read
+
+- Read when `JURISDICTION = "CN"` or `JURISDICTION = "ALL"`
+- Read before writing claims in Chinese format
+- Read during `/jurisdiction-format` for CN output
+- Read when choosing between invention patent (发明专利) and utility model (实用新型)
+
+## Applicable Law and Regulations
+
+- Patent Law of the People's Republic of China (中华人民共和国专利法, 2020 amendment)
+- Implementing Regulations of the Patent Law (专利法实施细则)
+- Guidelines for Patent Examination (专利审查指南, 2023 revision)
+
+## Document Structure
+
+A CNIPA patent application consists of:
+
+### 1. 权利要求书 (Claims)
+
+**Format rules:**
+- Independent claims use two-part form (two-part form / 两部式):
+  - 前序部分 (Preamble): Known technical features shared with closest prior art
+  - 特征部分 (Characterizing part): After "其特征在于" -- the inventive features
+- Dependent claims: "根据权利要求X所述的..., 其特征在于..."
+- Each claim must be a single technical solution
+- Claims must be clear, concise, and supported by the description
+- Method claims: "一种...的方法，其特征在于，包括以下步骤："
+- Apparatus claims: "一种...的装置/设备/系统，其特征在于，包括："
+
+**Numbering:**
+- Arabic numerals: 权利要求1, 权利要求2, ...
+- Dependent claims must reference prior claims by number
+- Multiple dependent claims are allowed but should be used sparingly
+
+**Example structure:**
+```
+1. 一种[技术主题]的方法，包括：
+   前序部分的已知技术特征；
+   其特征在于，还包括：
+   特征部分的技术特征。
+
+2. 根据权利要求1所述的方法，其特征在于，所述[技术特征]具体为...
+```
+
+### 2. 说明书 (Description)
+
+Required sections in order:
+
+#### 发明名称 (Title)
+- Concise, typically under 25 characters
+- Must reflect the technical content, not marketing language
+- No trademarks, no "新型" or "改进的"
+- Format: "一种[技术领域]的[技术主题]" for methods; "[技术领域]的[技术主题]装置" for apparatus
+
+#### 技术领域 (Technical Field)
+- 1-2 sentences identifying the technical domain
+- Use IPC classification references where appropriate
+
+#### 背景技术 (Background Technology)
+- Describe the closest prior art (引用现有技术)
+- Identify specific deficiencies (不足之处)
+- This is NOT a literature review -- it directly sets up the problem the invention solves
+- Must cite specific prior art documents where possible
+
+#### 发明内容 (Summary of Invention)
+Three parts:
+1. **要解决的技术问题** (Technical Problem to Solve): Derived from background deficiencies
+2. **技术方案** (Technical Solution): How the invention solves the problem, matching claim scope
+3. **有益效果** (Beneficial Effects): Quantifiable advantages over prior art
+
+#### 附图说明 (Brief Description of Drawings)
+- List each figure with a one-sentence description
+- Format: "图1是...的示意图；图2是...的流程图；"
+
+#### 具体实施方式 (Detailed Description of Embodiments)
+- At least one complete embodiment (实施例)
+- Reference numerals must match figures exactly
+- Describe in sufficient detail for a skilled person to practice
+- Include specific parameters, ranges, materials where applicable
+- Multiple embodiments strengthen the application
+
+### 3. 说明书摘要 (Abstract)
+
+- Maximum 300 words (typically Chinese characters)
+- Must summarize the technical solution and key advantages
+- Include the most representative claim number
+- Abstract is for search purposes only, not for interpreting scope
+
+### 4. 摘要附图 (Abstract Drawing)
+
+- Select the most representative figure
+- Must be one of the figures in the application
+
+### 5. 附图 (Drawings)
+
+- Numbered sequentially: 图1, 图2, ...
+- Reference numerals in Arabic: 101, 102, 103...
+- No text in figures except reference numerals and standard terms
+- Black and white preferred; color only when necessary
+
+## Word Limits and Practical Constraints
+
+| Item | Limit |
+|------|-------|
+| Title | Typically under 25 characters |
+| Abstract | 300 words maximum |
+| Claims | No hard limit, but examiners prefer focused sets (10-20 claims typical) |
+| Description | No hard limit, but excessive length delays examination |
+| Figures | No hard limit, but cost increases per page |
+
+## Fees (2026 approximate, in CNY)
+
+| Item | Invention (发明专利) | Utility Model (实用新型) |
+|------|---------------------|------------------------|
+| Filing fee | 900 | 500 |
+| Claims fee (per claim over 10) | 150 each | 150 each |
+| Examination fee (invention only) | 2500 | N/A |
+| Annual fees | Increasing by year | Increasing by year |
+
+## Utility Model (实用新型) Specific Rules
+
+- Covers only product shape/structure or combination thereof (产品的形状、构造或其结合)
+- NO method claims allowed
+- NO process claims allowed
+- Lower inventive step requirement than invention patent
+- No substantive examination -- only formal examination
+- Faster grant: typically 6-8 months vs. 2-4 years for invention
+- Shorter protection: 10 years vs. 20 years
+
+## Critical Chinese Patent Writing Rules
+
+### Claims (权利要求书)
+
+1. **Continuous numbering required**: Claims must be numbered 1, 2, 3, ... sequentially without gaps. Independent and dependent claims are intermixed, NOT grouped separately. Even if independent claims are 1, 5, 8 in the hierarchy, the final numbering must be 1-10 continuous.
+
+2. **No experimental results in claims**: Claims must describe ONLY structural features or method steps. Do NOT include detection principles, signal characteristics, or measurement results (e.g., "产生负脉冲信号", "谐振频率下降" belong in the specification, not in claims).
+
+3. **Standard claim opening formats**:
+   - Product: "1. 一种[主题]，其特征在于，包括：[组件A]、[组件B]和[组件C]。"
+   - Method: "1. 一种[主题]的方法，其特征在于，包括以下步骤：步骤S1...；步骤S2...；"
+   - System: "1. 一种[主题]的系统，其特征在于，包括：[组件]。"
+
+4. **Two-part form (两部式)**: The "其特征在于" separates known features (before) from inventive features (after). Known features should be minimal — just enough to set context.
+
+### Specification (说明书)
+
+5. **No experimental data in 具体实施方式**: The detailed description teaches HOW to make and use the invention. Do NOT include test results, accuracy percentages, detection rates, precision values, or comparative performance data. These belong in papers, not patents.
+
+   WRONG: "传感器对直径超过150μm的金属颗粒实现了100%的检测精度，即使在检测限处仍保持94%的高精度。"
+   RIGHT: "当不锈钢颗粒通过间隙传感区域时，谐振频率下降。颗粒直径越大，频率偏移幅度越大。"
+
+6. **Formulas and principles go in 具体实施方式, NOT 发明内容**: The "发明内容" section is a high-level overview (problem + solution + advantages). Detailed derivation, RLC circuit models, and mathematical formulas belong in "具体实施方式".
+
+7. **有益效果 must be qualitative or derived from structure**: Avoid specific numerical claims unless they appear in the claims themselves. Use structural reasoning: "由于采用了...结构，因此具有...效果。"
+
+8. **Use "所述" consistently**: After first introducing a component with "一个" or "一种", all subsequent references must use "所述" (the said). Example: "一个处理器" → "所述处理器".
+
+### Common CN Patent Phrases
+
+| Usage | Correct Chinese |
+|-------|----------------|
+| Introducing invention | "本发明提供一种..." |
+| Problem statement | "本发明要解决的技术问题是..." |
+| Solution intro | "为解决上述技术问题，本发明采用的技术方案是：" |
+| Benefits intro | "本发明的有益效果是：" |
+| Embodiment intro | "下面结合附图和实施例对本发明作进一步详细描述。" |
+| Referring to figure | "参照图1" |
+| Component reference | "印刷电路板（101）" on first mention, "印刷电路板101" thereafter |
+
+## Chinese Patent Terminology Glossary
+
+| Chinese | English | Usage |
+|---------|---------|-------|
+| 权利要求 | Claim | "权利要求1" |
+| 说明书 | Description | "如说明书所述" |
+| 发明名称 | Title of invention | |
+| 技术领域 | Technical field | |
+| 背景技术 | Background technology | |
+| 发明内容 | Summary of invention | |
+| 附图说明 | Brief description of drawings | |
+| 具体实施方式 | Detailed description of embodiments | |
+| 其特征在于 | Characterized in that | Claim divider |
+| 所述 | Said / The (definite article) | "所述处理器" |
+| 包括 | Comprising (open) | |
+| 由...组成 | Consisting of (closed) | Use rarely |
+| 可选地 | Optionally | |
+| 优选地 | Preferably | |
+| 在一个实施例中 | In one embodiment | |
+| 在另一个实施例中 | In another embodiment | |
+| 进一步地 | Further / Furthermore | Dependent claims |
+| 其中 | Wherein | |
+| 与...通信 | In communication with | |
+| 响应于 | In response to | |
+| 基于 | Based on | |
+| 使得 | Such that | |

package/skills/shared-references/patent-format-ep.md

@@ -0,0 +1,173 @@
+# EPO Patent Format Guide
+
+Use this reference when drafting European patent applications for filing with the EPO.
+
+## When to Read
+
+- Read when `JURISDICTION = "EP"` or `JURISDICTION = "ALL"`
+- Read before writing claims in EP format
+- Read during `/jurisdiction-format` for EP output
+
+## Applicable Law
+
+- European Patent Convention (EPC), 2000 revision
+- Rules 42-43 EPC (Description and Claims format)
+- EPO Guidelines for Examination, Part F
+- Protocol on the Interpretation of Article 69 EPC
+
+## Document Structure
+
+### 1. Claims (Rule 43 EPC)
+
+**Two-part form is MANDATORY for independent claims (Rule 43(1) EPC):**
+
+The claim must contain:
+- **(a) Characterising portion**: A statement indicating:
+  - The category/title of the invention ("A method of...", "An apparatus for...")
+  - Those features of the invention which are necessary to define the claimed subject-matter but which, in combination, form part of the prior art
+- **(b) Characterising portion**: After the phrase "characterised in that" (or "characterised by")
+  - Those features of the invention for which protection is sought in combination with the features of part (a)
+
+```
+1. A method for [purpose], comprising:
+   [known feature A];
+   [known feature B]; and
+   [known feature C],
+   characterised in that
+   [inventive feature D],
+   [inventive feature E].
+```
+
+```
+10. A system for [purpose], comprising:
+    [known component A] configured to [function];
+    [known component B],
+    characterised in that the system further comprises:
+    [inventive component C] configured to [function].
+```
+
+**Important:** The two-part form separates known features from inventive features. This is NOT optional at the EPO -- it is a formal requirement. The examiner will raise an objection if the form is not followed.
+
+**When two-part form is NOT applicable:**
+- Product-by-process claims (rare exceptions)
+- Claims to new chemical compounds per se
+- Claims where the invention cannot be characterized by prior art features
+
+**Dependent claims (Rule 43(4) EPC):**
+```
+2. The method according to claim 1, characterised in that the [feature] comprises [specific limitation].
+3. The method according to any one of claims 1 to 2, characterised in that [additional limitation].
+```
+
+**Multiple dependent claims:**
+- EPO allows multiple dependent claims (unlike some jurisdictions)
+- May refer to multiple preceding claims: "The method according to any one of claims 1 to 3..."
+- However, examiners may raise clarity objections if excessive
+- Multiple dependent claims referring to other multiple dependent claims are NOT allowed
+
+### 2. Description (Rule 42 EPC)
+
+Required structure:
+
+#### Title of the Invention
+- Must correspond to the title in the claims
+- Should be clear and concise
+- No trademarks
+
+#### Technical Field
+- "The invention relates to..."
+- Identify the technical area
+
+#### Background Art
+- Cite relevant prior art documents
+- "Document D1 (EP XXXXXXXX) discloses..."
+- "However, this approach has the disadvantage that..."
+- Distinguish from "Related Work" in academic papers -- focus on technical deficiencies
+
+#### Disclosure of the Invention
+
+**The EPO has a specific structure for this section:**
+
+1. **Problem to be solved**: State the technical problem underlying the invention
+2. **Solution**: How the invention solves this problem, referencing the claim features
+3. **Advantageous effects**: The advantages of the invention over the prior art
+
+```
+The invention is defined in claim 1.
+
+The problem underlying the present invention is to [state problem].
+
+This problem is solved by [reference to characterising features].
+
+The invention has the advantage that [state advantages].
+```
+
+**Inventive step (Article 56 EPC):**
+- The description should support arguments for inventive step
+- Unexpected technical effects strengthen inventive step arguments
+- "Compared to the closest prior art (D1), the invention achieves [specific technical effect] which would not have been predictable from the prior art"
+
+#### Description of Embodiments
+- Detailed description with reference to figures
+- "FIG. 1 shows..." or "Figure 1 shows..."
+- Reference numerals in brackets: "the processor (102) is connected to the memory (104)"
+- At least one embodiment corresponding to the claims
+- Include variations and alternatives
+
+#### Reference Signs List
+- EPO requires a list of reference signs at the end of the description
+- Format: "LIST OF REFERENCE SIGNS: 102 processor, 104 memory, 106 bus..."
+- Organized by figure or alphabetically
+
+### 3. Abstract
+
+- Maximum 150 words (Rule 47(1) EPO)
+- Should indicate the technical field and the gist of the invention
+- Must not contain statements on the alleged merits or value of the invention
+- Must not contain any matter not disclosed in the application
+
+### 4. Drawings
+
+- Reference numerals must match description
+- Must show all features of at least one claim
+- Format: "FIG. 1" or "Figure 1" (both acceptable)
+
+## Key EPO-Specific Rules
+
+### No Functional Claiming Without Disclosure
+
+The EPO is stricter than USPTO on functional claiming:
+- Features defined by their function are allowed only if the specification provides sufficient disclosure
+- "configured to" is acceptable but must be supported by detailed description
+- Pure result-to-be-achieved claims will be rejected under Article 84 EPC
+
+### Inventive Step (Problem-Solution Approach)
+
+The EPO uses a specific three-step approach:
+1. Determine the closest prior art
+2. Identify the distinguishing features and the objective technical problem
+3. Assess whether the claimed invention would have been obvious to a skilled person
+
+The description should be written to support this analysis.
+
+### Added Matter (Article 123(2) EPC)
+
+The EPO is extremely strict about added matter:
+- Nothing may be added that is not directly and unambiguously derivable from the application as filed
+- Even "implicit" disclosures must be truly unambiguous
+- This is stricter than the US written description standard
+
+### Clarity (Article 84 EPC)
+
+- Claims must be clear and concise
+- Claims must be supported by the description
+- The EPO interprets "supported by" strictly: the description must provide basis for every claim feature
+
+## PCT Entry into European Phase
+
+For PCT applications entering the European phase:
+- Deadline: 31 months from priority date
+- Must file translation if not in EN/FR/DE
+- Must pay designation fees
+- Must file request for examination (can be filed with application)
+- Must respond to Rule 161/162 communication (optional amendment opportunity)

package/skills/shared-references/patent-format-us.md

@@ -0,0 +1,161 @@
+# USPTO Patent Format Guide
+
+Use this reference when drafting US patent applications for filing with USPTO.
+
+## When to Read
+
+- Read when `JURISDICTION = "US"` or `JURISDICTION = "ALL"`
+- Read before writing claims in US format
+- Read during `/jurisdiction-format` for US output
+
+## Applicable Law
+
+- Title 35, United States Code
+- Manual of Patent Examining Procedure (MPEP), 9th Edition, Rev. 2024
+- America Invents Act (AIA, 2011)
+
+## Document Structure
+
+A USPTO patent application consists of:
+
+### 1. Claims Section
+
+**Format rules:**
+- Claims are numbered sequentially with Arabic numerals starting from 1
+- Independent claims stand alone; dependent claims reference prior claims
+- Each claim is a single sentence (grammatically complex but technically one sentence)
+- Use semicolons to separate elements within a claim
+
+**Claim Preamble Types:**
+
+**Process/Method claims:**
+```
+1. A method for [purpose], comprising:
+   [step A];
+   [step B]; and
+   [step C].
+```
+
+**System/Apparatus claims:**
+```
+10. A system for [purpose], comprising:
+    a [component A] configured to [function];
+    a [component B] in communication with the [component A]; and
+    a [component C] configured to [function].
+```
+
+**Computer-readable medium claims (US-specific):**
+```
+15. A non-transitory computer-readable storage medium storing instructions that, when executed by a processor, cause the processor to perform operations comprising:
+    [operation A];
+    [operation B].
+```
+
+**Transitional Phrases:**
+| Phrase | Type | Meaning |
+|--------|------|---------|
+| comprising | Open | Includes the listed elements but may also include others |
+| consisting of | Closed | Limited to ONLY the listed elements |
+| consisting essentially of | Semi-open | Allows only insubstantial additional elements |
+
+**Default: use "comprising"** unless there is a specific reason to use a closed transition.
+
+**Dependent Claim Format:**
+```
+2. The method of claim 1, wherein the [element] comprises [specific limitation].
+3. The method of claim 1 or claim 2, further comprising [additional step].
+4. The system of claim 10, wherein the [component A] is a [specific type].
+```
+
+**Multiple Dependent Claims (US rules):**
+- US allows multiple dependent claims but ONLY in the alternative ("or", not "and")
+- "The method of claim 1 or claim 2, wherein..." -- VALID
+- "The method of claims 1 and 2, wherein..." -- INVALID
+- Each multiple dependent claim counts as one claim for fee purposes
+
+### 2. Specification
+
+#### Title
+- Concise and specific (MPEP 606)
+- No more than 500 characters
+- No trademarks, no "improved", no "new"
+- Must describe the invention, not its use
+
+#### Cross-Reference to Related Applications
+- If claiming priority to earlier applications, include at the very beginning
+- Format: "This application claims the benefit of U.S. Provisional Application No. XX/XXX,XXX, filed [date]"
+
+#### Statement Regarding Federally Sponsored Research
+- Include if invention was made with government funding
+
+#### Field of the Invention
+- 1-2 sentences: "The present invention relates generally to [field], and more particularly to [specific area]."
+
+#### Background of the Invention
+- Describe the field
+- Describe existing approaches and their limitations
+- Do NOT admit prior art as "the best" or "superior"
+- Set up the technical problem the invention solves
+- Do NOT include citations to prior art here (that's for IDS)
+
+#### Brief Summary of the Invention
+- "In accordance with one or more embodiments..."
+- Problem-Solution-Advantage structure
+- Mirror the claim scope
+
+#### Brief Description of the Drawings
+- "FIG. 1 is a block diagram showing..."
+- "FIG. 2 is a flowchart illustrating..."
+- One sentence per figure
+
+#### Detailed Description of Preferred Embodiments
+- Must enable a POSITA to make and use the invention (35 USC 112(a))
+- Must provide written description support for all claim scope (35 USC 112(a))
+- Reference numerals: use consistent numbering (100-series for FIG. 1, 200-series for FIG. 2)
+- Include at least one "preferred embodiment" or "exemplary embodiment"
+- Describe alternatives and variations to support broad claim interpretation
+- Best mode: must disclose the best way known to the inventor (less enforced post-AIA but still required by statute)
+
+#### Abstract
+- 150 words or 2500 characters maximum (37 CFR 1.72(b))
+- Purpose: enable efficient prior art searching
+- Include the most important technical features
+- Do NOT include legal phrases or claim references
+
+### 3. Drawings (Figures)
+
+- Must show every feature specified in the claims
+- Reference numerals must match specification
+- Black and white line drawings preferred
+- Format: "FIG. 1", "FIG. 2" (not "Figure 1")
+- No text except reference numerals and essential labels
+
+## IDS (Information Disclosure Statement)
+
+Under the duty of disclosure (37 CFR 1.56), applicants must cite all known material prior art:
+- List all patents, publications, and other references known to be material
+- Use form PTO/SB/08 for listing references
+- Filed during prosecution, not as part of the initial application
+
+## Means-Plus-Function (35 USC 112(f))
+
+When a claim element uses "means for [function]" or equivalent language:
+- The claim is limited to the corresponding structure, material, or acts described in the specification AND equivalents thereof
+- Must disclose the algorithm/structure that performs the function
+- Software "means for" claims MUST disclose the algorithm (flowchart, pseudocode)
+
+**Safer alternative:** Use "a processor configured to [function]" instead of "means for [function]"
+
+## Continuation and CIP Strategy
+
+- **Continuation**: Same disclosure, new claims
+- **Continuation-in-part (CIP)**: Adds new matter, claims to new matter get new priority date
+- **Divisional**: Required when examiner issues restriction requirement
+
+## Common 102/103 Rejection Responses
+
+Document these patterns for use in `/patent-review`:
+- Amend claims to distinguish over cited reference
+- Argue the reference does not teach a specific claim element
+- Argue the combination of references would not have been obvious
+- Provide evidence of unexpected results or commercial success