Candidate arguments for counsel, ranked strongest-first — brainstorming inputs for counsel to evaluate, not a drafted response.
the amount of bictegravir or pharmaceutically acceptable salt thereof corresponds to about 75 mg bictegravir free acid
Bekerman is the sole reference in Rejection 2 and is fully grounded as to its claims, so what those claims disclose is squarely before counsel. As to bictegravir, Bekerman's retrieved claims give only a broad genus range of "from about 10 mg to about 2000 mg" (claim 38) and "from about 10 mg to about 1000 mg" (claim 39), and its one enumerated list of specific bictegravir doses (claim 40) runs "about 50 mg, about 100 mg, about 150 mg... about 600 mg" — it jumps from 50 mg to 100 mg and never recites 75 mg. The examiner's only support for the specific "about 75 mg" value is Bekerman specification paragraph [00312]/pg.137, which OA2 confirms is outside the retrieved claims/abstract text. Counsel should obtain and read [00312] before relying on this as a distinction; if the specification likewise does not disclose 75 mg specifically (and especially the specific 75 mg bictegravir / 50 mg lenacapavir pairing recited together), the absence of that exact value is a potentially dispositive gap for independent claims 19 and 84 and everything depending from them. Note that 50 mg lenacapavir IS grounded in Bekerman claim 13, so the contest for counsel is confined to the 75 mg bictegravir value and the specific two-dose pairing.
- —Bekerman claim 38: bictegravir "administered in a dosage of from about 10 mg to about 2000 mg"
- —Bekerman claim 40: enumerated doses "about 50 mg, about 100 mg, about 150 mg... about 600 mg" (no 75 mg)
- —Bekerman claim 13: "the tablet comprises about 50 mg of the compound of Formula (Ia)"
- —Office action ¶22: 75 mg cited only to "[00312]" / "pg.137, lines 1-2"
- —OA2: excipient, dose, and related teachings "are cited to specification paragraphs (e.g., [00261]-[00312]) that are NOT part of the available claims/abstract text"
MPEP § 2131 (a single reference must disclose every element); on the counter-doctrine the examiner will invoke, MPEP § 2144.05 / In re Peterson & In re Wertheim (selection of a specific value from a disclosed range)
⚠ Risk The examiner will likely respond that the broad 10-2000 mg genus of claim 38 encompasses 75 mg, that selecting a workable dose is routine optimization, and that [00312] expressly recites 75 mg. This argument is VERIFY-FIRST: because the full Bekerman specification was not retrieved, counsel cannot yet assert the reference lacks 75 mg — [00312] must be pulled and read first. Prosecution-history-estoppel caution: characterizing 75 mg bictegravir / 50 mg lenacapavir as the distinguishing point may narrow the file wrapper around those exact amounts and foreclose equivalents to nearby doses.
Likely examiner response◐ survives — moderate
The examiner can respond that the rejection is not confined to Bekerman's claim text: the office action cites Bekerman specification ¶[00312]/pg.137 for the specific about-75 mg value, and a reference is evaluated on its entire disclosure (MPEP § 2131 for anticipation; the whole specification, not just the claims). If [00312] recites 75 mg, the asserted gap disappears. Even if 75 mg is not literally recited, the examiner can invoke routine optimization / overlapping-range obviousness (MPEP § 2144.05): Bekerman claim 38 discloses a 10–2000 mg genus and claim 40 brackets the value with about 50 mg and about 100 mg, so about 75 mg lies squarely within a disclosed range and choosing it would be prima facie obvious absent a showing of criticality or unexpected results. Whether this comeback lands depends on whether Rejection 2 is framed under §102 (where a truly missing specific value is dispositive) or §103 (where dose optimization applies) — counsel should confirm the statutory basis of Rejection 2 from the office action.
How to adjust Obtain and read [00312] first — the entire argument turns on whether the spec discloses about 75 mg (and, ideally, whether it discloses the specific 75 mg bictegravir / 50 mg lenacapavir pairing recited together, which is a narrower and harder target for the examiner to hit). Confirm whether Rejection 2 is §102 or §103: if §102, press the missing-element/arranged-as-in-the-claim theory (a specific value the single reference never discloses); if §103, the range-optimization comeback (MPEP § 2144.05) is the real threat, so pair the argument with criticality/unexpected-results evidence (a §1.132 showing that 75/50 produces results a PHOSITA would not have predicted) or consider amending toward the specific two-dose pairing as the distinguishing feature.
the film coating comprises Opadry II or Opdary TF
The § 112(b) rejection treats "Opadry II" and "Opadry TF" as trademarks that identify a source rather than a composition, and thus as indefinite under Ex parte Simpson (office action ¶18). The correct lever for counsel is not to attack the pairing with the § 103 rejection — compact prosecution permits both — but to show the claim scope is reasonably certain under BRI: the office action itself describes Opadry II as "an immediate-release coating containing PVA or HPMC, plasticizers (like PEG) and pigments (including titanium dioxide and iron oxides)" and Opadry TF as a "TiO2-free" one-step film coating, indicating the terms map to a knowable class of coating compositions. Counsel should weigh whether that recognized-composition showing meets the In re Packard / § 2173.02 examination standard, or whether the cleaner route is to amend to recite the coating composition functionally rather than by trade name. Because the examination standard here is In re Packard / MPEP § 2173.02, counsel should avoid citing the litigation "reasonable certainty" test.
- —Office action ¶18: trademark "cannot be used properly to identify any particular material or product" (citing Ex parte Simpson, 218 USPQ 1020)
- —Office action ¶18: Opadry II described as "an immediate-release coating containing PVA or HPMC, plasticizers (like PEG) and pigments"; Opadry TF as a "TiO2-free, high-performance coating"
- —Office action ¶22 (¶41-42): the same Opadry II is treated as taught by Bekerman "[00280]-[00281]"
MPEP § 2173.02 / In re Packard (examination definiteness standard); MPEP § 2173.05(u) (trademarks/trade names in claims); do NOT argue § 112(b)+§103 inconsistency (§ 2173.06(II))
⚠ Risk The examiner will likely maintain that a trademark can shift in composition over time and so does not fix claim scope, making amendment the practical path. Prosecution-history caution: arguing that Opadry II denotes a fixed known composition may bind the claim to that composition; amending to a generic film-coating recitation avoids that estoppel but broadens/alters scope in ways counsel must reconcile with support.
Likely examiner response◐ survives — moderate
The examiner can maintain, under Ex parte Simpson, that a trademark identifies a source and not a fixed composition, and that a manufacturer can change what it sells under 'Opadry II'/'Opadry TF' over time, so the claim scope remains amenable to more than one construction under BRI (Ex parte Miyazaki, MPEP § 2173.02). The examiner can add that the office action's own composition description uses open/illustrative language ('containing... including...'), which shows the composition is variable rather than definitionally fixed, so the recognized-class showing does not resolve the indefiniteness.
How to adjust This argument is doctrinally well-built — it correctly declines the losing 'the §112(b) and §103 pairing is inconsistent' theory (compact prosecution permits both, MPEP § 2173.06(II)) and correctly cites the In re Packard / § 2173.02 examination standard rather than Nautilus. Its self-contained strength is that the definitional support comes from the office action's own text, not from unretrieved references. Note the office action's composition description is exemplary ('including'/'containing'), so it illustrates rather than fixes scope — do not overclaim it as definitional. Given the examiner's Simpson-based source-vs-composition point, weigh the cleaner alternative of amending claim 42 to recite the coating by composition/function rather than trade name, which resolves the §112(b) basis outright.
Conclusory / hindsight motivation to reformulate the specific bictegravir+lenacapavir tablet as a monolayer
Conclusory rationaleClaim 22Claim 30Claim 47Claim 48Claim 84Claim 85Claim 86Claim 87Claim 88Rebuts: §103 rejection of claims 22, 30, 47, 48, 49, 84, 85, 86, 87, 88
the tablet is a monolayer tablet
The office action concedes Bekerman "does not explicitly teach that its tablet is to be a monolayer tablet" (¶23) and supplies that limitation only through Thomas, relying on a generic proposition that monolayer tablets are "less complex to formulate" and involve less "time-consuming" analysis, validation, and quality control than bi-layer tablets. That rationale is stated at the level of general convenience and does not articulate why a PHOSITA would specifically choose a single-layer architecture for THIS combination of two distinct APIs (a crystalline integrase inhibitor and a capsid inhibitor that claim 57 recites as a spray-dried dispersion). For counsel to weigh: a generalized "simpler and faster" preference is the kind of untethered convenience rationale that KSR still requires be supported by articulated reasoning with a rational underpinning connecting the teaching to the claimed subject matter. Because Thomas's text was never retrieved (unverifiable), counsel should obtain the article and confirm the cited passages before pressing this, and should frame the point as the examiner's rationale being conclusory rather than as an assertion about what Thomas does or does not teach.
- —Office action ¶23: "Bekerman does not explicitly teach that its tablet is to be a monolayer tablet"
- —Office action ¶23: monolayer tablets are "less complex to formulate" and bi-layer analysis/validation/QC "more complex... and thus can be a more time-consuming process"
- —Pending claim 57: "the lenacapavir or pharmaceutically acceptable salt thereof is present in a spray dried dispersion"
- —Reference grounding: Thomas is not listed / its text was never retrieved (UNVERIFIABLE)
MPEP § 2143.01 — a §103 rejection requires articulated reasoning with rational underpinning; see also § 2145 (hindsight) and § 2143 (the KSR rationales)
Risk The examiner will respond that monolayer manufacturing simplicity is a recognized design incentive (KSR rationale (F)) and needs no product-specific motive. Because Thomas is unverifiable, this argument ranks below the Bekerman-grounded points and must not be framed as a missing-element finding. Prosecution-history caution: arguing that a monolayer is non-trivial for these two APIs could later be read as an admission that layer architecture is a material, potentially limiting feature.
Likely examiner response◐ survives — moderate
The examiner can characterize the monolayer rationale as a recognized KSR line of reasoning — reduced formulation complexity and shorter validation/QC as a design incentive or predictable improvement (MPEP § 2143 rationales D/F) — and argue that KSR does not require the motivation to be tailored to the exact API pair; a general, art-recognized reason to prefer a single-layer architecture, supported by Thomas, can suffice. The examiner can add that the rationale need only have a rational underpinning, not exhaustively address every property of the specific combination.
How to adjust Do not overstate the 'conclusory' label — a convenience/design-incentive motive is a permitted KSR rationale, so the winning angle is that the office action never connects that generic teaching to why a PHOSITA would monolayer THIS specific crystalline-plus-SDD pair with a reasonable expectation of success (MPEP § 2143.01/§ 2143.02). Best pressed jointly with argument 4. Obtain Thomas and confirm the cited passages before asserting anything about its content; frame the point as a rational-underpinning gap in the examiner's reasoning, not as a claim about Thomas's teachings. Given this examiner's high interview-to-allowance correlation, an interview to probe the motivation basis may be worth weighing.
No reasonable expectation of success combining a spray-dried-dispersion API with a crystalline API in a single monolayer tablet
No reasonable expectation of successClaim 22Claim 47Claim 48Claim 84Claim 88Rebuts: §103 rejection of claims 22, 30, 47, 48, 49, 84, 85, 86, 87, 88
the tablet is a monolayer tablet ... comprising bictegravir ... and lenacapavir ... [lenacapavir] present in a spray dried dispersion
The claimed product co-formulates two mechanistically distinct APIs — bictegravir and lenacapavir — with lenacapavir provided as a spray-dried dispersion (claim 57), in a single monolayer layer. The examiner's monolayer rationale (office action ¶23) speaks only to manufacturing convenience and does not address whether a PHOSITA would have had a reasonable expectation that an amorphous spray-dried dispersion and a separate active could be blended into one homogeneous compressed layer without compatibility, content-uniformity, or physical-stability problems. Pharmaceutical formulation is a field with recognized unpredictability, and a bare convenience motive does not establish the reasonable expectation of success that § 103 requires. Counsel should confirm the spray-dried-dispersion teaching (currently supported only by Bekerman spec [00261], unretrieved) and consider a § 1.132 declaration from a formulation scientist addressing single-layer co-formulation risks for these specific components.
- —Pending claim 57: lenacapavir "present in a spray dried dispersion"
- —Office action ¶23: monolayer rationale limited to being "much less complex" and "less time-consuming"
- —OA2: spray-dried-dispersion teaching cited to spec "[00261]" outside the available claims/abstract text
- —OA4: field is "Pharmaceutical formulation of anti-HIV agents" involving "granulation/spray-dried dispersions"
MPEP § 2143.02 — obviousness requires a reasonable expectation of success, not a hope; unpredictability in the art cuts against itEvidence needed: A § 1.132 declaration from a formulation scientist addressing the difficulty / lack of predictable success in co-formulating a lenacapavir spray-dried dispersion with bictegravir in a single monolayer tablet (content uniformity, compatibility, stability).
Risk The examiner may respond that co-formulating two known antiretrovirals in one tablet is routine and that Bekerman already contemplates a fixed-dose combination tablet (claims 34, 37), so success was expected. This point is strengthened only by evidence; attorney argument about unpredictability alone will likely be discounted. The spray-dried-dispersion basis is verify-first (spec [00261] unretrieved).
Likely examiner response⚠ fragile — the comeback likely defeats it
The examiner can respond that co-formulating an amorphous spray-dried dispersion with a crystalline API in a single compressed layer is an established formulation practice and that reasonable expectation of success does not demand absolute predictability (MPEP § 2143.02). Critically, unpredictability and compatibility/uniformity/stability risk are factual assertions that require evidence — attorney argument alone does not rebut a prima facie case (MPEP § 2145). Absent a declaration, the examiner can dismiss the unpredictability contention as unsupported.
How to adjust As currently framed (attorney argument), this is unlikely to carry — MPEP § 2145 requires evidence for unpredictability/unexpected-difficulty contentions. The path to strength is a § 1.132 declaration from a formulation scientist addressing content-uniformity, physical-stability, and compatibility risks specific to blending this SDD with this crystalline API in one layer; with that declaration this argument could move from fragile to strong. Also verify the spray-dried-dispersion teaching (Bekerman [00261], unretrieved) before relying on the SDD limitation. Consider whether amending to features the declaration substantiates is a more durable posture than argument alone.
the tablet comprises about 5-50 mg copovidone, about 0.5-10 mg poloxamer, about 50-200 mg mannitol, about 50-250 mg microcrystalline cellulose, about 25-50 mg croscarmellose sodium and about 1-10 mg magnesium stearate
The retrieved Bekerman claims and abstract disclose no excipients and no weight-percentage ranges; every excipient identity and amount the examiner relies on is cited to Bekerman specification paragraphs [00269]-[00278], which OA2 states are not part of the available claims/abstract text. The examiner's milligram ranges are not read from the reference but built by a multi-step derivation: taking a spec wt.% range for lenacapavir sodium, computing a "total tablet weight can range from 114 mg to 1,022 mg" (office action ¶22), then multiplying each excipient's spec wt.% by those endpoints. Every input to that derivation comes from unseen specification text, and the resulting ranges (e.g., copovidone "from 1.14 mg to 102.2 mg") are so broad that counsel may separately question whether such an expansive prior-art range renders the comparatively narrow claimed ranges prima facie obvious. Counsel should obtain [00269]-[00278] and confirm both the excipient list and the wt.% ranges before treating this as a distinction; until then this is a VERIFY-FIRST point resting on a fully-grounded reference whose relied-upon passages were not retrieved.
- —Office action ¶22: excipients cited to "[00269]-[00270]" and wt.% ranges to "[00273]-[00278]"; lenacapavir sodium 5-45 wt.% to "[00272]"
- —Office action ¶22: "the total tablet weight can range from 114 mg to 1,022 mg" and "copovidone in the tablet ranges from 1.14 mg to 102.2 mg"
- —OA2: the relied-upon excipient/wt.% paragraphs "are NOT part of the available claims/abstract text"
- —Office action ¶22 relies on In re Wertheim for overlapping ranges
MPEP § 2131 / § 2141.02 (each limitation must be found in the reference considered as a whole); MPEP § 2144.05 (overlapping/optimized ranges — the examiner's In re Wertheim reliance)
Risk The examiner will reaffirm that [00269]-[00278] expressly teach these excipients and wt.% ranges and that overlapping ranges are prima facie obvious under In re Wertheim absent unexpected results. VERIFY-FIRST: the specification was not retrieved, so absence cannot be asserted yet — pull the cited paragraphs. If counsel instead argues the derived range is too broad to render the narrow claimed ranges obvious, be prepared for a routine-optimization rebuttal.
Likely examiner response⚠ fragile — the comeback likely defeats it
The examiner can note that the excipient identities and wt.% ranges are expressly cited to Bekerman specification ¶[00269]–[00278], part of the reference's full disclosure, and that reading claimed mg amounts against disclosed wt.% ranges applied to a computed tablet weight is a standard obviousness derivation. More damaging, the argument concedes the prior-art ranges are broad and overlap the claimed ranges — under MPEP § 2144.05, a prior-art range that encompasses or overlaps the claimed range establishes a prima facie case of obviousness, so the very breadth the argument highlights cuts in the examiner's favor, not the applicant's, absent a showing that the narrower claimed amounts are critical.
How to adjust This is double-edged: pressing 'the range is too broad' can hand the examiner the overlapping-range rationale (MPEP § 2144.05). First verify [00269]–[00278] — confirm whether the six named excipients and the wt.% ranges are actually disclosed. If they are, the productive lever is not the derivation critique but a criticality / unexpected-results showing for the specific claimed mg amounts (evidence, per MPEP § 2145, not attorney argument), or amendment to a narrower excipient profile tied to demonstrated performance. If any of the six excipients is genuinely absent from the spec, that specific-excipient absence is the cleaner point than the derivation chain.
a tablet comprising bictegravir ... about 75 mg ... and lenacapavir ... about 50 mg
If the § 103 rejection is otherwise maintained, counsel may develop objective indicia tied to the specific fixed-dose combination claimed. A nexus argument would need to connect any commercial success, long-felt need for a complete single-tablet regimen pairing an integrase inhibitor with a capsid inhibitor, or industry skepticism/praise directly to the claimed 75 mg bictegravir / 50 mg lenacapavir monolayer tablet — not to the individual APIs, which were separately known. Secondary considerations carry weight only with an evidentiary showing and a demonstrated nexus, so this is a supplementary avenue to be built only if the primary distinctions above do not resolve the rejection. Counsel should assess what data exist (sales, regulatory milestones, published skepticism about co-formulating these two drug classes) before investing in a declaration.
- —Pending claims 19 and 84 recite the specific about-75 mg bictegravir / about-50 mg lenacapavir combination
- —OA4: the invention is a fixed-dose combination pairing an integrase inhibitor (bictegravir) with a capsid inhibitor (lenacapavir)
MPEP § 2145 — objective indicia of non-obviousness require a nexus to the claimed features and evidentiary supportEvidence needed: A § 1.132 declaration establishing a nexus between objective evidence (commercial success, long-felt unmet need, skepticism, or praise) and the specific claimed 75 mg bictegravir / 50 mg lenacapavir monolayer tablet, with underlying data.
Risk Without a documented nexus, the examiner will accord this no weight and may attribute any success to the individually known APIs or to marketing. Prosecution-history caution: emphasizing the commercial embodiment can invite arguments that unclaimed features drive success, weakening nexus.
Likely examiner response⚠ fragile — the comeback likely defeats it
The examiner can note that objective indicia carry weight only with evidentiary support and a demonstrated nexus to the specific claimed features (MPEP § 2145), and that any commercial success or long-felt need may be attributable to the individually known APIs rather than to the claimed 75/50 monolayer combination. As presently stated — no data, no declaration — the examiner can give the point no weight.
How to adjust Supplementary only; build it solely if the primary distinctions do not resolve the rejection. Requires actual evidence (sales, regulatory milestones, documented skepticism about co-formulating these two drug classes) and a nexus tied specifically to the claimed 75 mg/50 mg monolayer FDC, not the individual drugs. Assess data availability before investing in a declaration.