Overview
Fully automatically generates a technology landscape map (technology source-tracing mapping) for a specified cutting-edge technology domain. Through a systematic workflow of 6 phases, it automatically completes domain analysis, target discovery, mentorship tracing, pruning and clustering, visualization output, and quality validation.
Core Features:
- 🧠 Domain Adaptation: The LLM dynamically analyzes domain characteristics at runtime and generates customized search strategies (replacing fixed templates)
- 🔄 Bidirectional Mining: Forward tracking of academic origins + reverse tracing of star project founding teams
- 🔗 Wikidata Mentorship Query: Integrates 380,000 doctoral advisor relationship records, greatly reducing tracing breakpoints
- ✂️ Powerful Pruning + Connection Strength Grading: A three-level connection strength system, retaining only Tier 1/2 connections
- 📊 Measurable Tracing Quality: Automatically calculates tracing completion rate, verification rate, and orphan rate
When to Use
Use when the user needs to conduct panoramic research on atechnology-centric cutting-edge track:
- "Help me do a technology mapping of neutral-atom quantum computing"
- "Generate a technology landscape of LLM Agent frameworks"
- "Track map of the nuclear fusion field"
Not Applicable: Highly mature, non-technology-driven industries.
Input and Output
Input
The user provides a technology domain keyword:"中性原子量子计算" / "LLM Agent 框架" / "核聚变磁约束"
Output
[Topic]_TechMap.svg— SVG vector map generated by Graphviz dot[Topic]_TechMap_Report.md— Accompanying text report (node summaries + confidence annotations + tracing statistics + VC analysis conclusions)generate_techmap.py— Map generation script (reproducible, iteratively modifiable)
Data Schema
For the node type table, edge type table, and confidence rules, see data_schema.md For the three-level connection strength hierarchy, see connection_strength.md For the visualization node color scheme/edge styles/timeline/Legend specifications, see visual_spec.md For the VC analysis framework (founder evaluation + technology route + China-foreign comparison + traceability), see vc_framework.md
Search Tool Selection Specifications
In any step that requires executing a web search, select tools according to the following process:
1. 尝试调用 tavily-search 技能
2. IF tavily-search 调用成功 → 使用结果
3. IF tavily-search 未安装 OR 调用报错(ImportError / HTTP 错误 / 超时):
→ 记录降级原因
→ 调用系统原生 search_web 工具(相同 query)
→ 使用 search_web 结果
4. IF search_web 也失败 → 标记该搜索步骤为「未完成」,继续下一步
Execute Workflow
[!CAUTION] Strictly execute in the order Phase 0 → 1 → 2 → 3 → 4 → 5. After each Phase is completed, internally check the output quality before proceeding to the next Phase.
Phase 0: Domain Adaptation & Strategy Generation 🧠
Purpose: Let the LLM analyze the characteristics of the technology domain at runtime and dynamically generate adapted search strategies and tracing paths.
Steps:
-
Domain Feature Analysis: Based on the LLM's own knowledge, analyze the following dimensions and output
domain_profile:{ "domain": "量子计算-中性原子", "knowledge_carrier": { "论文": 0.8, "专利": 0.3, "开源代码": 0.1, "产品": 0.05 }, "talent_flow_pattern": "大学PhD → 博后 → 教授创业 or 大厂", "known_anchor_persons": ["Mikhail Lukin", "Antoine Browaeys", "..."], "known_anchor_companies": ["QuEra", "Pasqal", "..."], "china_pattern": "海归教授 + 中科大/清华系", "upstream_path_type": "PhD advisor chain (2-3 layers)", "special_relations": ["同实验室师兄弟", "共同导师", "技术迁移(冷原子→中性原子)"], "search_templates": { "company_overseas": "[keyword] startup unicorn funding series", "company_china": "[关键词] 中国 创业公司 融资 A轮 B轮", "academic": "[person] PhD advisor [field] university", "academic_china": "[中文名] 博士 导师 留学 [领域]", "lab_alumni": "[advisor] lab alumni students notable startup" } }- ⚠️ AI/open-source domains:
talent_flow_patternshould be"大厂核心团队 → 独立创业"or"顶级实验室 → 开源项目 → 创业" - ⚠️ Hard-tech domains (quantum/nuclear fusion/biology): should be
"大学PhD → 博后/教授 → 创业"
- ⚠️ AI/open-source domains:
-
Anchor Validation: Use a search engine to quickly validate 2-3 anchors and correct deviations.
-
User confirmation ⚠️: Display the domain_profile summary and ask whether correction or supplementation is needed.
Phase 0 deliverables:domain_profile(domain characteristics + search strategy + anchor list), confirmed by the user.
Phase 1: Global Target Discovery
Purpose: Find the "North Star" nodes of the track—leading overseas companies, domestic startups, core open-source projects, and academic milestones.
Steps:
- Search leading companies (overseas): Use
search_templates.company_overseas, and filter for benchmark projects of unicorns valued at >$1B or big tech companies. - Search domestic startups: Use
search_templates.company_china, and filter for total funding >100 million yuan or public funding in the past two years.- ⚠️ The above templates default to the Chinese market. If coverage of other startup ecosystems such as Japan/South Korea/Israel is needed, adapt to the local language.
- Search core open-source projects(when
knowledge_carrier.开源代码 > 0.3): industry-recognized foundational frameworks/models. - Search academic milestones and major awards(when
knowledge_carrier.论文 > 0.3): use theopenalex-databaseskill. ⚠️ Nobel Prize/Wolf Prize/National Highest Award winners must be included. - Search domestic academic origins: the Chinese Academy of Sciences system, Tsinghua/Peking University/Fudan/USTC and other important research institutions.
- Build a technology evolution timeline: Extract 3-7 key technology milestone years.
- Interactive confirmation ⚠️: Show the user the list that has been discovered and wait for additions.
Phase 1 deliverables: Target list (12-25 high-value nodes) + technology evolution timeline, confirmed by the user.
Phase 2: Upstream Tracing
Purpose: Starting from all Targets, trace upstream to uncover source figures and lineage networks. Tracing depth: 2-3 layers.
⚠️ Connection strength rules: All relationships must be classified by connection_strength.md . Only Tier 1/2 enters the graph. Core criterion: citation ≠ lineage。
Steps:
-
Wikidata P184 quick query (priority): For each person, first query
scripts/wikidata_client.py'squery_doctoral_advisor(). If there is a result → skip search; if there is no result → enter the progressive search funnel. At the same time, usequery_students()to horizontally discover more entrepreneurs.- Use batch queries with
batch_query_advisors()(SPARQL VALUES batch query to avoid N+1)
- Use batch queries with
-
Progressive search funnel(when Wikidata has no result):
- Layer 1(<30s/person): Directly search the search engine for PhD advisor / educational background
- Layer 2(<60s/person): OpenAlex co-author cross-validation + university official websites
- Layer 3(<2min/person): Chinese-specific templates + news/interviews + indirect Wikidata inference
- Still not found → mark as an orphan node
-
Continue tracing the advisor's advisor (2-3 layers): Retention conditions—Nobel Prize level / trained 2+ core figures / bridge node.
-
Tracing termination rules: Stop when any condition is met — domain founder / Nobel Prize or Turing Award / cross-domain boundary / information unavailable / age exceeds threshold (60 years for hard tech, 20 years for AI/software).
⚠️ For each leaf node founder, if the technology is not independently original, it must be traced back to the independent proposer or domain founder.
-
Laboratory lateral scan: Search all important students/postdocs of core advisors to discover fellow lab entrepreneurs.
-
AI/open-source domain adaptation(when
talent_flow_patterncontains "big tech"): Build a "big tech Lab → startup company" provenance chain. -
VC analysis framework: Each company node must be labeled with a technology source tag according to vc_framework.md .
-
Provenance completeness check ⛔: Check nodes one by one, and calculate the provenance completion rate / verification rate / orphan rate. Target: completion rate >70%, orphan rate <20%.
-
Entity disambiguation: Multi-source cross-validation. Use
query_person_info(name, expected_field=...)for Wikidata disambiguation.
Phase 2 Deliverables: Origin node list + relationship edges + orphan node list + provenance metrics. Expected 30-50 nodes.
Phase 3: Powerful Pruning & Forward Fill (Pruning & Forward Fill)
Purpose: Clean data quality and aggregate into technology schools.
Steps:
- Connection strength filtering: Tier 1 → keep; Tier 2 → keep but mark as weak connection; Tier 3 → delete.
- Node pruning: Keep — pioneers of subdirections / trained 2+ entrepreneurial students / founded open source / top-tier awards / bridge nodes. Delete — pure optimization papers / purely academic with no commercialization / intermediate nodes covered by upstream / isolated nodes with only Tier 3 relationships.
- Forward fill: For grandmaster-level nodes, forward-search for missed commercialization transformations. ⚠️ Especially check domestic scholars/students.
- Clustering and grouping: Aggregate into 3-8 schools by core technology framework/route name. ⛔ Grouping by country/region is absolutely not allowed。
- Generate technical route difference annotations: Generate a "route feature card" for each Group (format see data_schema.md)。
Phase 3 Deliverables: Clean graph data (nodes + edges + groups + route_notes + timeline), expected 40-60 nodes.
Phase 4: Visualized Output (Graphviz SVG)
Purpose: Convert graph data into a high-quality, structured SVG vector graph.
Technical solution: Use Python graphviz library + dot layout engine.
[!CAUTION] The Graphviz dot engine must be used to generate SVG. Obsidian Canvas (.canvas), NetworkX + PyVis HTML, or any alternative solution is prohibited. Generation script
generate_techmap.pymust useimport graphvizand callgraphviz.Digraph, output.svgfile.
⚠️ Prerequisite dependencies: The system needs Graphviz installed (
winget install Graphviz.Graphviz). Python libraries:pip install graphviz。
Steps:
- Create
generate_techmap.py, usegraphviz.Digraph(format='svg', engine='dot') - Graph global settings: white background academic style,
rankdir: TB,dpi: 150,fontname: Microsoft YaHei - Node colors, edge styles, timeline, Legend — strictly follow visual_spec.md
- Layout constraints — Strictly follow visual_spec.md layout constraint specification(edge direction, cluster clustering, weight/constraint, rank anchoring)
- Node/edge type definitions — Strictly follow data_schema.md
- VC analysis annotations — Strictly follow vc_framework.md
- Layout verification — After generating the SVG, follow the debugging checklist to check layout correctness
Phase 4 deliverables: SVG vector graph + generation script.
Phase 5: Quality verification & report generation 📊
Purpose: Generate a quality report so users can understand the credibility and completeness of the graph.
Steps:
-
Generate accompanying report (
[Topic]_TechMap_Report.md):- Track overview + domain adaptation analysis + technology route list + full node list table + key findings
- VC analysis conclusions(independent section, must include): in-depth founder ranking, technology route maturity comparison, clarity rating of overseas origins for Chinese companies, summary of investment risk signals
-
Traceability verification table ⚠️ (must include):
| 人物 | 关系声明 | Source 1 (URL) | Source 2 (URL) | 置信度 | 状态 | -
Traceability quality statistics: traceability completion rate / multi-source verification rate / orphan rate / average confidence
Phase 5 deliverables: Text report (including traceability verification table + quality statistics).
Dependent skills
| Skill | Purpose | Required |
|---|---|---|
tavily-search |
Preferred search: If the environment is missing, downgrade to search_web |
Optional (has fallback) |
openalex-database |
Query academic papers, authors, institutions, citation networks | Optional (recommended for academic domains) |
graphviz (system + Python library) |
The only diagramming solution for Phase 4: the dot engine generates an SVG vector graph | ⚠️ Required |
⛔ Deprecated: As of v2.0.1, Obsidian Canvas (.canvas) and NetworkX + PyVis HTML output are no longer supported.
Auxiliary scripts
| Script | Purpose |
|---|---|
scripts/wikidata_client.py |
Query Wikidata doctoral advisor (P184) relationships, reverse lookup students, obtain academic information about people, batch queries |
Reference documents
| Document | Content |
|---|---|
| data_schema.md | Node/edge type definitions, confidence rules, technology route feature card format |
| connection_strength.md | Three-level connection strength criteria + 7 boundary cases |
| visual_spec.md | Graphviz node color scheme, edge styles, timeline, Legend specification |
| vc_framework.md | VC analysis framework (founder evaluation + technology routes + traceability) |
Important principles
- Fully automatic + interactive confirmation: Users only need to provide keywords to start; automatically pause for confirmation at the end of Phase 0 and Phase 1
- Domain adaptive: Dynamically generate strategies through Phase 0, without relying on fixed templates
- Moderately dense: Target number of nodes is 40-60
- Domestic coverage: Must actively search for domestic startups (financing > 100 million yuan or financing in the past two years)
- Technology differences visible: Each technology route Group must have a route feature card annotation
- Nobel Prize exception preserved: Top-tier award-winning scholars are retained as long as they are relevant to the technical路线
- Wikidata first: When tracing, check Wikidata first; if there is a result, use it directly; for batch queries use
batch_query_advisors() - Confidence transparency: When unable to confirm, mark the confidence level; never fabricate mentorship relationships
- Color is semantics: Strictly follow the visual_spec.md color system
- Chinese annotation: Keep the original English name for personal names + Chinese annotation; 🇨🇳 marks Chinese companies/scholars
- Timeline required: There must be a timeline anchored on the left side
- VC analysis required: Each company node must be annotated with 🏷️ technical source, see vc_framework.md
- Graphviz dot standard: SVG output, white-background research-style color scheme