arXiv:2605.17812cs.AI2026-05

垂直AI公司该保留核心责任还是剥离界面?关键在区分可变接口与不可让渡的责任边界。

Going Headless? On the Boundaries of Vertical AI Firms

  • 按责任归属而非界面设计拆分系统,避免价值流失。
  • 未来治理负担(规则债务)由客户承担,集成平台可规避此风险。
  • 适合需专业签发、合规流程的领域,如医疗、法律等场景。

垂直AI企业传统上将工作流、领域逻辑与责任整合于单一应用中。通用AI代理正打破这一结构,促使创始人和投资者倡导“去头化”:将界面与工作流交由代理,仅以可调用服务形式暴露领域专长。本文指出,去头化对某些企业合理,对另一些则具有破坏性,后者常因看似界面选择的架构决策而无意丧失价值捕获能力。这本质是边界问题——界面边界可迁移,但责任边界通常不可动摇。基于科斯的企业理论、Eisenmann等人的平台包裹框架及Teece的互补资产与收益捕获分析,文章揭示:即使技术互操作性提升,通过开放协议运营的协调者仍能获得包裹优势;持久价值集中在共协责任资产上——专业签发、受监管流程、证据链与可信记录系统。文章提出三类定位(组件、集成平台、双轨制),不取决于行业,而取决于任务-责任模式,并引入“规则债务”概念:当业务规则与专业标准从受控系统迁移至提示词与代理指令时,客户组织将承担未来的治理、维护与问责负担。由此衍生四条原则:按责任分解而非界面,倒置边缘同时守住核心,将规则债务视为集成平台为客户规避的成本,避免依赖单一协调者。

原文摘要 · Abstract (English)

Vertical AI firms in accounting, law, healthcare, procurement, and similar domains historically bundled workflow, domain logic, and accountability into a single application. General-purpose AI agents are now unbundling that package, prompting founders and investors to advocate "going headless": cede the workflow and interface to agents and expose domain expertise as callable services. This article argues that going headless is correct for some firms and destructive for others, and that the latter often cede their value capture inadvertently through architectural choices that look like interface decisions. This is a boundary question, and the answer turns on distinguishing the interface boundary, which can often move, from the accountability boundary, which often must not. Drawing on Coase's theory of the firm, Eisenmann, Parker, and Van Alstyne's platform envelopment framework, and Teece's analysis of complementary assets and appropriability, the article shows that orchestrators operating through open protocols acquire envelopment power even as technical interoperability improves, and that durable value capture concentrates in cospecialized accountability assets: professional signoff, regulated workflows, evidence trails, and trusted systems of record. The article proposes a three-position taxonomy (component, integrated software platform, dual-track) determined not by sector but by task-accountability regime, and formalizes the construct of rule debt: the future governance, maintenance, and accountability burden that accrues to customer organizations when business rules and professional standards migrate from governed systems into prompts and agent instructions. Four principles follow: decompose by accountability not interface, invert the edges while retaining the core, position rule debt as the customer cost the integrated platform prevents, and avoid single-orchestrator dependence.

AI战略企业边界规则债务平台架构

Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。