A real §103 rejection over a single reference. Below: the OA, the agent's risk + claim analysis, the proposed amendment + argument, and the bilingual report you'd send your client.
Parsed by the first node of the agent. Examiner reasoning summary on the left; the three OA passages that drive the rejection on the right.
Claims 1–20 are rejected under 35 U.S.C. § 103 as unpatentable over Agarwal in view of Masson. The examiner finds Agarwal teaches the claimed loan-processing/chat-interface features and relies on Masson to supply limitations such as mapping AUS results to system conditions and other lending-system integrations, and concludes it would have been obvious to combine these teachings.
Generated by the structured-analysis model. Each card holds the analysis summary an associate would otherwise spend hours hand-building.
Why this layer: The drafters treat your validated Structured Analysis as ground truth. Catch a missed gap here and every downstream argument and amendment is anchored on it. Sixty seconds of judgment at this layer beats sixty minutes of cleanup downstream.
Analysis is well-grounded on the examiner's specific cited passages (Agarwal Abstract/Para. 43–59; Masson Para. 16). The dispositive gap — Masson's static strategy list vs. the claimed dynamic, status-responsive task library — is clearly supported by the cited text. Confidence is moderate because the examiner provides no rationale for why a PHOSITA would restructure Masson's static repository into a dynamic generator beyond a generic 'strategy quality' assertion.
Capturing industry knowledge in pre-developed lending strategies to optimize revenue
A repository of automated lending strategies developed and finalized based on historical performance testing and optional manual changes (Masson ¶ 16)
Codifies institutional lending knowledge into reusable strategy modules; reduces strategy-development team load
Masson's task library is STATIC — strategies are finalized in advance. It is not a dynamic generator that iteratively updates in response to current loan status or AUS findings. The examiner's mapping of Masson's 'task library' to the claim's dynamic-generation requirement relies on the shared word 'library,' not on structural or functional equivalence.
using a task library to generate tasks according to the current loan status including AUS findings
Gap: No disclosure in Masson of dynamic task generation responsive to AUS findings or current loan status. The static-vs-dynamic distinction is dispositive.
mapping Automated Underwriting System (AUS) results to system conditions
Gap: The AUS-to-system-conditions mapping is absent from both references; the examiner provides no cited passage on this point.
The examiner's motivation is GENERIC: it addresses the general problem of strategy quality and team-coordination overhead, not a technical reason to restructure Masson's static architecture into a dynamic, status-responsive task generator. A PHOSITA reading Agarwal would see no shortcoming that Masson's static strategy repository would solve, much less be led to the iterative AUS-feedback loop recited in the claims.
Three indicators of hindsight reconstruction: (1) the examiner selects Masson's 'task library' only because it shares the word 'library' with the claim; (2) no articulated reason is given why Agarwal's form-completion system would need Masson's strategy repository; (3) the stated motivation is result-oriented ('reduce performance') rather than problem-solution based — i.e., the examiner reasons backward from the claim language.
The spec explicitly describes a dynamic task library updated from AUS feedback at multiple paragraphs (¶¶ [0059], [0062], [0067], [0069]). Narrowing claim 1 to recite this dynamic-update behavior adds only already-disclosed features.
Care needed on 'task library' vs 'strategy library' terminology — the spec uses 'task library' consistently; the amendment should preserve that term to avoid §112(b) issues. 'Current loan status' should be defined by reference to the spec's enumerated examples (borrower details, AUS findings) to avoid breadth ambiguity.
Each card is editable in the live workbench. Confirm or correct any field in your own voice before drafts fire — argument and amendment models treat your final read as ground truth.
Open the workbench previewThe amendment model drafts the claim revisions; the argument model drafts the response. Both consume the practitioner-validated Structured Analysis bundle, not the model's first guess.
Posture choice: Argue + amend paired removes the §103 vulnerability even if the argument loses. Argument-only is right when the rejection is structurally weak; amendment-only when you'd rather narrow than litigate. Belt and suspenders is the default — fewer one-way doors in prosecution.
Claim 1 is narrowed to recite (i) dynamic updating of the task library based on the current loan status and AUS findings, and (ii) mapping of AUS results to system conditions. Both limitations are explicitly disclosed in the spec at ¶¶ [0059] (dynamic generation based on real-time user interaction and the stage of a loan application process), [0062] (task library generates tasks based on a loan's current status), [0067] (task library generates further tasks based on the loan status), and [0069] (AUS results used to update system conditions and update the task library). These features are absent from Masson's static strategy list and from Agarwal's form-completion chat manager; the narrowing removes the §103 challenge without introducing new matter.
1Applicant respectfully submits that the rejection of claims 1–5 under 35 U.S.C. § 103 over Agarwal in view of Masson should be withdrawn because the Examiner has not established that the proposed combination teaches or suggests the dynamic task-library limitation that is central to independent claim 1. Claims 2–5 stand or fall with independent claim 1.
2The Examiner's combination relies on Masson (¶ 16) to supply the limitation requiring the system to use a task library to generate tasks according to the current loan status. However, the cited passage from Masson describes a static list of pre-defined lending strategies — a repository developed and finalized based on strategy performance and optional manual changes. Masson's 'task library' is not a dynamic generator that iteratively updates in response to current loan status. The Examiner has not identified any passage in Masson disclosing a task library that dynamically generates tasks based on the current loan status, including AUS findings.
3Furthermore, the Examiner has not articulated a sufficient motivation for a PHOSITA to modify Masson's static strategy list into the dynamically updatable task library recited in the claims. The Examiner's stated rationale — that Masson's system 'is unable to capture industry knowledge' and requires 'several teams' to produce a higher-quality strategy — addresses only the general problem of strategy quality and team coordination. It does not explain why a PHOSITA would have been led to restructure Masson's static strategy repository into a dynamic, status-responsive task generator. The reasoning is conclusory and does not satisfy KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), which requires a specific, articulable reason to combine.
4Applicant further notes that the combination, even if accepted, would not yield the claimed invention. Neither Agarwal nor Masson discloses the iterative feedback loop in which AUS findings are mapped to system conditions and used to dynamically update the task library. Accordingly, Applicant respectfully requests withdrawal of the rejection of claims 1–5.
The end-state document a practitioner sends the client. One source of truth, two registers, statute citations matched to the right jurisdiction.
Verdict. The §103 rejection over Agarwal in view of Masson is arguable. The combination requires Masson to supply the claimed dynamic, status-responsive task library, but Masson ¶ 16 actually discloses a STATIC strategy repository. The examiner's mapping relies on the shared word "library."
Recommended strategy. Argue + amend. Traverse the §103 on the static-vs-dynamic distinction; concurrently narrow claim 1 to recite that the task library is dynamically updated from current loan status including AUS findings.
Risk profile. Amendment risk is low; spec ¶¶ [0059], [0062], [0067], [0069] provide explicit support for the dynamic-update behavior. §112(b) clarity risk is medium — keep the spec's "task library" terminology consistent to mitigate.
判斷：以 Agarwal 與 Masson 之結合為基礎的 §103 核駁有強力答辯空間。結合需 Masson 提供請求項所述「動態且具狀態回應性之任務庫」，但 Masson 第 16 段所揭示者實為「靜態策略清單」。審查官之映射依賴於「library」一詞之共用而已。
建議策略：答辯加修正。以「靜態與動態」之區別答辯 §103，同時將請求項 1 限縮至「任務庫依當前貸款狀態（含 AUS findings）動態更新」之具體技術構造。
風險評估：修正風險低；說明書 ¶¶ [0059]、[0062]、[0067]、[0069] 對動態更新行為有明確支持。§112(b) 明確性風險為中等，使用說明書一致之「task library」用語可降低。
Sign in with Google to join the early-access list. We'll email you when uploads open.
Demo runs on a public USPTO sample. No upload required at v1.0; no client data is processed.