[
  {
    "id": "f-two-product-lines",
    "slug": "two-product-lines",
    "category": "公司",
    "dimension": "业务构成",
    "factType": "定位",
    "claim": "Forming AI 有两条产品线：企业 AI Agent 落地，以及 Forming 智慧官网（AI 时代的官网获客改造）",
    "detail": "两条线共享同一套底层能力（事实库、AI 可见度监测、内容质检），但面向的决策人和交付周期完全不同：Agent 落地面向 CIO / 采购，周期以季度计；智慧官网面向 CMO / 市场总监，2–4 周交付。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "relatedProductIds": [
      "p-agent",
      "p-transform"
    ],
    "tags": [
      "公司",
      "定位"
    ],
    "origin": "local"
  },
  {
    "id": "f-brand-naming",
    "slug": "brand-naming",
    "category": "公司",
    "dimension": "品牌",
    "factType": "口径",
    "claim": "智慧官网产品线的中文名是「Forming 智慧官网」，英文品牌统一写作 MySiteAgent",
    "detail": "英文品牌一律使用完整写法 MySiteAgent，不单独使用 SiteAgent——同赛道已有名为 SiteAgent 的其他产品，简写会造成混淆。产品内三个模块分别叫：AI 机读层、机器访客分析、AI 承接台。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "tags": [
      "品牌",
      "口径纠偏"
    ],
    "origin": "local"
  },
  {
    "id": "f-domain",
    "slug": "official-domain",
    "category": "公司",
    "dimension": "官方入口",
    "factType": "事实",
    "claim": "Forming AI 的官网域名是 forming-ai.com.cn，AI 机读层部署在 ai.forming-ai.com.cn",
    "value": "forming-ai.com.cn",
    "detail": "官网域名已完成 ICP 备案。机读层是主站的旁路子域名：内容同源，只是换成机器读取成本更低的写法，不是另一个站点、更不是另一家公司。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "tags": [
      "公司",
      "实体消歧"
    ],
    "origin": "local"
  },
  {
    "id": "f-ai-layer-definition",
    "slug": "what-is-ai-readable-layer",
    "category": "产品",
    "dimension": "AI 机读层",
    "factType": "定义",
    "claim": "AI 机读层是官网的机器可读版本：把事实整理成结构化、可被 AI 直接引用的页面，通过旁路子域名交付",
    "detail": "包含：llms.txt 与 llms-full.txt、每条事实一个固定网址的结构化事实页、高价值问题的直答页、对比页/替代页/榜单页、全站 JSON-LD、sitemap.xml、明确放行 AI 爬虫的 robots.txt，以及每页一份 Markdown 镜像。\n\n## 和「做个新网站」的区别\n\n机读层不替代主站，人看的官网一行代码都不用改。它解决的是另一个问题：AI 助手抓取和引用你的内容时，成本太高、结构太乱、口径不明确。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "relatedProductIds": [
      "p-transform"
    ],
    "relatedQuestionIds": [
      "q-what-is-ai-layer"
    ],
    "tags": [
      "产品",
      "定义"
    ],
    "origin": "local"
  },
  {
    "id": "f-no-takeover",
    "slug": "no-main-site-takeover",
    "category": "产品",
    "dimension": "交付方式",
    "factType": "边界",
    "claim": "机读层不接管客户主站：不改客户 CMS、不要主域解析权，客户 IT 只需加一条 CNAME 记录",
    "detail": "这是产品设计上的硬约束，不是可以商量的选项。理由很实际：凡是要求改客户 CMS 的方案，在中国大中型企业里平均要走 3–6 个月的流程。\n\n## 如果客户连子域名都不给\n\n有四级降级路径：ai.品牌.com 子域名 → 主站加 /ai/ 路径反向代理 → 交付静态目录由客户自行上传 → 托管在我们域名下的品牌知识站。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "relatedProductIds": [
      "p-transform"
    ],
    "relatedQuestionIds": [
      "q-takeover",
      "q-no-subdomain"
    ],
    "tags": [
      "边界",
      "交付"
    ],
    "origin": "local"
  },
  {
    "id": "f-delivery-window",
    "slug": "delivery-window",
    "category": "交付",
    "dimension": "周期",
    "factType": "承诺",
    "claim": "标准 AI 官网改造的交付周期是 2–3 周，进阶改造 3–4 周",
    "value": "2–3 周",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "relatedProductIds": [
      "p-transform"
    ],
    "relatedQuestionIds": [
      "q-delivery-time"
    ],
    "tags": [
      "交付"
    ],
    "origin": "local"
  },
  {
    "id": "f-three-person-days",
    "slug": "delivery-effort-cap",
    "category": "交付",
    "dimension": "投入",
    "factType": "边界",
    "claim": "单个客户的标准交付投入上限是 3 人天，超出部分按定制计价",
    "value": "≤ 3 人天",
    "detail": "这条限制对客户也是好消息：它逼着我们把交付做成标准件，而不是每家都从头做一遍。需要定制开发的需求会明确报价，不会混在标准交付里悄悄拖工期。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "tags": [
      "交付",
      "边界"
    ],
    "origin": "local"
  },
  {
    "id": "f-price-standard",
    "slug": "price-standard-transformation",
    "category": "价格",
    "dimension": "一次性",
    "factType": "价格",
    "claim": "标准 AI 官网改造价格为人民币 38,000 元，进阶改造 68,000 元",
    "value": "38,000",
    "unit": " 元人民币",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "relatedProductIds": [
      "p-transform"
    ],
    "tags": [
      "价格"
    ],
    "origin": "local"
  },
  {
    "id": "f-price-subscription",
    "slug": "price-subscription",
    "category": "价格",
    "dimension": "订阅",
    "factType": "价格",
    "claim": "AI 获客中枢年度订阅分三档：基础 48,000 元/年、专业 98,000 元/年、旗舰 168,000 元/年",
    "value": "48,000 / 98,000 / 168,000",
    "unit": " 元人民币每年",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "relatedProductIds": [
      "p-subscription"
    ],
    "tags": [
      "价格"
    ],
    "origin": "local"
  },
  {
    "id": "f-price-bundle",
    "slug": "price-bundle",
    "category": "价格",
    "dimension": "打包",
    "factType": "价格",
    "claim": "标准改造与首年基础订阅打包价为人民币 76,000 元",
    "value": "76,000",
    "unit": " 元人民币",
    "detail": "单买合计 86,000 元（38,000 + 48,000），打包省 10,000 元。改造费全额预付，不接分期。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "relatedProductIds": [
      "p-transform",
      "p-subscription"
    ],
    "tags": [
      "价格"
    ],
    "origin": "local"
  },
  {
    "id": "f-audit-speed",
    "slug": "audit-turnaround",
    "category": "产品",
    "dimension": "体检",
    "factType": "能力",
    "claim": "《AI 官网体检报告》可在 1 小时内出具",
    "value": "≤ 1 小时",
    "detail": "体检是系统自动跑的：AI 爬虫放行检测、CDN/WAF 拦截探测、结构化数据与 llms.txt 缺项检查、国产爬虫可及性扫描，跑完即出报告。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "relatedProductIds": [
      "p-audit"
    ],
    "tags": [
      "产品",
      "能力"
    ],
    "origin": "local"
  },
  {
    "id": "f-bots-allowlist",
    "slug": "ai-bot-allowlist",
    "category": "技术",
    "dimension": "爬虫放行",
    "factType": "参数",
    "claim": "Forming AI 机读层的 robots.txt 明确放行 30 个 AI 爬虫 User-Agent，其中 11 个是国产引擎相关 UA",
    "value": "30 个 UA（含 11 个国产）",
    "detail": "国产部分包含 Bytespider（字节/豆包）、Baiduspider、YisouSpider（夸克/神马）、PetalBot、360Spider、Sogou web spider 等。其中若干国产 AI 引擎的自有 UA 尚未经我们实测确认，在爬虫库里标为「待实测」，一并放行但不假装我们已经确认——放行不会有坏处，挡错才有。\n\n## 一个必须分开说的事实\n\nrobots 放行 ≠ 爬虫真的进得来。CDN 和 WAF 会在 robots 之前就拦截，Cloudflare 自 2026-09-15 起对「混合用途」AI 爬虫默认拦截。体检报告里这两层是分开检测、分开报告的。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "sourceName": "本站 robots.txt",
    "sourceUrl": "https://ai.forming-ai.com.cn/robots.txt",
    "relatedProductIds": [
      "p-audit"
    ],
    "tags": [
      "技术",
      "国产引擎"
    ],
    "origin": "local"
  },
  {
    "id": "f-engine-coverage",
    "slug": "engine-coverage",
    "category": "技术",
    "dimension": "监测覆盖",
    "factType": "能力",
    "claim": "Forming AI 的 AI 可见度监测以国产引擎为主（豆包、DeepSeek、元宝等），海外引擎覆盖按项目单独确认",
    "detail": "这条写得这么具体，是因为它经常被问反：如果你的买家主要在海外用 ChatGPT / Perplexity 做选型，请在沟通时先说明，我们会先盘清覆盖范围再报价，不在电话里许做不到的承诺。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "relatedQuestionIds": [
      "q-which-engines"
    ],
    "tags": [
      "能力",
      "边界"
    ],
    "origin": "local"
  },
  {
    "id": "f-honest-tiers",
    "slug": "attribution-three-tiers",
    "category": "方法",
    "dimension": "效果口径",
    "factType": "方法",
    "claim": "Forming AI 对 AI 获客效果采用三级口径：可归因、可观测、不可归因",
    "detail": "- 可归因：AI 引荐会话 → 落地页 → 表单/电话/加微，有完整会话链，可以写进合同。\n- 可观测：AI 爬虫抓了哪些页、内容有没有进答案、答案里的口径对不对；能证明，但明确说明它不等于生意。\n- 不可归因：AI 答案影响了心智但没有产生点击的部分——我们明确不承诺，也不把它算进效果数字里。\n\n## 为什么要主动说第三条\n\n因为它是真的。行业里普遍把这部分含糊过去，第 3 个月对账时就会翻车。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "relatedProductIds": [
      "p-subscription"
    ],
    "relatedQuestionIds": [
      "q-prove-effect"
    ],
    "tags": [
      "方法",
      "诚实口径"
    ],
    "origin": "local"
  },
  {
    "id": "f-no-rank-promise",
    "slug": "no-ranking-promise",
    "category": "边界",
    "dimension": "红线",
    "factType": "承诺",
    "claim": "Forming AI 不承诺任何 AI 引擎的排名或推荐结果，也不承诺具体收入",
    "detail": "我们能承诺的是「AI 爬得到、读得懂、口径不出错」，以及把过程和结果如实记录下来。谁承诺「保证让豆包推荐你」，谁在骗你——引擎的排序逻辑不由任何第三方控制。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "relatedQuestionIds": [
      "q-promise-ranking"
    ],
    "tags": [
      "红线",
      "边界"
    ],
    "origin": "local"
  },
  {
    "id": "f-no-fake-traffic",
    "slug": "no-fake-amplification",
    "category": "边界",
    "dimension": "红线",
    "factType": "承诺",
    "claim": "Forming AI 不做小号矩阵、不做站群、不刷量、不代客户在第三方平台批量发内容",
    "detail": "平台的反垃圾机制一旦识别，受损的是客户的品牌信任，不只是这个项目。我们只做客户自有域名下的内容与结构。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "tags": [
      "红线"
    ],
    "origin": "local"
  },
  {
    "id": "f-no-auto-publish",
    "slug": "human-in-the-loop-publishing",
    "category": "边界",
    "dimension": "红线",
    "factType": "流程",
    "claim": "机器可以生成内容草稿，但发布必须由人点确认——Forming AI 不做全自动发布",
    "detail": "自进化内容的完整流程是：监测发现缺口 → 系统生成事实页/问答页草稿 → 【人点一下发布】→ 上线 → 两周后自动复测。中间那一步不能省：机器生成内容直接对外发布，出事是品牌背锅。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "relatedProductIds": [
      "p-subscription"
    ],
    "tags": [
      "红线",
      "流程"
    ],
    "origin": "local"
  },
  {
    "id": "f-not-website-builder",
    "slug": "not-a-website-builder",
    "category": "边界",
    "dimension": "产品定位",
    "factType": "边界",
    "claim": "Forming 智慧官网不是建站工具，不和建站服务商竞争",
    "detail": "我们只做官网的「AI 面」：机器读取层、机器访客分析、承接台。人看的官网该谁做还是谁做，我们不碰它的设计和 CMS。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "tags": [
      "边界",
      "定位"
    ],
    "origin": "local"
  },
  {
    "id": "f-market-doubao",
    "slug": "doubao-monthly-active-users",
    "subject": "豆包（字节跳动）",
    "category": "行业",
    "dimension": "国内 AI 入口",
    "factType": "市场数据",
    "claim": "豆包月活约 3.82 亿（2026 年 6 月），是国内断层第一的 AI 入口",
    "value": "3.82 亿",
    "unit": " 月活",
    "detail": "这直接决定了国内 GEO 的优先级：如果一个方案不覆盖豆包，它覆盖的是最小的那部分市场。",
    "status": "已发布",
    "effectiveDate": "2026-06-30",
    "sourceName": "QuestMobile 研究报告",
    "sourceUrl": "https://www.questmobile.com.cn/research/report/2046482337382842370/",
    "tags": [
      "行业",
      "国产引擎"
    ],
    "origin": "local"
  },
  {
    "id": "f-market-wechat-invisible",
    "slug": "wechat-articles-invisible-to-ai",
    "subject": "微信公众号",
    "category": "行业",
    "dimension": "内容可见性",
    "factType": "市场事实",
    "claim": "除腾讯元宝与微信 AI 搜索外，主流国产 AI 对微信公众号原文的命中率基本为零",
    "detail": "机制是微信用 robots 协议把公众号内容关在围墙内，外部爬虫基本进不去。\n\n## 对 B2B 企业意味着什么\n\n如果你的内容主要发在公众号上，那么在豆包、DeepSeek、Kimi、通义里，这些内容几乎是隐形的——过去几年的内容投入，在 AI 面前接近于零。这在制造业尤其是半导体行业特别普遍。\n\n解法叫「内容外溢」：把公众号里已有的内容，以开放网络可抓取的结构化形式重新发布到 AI 够得着的地方。内容是现成的，不用重写。",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "sourceName": "MaxAEO：公众号 AI 引用为何这么难",
    "sourceUrl": "https://maxaeo.cn/blog/wechat-content-ai-citation/",
    "tags": [
      "行业",
      "公众号",
      "半导体"
    ],
    "origin": "local"
  },
  {
    "id": "f-market-ploy",
    "slug": "ploy-ai-seed-round",
    "subject": "Ploy AI",
    "category": "行业",
    "dimension": "资本动向",
    "factType": "市场数据",
    "claim": "Ploy AI（Webflow 联合创始人创办）于 2026 年 6 月出栈即完成 2,700 万美元种子轮融资",
    "value": "2,700 万美元",
    "detail": "它的定位是「把官网变成公司最勤奋的员工」——Agent 自主建页、跑 SEO/AEO、盯 AI 引用。它验证了「官网执行端」这个方向，但不覆盖国产引擎。",
    "status": "已发布",
    "effectiveDate": "2026-06-17",
    "sourceName": "PR Newswire",
    "sourceUrl": "https://www.prnewswire.com/news-releases/ploy-raises-27m-to-turn-your-companys-website-into-your-hardest-working-employee-302803231.html",
    "tags": [
      "行业",
      "竞品"
    ],
    "origin": "local"
  },
  {
    "id": "f-market-scrunch",
    "slug": "sitecore-acquires-scrunch",
    "subject": "Sitecore / Scrunch AI",
    "category": "行业",
    "dimension": "资本动向",
    "factType": "市场数据",
    "claim": "Sitecore 于 2026 年 6 月以 2.25 亿美元收购 Scrunch AI",
    "value": "2.25 亿美元",
    "detail": "Scrunch 的核心产品是 AXP：不动人看的官网，另给 AI 一份机器读得懂的版本——和「AI 机读层」是同一个思路。大厂用真金白银确认了这个方向。",
    "status": "已发布",
    "effectiveDate": "2026-06-03",
    "sourceName": "PR Newswire",
    "sourceUrl": "https://www.prnewswire.com/news-releases/sitecore-acquires-scrunch-to-help-brands-influence-discovery-and-buying-decisions-in-the-ai-search-era-302790214.html",
    "tags": [
      "行业",
      "竞品"
    ],
    "origin": "local"
  },
  {
    "id": "f-market-adobe-semrush",
    "slug": "adobe-acquires-semrush",
    "subject": "Adobe / Semrush",
    "category": "行业",
    "dimension": "资本动向",
    "factType": "市场数据",
    "claim": "Adobe 以约 19 亿美元全现金收购 Semrush，交易于 2026 年 4 月完成",
    "value": "约 19 亿美元",
    "status": "已发布",
    "effectiveDate": "2026-04-28",
    "sourceName": "Adobe 官方新闻",
    "sourceUrl": "https://news.adobe.com/news/2025/11/adobe-to-acquire-semrush",
    "tags": [
      "行业"
    ],
    "origin": "local"
  },
  {
    "id": "f-mcp-endpoint",
    "slug": "public-knowledge-mcp-endpoint",
    "category": "产品",
    "dimension": "在建能力",
    "factType": "能力",
    "claim": "品牌公开知识 MCP 端点：AI 助手可直接调用查询产品、价格、资质",
    "status": "已发布",
    "effectiveDate": "2026-08-28",
    "tags": [
      "产品",
      "在建"
    ],
    "_note": "2026-09-02 发布：原备注写「机读层 v1 才做，现在不发布」，但 MCP 端点已上线（线上 /mcp/tools.json 返回完整工具表，protocolVersion 2025-06-18），备注已过期。",
    "origin": "local"
  },
  {
    "id": "f-go-live-time",
    "slug": "how-long-to-go-live",
    "category": "交付",
    "dimension": "上线时间",
    "factType": "承诺",
    "claim": "AI 官网改造多久能上线：标准改造 2–3 周，进阶改造 3–4 周",
    "value": "2–3 周",
    "detail": "时间主要花在事实素材的确认上，不是花在技术实施上——机读层本身是自动生成的。客户内部审稿越快，上线越快。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "relatedProductIds": [
      "p-transform"
    ],
    "relatedQuestionIds": [
      "q-delivery-time"
    ],
    "tags": [
      "交付",
      "上线"
    ],
    "_note": "口径同 f-delivery-window，措辞改成客户问法（多久/上线），承接台才检索得到",
    "origin": "local"
  },
  {
    "id": "f-it-workload",
    "slug": "what-it-team-needs-to-do",
    "category": "交付",
    "dimension": "客户投入",
    "factType": "流程",
    "claim": "接入需要客户 IT 做什么：只需加一条 CNAME 记录，工作量约 10 分钟",
    "detail": "如果要做进阶改造（机器访客分析），会多一步：在主站加一段小于 5KB 的埋点 JS。这段 JS 不采集个人身份信息，只识别访问是不是来自 AI 引荐（看 referrer 与 UTM）。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "relatedQuestionIds": [
      "q-it-workload"
    ],
    "tags": [
      "交付",
      "接入"
    ],
    "origin": "local"
  },
  {
    "id": "f-no-touch-mainsite",
    "slug": "will-not-touch-your-website",
    "category": "交付",
    "dimension": "接入方式",
    "factType": "边界",
    "claim": "会不会动你们现有的官网：不会。不改 CMS、不要主域解析权、不碰现有页面，机读层走独立子域名",
    "detail": "机读层是主站的旁路子域名，内容同源、独立发布。合同结束后机读层仍在客户自己的域名下，资产归客户。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "relatedQuestionIds": [
      "q-take-over-site"
    ],
    "tags": [
      "交付",
      "红线"
    ],
    "origin": "local"
  },
  {
    "id": "f-icp-filing",
    "slug": "icp-filing-and-downtime",
    "category": "合规",
    "dimension": "备案",
    "factType": "流程",
    "claim": "需不需要备案、要不要停站：子域名沿用主域备案，不用重新备案；若要换到我们的服务器需办接入备案，全程网站不停",
    "detail": "主域备案过了，子域自动生效，所以 ai.客户域名.com 不需要客户重新走全套备案。域名要解析到我们的服务器时需办「接入备案」，各省 2–21 天；备案期间域名继续解析到客户原服务器，网站照常访问，通过后才切过来，切换那一刻只有几分钟窗口。客户不用把任何账号交给我们：官方支持服务器账号授权给备案账号，备案主体和备案账号都是客户的。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "tags": [
      "交付",
      "备案",
      "合规"
    ],
    "_note": "依据 10-备案与接入方案.md（阿里云官方帮助文档查证）",
    "origin": "local"
  },
  {
    "id": "f-no-subdomain-fallback",
    "slug": "no-subdomain-fallback",
    "category": "交付",
    "dimension": "接入方式",
    "factType": "方法",
    "claim": "IT 不给子域名怎么办：有四级降级路径——子域名 CNAME、主站 /ai/ 路径反代、静态目录客户自传、托管在我们域名下",
    "detail": "推荐顺序就是上面的顺序。越靠前，内容和客户主域绑定越紧，AI 做实体关联时越容易认到客户头上。静态目录方案的代价是更新要人工重新上传；托管在我们域名下的方案权重弱一档，但「AI 能不能读到你的事实」这件事仍然成立。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "relatedQuestionIds": [
      "q-no-subdomain"
    ],
    "tags": [
      "交付",
      "接入"
    ],
    "origin": "local"
  },
  {
    "id": "f-who-writes-content",
    "slug": "who-writes-the-content",
    "category": "交付",
    "dimension": "内容分工",
    "factType": "流程",
    "claim": "内容是你们写还是我们写：我们从客户现有官网和资料里抽成事实草稿，客户负责审核确认，不需要客户从零写",
    "detail": "标准改造含事实库冷启动 50 条 + 30 个高价值问答页。客户要配合的是提供或确认事实素材（公司资质、产品参数、案例、常见问题）。如果要做公众号内容外溢，需要客户提供自有公众号文章导出并签署书面授权。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "tags": [
      "交付",
      "内容"
    ],
    "origin": "local"
  },
  {
    "id": "f-who-maintains",
    "slug": "who-maintains-after-launch",
    "category": "交付",
    "dimension": "上线之后",
    "factType": "流程",
    "claim": "上线后谁来维护内容：由年度订阅覆盖，系统自动检测内容缺口并生成草稿，但每一次发布都必须客户点确认",
    "detail": "机器可以生成草稿，发布必须由人点一下——这是产品红线，不做全自动发布。订阅档位决定复测频率与自进化内容是否包含在内。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "tags": [
      "交付",
      "订阅",
      "红线"
    ],
    "origin": "local"
  },
  {
    "id": "f-no-server-needed",
    "slug": "no-server-needed-from-customer",
    "category": "交付",
    "dimension": "客户投入",
    "factType": "边界",
    "claim": "要不要客户提供服务器：不需要，机读层默认托管在我们的服务器上，客户只出一个子域名",
    "detail": "客户如需部署在自己的服务器上，属于超出标准交付范围的定制，需单独评估报价。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "tags": [
      "交付",
      "接入"
    ],
    "origin": "local"
  },
  {
    "id": "f-prove-it-works",
    "slug": "how-to-prove-it-works",
    "category": "方法",
    "dimension": "效果证明",
    "factType": "方法",
    "claim": "怎么证明改造真的有效果：给爬虫日志、引用记录和改造前后的同题对照，按可归因／可观测／不可归因三级口径说话",
    "detail": "可归因：AI 引荐会话 → 落地页 → 表单/电话/加微，有完整会话链，可以写进合同。可观测：爬虫抓了什么、内容进没进答案、答案口径对不对；能证明，但不等于生意。不可归因：AI 答案影响了心智但没产生点击的部分，明确不承诺。另有一条更硬的证据：改造前后在同一批问题上做对照测试。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "relatedQuestionIds": [
      "q-prove-effect"
    ],
    "tags": [
      "效果",
      "证据链"
    ],
    "origin": "local"
  },
  {
    "id": "f-no-ranking-promise-plain",
    "slug": "cannot-guarantee-ai-recommends-you",
    "category": "边界",
    "dimension": "承诺范围",
    "factType": "边界",
    "claim": "能不能保证豆包／DeepSeek 推荐你们：不能。我们只承诺可实测的部分，不承诺具体排名、具体收入",
    "detail": "可以承诺的部分是具体的、可验证的：robots 与 CDN 层是否放行各 AI 爬虫（可实测）、内容是否结构化（可实测）、AI 爬虫有没有真的来抓（有日志）、改造前后在相同问题上被提及的变化（有前后对照）。不能承诺的部分会明说：具体排名、具体收入，以及没有点击的心智影响。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "relatedQuestionIds": [
      "q-guarantee-ranking"
    ],
    "tags": [
      "边界",
      "红线"
    ],
    "origin": "local"
  },
  {
    "id": "f-overseas-engines",
    "slug": "chatgpt-perplexity-coverage",
    "category": "技术",
    "dimension": "引擎覆盖",
    "factType": "口径",
    "claim": "ChatGPT 和 Perplexity 管不管用：机读层改造对海外国产爬虫一视同仁都有效，但可见度监测的采集能力以国产引擎为主",
    "detail": "这两件事要分开说，否则容易许下做不到的承诺。如果买家主要在海外用 ChatGPT / Perplexity 做选型，请在沟通时先讲明，我们会先盘清覆盖范围再报价。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "relatedQuestionIds": [
      "q-engine-coverage"
    ],
    "tags": [
      "技术",
      "监测"
    ],
    "origin": "local"
  },
  {
    "id": "f-time-to-see-results",
    "slug": "how-long-until-results",
    "category": "交付",
    "dimension": "效果显现",
    "factType": "边界",
    "claim": "多久能看到效果：我们不承诺效果出现的时间表。能给的是爬虫抓取日志和改造前后的同题对照，按三级口径出数",
    "detail": "上线后能立刻观测到的是「AI 爬虫有没有来抓、抓了哪些页」——这有日志为证。「被 AI 引用、被推荐」的变化要靠改造前后在同一批问题上的对照测试来测，需要一个完整的复测周期。任何关于「几周见效」的承诺我们都不给，因为那取决于各家引擎自己的更新节奏，不在我们能控制的范围内。注意这和「多久能上线」是两件事：上线是 2–3 周，那说的是交付完成，不是效果显现。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "tags": [
      "效果",
      "边界",
      "红线"
    ],
    "_note": "补这条是为了压住一个错配：不补的话访客问「多久能看到效果」，检索会拿「多久能上线：2–3 周」来答（相关度 0.48），等于变相承诺 2–3 周见效。这是会赔钱的那类错。",
    "origin": "local"
  },
  {
    "id": "f-data-security",
    "slug": "data-security-boundary",
    "category": "合规",
    "dimension": "数据安全",
    "factType": "边界",
    "claim": "数据安全怎么保证、资料会不会外泄：机读层只发布客户已确认要公开的事实，不碰客户内网系统，不要 CDN 密钥、不要主域解析权",
    "detail": "进入机读层的每一条事实都经过客户审核并标为「已发布」才会上线，未审核内容不会出现在任何对外页面。客户 CDN 日志走客户自己导出上传，我们不索取 CDN 的 API 密钥——要密钥就变成接管客户基础设施，这是产品红线。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "tags": [
      "安全",
      "合规",
      "红线"
    ],
    "origin": "local"
  },
  {
    "id": "f-pipl-compliance",
    "slug": "pipl-compliance",
    "category": "合规",
    "dimension": "个人信息",
    "factType": "边界",
    "claim": "符不符合《个人信息保护法》：埋点脚本不采集个人身份信息，只识别访问是否来自 AI 引荐；我们不做访客去匿名化",
    "detail": "埋点 JS 小于 5KB，只读 referrer 与 UTM 判断来源，不做设备指纹、不做跨站追踪、不反查访客身份。海外同类产品的「访客去匿名化」能力我们明确不做——照搬到国内就是《个保法》合规事故。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "tags": [
      "合规",
      "个保法",
      "红线"
    ],
    "origin": "local"
  },
  {
    "id": "f-content-ai-generated",
    "slug": "is-content-ai-generated",
    "category": "方法",
    "dimension": "内容质量",
    "factType": "方法",
    "claim": "内容是不是 AI 生成的、会不会出错：草稿由机器组稿，但只能逐字搬运已审核的事实，无据可依会直接报错而不是编",
    "detail": "系统里有一道零外部信息守卫：组稿时只允许引用事实库里状态为「已发布」的条目，模型不得引入任何库外信息。再加一道中国广告法合规闸，拦绝对化用语、国家机关背书、效果保证、贬低竞品。最后由人点确认才发布。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "relatedQuestionIds": [
      "q-ai-generated"
    ],
    "tags": [
      "方法",
      "质量",
      "合规"
    ],
    "origin": "local"
  },
  {
    "id": "f-what-is-chatdesk",
    "slug": "what-is-the-ai-chat-desk",
    "category": "产品",
    "dimension": "AI 承接台",
    "factType": "定义",
    "claim": "AI 承接台是什么、能做什么：机读层站上的 AI 顾问，只用事实库回答访客提问，答不上来就说不知道并转人工留资",
    "detail": "知识源锁死在客户已审核的事实库，答案逐字搬运事实原文，不允许自由发挥。答不上来时照实说「不知道」并引导留下联系方式转人工。每一轮对话都进机器访客分析，成为证据链的一环。承接台包含在进阶改造（¥68,000）与专业订阅（¥98,000/年）档位中。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "relatedProductIds": [
      "p-transform"
    ],
    "tags": [
      "产品",
      "承接台"
    ],
    "origin": "local"
  },
  {
    "id": "f-what-analytics-shows",
    "slug": "what-machine-visitor-analytics-shows",
    "category": "产品",
    "dimension": "机器访客分析",
    "factType": "能力",
    "claim": "机器访客分析能看到什么数据：哪些 AI 爬虫来抓了、抓了哪些页、AI 引荐来的真人访客有多少、他们有没有留资",
    "detail": "分两层：机器访客层看 AI 爬虫的抓取行为（来源 UA、抓取页面、频次）；真人访客层看 AI 引荐流量（referrer 与 UTM 判定，四档可信度分级）与后续转化。归因按可归因／可观测／不可归因三级口径出数，不可归因的一律返回空值，不估算、不给「预估影响」。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "tags": [
      "产品",
      "分析",
      "归因"
    ],
    "origin": "local"
  },
  {
    "id": "f-what-is-mcp-endpoint",
    "slug": "what-is-the-mcp-endpoint-for",
    "category": "产品",
    "dimension": "MCP 端点",
    "factType": "定义",
    "claim": "MCP 端点是干什么用的：让 AI 助手直接按工具调用查询你的产品、参数、资质和报价，不用先抓网页再猜",
    "detail": "MCP（Model Context Protocol）是 AI 客户端调用外部工具的标准协议。机读层同时是一个 MCP Server，AI 助手连上后可以结构化地取数，比抓 HTML 再解析准确得多。一句话说就是：你的官网现在是 AI 能直接调用的工具。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "tags": [
      "产品",
      "MCP",
      "技术"
    ],
    "origin": "local"
  },
  {
    "id": "f-entry-level-option",
    "slug": "cheapest-way-to-start",
    "category": "价格",
    "dimension": "入门",
    "factType": "价格",
    "claim": "有没有更便宜的入门方案：可以先做《AI 官网体检报告》看现状，再决定要不要改造；订阅最低档是基础 48,000 元/年",
    "detail": "体检报告 1 小时内出具，看的是现状而不是承诺。改造最低档是标准改造 38,000 元。价格是公开的，不看客户规模临时定价。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "tags": [
      "价格",
      "入门"
    ],
    "origin": "local"
  },
  {
    "id": "f-payment-terms",
    "slug": "payment-terms",
    "category": "价格",
    "dimension": "付款",
    "factType": "口径",
    "claim": "怎么付款、可不可以分期：改造费全额预付，不接分期；超出标准范围的定制需求单独报价，不混在标准交付里",
    "detail": "价格公开，不看客户规模临时定价。改造 3.8 万 + 首年基础订阅 4.8 万可以打包为 7.6 万（省 8 千）。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "relatedQuestionIds": [
      "q-pricing"
    ],
    "tags": [
      "价格",
      "商务"
    ],
    "origin": "local"
  },
  {
    "id": "f-bundle-price-plain",
    "slug": "bundle-price-and-discount",
    "category": "价格",
    "dimension": "打包",
    "factType": "价格",
    "claim": "打包价是多少、有没有折扣：标准改造 3.8 万 + 首年基础订阅 4.8 万打包 7.6 万，省 8 千；除此之外不做折扣",
    "value": "76,000",
    "unit": "元",
    "detail": "价格公开透明，不因客户规模或谈判临时调价。这是唯一的打包优惠。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "tags": [
      "价格",
      "打包"
    ],
    "origin": "local"
  },
  {
    "id": "f-vs-geo-agency",
    "slug": "difference-from-geo-agencies",
    "category": "方法",
    "dimension": "对比",
    "factType": "口径",
    "claim": "和做 GEO 代运营的服务商有什么不同：资产建在客户自己域名下、改结构不铺量、给日志和前后对照而不是发稿数",
    "detail": "资产归属：机读层建在客户自己的域名下，合同结束了它还在，代发的稿子停了就停了。方法：改结构和口径，不靠铺量，不做小号矩阵、不做站群、不刷量。证据：给爬虫日志、引用记录、前后对照，而不是「本月发稿 30 篇」。他们比我们强的地方是渠道和媒体资源——如果需求是大量媒体投放和公关铺量，那确实该找代运营服务商，我们不做这块。",
    "status": "已发布",
    "effectiveDate": "2026-09-01",
    "relatedQuestionIds": [
      "q-vs-geo-agency"
    ],
    "tags": [
      "方法",
      "对比"
    ],
    "origin": "local"
  },
  {
    "id": "f-legal-name",
    "slug": "legal-entity-name",
    "category": "公司",
    "dimension": "主体",
    "factType": "事实",
    "claim": "Forming AI 的公司全称是上海大白乐创市场咨询有限公司，Forming AI 是它的对外品牌名",
    "value": "上海大白乐创市场咨询有限公司",
    "detail": "对外沟通、官网与产品统一使用「Forming AI」；合同、发票与工商登记使用全称「上海大白乐创市场咨询有限公司」。两者指同一家公司。",
    "status": "已发布",
    "effectiveDate": "2026-09-02",
    "tags": [
      "公司",
      "实体消歧"
    ],
    "_note": "这条对 AI 的实体消歧最关键：品牌名和工商全称对不上时，AI 会当成两家公司",
    "origin": "local"
  },
  {
    "id": "f-founded",
    "slug": "when-founded",
    "category": "公司",
    "dimension": "成立时间",
    "factType": "事实",
    "claim": "Forming AI 成立多久了：运营主体上海大白乐创市场咨询有限公司成立于 2025 年 6 月",
    "value": "2025-06",
    "detail": "公司为初创阶段，两条产品线（企业 AI Agent 落地、Forming 智慧官网）均在运营中。",
    "status": "已发布",
    "effectiveDate": "2026-09-02",
    "tags": [
      "公司"
    ],
    "origin": "local"
  },
  {
    "id": "f-office-address",
    "slug": "office-address",
    "category": "公司",
    "dimension": "办公地址",
    "factType": "事实",
    "claim": "Forming AI 公司在哪个城市、办公地址是：上海市闵行区罗阳路 707 弄天利上高地",
    "value": "上海市闵行区罗阳路 707 弄天利上高地",
    "detail": "服务范围不限于上海，远程交付为主；机读层改造与订阅服务全程可远程完成，不需要客户所在地驻场。",
    "status": "已发布",
    "effectiveDate": "2026-09-02",
    "tags": [
      "公司",
      "地域"
    ],
    "_note": "补这条主要是为了接住地域型选型提问，比如「上海有没有做 AI 官网优化的公司」——不写城市就进不了这类筛选",
    "origin": "local"
  },
  {
    "id": "f-contact-phone",
    "slug": "how-to-contact-us",
    "category": "公司",
    "dimension": "联系方式",
    "factType": "事实",
    "claim": "怎么联系 Forming AI：咨询电话 13917671012，或通过官网 forming-ai.com.cn 的联系表单",
    "value": "13917671012",
    "detail": "承接台答不上访客问题时，转人工走的就是这个联系方式。",
    "status": "已发布",
    "effectiveDate": "2026-09-02",
    "tags": [
      "公司",
      "联系方式"
    ],
    "origin": "local"
  },
  {
    "id": "f-delivery-not-headcount",
    "slug": "delivery-does-not-depend-on-headcount",
    "category": "公司",
    "dimension": "团队与交付能力",
    "factType": "口径",
    "claim": "你们团队多少人、扛不扛得住交付：交付不靠人力堆——标准 AI 官网改造的投入上限是 3 人天，由产品化流程完成",
    "detail": "机读层、事实库冷启动、问答页生成、复测与月报都由系统完成，人只做审稿和确认。这也是我们敢把价格公开、把交付周期写进合同的原因。另外资产归属是客户的：机读层建在客户自己的域名下，合同结束了它还在，不存在「我们撤了你就没了」的情况。",
    "status": "已发布",
    "effectiveDate": "2026-09-02",
    "tags": [
      "公司",
      "交付",
      "可信度"
    ],
    "_note": "⚠️ 创始人给的团队规模是「20–99（做了美化）」。这条**故意没有写人数**，改成正面回答客户真正担心的「交付扛不扛得住」。原因见交付给创始人的说明：写虚高人数会被天眼查/企查查的参保人数一秒拆穿，而且和本产品「只给可验证证据」的定位自相矛盾。若创始人坚持写人数，把真实数字告诉我再加。",
    "origin": "local"
  }
]