One §103, from the action to the draft.

Follow a single obviousness rejection through the workbench. The example is illustrative — a sensor claim over two references, Smith and Lee — but the path is the real one: structure first, prose last, a source behind every step.

01 — Parse

Read the action into structure

The workbench detects whether the action is final, then pulls each rejection apart: its statutory basis, the claims it touches, the references cited against them, and the examiner's stated rationale.

Nothing here is guessed past what's on the page. Where the action is ambiguous — a reference cited by shorthand, a claim group left implicit — it's flagged for you to confirm, not silently resolved. Every parsed field is editable, and a correction re-runs what depends on it.

BasisClaimsReferences
§103 · final1–12Smith in view of Lee
§112(b)7antecedent basis — “the alert”

Examiner rationale captured verbatim · final status detected · 1 item flagged for confirmation

02 — Segment

Break the claim into limitations

An independent claim is only arguable element by element, so the workbench splits it into limitations and preserves the original language exactly. You can re-segment — split a clause, merge two — and the mappings that hang off the old segmentation are dropped and rebuilt, not left stale.

This is the spine the rest of the analysis hangs on. Get it right and everything downstream lines up.

Claim 1 — segmented
1 — a housing;
2 — a sensor configured to generate readings representing an environmental condition;
3 — a processor configured to receive the sensor readings;
4 — and transmit an alert when the reading exceeds a learned threshold.

4 limitations · original language preserved · editable

03 — Map

Line the art up against each element

For every limitation, the workbench finds the passage the art relies on and quotes it — then verifies that quote against the reference text. A quote found verbatim is anchored to its exact location. A quote that's only paraphrased is marked partial; one that can't be found is marked unverified and held out of the analysis rather than counted as coverage.

That last rule matters: fabricated evidence can't quietly close a gap. When Smith and Lee both teach a fixed limit and neither teaches a learned threshold, the workbench shows the gap — the opening you'd argue.

§103 element 4 missing / weak
Claim element
…transmit an alert when the reading exceeds a learned threshold.
Nearest passage — Lee, US 9,876,543
“…compares the reading against a predetermined threshold and raises a warning.”
Lee col. 6, ll. 41–48 predetermined ≠ learned
Gap preserved · not counted as disclosure · this is the argument
04 — Weigh

Lay the options out with their costs

Two honest paths usually exist: amend to add the distinguishing limitation, or traverse on the merits. The workbench builds both and attaches what each one costs — argument strength, scope surrendered, new-matter risk, and prosecution-history estoppel exposure — so the comparison is explicit.

It won't pick for you. Allowance is one goal; not giving away valuable scope is another, and the tradeoff is yours to make.

Amendadd “learned threshold”
Strength
Scope cost
Estoppel
Traverseno expectation of success
Strength
Scope cost
Estoppel
05 — Draft

Render the skeleton, not the verdict

Once you've selected a path, the workbench renders a response skeleton organized by rejection: the amendment in USPTO redline format, remarks built from your selected argument, and the sources behind each section carried along. Open questions become highlighted [ATTORNEY: …] placeholders — a checklist, not filler.

It exports to Word with a page-broken “Attorney Work Product — remove before filing” appendix listing every open issue, source, and low-confidence flag. You finish it. It never files.

Remarks — Claim 1 · §103

Claim 1 has been amended to recite a learned predetermined threshold. Neither Smith nor Lee discloses a learned threshold; both teach a fixed limit Lee col.6.

[ATTORNEY: confirm spec support for “learned” at ¶[0031]]

Exported to .docx · work-product appendix attached · nothing filed

See it on your own Office action

The map is the point. The draft is downstream.

Bring a real action and claims; watch the rejection graph build, then check every line back to its source.