matrix.html

<!doctype html>
<html lang="zh-CN">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <meta name="description" content="Virtual Intelligent Dev Team 与普通多角色提示词、单一编码 Agent、无边界自动循环的能力矩阵。">
  <meta name="theme-color" content="#14241f">
  <title>能力矩阵 — Virtual Intelligent Dev Team</title>
  <link rel="icon" href="data:,">
  <link rel="stylesheet" href="assets/site.css?v=v6.1.0">
  <script src="assets/site.js?v=v6.1.0" defer></script>
</head>
<body>
  <a class="skip-link" href="#main-content">跳到主要内容</a>
  <header class="site-header" data-site-header>
    <div class="container nav-shell">
      <a class="brand" href="index.html" aria-label="Virtual Intelligent Dev Team 首页"><span class="brand-mark">VITD</span><span class="brand-copy">Virtual Intelligent Dev Team<small>Evidence-driven delivery system</small></span></a>
      <button class="nav-toggle" type="button" aria-expanded="false" aria-controls="site-navigation" aria-label="打开导航" data-nav-toggle><span></span><span></span></button>
      <nav class="site-nav" id="site-navigation" aria-label="主导航" data-site-nav><a href="index.html">概览</a><a href="architecture.html">架构</a><a href="engineering.html">工程化</a><a href="agents.html">角色</a><a href="matrix.html" aria-current="page">对比</a><a class="nav-github" href="https://github.com/fxbin/virtual-intelligent-dev-team">GitHub ↗</a></nav>
    </div>
  </header>

  <main id="main-content">
    <section class="page-hero">
      <div class="container">
        <p class="eyebrow">Capability matrix · v6.1.0</p>
        <h1>它解决的不是“谁来回答”，而是<span class="accent-text">如何完成。</span></h1>
        <p class="lede">普通多角色提示词擅长提供视角，单一编码 Agent 擅长直接实现，自动循环擅长持续尝试。VITD 的重点是把这些能力放进有边界、可恢复、可验收的生命周期。</p>
        <div class="page-index" aria-label="本页目录"><a href="#comparison">十四维对比</a><a href="#use-when">适用边界</a><a href="#tradeoffs">取舍</a></div>
      </div>
    </section>

    <section class="section section-cream" id="comparison">
      <div class="container">
        <div class="section-head"><div><span class="section-kicker">14 dimensions</span><h2>对比协作协议，不比较模型智商。</h2></div><p>矩阵描述默认工作方式。任何工具都能通过额外工程补齐缺口；关键区别是这些能力是否已成为可验证的运行时契约。</p></div>
        <div class="table-wrap">
          <table>
            <thead><tr><th>维度</th><th>VITD</th><th>普通多角色提示词</th><th>单一编码 Agent</th><th>无边界自动循环</th></tr></thead>
            <tbody>
              <tr><th>任务分流</th><td class="cell-strong">Lead + bundle + risk</td><td class="cell-soft">按角色模板</td><td class="cell-soft">通常直接执行</td><td class="cell-soft">由循环策略决定</td></tr>
              <tr><th>责任中心</th><td class="cell-strong">唯一 Lead</td><td class="cell-soft">多视角易并列</td><td>单 Agent 明确</td><td class="cell-soft">可能随轮次漂移</td></tr>
              <tr><th>目标边界</th><td class="cell-strong">GoalFrame / Quick Slice</td><td class="cell-soft">依赖 prompt</td><td class="cell-soft">依赖任务说明</td><td class="cell-soft">容易由反馈改写</td></tr>
              <tr><th>生产 / 验收分离</th><td class="cell-strong">Worker / Verifier</td><td class="cell-soft">常为同轮互评</td><td class="cell-soft">通常自验</td><td class="cell-soft">通常自我反馈</td></tr>
              <tr><th>失败状态</th><td class="cell-strong">14 状态 + 合法转换</td><td class="cell-soft">自然语言</td><td class="cell-soft">工具状态</td><td class="cell-soft">重试 / 继续</td></tr>
              <tr><th>最大循环</th><td class="cell-strong">有 max cycles</td><td class="cell-soft">通常无循环</td><td>可配置</td><td class="cell-soft">可能持续运行</td></tr>
              <tr><th>人工边界</th><td class="cell-strong">Human decision plane</td><td class="cell-soft">随时提问</td><td>权限时提问</td><td class="cell-soft">往往晚触发</td></tr>
              <tr><th>恢复能力</th><td class="cell-strong">状态优先 resume</td><td class="cell-soft">依赖对话上下文</td><td class="cell-soft">依赖 session</td><td>通常有循环状态</td></tr>
              <tr><th>发布门禁</th><td class="cell-strong">ship / hold + evidence</td><td class="cell-soft">建议型</td><td>依赖宿主流程</td><td class="cell-soft">目标完成即停止</td></tr>
              <tr><th>发布后反馈</th><td class="cell-strong">Feedback closure</td><td class="cell-soft">新对话处理</td><td class="cell-soft">另起任务</td><td>可持续观察</td></tr>
              <tr><th>反熵治理</th><td class="cell-strong">删除 / 兼容 / 确认分类</td><td class="cell-soft">无内建协议</td><td class="cell-soft">依赖代码规范</td><td class="cell-soft">易增加 fallback</td></tr>
              <tr><th>完成证据</th><td class="cell-strong">结构化 evidence</td><td class="cell-soft">总结型</td><td>命令与 diff</td><td class="cell-soft">循环 metric</td></tr>
              <tr><th>真实多 Agent 声明</th><td class="cell-strong">三档 fail-closed</td><td class="cell-soft">常为角色模拟</td><td class="cell-soft">通常不声明</td><td>取决于宿主</td></tr>
              <tr><th>简单任务成本</th><td>最小路线但有协议成本</td><td class="cell-strong">很低</td><td class="cell-strong">最低</td><td class="cell-soft">可能过重</td></tr>
            </tbody>
          </table>
        </div>
      </div>
    </section>

    <section class="section" id="use-when">
      <div class="container">
        <div class="section-head"><div><span class="section-kicker">Use boundary</span><h2>适合复杂交付，不必接管所有请求。</h2></div><p>最好的路由器也应该知道什么时候不要出现。能用一步安全完成的任务，不应被包装成大型虚拟团队。</p></div>
        <div class="grid-2">
          <article class="card"><span class="card-kicker">Use VITD when</span><h3>值得启用</h3><ul><li>任务跨规划、实现、验证或发布多个阶段</li><li>需要唯一 Lead 与多个专业边界协同</li><li>重复失败，需要根因迭代与明确停止条件</li><li>存在生产、数据、API 或迁移风险</li><li>完成声明必须留下结构化证据</li><li>需要 Beta、release、feedback 或 resume</li></ul></article>
          <article class="card"><span class="card-kicker">Use a smaller tool when</span><h3>直接处理更合适</h3><ul><li>只是解释一个概念或回答单点问题</li><li>任务无需改动、交接或发布判断</li><li>一个明确命令就能安全验证并完成</li><li>只需要一次轻量 brainstorm</li><li>没有足够上下文建立可靠边界</li><li>用户明确不需要流程化产物</li></ul></article>
        </div>
      </div>
    </section>

    <section class="section section-dark" id="tradeoffs">
      <div class="container">
        <div class="section-head"><div><span class="section-kicker">Tradeoffs</span><h2>它用协议成本，换取交付可控性。</h2></div><p>这不是免费收益。任务越简单，结构化路由和证据门禁的相对成本越高；任务越复杂，责任和恢复能力越有价值。</p></div>
        <div class="grid-3">
          <article class="card"><span class="card-kicker">Cost</span><h3>更多显式产物</h3><p>复杂任务会生成约束、WorkOrder、验证报告和 completion evidence，需要维护者理解这些对象。</p></article>
          <article class="card"><span class="card-kicker">Boundary</span><h3>不替代模型与工具</h3><p>系统协调现有编码、浏览、测试和 Agent 能力；它不会凭空创造宿主没有的 runtime。</p></article>
          <article class="card"><span class="card-kicker">Payoff</span><h3>更少隐性状态</h3><p>范围、失败、恢复、人工介入和发布判断有固定位置，跨轮次交付不必靠记忆重建。</p></article>
        </div>
      </div>
    </section>

    <section class="section">
      <div class="container">
        <div class="two-column-copy">
          <div class="sticky-copy"><span class="section-kicker">Decision guide</span><h2>三问判断是否值得启用。</h2><p>如果三个问题都是否，直接使用更轻量的工具通常更好。</p></div>
          <ol class="process-list">
            <li><div><strong>是否存在多个责任阶段？</strong><p>例如定义、实现、独立验证、Beta、发布或上线反馈。</p></div></li>
            <li><div><strong>失败是否需要可恢复？</strong><p>任务跨 session、可能重复失败，或需要保留回滚与人工检查点。</p></div></li>
            <li><div><strong>完成是否必须被复核？</strong><p>需要另一个人或自动门禁根据同一份证据做出 ship / hold 判断。</p></div></li>
          </ol>
        </div>
      </div>
    </section>

    <section class="section section-compact"><div class="container"><div class="cta-panel"><div><h2>需要闭环时启用，需要速度时走最小路线。</h2><p>从一次真实的小切片开始，再按风险扩展协作。</p></div><a class="button button-primary" href="index.html#quick-start">开始使用</a></div></div></section>
  </main>

  <footer class="site-footer"><div class="container"><div class="footer-grid"><div class="footer-copy"><a class="brand" href="index.html"><span class="brand-mark">VITD</span><span>Virtual Intelligent Dev Team</span></a><p>比较协议边界与交付能力，而不是比较模型智商。</p></div><nav class="footer-links" aria-label="页脚导航"><a href="index.html">概览</a><a href="architecture.html">架构</a><a href="engineering.html">工程化</a><a href="agents.html">角色</a><a href="https://github.com/fxbin/virtual-intelligent-dev-team">GitHub</a></nav></div><div class="footer-bottom"><span>Capability matrix · v6.1.0</span><span>© <span data-current-year>2026</span> fxbin</span></div></div></footer>
</body>
</html>