Switch autoware-patent-search to module-based BigQuery workflow; add SQL examples and tests (#5)

* Clean up patent search examples before merge

* Constrain patent search SQL to feature terms

Author: kenta0705

.agents/skills/autoware-patent-search/SKILL.md

@@ -1,4 +1,4 @@
 interface:
   display_name: "Autoware Patent Search"
-  short_description: "Search patent DBs and scaffold Autoware IP review charts/alerts."
-  default_prompt: "Review this Autoware change for patent-sensitive technical features, search only Google Patents and J-PlatPat when available, and generate non-legal candidate matching, claim-comparison, and monitoring notes for IP review."
+  short_description: "Generate BigQuery patent triage for Autoware modules."
+  default_prompt: "Review this existing Autoware module for patent-sensitive technical features, generate Google Patents Public Data BigQuery SQL for candidate retrieval, and produce non-legal candidate matching, claim-comparison, and monitoring notes for human IP review."

.agents/skills/autoware-patent-search/agents/openai.yaml

@@ -0,0 +1,52 @@
+-- Google Patents Public Data candidate search for Autoware module: planning/behavior_path_planner/lane_change
+-- Technical triage only; results are candidates for human IP-professional review.
+SELECT
+  p.publication_number,
+  p.application_number,
+  p.publication_date,
+  p.filing_date,
+  (SELECT text FROM UNNEST(p.title_localized) LIMIT 1) AS title,
+  (SELECT text FROM UNNEST(p.abstract_localized) LIMIT 1) AS abstract,
+  ARRAY(SELECT a.name FROM UNNEST(p.assignee_harmonized) a LIMIT 10) AS assignees,
+  ARRAY(SELECT c.code FROM UNNEST(p.cpc) c LIMIT 10) AS cpc_codes,
+  (IF((EXISTS (SELECT 1 FROM UNNEST(p.title_localized) txt WHERE LOWER(txt.text) LIKE '%autonomous vehicle%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.abstract_localized) txt WHERE LOWER(txt.text) LIKE '%autonomous vehicle%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.description_localized) txt WHERE LOWER(txt.text) LIKE '%autonomous vehicle%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.claims_localized) txt WHERE LOWER(txt.text) LIKE '%autonomous vehicle%')), 1, 0) +
+  IF((EXISTS (SELECT 1 FROM UNNEST(p.title_localized) txt WHERE LOWER(txt.text) LIKE '%automated driving%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.abstract_localized) txt WHERE LOWER(txt.text) LIKE '%automated driving%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.description_localized) txt WHERE LOWER(txt.text) LIKE '%automated driving%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.claims_localized) txt WHERE LOWER(txt.text) LIKE '%automated driving%')), 1, 0) +
+  IF((EXISTS (SELECT 1 FROM UNNEST(p.title_localized) txt WHERE LOWER(txt.text) LIKE '%trajectory planning%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.abstract_localized) txt WHERE LOWER(txt.text) LIKE '%trajectory planning%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.description_localized) txt WHERE LOWER(txt.text) LIKE '%trajectory planning%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.claims_localized) txt WHERE LOWER(txt.text) LIKE '%trajectory planning%')), 1, 0) +
+  IF((EXISTS (SELECT 1 FROM UNNEST(p.title_localized) txt WHERE LOWER(txt.text) LIKE '%vehicle control%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.abstract_localized) txt WHERE LOWER(txt.text) LIKE '%vehicle control%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.description_localized) txt WHERE LOWER(txt.text) LIKE '%vehicle control%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.claims_localized) txt WHERE LOWER(txt.text) LIKE '%vehicle control%')), 1, 0)) AS broad_context_match_count,
+  CONCAT('https://patents.google.com/patent/', p.publication_number) AS google_patents_url
+FROM `patents-public-data.patents.publications` AS p
+WHERE (
+    (EXISTS (SELECT 1 FROM UNNEST(p.title_localized) txt WHERE LOWER(txt.text) LIKE '%lane change path generation with collision check using predicted objects%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.abstract_localized) txt WHERE LOWER(txt.text) LIKE '%lane change path generation with collision check using predicted objects%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.description_localized) txt WHERE LOWER(txt.text) LIKE '%lane change path generation with collision check using predicted objects%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.claims_localized) txt WHERE LOWER(txt.text) LIKE '%lane change path generation with collision check using predicted objects%'))
+    OR (EXISTS (SELECT 1 FROM UNNEST(p.title_localized) txt WHERE LOWER(txt.text) LIKE '%behavior planning%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.abstract_localized) txt WHERE LOWER(txt.text) LIKE '%behavior planning%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.description_localized) txt WHERE LOWER(txt.text) LIKE '%behavior planning%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.claims_localized) txt WHERE LOWER(txt.text) LIKE '%behavior planning%'))
+    OR (EXISTS (SELECT 1 FROM UNNEST(p.title_localized) txt WHERE LOWER(txt.text) LIKE '%safety margin%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.abstract_localized) txt WHERE LOWER(txt.text) LIKE '%safety margin%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.description_localized) txt WHERE LOWER(txt.text) LIKE '%safety margin%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.claims_localized) txt WHERE LOWER(txt.text) LIKE '%safety margin%'))
+    OR (EXISTS (SELECT 1 FROM UNNEST(p.title_localized) txt WHERE LOWER(txt.text) LIKE '%車線変更 経路生成 衝突判定 予測物体%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.abstract_localized) txt WHERE LOWER(txt.text) LIKE '%車線変更 経路生成 衝突判定 予測物体%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.description_localized) txt WHERE LOWER(txt.text) LIKE '%車線変更 経路生成 衝突判定 予測物体%') OR
+      EXISTS (SELECT 1 FROM UNNEST(p.claims_localized) txt WHERE LOWER(txt.text) LIKE '%車線変更 経路生成 衝突判定 予測物体%'))
+  )
+  AND (EXISTS (SELECT 1 FROM UNNEST(p.cpc) c WHERE STARTS_WITH(c.code, 'B60W')) OR EXISTS (SELECT 1 FROM UNNEST(p.cpc) c WHERE STARTS_WITH(c.code, 'G05D1/00')) OR EXISTS (SELECT 1 FROM UNNEST(p.cpc) c WHERE STARTS_WITH(c.code, 'G08G1/00')))
+  AND (EXISTS (SELECT 1 FROM UNNEST(p.assignee_harmonized) a WHERE LOWER(a.name) LIKE '%toyota%') OR EXISTS (SELECT 1 FROM UNNEST(p.assignee_harmonized) a WHERE LOWER(a.name) LIKE '%toyota motor%'))
+  AND p.publication_date >= 20180101
+ORDER BY broad_context_match_count DESC, p.publication_date DESC
+LIMIT 25;

.agents/skills/autoware-patent-search/examples/lane_change_bigquery.sql

@@ -0,0 +1,76 @@
+# Sample module-based patent review report: lane change planning
+
+This is sample output for validating the `autoware-patent-search` MVP workflow. It is technical triage only and is not a legal opinion about infringement, validity, freedom to operate, or non-infringement.
+
+## 1. Module/package name
+
+`planning/behavior_path_planner/lane_change` (example module target)
+
+## 2. Files/classes/functions/ROS nodes/topics reviewed
+
+Sample placeholders for a real module review:
+
+- README/package documentation: `README.md`
+- Launch/config/parameters: lane-change safety threshold and collision-check parameters
+- Source/classes/functions: lane-change path generation, predicted-object collision check, safety evaluation
+- ROS interfaces: route/lanelet inputs, predicted objects, candidate path output, behavior-planning status topics
+
+## 3. Technical feature summary
+
+Lane-change path generation that evaluates candidate paths against predicted objects and applies collision-check or safety-margin logic before accepting a lane-change maneuver.
+
+## 4. Inputs and outputs
+
+- Inputs: ego pose/velocity, route/lanelet map, predicted objects, candidate lane-change paths, safety thresholds
+- Outputs: accepted/rejected lane-change path, behavior-planning status, optional diagnostic or debug markers
+
+## 5. Algorithmic steps or behavior logic
+
+1. Generate candidate lane-change paths from current lane to target lane.
+2. Estimate object interactions using predicted object trajectories.
+3. Apply collision or safety-margin checks over the candidate path horizon.
+4. Accept, reject, or defer the lane-change maneuver based on safety logic.
+
+## 6. Why the feature may be patent-sensitive
+
+The feature combines autonomous-driving behavior planning, path generation, object prediction, and collision/safety decision logic. These are common areas for patent filings, so matching patent documents should be treated as candidates for human IP review.
+
+## 7. English patent search keywords
+
+lane change, path generation, collision check, predicted objects, behavior planning, autonomous vehicle, trajectory planning, safety margin
+
+## 8. Japanese patent search keywords
+
+車線変更, 経路生成, 衝突判定, 予測物体, 行動計画, 自動運転, 安全余裕
+
+## 9. CPC/IPC hints
+
+- B60W
+- G05D1/00
+- G08G1/00
+
+## 10. BigQuery SQL queries generated for Google Patents Public Data
+
+See `examples/lane_change_bigquery.sql`. The SQL is structurally validated in this repository, but it has not been executed in this environment.
+
+## 11. Candidate patent documents and assignees
+
+| Publication | Assignee | Title | Status |
+| --- | --- | --- | --- |
+| TBD from BigQuery result | TBD | TBD | candidate for IP review |
+
+## 12. Technical reason for relevance
+
+Placeholder candidates should be reviewed for overlap with lane-change path generation, predicted-object collision checks, safety margins, and autonomous-driving behavior-planning decision logic.
+
+## 13. Risk level
+
+Watch
+
+## 14. Reason for risk level
+
+This sample describes a patent-sensitive technical area, but candidate patent documents have not been retrieved or reviewed in this placeholder report.
+
+## 15. Recommended next human IP review action
+
+After configuring a Google Cloud project with BigQuery access, run a BigQuery dry run or a small `LIMIT 10` query, then collect candidate publication records, and have an IP professional review the technical overlap. Use "needs human IP review" or "not enough evidence" as dispositions; do not make legal conclusions.

.agents/skills/autoware-patent-search/examples/module_review_lane_change.md

@@ -0,0 +1,14 @@
+# Patent review workflow sample data
+
+This directory contains test-only documentation and sample configuration data for
+validating the `autoware-patent-search` module-based BigQuery workflow.
+
+These files are **not** an Autoware runtime module and should not be installed,
+launched, or proposed upstream. They are intentionally stored under the skill's
+`examples/` directory so reviewers can exercise the patent-review workflow
+without changing the real Autoware source tree or repository dependencies.
+
+The sample configuration represents a conceptual behavior-planning review target:
+lane-change path generation with a predicted-object collision-check margin. Use
+it as workflow documentation/test data for extracting technical features,
+bilingual search keywords, CPC/IPC hints, and BigQuery SQL.

.agents/skills/autoware-patent-search/examples/patent_review_sample/README.md

@@ -0,0 +1,10 @@
+# Test-only patent-review workflow sample data.
+# This file is not an Autoware runtime module, launch input, or upstream proposal.
+# It represents a conceptual lane-change behavior-planning threshold for examples.
+
+/**:
+  ros__parameters:
+    # Sample collision-check margin for lane-change path generation.
+    # Raising this value makes the validation scenario conceptually more conservative
+    # around predicted objects during lane-change safety evaluation.
+    lane_change_predicted_object_collision_margin_m: 1.8

.agents/skills/autoware-patent-search/examples/patent_review_sample/lane_change_safety_threshold.param.yaml

@@ -1,13 +1,21 @@
 # Autoware patent-search taxonomy
 
-Use these terms to build cross-database patent queries. Mix broad domain terms with the changed algorithm's specific terms.
+Use these terms to build module-based Google Patents Public Data BigQuery queries. Mix broad domain terms with the existing module's specific functions, topics, parameters, and behavior logic.
 
-## Target databases
+## Primary patent data source
 
-Only use these patent databases unless the user explicitly changes scope later:
+Use **Google Patents Public Data via BigQuery** as the primary retrieval mechanism. Generate reproducible Standard SQL against `patents-public-data.patents.publications`. Optional Google Patents search URLs may be produced only as supporting human-review links.
 
-- **Google Patents**: useful for international full-text searching, English/Japanese terms, CPC hints, and assignee filters.
-- **J-PlatPat**: useful for Japan-focused searches, FI/F-term exploration, Japanese terminology, and Japanese assignee names. Prefer recording the keywords and filters used because stable deep links may not always be available.
+Do not use non-Google patent databases for this MVP unless the user explicitly changes scope later.
+
+## Suggested MVP module targets
+
+- planning, behavior planning, trajectory planning, route planning
+- obstacle avoidance, lane change, stop decision, drivable area generation
+- vehicle control, lateral control, longitudinal control, trajectory tracking
+- fallback, MRM, safety monitor, fail operational, emergency stop, degradation
+- perception-to-planning interfaces, object prediction, predicted paths, occupancy grids
+- traffic signals, intersections, stop lines, maps, lanelets, infrastructure, V2X
 
 ## English terms
 
@@ -45,9 +53,9 @@ Use these only when the user asks to review a particular company's portfolio or
 - English examples: Toyota, Honda, Nissan, Denso, Aisin, Hitachi Astemo, Bosch, Continental, Mobileye, Waymo, Aptiv, ZF
 - Japanese examples: トヨタ, 本田技研, ホンダ, 日産, デンソー, アイシン, 日立Astemo, ボッシュ, コンチネンタル
 
-## CPC/IPC and Japan classification hints
+## CPC/IPC classification hints
 
-Use these only as search hints:
+Use these only as search hints, not legal conclusions:
 
 - B60W: vehicle control systems for different vehicle sub-units, ADAS, automated driving control
 - G05D1/00: control of position, course, altitude, or attitude of vehicles
@@ -57,4 +65,3 @@ Use these only as search hints:
 - G06V20/56: image/video understanding for autonomous driving scenes
 - G01C21/00: navigation and route guidance
 - H04W4/40: vehicle communication services, V2X-related communication
-- J-PlatPat FI/F-term exploration is useful after a relevant Japanese document is found; record FI/F-term values if they appear in candidate results.

.agents/skills/autoware-patent-search/references/search-taxonomy.md

@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-"""Compatibility wrapper that emits Google Patents search URLs for Autoware IP triage."""
+"""Compatibility wrapper that emits optional Google Patents review URLs."""
 
 from __future__ import annotations