Update nexus wiki content
This commit is contained in:
43
wiki/entities/NEXUS.md
Normal file
43
wiki/entities/NEXUS.md
Normal file
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: "NEXUS"
|
||||
type: entity
|
||||
tags: [multi-agent-orchestration, the-agency, strategy]
|
||||
sources: [executive-brief, quickstart, nexus-spatial-discovery]
|
||||
last_updated: 2026-05-01
|
||||
aliases:
|
||||
- NEXUS Framework
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
NEXUS(Network of EXperts, Unified in Strategy)是 The Agency 的多 Agent 编排框架——将 9 大专业化部门(Engineering、Design、Marketing、Product、Project Management、Testing、Support、Spatial Computing、Specialized Operations)共 147+ Agent 从"各自为战"转化为"协调统一的智能网络"。
|
||||
|
||||
## Key Facts
|
||||
|
||||
- **全称**:Network of EXperts, Unified in Strategy
|
||||
- **组织背景**:The Agency 多 Agent 协调框架
|
||||
- **三大部署模式**:
|
||||
- **NEXUS-Full**:12-24周,All agents,用于完整产品生命周期
|
||||
- **NEXUS-Sprint**:2-6周,15-25 agents,用于功能或 MVP 构建(推荐默认模式)
|
||||
- **NEXUS-Micro**:1-5天,5-10 agents,用于精准单一任务执行
|
||||
- **核心量化数据**:
|
||||
- 无协调时交接边界失败率:73%
|
||||
- 并行执行时间线压缩:40-60%
|
||||
- Dev↔QA 循环集成前缺陷捕获率:95%
|
||||
- Phase 4 硬化时间减少:50%
|
||||
|
||||
## Core Components
|
||||
|
||||
- **Master Strategy**:800+行操作 doctrine,覆盖全部 Agent 跨越 7 阶段
|
||||
- **Phase Playbooks(7份)**:Phase 0 Discovery → Phase 1 Strategy → Phase 2 Foundation → Phase 3 Build → Phase 4 Hardening → Phase 5 Launch → Phase 6 Operate
|
||||
- **Handoff Templates(7份)**:QA pass/fail、Escalation、Phase gates、Sprints、Incidents 等标准化交接格式
|
||||
- **Scenario Runbooks(4份)**:Startup MVP、Enterprise Feature、Marketing Campaign、Incident Response
|
||||
|
||||
## Relationships
|
||||
|
||||
- [[executive-brief]]:战略概览,从商业价值层面论证 NEXUS 的必要性与量化收益
|
||||
- [[quickstart]]:快速启动指南,5分钟激活 NEXUS 流水线
|
||||
- [[nexus-strategy]]:完整操作 doctrine,800+行战略文档
|
||||
- [[agents-orchestrator]]:NEXUS 管道的核心执行控制器
|
||||
- [[Reality-Checker]]:NEXUS 质量门控体系的最终守门人
|
||||
- [[nexus-spatial-discovery]]:NEXUS 并行 Agent 协作的执行案例(8 Agent 10分钟完成完整规划)
|
||||
Reference in New Issue
Block a user