# Industry Schema 行业资料笔记使用 YAML frontmatter 加正文。 ## Frontmatter ```yaml --- type: industry company: team: title: url: source_name: source_type: technical-report / research-blog / engineering-blog / product-blog / product-doc / code-release / benchmark / talk / other source_quality: official / official-adjacent / secondary / unknown published_at: collected_at: YYYY-MM-DD status: queued / summarized / analyzed / deprecated topics: - agent implementation_signals: - tool-use product_area: - coding-agent models: - tools: - benchmarks: - related_papers: - related_jobs: - related_experiments: - related_projects: - evidence_level: high / medium / low relevance: high / medium / low --- ``` ## Body ```text # - ## One-line Takeaway 一句话说明这条资料暴露了什么行业趋势或工程经验。 ## Source Snapshot 来源、发布日期、采集日期、来源质量。 ## What They Built or Claimed 公司发布了什么产品、系统、能力、报告或代码? ## Technical Signals - architecture: - tool use: - memory: - evaluation: - safety: - deployment: - data: ## Product and Business Signals - users: - scenario: - pricing / availability: - go-to-market: ## Evidence Quality 判断它是强证据还是弱信号。是否有论文、技术报告、benchmark、代码或只是营销描述? ## Links - papers: - jobs: - experiments: - projects: - docs: ## Gaps for Us - ## Notes - ``` ## Field Rules - `url` 和 `collected_at` 必填。 - 优先官方来源;二手来源只能作为线索。 - `evidence_level` 和 `source_quality` 必须分开:官方产品博客也可能证据很弱。 - 技术细节不足时标记为 `low`,不要强行推断实现。