# Agency Nexus Playbook

> The Agency NEXUS Strategic Playbook: Comprehensive 7-phase operating model for multi-agent autonomous engineering.

- Skill: `blackpearl-ai/agency-nexus-playbook` (Agent Skill)
- Install (CLI): `npx skillmds@latest add blackpearl-ai/agency-nexus-playbook`
- Raw SKILL.md: https://api.skillmd.com/api/skills/blackpearl-ai/agency-nexus-playbook/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: BlackPearl-AI (https://skillmd.com/u/blackpearl-ai)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/blackpearl-ai/agency-nexus-playbook

---


# Strategy & Runbook Note
> **Harmonized with ECC Rules**: All implementations triggered by this runbook MUST strictly obey the Modular Architecture Hard Rule (5-level decomposition) and Documentation-First Sequential Execution (one micro-task at a time).

---

# 🌐 NEXUS — Network of EXperts, Unified in Strategy

## The Agency's Complete Operational Playbook for Multi-Agent Orchestration

> **NEXUS** transforms The Agency's independent AI specialists into a synchronized intelligence network. This is not a prompt collection — it is a **deployment doctrine** that turns The Agency into a force multiplier for any project, product, or organization.

---

## Table of Contents

1. [Strategic Foundation](#1-strategic-foundation)
2. [The NEXUS Operating Model](#2-the-nexus-operating-model)
3. [Phase 0 — Intelligence & Discovery](#3-phase-0--intelligence--discovery)
4. [Phase 1 — Strategy & Architecture](#4-phase-1--strategy--architecture)
5. [Phase 2 — Foundation & Scaffolding](#5-phase-2--foundation--scaffolding)
6. [Phase 3 — Build & Iterate](#6-phase-3--build--iterate)
7. [Phase 4 — Quality & Hardening](#7-phase-4--quality--hardening)
8. [Phase 5 — Launch & Growth](#8-phase-5--launch--growth)
9. [Phase 6 — Operate & Evolve](#9-phase-6--operate--evolve)
10. [Agent Coordination Matrix](#10-agent-coordination-matrix)
11. [Handoff Protocols](#11-handoff-protocols)
12. [Quality Gates](#12-quality-gates)
13. [Risk Management](#13-risk-management)
14. [Success Metrics](#14-success-metrics)
15. [Quick-Start Activation Guide](#15-quick-start-activation-guide)

---

## 1. Strategic Foundation

### 1.1 What NEXUS Solves

Individual agents are powerful. But without coordination, they produce:
- Conflicting architectural decisions
- Duplicated effort across divisions
- Quality gaps at handoff boundaries
- No shared context or institutional memory

**NEXUS eliminates these failure modes** by defining:
- **Who** activates at each phase
- **What** they produce and for whom
- **When** they hand off and to whom
- **How** quality is verified before advancement
- **Why** each agent exists in the pipeline (no passengers)

### 1.2 Core Principles

| Principle | Description |
|-----------|-------------|
| **Pipeline Integrity** | No phase advances without passing its quality gate |
| **Context Continuity** | Every handoff carries full context — no agent starts cold |
| **Parallel Execution** | Independent workstreams run concurrently to compress timelines |
| **Evidence Over Claims** | All quality assessments require proof, not assertions |
| **Fail Fast, Fix Fast** | Maximum 3 retries per task before escalation |
| **Single Source of Truth** | One canonical spec, one task list, one architecture doc |

### 1.3 The Agent Roster by Division

| Division | Agents | Primary NEXUS Role |
|----------|--------|--------------------|
| **Engineering** | Frontend Developer, Backend Architect, Mobile App Builder, AI Engineer, DevOps Automator, Rapid Prototyper, Senior Developer | Build, deploy, and maintain all technical systems |
| **Design** | UI Designer, UX Researcher, UX Architect, Brand Guardian, Visual Storyteller, Whimsy Injector, Image Prompt Engineer | Define visual identity, user experience, and brand consistency |
| **Marketing** | Growth Hacker, Content Creator, Twitter Engager, TikTok Strategist, Instagram Curator, Reddit Community Builder, App Store Optimizer, Social Media Strategist | Drive acquisition, engagement, and market presence |
| **Product** | Sprint Prioritizer, Trend Researcher, Feedback Synthesizer | Define what to build, when, and why |
| **Project Management** | Studio Producer, Project Shepherd, Studio Operations, Experiment Tracker, Senior Project Manager | Orchestrate timelines, resources, and cross-functional coordination |
| **Testing** | Evidence Collector, Reality Checker, Test Results Analyzer, Performance Benchmarker, API Tester, Tool Evaluator, Workflow Optimizer | Verify quality through evidence-based assessment |
| **Support** | Support Responder, Analytics Reporter, Finance Tracker, Infrastructure Maintainer, Legal Compliance Checker, Executive Summary Generator | Sustain operations, compliance, and business intelligence |
| **Spatial Computing** | XR Interface Architect, macOS Spatial/Metal Engineer, XR Immersive Developer, XR Cockpit Interaction Specialist, visionOS Spatial Engineer, Terminal Integration Specialist | Build immersive and spatial computing experiences |
| **Specialized** | Agents Orchestrator, Analytics Reporter, LSP/Index Engineer, Sales Data Extraction Agent, Data Consolidation Agent, Report Distribution Agent | Cross-cutting coordination, deep analytics, and code intelligence |

---

## 2. The NEXUS Operating Model

### 2.1 The Seven-Phase Pipeline

```
┌─────────────────────────────────────────────────────────────────────────┐
│                        NEXUS PIPELINE                                   │
│                                                                         │
│  Phase 0        Phase 1         Phase 2          Phase 3                │
│  DISCOVER  ───▶ STRATEGIZE ───▶ SCAFFOLD   ───▶  BUILD                 │
│  Intelligence   Architecture    Foundation       Dev ↔ QA Loop          │
│                                                                         │
│  Phase 4        Phase 5         Phase 6                                 │
│  HARDEN   ───▶  LAUNCH    ───▶  OPERATE                                │
│  Quality Gate   Go-to-Market    Sustained Ops                           │
│                                                                         │
│  ◆ Quality Gate between every phase                                     │
│  ◆ Parallel tracks within phases                                        │
│  ◆ Feedback loops at every boundary                                     │
└─────────────────────────────────────────────────────────────────────────┘
```

### 2.2 Command Structure

```
                    ┌──────────────────────┐
                    │  Agents Orchestrator  │  ◄── Pipeline Controller
                    │  (Specialized)        │
                    └──────────┬───────────┘
                               │
              ┌────────────────┼────────────────┐
              │                │                │
     ┌────────▼──────┐ ┌──────▼───────┐ ┌──────▼──────────┐
     │ Studio        │ │ Project      │ │ Senior Project   │
     │ Producer      │ │ Shepherd     │ │ Manager          │
     │ (Portfolio)   │ │ (Execution)  │ │ (Task Scoping)   │
     └───────────────┘ └──────────────┘ └─────────────────┘
              │                │                │
              ▼                ▼                ▼
     ┌─────────────────────────────────────────────────┐
     │           Division Leads (per phase)             │
     │  Engineering │ Design │ Marketing │ Product │ QA │
     └─────────────────────────────────────────────────┘
```

### 2.3 Activation Modes

NEXUS supports three deployment configurations:

| Mode | Agents Active | Use Case | Timeline |
|------|--------------|----------|----------|
| **NEXUS-Full** | All | Enterprise product launch, full lifecycle | 12-24 weeks |
| **NEXUS-Sprint** | 15-25 | Feature development, MVP build | 2-6 weeks |
| **NEXUS-Micro** | 5-10 | Bug fix, content campaign, single deliverable | 1-5 days |

---

## 3. Phase 0 — Intelligence & Discovery

> **Objective**: Understand the landscape before committing resources. No building until the problem is validated.

### 3.1 Active Agents

| Agent | Role in Phase | Primary Output |
|-------|--------------|----------------|
| **Trend Researcher** | Market intelligence lead | Market Analysis Report with TAM/SAM/SOM |
| **Feedback Synthesizer** | User needs analysis | Synthesized Feedback Report with pain points |
| **UX Researcher** | User behavior analysis | Research Findings with personas and journey maps |
| **Analytics Reporter** | Data landscape assessment | Data Audit Report with available signals |
| **Legal Compliance Checker** | Regulatory scan | Compliance Requirements Matrix |
| **Tool Evaluator** | Technology landscape | Tech Stack Assessment |

### 3.2 Parallel Workstreams

```
WORKSTREAM A: Market Intelligence          WORKSTREAM B: User Intelligence
├── Trend Researcher                       ├── Feedback Synthesizer
│   ├── Competitive landscape              │   ├── Multi-channel feedback collection
│   ├── Market sizing (TAM/SAM/SOM)        │   ├── Sentiment analysis
│   └── Trend lifecycle mapping            │   └── Pain point prioritization
│                                          │
├── Analytics Reporter                     ├── UX Researcher
│   ├── Existing data audit                │   ├── User interviews/surveys
│   ├── Signal identification              │   ├── Persona development
│   └── Baseline metrics                   │   └── Journey mapping
│                                          │
└── Legal Compliance Checker               └── Tool Evaluator
    ├── Regulatory requirements                ├── Technology assessment
    ├── Data handling constraints               ├── Build vs. buy analysis
    └── Jurisdiction mapping                   └── Integration feasibility
```

### 3.3 Phase 0 Quality Gate

**Gate Keeper**: Executive Summary Generator

| Criterion | Threshold | Evidence Required |
|-----------|-----------|-------------------|
| Market opportunity validated | TAM > minimum viable threshold | Trend Researcher report with sources |
| User need confirmed | ≥3 validated pain points | Feedback Synthesizer + UX Researcher data |
| Regulatory path clear | No blocking compliance issues | Legal Compliance Checker matrix |
| Data foundation assessed | Key metrics identified | Analytics Reporter audit |
| Technology feasibility confirmed | Stack validated | Tool Evaluator assessment |

**Output**: Executive Summary (≤500 words, SCQA format) → Decision: GO / NO-GO / PIVOT

---

## 4. Phase 1 — Strategy & Architecture

> **Objective**: Define what we're building, how it's structured, and what success looks like — before writing a single line of code.

### 4.1 Active Agents

| Agent | Role in Phase | Primary Output |
|-------|--------------|----------------|
| **Studio Producer** | Strategic portfolio alignment | Strategic Portfolio Plan |
| **Senior Project Manager** | Spec-to-task conversion | Comprehensive Task List |
| **Sprint Prioritizer** | Feature prioritization | Prioritized Backlog (RICE scored) |
| **UX Architect** | Technical architecture + UX foundation | Architecture Spec + CSS Design System |
| **Brand Guardian** | Brand identity system | Brand Foundation Document |
| **Backend Architect** | System architecture | System Architecture Specification |
| **AI Engineer** | AI/ML architecture (if applicable) | ML System Design |
| **Finance Tracker** | Budget and resource planning | Financial Plan with ROI projections |

### 4.2 Execution Sequence

```
STEP 1: Strategic Framing (Parallel)
├── Studio Producer → Strategic Portfolio Plan (vision, objectives, ROI targets)
├── Brand Guardian → Brand Foundation (purpose, values, visual identity system)
└── Finance Tracker → Budget Framework (resource allocation, cost projections)

STEP 2: Technical Architecture (Parallel, after Step 1)
├── UX Architect → CSS Design System + Layout Framework + UX Structure
├── Backend Architect → System Architecture (services, databases, APIs)
├── AI Engineer → ML Architecture (models, pipelines, inference strategy)
└── Senior Project Manager → Task List (spec → tasks, exact requirements)

STEP 3: Prioritization (Sequential, after Step 2)
└── Sprint Prioritizer → RICE-scored backlog with sprint assignments
    ├── Input: Task List + Architecture Spec + Budget Framework
    ├── Output: Prioritized sprint plan with dependency map
    └── Validation: Studio Producer confirms strategic alignment
```

### 4.3 Phase 1 Quality Gate

**Gate Keeper**: Studio Producer + Reality Checker (dual sign-off)

| Criterion | Threshold | Evidence Required |
|-----------|-----------|-------------------|
| Architecture covers all requirements | 100% spec coverage | Senior PM task list cross-referenced |
| Brand system complete | Logo, colors, typography, voice defined | Brand Guardian deliverable |
| Technical feasibility validated | All components have implementation path | Backend Architect + UX Architect specs |
| Budget approved | Within organizational constraints | Finance Tracker plan |
| Sprint plan realistic | Velocity-based estimation | Sprint Prioritizer backlog |

**Output**: Approved Architecture Package → Phase 2 activation

---

## 5. Phase 2 — Foundation & Scaffolding

> **Objective**: Build the technical and operational foundation that all subsequent work depends on. Get the skeleton standing before adding muscle.

### 5.1 Active Agents

| Agent | Role in Phase | Primary Output |
|-------|--------------|----------------|
| **DevOps Automator** | CI/CD pipeline + infrastructure | Deployment Pipeline + IaC Templates |
| **Frontend Developer** | Project scaffolding + component library | App Skeleton + Design System Implementation |
| **Backend Architect** | Database + API foundation | Schema + API Scaffold + Auth System |
| **UX Architect** | CSS system implementation | Design Tokens + Layout Framework |
| **Infrastructure Maintainer** | Cloud infrastructure setup | Monitoring + Logging + Alerting |
| **Studio Operations** | Process setup | Collaboration tools + workflows |

### 5.2 Parallel Workstreams

```
WORKSTREAM A: Infrastructure              WORKSTREAM B: Application Foundation
├── DevOps Automator                      ├── Frontend Developer
│   ├── CI/CD pipeline (GitHub Actions)   │   ├── Project scaffolding
│   ├── Container orchestration           │   ├── Component library setup
│   └── Environment provisioning          │   └── Design system integration
│                                         │
├── Infrastructure Maintainer             ├── Backend Architect
│   ├── Cloud resource provisioning       │   ├── Database schema deployment
│   ├── Monitoring (Prometheus/Grafana)   │   ├── API scaffold + auth
│   └── Security hardening               │   └── Service communication layer
│                                         │
└── Studio Operations                     └── UX Architect
    ├── Git workflow + branch strategy        ├── CSS design tokens
    ├── Communication channels                ├── Responsive layout system
    └── Documentation templates               └── Theme system (light/dark/system)
```

### 5.3 Phase 2 Quality Gate

**Gate Keeper**: DevOps Automator + Evidence Collector

| Criterion | Threshold | Evidence Required |
|-----------|-----------|-------------------|
| CI/CD pipeline operational | Build + test + deploy working | Pipeline execution logs |
| Database schema deployed | All tables/indexes created | Migration success + schema dump |
| API scaffold responding | Health check endpoints live | curl response screenshots |
| Frontend rendering | Skeleton app loads in browser | Evidence Collector screenshots |
| Monitoring active | Dashboards showing metrics | Grafana/monitoring screenshots |
| Design system implemented | Tokens + components available | Component library demo |

**Output**: Working skeleton application with full DevOps pipeline → Phase 3 activation

---

## 6. Phase 3 — Build & Iterate

> **Objective**: Implement features through continuous Dev↔QA loops. Every task is validated before the next begins. This is where the bulk of the work happens.

### 6.1 The Dev↔QA Loop

This is the heart of NEXUS. The Agents Orchestrator manages a **task-by-task quality loop**:

```
┌─────────────────────────────────────────────────────────┐
│                   DEV ↔ QA LOOP                          │
│                                                          │
│  ┌──────────┐    ┌──────────┐    ┌──────────────────┐   │
│  │ Developer │───▶│ Evidence │───▶│ Decision Logic    │   │
│  │ Agent     │    │ Collector│    │                   │   │
│  │           │    │ (QA)     │    │ PASS → Next Task  │   │
│  │ Implements│    │          │    │ FAIL → Retry (≤3) │   │
│  │ Task N    │    │ Tests    │    │ BLOCKED → Escalate│   │
│  │           │◀───│ Task N   │◀───│                   │   │
│  └──────────┘    └──────────┘    └──────────────────┘   │
│       ▲                                    │             │
│       │            QA Feedback             │             │
│       └────────────────────────────────────┘             │
│                                                          │
│  Orchestrator tracks: attempt count, QA feedback,        │
│  task status, cumulative quality metrics                 │
└─────────────────────────────────────────────────────────┘
```

### 6.2 Agent Assignment by Task Type

| Task Type | Primary Developer | QA Agent | Specialist Support |
|-----------|------------------|----------|-------------------|
| Frontend UI | Frontend Developer | Evidence Collector | UI Designer, Whimsy Injector |
| Backend API | Backend Architect | API Tester | Performance Benchmarker |
| Database | Backend Architect | API Tester | Analytics Reporter |
| Mobile | Mobile App Builder | Evidence Collector | UX Researcher |
| AI/ML Feature | AI Engineer | Test Results Analyzer | Analytics Reporter |
| Infrastructure | DevOps Automator | Performance Benchmarker | Infrastructure Maintainer |
| Premium Polish | Senior Developer | Evidence Collector | Visual Storyteller |
| Rapid Prototype | Rapid Prototyper | Evidence Collector | Experiment Tracker |
| Spatial/XR | XR Immersive Developer | Evidence Collector | XR Interface Architect |
| visionOS | visionOS Spatial Engineer | Evidence Collector | macOS Spatial/Metal Engineer |
| Cockpit UI | XR Cockpit Interaction Specialist | Evidence Collector | XR Interface Architect |
| CLI/Terminal | Terminal Integration Specialist | API Tester | LSP/Index Engineer |
| Code Intelligence | LSP/Index Engineer | Test Results Analyzer | Senior Developer |

### 6.3 Parallel Build Tracks

For complex projects, multiple tracks run simultaneously:

```
TRACK A: Core Product                    TRACK B: Growth & Marketing
├── Frontend Developer                   ├── Growth Hacker
│   └── UI implementation                │   └── Viral loops + referral system
├── Backend Architect                    ├── Content Creator
│   └── API + business logic             │   └── Launch content + editorial calendar
├── AI Engineer                          ├── Social Media Strategist
│   └── ML features + pipelines          │   └── Cross-platform campaign
│                                        ├── App Store Optimizer (if mobile)
│                                        │   └── ASO strategy + metadata
│                                        │
TRACK C: Quality & Operations            TRACK D: Brand & Experience
├── Evidence Collector                   ├── UI Designer
│   └── Continuous QA screenshots        │   └── Component refinement
├── API Tester                           ├── Brand Guardian
│   └── Endpoint validation              │   └── Brand consistency audit
├── Performance Benchmarker              ├── Visual Storyteller
│   └── Load testing + optimization      │   └── Visual narrative assets
├── Workflow Optimizer                   └── Whimsy Injector
│   └── Process improvement                  └── Delight moments + micro-interactions
└── Experiment Tracker
    └── A/B test management
```

### 6.4 Phase 3 Quality Gate

**Gate Keeper**: Agents Orchestrator

| Criterion | Threshold | Evidence Required |
|-----------|-----------|-------------------|
| All tasks pass QA | 100% task completion | Evidence Collector screenshots per task |
| API endpoints validated | All endpoints tested | API Tester report |
| Performance baselines met | P95 < 200ms, LCP < 2.5s | Performance Benchmarker report |
| Brand consistency verified | 95%+ adherence | Brand Guardian audit |
| No critical bugs | Zero P0/P1 open issues | Test Results Analyzer summary |

**Output**: Feature-complete application → Phase 4 activation

---

## 7. Phase 4 — Quality & Hardening

> **Objective**: The final quality gauntlet. The Reality Checker defaults to "NEEDS WORK" — you must prove production readiness with overwhelming evidence.

### 7.1 Active Agents

| Agent | Role in Phase | Primary Output |
|-------|--------------|----------------|
| **Reality Checker** | Final integration testing (defaults to NEEDS WORK) | Reality-Based Integration Report |
| **Evidence Collector** | Comprehensive visual evidence | Screenshot Evidence Package |
| **Performance Benchmarker** | Load testing + optimization | Performance Certification |
| **API Tester** | Full API regression suite | API Test Report |
| **Test Results Analyzer** | Aggregate quality metrics | Quality Metrics Dashboard |
| **Legal Compliance Checker** | Final compliance audit | Compliance Certification |
| **Infrastructure Maintainer** | Production readiness check | Infrastructure Readiness Report |
| **Workflow Optimizer** | Process efficiency review | Optimization Recommendations |

### 7.2 The Hardening Sequence

```
STEP 1: Evidence Collection (Parallel)
├── Evidence Collector → Full screenshot suite (desktop, tablet, mobile)
├── API Tester → Complete endpoint regression
├── Performance Benchmarker → Load test at 10x expected traffic
└── Legal Compliance Checker → Final regulatory audit

STEP 2: Analysis (Parallel, after Step 1)
├── Test Results Analyzer → Aggregate all test data into quality dashboard
├── Workflow Optimizer → Identify remaining process inefficiencies
└── Infrastructure Maintainer → Production environment validation

STEP 3: Final Judgment (Sequential, after Step 2)
└── Reality Checker → Integration Report
    ├── Cross-validates ALL previous QA findings
    ├── Tests complete user journeys with screenshot evidence
    ├── Verifies specification compliance point-by-point
    ├── Default verdict: NEEDS WORK
    └── READY only with overwhelming evidence across all criteria
```

### 7.3 Phase 4 Quality Gate (THE FINAL GATE)

**Gate Keeper**: Reality Checker (sole authority)

| Criterion | Threshold | Evidence Required |
|-----------|-----------|-------------------|
| User journeys complete | All critical paths working | End-to-end screenshots |
| Cross-device consistency | Desktop + Tablet + Mobile | Responsive screenshots |
| Performance certified | P95 < 200ms, uptime > 99.9% | Load test results |
| Security validated | Zero critical vulnerabilities | Security scan report |
| Compliance certified | All regulatory requirements met | Legal Compliance Checker report |
| Specification compliance | 100% of spec requirements | Point-by-point verification |

**Verdict Options**:
- **READY** — Proceed to launch (rare on first pass)
- **NEEDS WORK** — Return to Phase 3 with specific fix list (expected)
- **NOT READY** — Major architectural issues, return to Phase 1/2

**Expected**: First implementations typically require 2-3 revision cycles. A B/B+ rating is normal and healthy.

---

## 8. Phase 5 — Launch & Growth

> **Objective**: Coordinate the go-to-market execution across all channels simultaneously. Maximum impact at launch.

### 8.1 Active Agents

| Agent | Role in Phase | Primary Output |
|-------|--------------|----------------|
| **Growth Hacker** | Launch strategy lead | Growth Playbook with viral loops |
| **Content Creator** | Launch content | Blog posts, videos, social content |
| **Social Media Strategist** | Cross-platform campaign | Campaign Calendar + Content |
| **Twitter Engager** | Twitter/X launch campaign | Thread strategy + engagement plan |
| **TikTok Strategist** | TikTok viral content | Short-form video strategy |
| **Instagram Curator** | Visual launch campaign | Visual content + stories |
| **Reddit Community Builder** | Authentic community launch | Community engagement plan |
| **App Store Optimizer** | Store optimization (if mobile) | ASO Package |
| **Executive Summary Generator** | Stakeholder communication | Launch Executive Summary |
| **Project Shepherd** | Launch coordination | Launch Checklist + Timeline |
| **DevOps Automator** | Deployment execution | Zero-downtime deployment |
| **Infrastructure Maintainer** | Launch monitoring | Real-time dashboards |

### 8.2 Launch Sequence

```
T-7 DAYS: Pre-Launch
├── Content Creator → Launch content queued and scheduled
├── Social Media Strategist → Campaign assets finalized
├── Growth Hacker → Viral mechanics tested and armed
├── App Store Optimizer → Store listing optimized
├── DevOps Automator → Blue-green deployment prepared
└── Infrastructure Maintainer → Auto-scaling configured for 10x

T-0: Launch Day
├── DevOps Automator → Execute deployment
├── Infrastructure Maintainer → Monitor all systems
├── Twitter Engager → Launch thread + real-time engagement
├── Reddit Community Builder → Authentic community posts
├── Instagram Curator → Visual launch content
├── TikTok Strategist → Launch videos published
├── Support Responder → Customer support active
└── Analytics Reporter → Real-time metrics dashboard

T+1 TO T+7: Post-Launch
├── Growth Hacker → Analyze acquisition data, optimize funnels
├── Feedback Synthesizer → Collect and analyze early user feedback
├── Analytics Reporter → Daily metrics reports
├── Content Creator → Response content based on reception
├── Experiment Tracker → Launch A/B tests
└── Executive Summary Generator → Daily stakeholder briefings
```

### 8.3 Phase 5 Quality Gate

**Gate Keeper**: Studio Producer + Analytics Reporter

| Criterion | Threshold | Evidence Required |
|-----------|-----------|-------------------|
| Deployment successful | Zero-downtime, all health checks pass | DevOps deployment logs |
| Systems stable | No P0/P1 incidents in first 48 hours | Infrastructure monitoring |
| User acquisition active | Channels driving traffic | Analytics Reporter dashboard |
| Feedback loop operational | User feedback being collected | Feedback Synthesizer report |
| Stakeholders informed | Executive summary delivered | Executive Summary Generator output |

**Output**: Stable launched product with active growth channels → Phase 6 activation

---

## 9. Phase 6 — Operate & Evolve

> **Objective**: Sustained operations with continuous improvement. The product is live — now make it thrive.

### 9.1 Active Agents (Ongoing)

| Agent | Cadence | Responsibility |
|-------|---------|---------------|
| **Infrastructure Maintainer** | Continuous | System reliability, uptime, performance |
| **Support Responder** | Continuous | Customer support and issue resolution |
| **Analytics Reporter** | Weekly | KPI tracking, dashboards, insights |
| **Feedback Synthesizer** | Bi-weekly | User feedback analysis and synthesis |
| **Finance Tracker** | Monthly | Financial performance, budget tracking |
| **Legal Compliance Checker** | Monthly | Regulatory monitoring and compliance |
| **Trend Researcher** | Monthly | Market intelligence and competitive analysis |
| **Executive Summary Generator** | Monthly | C-suite reporting |
| **Sprint Prioritizer** | Per sprint | Backlog grooming and sprint planning |
| **Experiment Tracker** | Per experiment | A/B test management and analysis |
| **Growth Hacker** | Ongoing | Acquisition optimization and growth experiments |
| **Workflow Optimizer** | Quarterly | Process improvement and efficiency gains |

### 9.2 Continuous Improvement Cycle

```
┌──────────────────────────────────────────────────────────┐
│              CONTINUOUS IMPROVEMENT LOOP                   │
│                                                           │
│  MEASURE          ANALYZE           PLAN          ACT     │
│  ┌─────────┐     ┌──────────┐     ┌─────────┐   ┌─────┐ │
│  │Analytics │────▶│Feedback  │────▶│Sprint   │──▶│Build│ │
│  │Reporter  │     │Synthesizer│    │Prioritizer│  │Loop │ │
│  └─────────┘     └──────────┘     └─────────┘   └─────┘ │
│       ▲                                            │      │
│       │              Experiment                    │      │
│       │              Tracker                       │      │
│       └────────────────────────────────────────────┘      │
│                                                           │
│  Monthly: Executive Summary Generator → C-suite report    │
│  Monthly: Finance Tracker → Financial performance         │
│  Monthly: Legal Compliance Checker → Regulatory update    │
│  Monthly: Trend Researcher → Market intelligence          │
│  Quarterly: Workflow Optimizer → Process improvements     │
└──────────────────────────────────────────────────────────┘
```

---

## 10. Agent Coordination Matrix

### 10.1 Full Cross-Division Dependency Map

This matrix shows which agents produce outputs consumed by other agents. Read as: **Row agent produces → Column agent consumes**.

```
PRODUCER →          │ ENG │ DES │ MKT │ PRD │ PM  │ TST │ SUP │ SPC │ SPZ
────────────────────┼─────┼─────┼─────┼─────┼─────┼─────┼─────┼─────┼────
Engineering         │  ●  │     │     │     │     │  ●  │  ●  │  ●  │
Design              │  ●  │  ●  │  ●  │     │     │  ●  │     │  ●  │
Marketing           │     │     │  ●  │  ●  │     │     │  ●  │     │
Product             │  ●  │  ●  │  ●  │  ●  │  ●  │     │     │     │  ●
Project Management  │  ●  │  ●  │  ●  │  ●  │  ●  │  ●  │  ●  │  ●  │  ●
Testing             │  ●  │  ●  │     │  ●  │  ●  │  ●  │     │  ●  │
Support             │  ●  │     │  ●  │  ●  │  ●  │     │  ●  │     │  ●
Spatial Computing   │  ●  │  ●  │     │     │     │  ●  │     │  ●  │
Specialized         │  ●  │     │     │  ●  │  ●  │  ●  │  ●  │     │  ●

● = Active dependency (producer creates artifacts consumed by this division)
```

### 10.2 Critical Handoff Pairs

These are the highest-traffic handoff relationships in NEXUS:

| From | To | Artifact | Frequency |
|------|----|----------|-----------|
| Senior Project Manager | All Developers | Task List | Per sprint |
| UX Architect | Frontend Developer | CSS Design System + Layout Spec | Per project |
| Backend Architect | Frontend Developer | API Specification | Per feature |
| Frontend Developer | Evidence Collector | Implemented Feature | Per task |
| Evidence Collector | Agents Orchestrator | QA Verdict (PASS/FAIL) | Per task |
| Agents Orchestrator | Developer (any) | QA Feedback + Retry Instructions | Per failure |
| Brand Guardian | All Design + Marketing | Brand Guidelines | Per project |
| Analytics Reporter | Sprint Prioritizer | Performance Data | Per sprint |
| Feedback Synthesizer | Sprint Prioritizer | User Insights | Per sprint |
| Trend Researcher | Studio Producer | Market Intelligence | Monthly |
| Reality Checker | Agents Orchestrator | Integration Verdict | Per phase |
| Executive Summary Generator | Studio Producer | Executive Brief | Per milestone |

---

## 11. Handoff Protocols

### 11.1 Standard Handoff Template

Every agent-to-agent handoff must include:

```markdown
## NEXUS Handoff Document

### Metadata
- **From**: [Agent Name] ([Division])
- **To**: [Agent Name] ([Division])
- **Phase**: [Current NEXUS Phase]
- **Task Reference**: [Task ID from Sprint Prioritizer backlog]
- **Priority**: [Critical / High / Medium / Low]
- **Timestamp**: [ISO 8601]

### Context
- **Project**: [Project name and brief description]
- **Current State**: [What has been completed so far]
- **Relevant Files**: [List of files/artifacts to review]
- **Dependencies**: [What this work depends on]

### Deliverable Request
- **What is needed**: [Specific, measurable deliverable]
- **Acceptance criteria**: [How success will be measured]
- **Constraints**: [Technical, timeline, or resource constraints]
- **Reference materials**: [Links to specs, designs, previous work]

### Quality Expectations
- **Must pass**: [Specific quality criteria]
- **Evidence required**: [What proof of completion looks like]
- **Handoff to next**: [Who receives the output and what they need]
```

### 11.2 QA Feedback Loop Protocol

When a task fails QA, the feedback must be actionable:

```markdown
## QA Failure Feedback

### Task: [Task ID and description]
### Attempt: [1/2/3] of 3 maximum
### Verdict: FAIL

### Specific Issues Found
1. **[Issue Category]**: [Exact description with screenshot reference]
   - Expected: [What should happen]
   - Actual: [What actually happens]
   - Evidence: [Screenshot filename or test output]

2. **[Issue Category]**: [Exact description]
   - Expected: [...]
   - Actual: [...]
   - Evidence: [...]

### Fix Instructions
- [Specific, actionable fix instruction 1]
- [Specific, actionable fix instruction 2]

### Files to Modify
- [file path 1]: [what needs to change]
- [file path 2]: [what needs to change]

### Retry Expectations
- Fix the above issues and re-submit for QA
- Do NOT introduce new features — fix only
- Attempt [N+1] of 3 maximum
```

### 11.3 Escalation Protocol

When a task exceeds 3 retry attempts:

```markdown
## Escalation Report

### Task: [Task ID]
### Attempts Exhausted: 3/3
### Escalation Level: [To Agents Orchestrator / To Studio Producer]

### Failure History
- Attempt 1: [Summary of issues and fixes attempted]
- Attempt 2: [Summary of issues and fixes attempted]
- Attempt 3: [Summary of issues and fixes attempted]

### Root Cause Analysis
- [Why the task keeps failing]
- [What systemic issue is preventing resolution]

### Recommended Resolution
- [ ] Reassign to different developer agent
- [ ] Decompose task into smaller sub-tasks
- [ ] Revise architecture/approach
- [ ] Accept current state with known limitations
- [ ] Defer to future sprint

### Impact Assessment
- **Blocking**: [What other tasks are blocked by this]
- **Timeline Impact**: [How this affects the overall schedule]
- **Quality Impact**: [What quality compromises exist]
```

---

## 12. Quality Gates

### 12.1 Gate Summary

| Phase | Gate Name | Gate Keeper | Pass Criteria |
|-------|-----------|-------------|---------------|
| 0 → 1 | Discovery Gate | Executive Summary Generator | Market validated, user need confirmed, regulatory path clear |
| 1 → 2 | Architecture Gate | Studio Producer + Reality Checker | Architecture complete, brand defined, budget approved, sprint plan realistic |
| 2 → 3 | Foundation Gate | DevOps Automator + Evidence Collector | CI/CD working, skeleton app running, monitoring active |
| 3 → 4 | Feature Gate | Agents Orchestrator | All tasks pass QA, no critical bugs, performance baselines met |
| 4 → 5 | Production Gate | Reality Checker (sole authority) | User journeys complete, cross-device consistent, security validated, spec compliant |
| 5 → 6 | Launch Gate | Studio Producer + Analytics Reporter | Deployment successful, systems stable, growth channels active |

### 12.2 Gate Failure Handling

```
IF gate FAILS:
  ├── Gate Keeper produces specific failure report
  ├── Agents Orchestrator routes failures to responsible agents
  ├── Failed items enter Dev↔QA loop (Phase 3 mechanics)
  ├── Maximum 3 gate re-attempts before escalation to Studio Producer
  └── Studio Producer decides: fix, descope, or accept with risk
```

---

## 13. Risk Management

### 13.1 Risk Categories and Owners

| Risk Category | Primary Owner | Mitigation Agent | Escalation Path |
|---------------|--------------|-------------------|-----------------|
| Technical Debt | Backend Architect | Workflow Optimizer | Senior Developer |
| Security Vulnerability | Legal Compliance Checker | Infrastructure Maintainer | DevOps Automator |
| Performance Degradation | Performance Benchmarker | Infrastructure Maintainer | Backend Architect |
| Brand Inconsistency | Brand Guardian | UI Designer | Studio Producer |
| Scope Creep | Senior Project Manager | Sprint Prioritizer | Project Shepherd |
| Budget Overrun | Finance Tracker | Studio Operations | Studio Producer |
| Regulatory Non-Compliance | Legal Compliance Checker | Support Responder | Studio Producer |
| Market Shift | Trend Researcher | Growth Hacker | Studio Producer |
| Team Bottleneck | Project Shepherd | Studio Operations | Studio Producer |
| Quality Regression | Reality Checker | Evidence Collector | Agents Orchestrator |

### 13.2 Risk Response Matrix

| Severity | Response Time | Decision Authority | Action |
|----------|--------------|-------------------|--------|
| **Critical** (P0) | Immediate | Studio Producer | All-hands, stop other work |
| **High** (P1) | < 4 hours | Project Shepherd | Dedicated agent assignment |
| **Medium** (P2) | < 24 hours | Agents Orchestrator | Next sprint priority |
| **Low** (P3) | < 1 week | Sprint Prioritizer | Backlog item |

---

## 14. Success Metrics

### 14.1 Pipeline Metrics

| Metric | Target | Measurement Agent |
|--------|--------|-------------------|
| Phase completion rate | 95% on first attempt | Agents Orchestrator |
| Task first-pass QA rate | 70%+ | Evidence Collector |
| Average retries per task | < 1.5 | Agents Orchestrator |
| Pipeline cycle time | Within sprint estimate ±15% | Project Shepherd |
| Quality gate pass rate | 80%+ on first attempt | Reality Checker |

### 14.2 Product Metrics

| Metric | Target | Measurement Agent |
|--------|--------|-------------------|
| API response time (P95) | < 200ms | Performance Benchmarker |
| Page load time (LCP) | < 2.5s | Performance Benchmarker |
| System uptime | > 99.9% | Infrastructure Maintainer |
| Lighthouse score | > 90 (Performance + Accessibility) | Frontend Developer |
| Security vulnerabilities | Zero critical | Legal Compliance Checker |
| Spec compliance | 100% | Reality Checker |

### 14.3 Business Metrics

| Metric | Target | Measurement Agent |
|--------|--------|-------------------|
| User acquisition (MoM) | 20%+ growth | Growth Hacker |
| Activation rate | 60%+ in first week | Analytics Reporter |
| Retention (Day 7 / Day 30) | 40% / 20% | Analytics Reporter |
| LTV:CAC ratio | > 3:1 | Finance Tracker |
| NPS score | > 50 | Feedback Synthesizer |
| Portfolio ROI | > 25% | Studio Producer |

### 14.4 Operational Metrics

| Metric | Target | Measurement Agent |
|--------|--------|-------------------|
| Deployment frequency | Multiple per day | DevOps Automator |
| Mean time to recovery | < 30 minutes | Infrastructure Maintainer |
| Compliance adherence | 98%+ | Legal Compliance Checker |
| Stakeholder satisfaction | 4.5/5 | Executive Summary Generator |
| Process efficiency gain | 20%+ per quarter | Workflow Optimizer |

---

## 15. Quick-Start Activation Guide

### 15.1 NEXUS-Full Activation (Enterprise)

```bash
# Step 1: Initialize NEXUS pipeline
"Activate Agents Orchestrator in NEXUS-Full mode for [PROJECT NAME].
 Project specification: [path to spec file].
 Execute complete 7-phase pipeline with all quality gates."

# The Orchestrator will:
# 1. Read the project specification
# 2. Activate Phase 0 agents for discovery
# 3. Progress through all phases with quality gates
# 4. Manage Dev↔QA loops automatically
# 5. Report status at each phase boundary
```

### 15.2 NEXUS-Sprint Activation (Feature/MVP)

```bash
# Step 1: Initialize sprint pipeline
"Activate Agents Orchestrator in NEXUS-Sprint mode for [FEATURE/MVP NAME].
 Requirements: [brief description or path to spec].
 Skip Phase 0 (market already validated).
 Begin at Phase 1 with architecture and sprint planning."

# Recommended agent subset (15-25):
# PM: Senior Project Manager, Sprint Prioritizer, Project Shepherd
# Design: UX Architect, UI Designer, Brand Guardian
# Engineering: Frontend Developer, Backend Architect, DevOps Automator
# + AI Engineer or Mobile App Builder (if applicable)
# Testing: Evidence Collector, Reality Checker, API Tester, Performance Benchmarker
# Support: Analytics Reporter, Infrastructure Maintainer
# Specialized: Agents Orchestrator
```

### 15.3 NEXUS-Micro Activation (Targeted Task)

```bash
# Step 1: Direct agent activation
"Activate [SPECIFIC AGENT] for [TASK DESCRIPTION].
 Context: [relevant background].
 Deliverable: [specific output expected].
 Quality check: Evidence Collector to verify upon completion."

# Common NEXUS-Micro configurations:
#
# Bug Fix:
# 

…(truncated)