↓ Data Flow

The Pipeline

From your idea to deployed code — here's every step the system takes.

End-to-End Data Flow

This diagram traces the complete data flow from AI Terminal (Agent Mode) submission, through the 8-node Project Plan Generator (Chat Router, Architect, Council Review, Plan Revision, Human-in-the-Loop Review, Compiler, Executor), to Nexus Project & Task Creation via Supabase.

Infrastructure: Blackboard (shared memory), Glass Box Broadcasting (WebSocket artifacts for real-time visibility).

END-TO-END DATA FLOW AI TERMINAL Agent Mode 1 NEXUS SERVER Proxy → Python 2 🔀 Chat Router Intent Detection 3 ? chat 💬 Chat Response Direct LLM → END build 🧠 Architect Draft MarkdownPlan 4 📋 Blackboard Shared Memory 🗳️ COUNCIL REVIEW asyncio.gather — Unique Models (anti-groupthink) 5 🎨 Frontend/UX Components • A11y • Responsive → VoteReceipt + LineComments ⚙️ Systems Engineer DB • API • Auth • Security → VoteReceipt + LineComments 🧪 QA Strategist Acceptance Criteria • Edge Cases → VoteReceipt + LineComments 🔍 Gap Analyst Integration Gaps • Shortcuts → VoteReceipt + LineComments 📊 Vote Aggregation approve | reject | request_info V? Reject ≥ Majority Approve All LineComments → prior_comments[] 📝 Plan Revision Apply LineComments v{n} → v{n+1} 6 ⏸️ HUMAN REVIEW interrupt_before 7 Reject → Architect drafts v{n+1} Approve 🔧 Compiler MD → JSON 8 🚀 Executor NexusClient API 9 📁 Project Supabase 10 Tasks Task 1 idea Task 2 idea Task 3 idea 11 Workflow Selector 12

Initiative Hierarchy

This diagram illustrates the cascading structure of The Nexus. Top-level Dashboard Initiatives kick off one or multiple Project Level Workflows. These workflows generate scoped Projects in Supabase, which in turn schedule and execute specific Tasks. End tasks can optionally trigger further nested workflows via a Workflow Selector.

Dashboard Initiative Kicks off Kicks off Full Cortex Workflow Agentic Project-Level Orchestration Simple Execution Direct Execution Pipeline Generates Generates Project Alpha Supabase: Context & Scope defined Project Beta Supabase: Context & Scope defined Schedules Tasks Schedules Tasks Task 1 Database Schema Task 2 API Routes Task 3 UI Components Task 4 Testing Workflow Selector Workflow Selector Workflow Selector Workflow Selector FIG 1.3 - INITIATIVE STRUCTURAL HIERARCHY
The pipeline is fractal. Every task goes through the same rigorous process as the initiative that spawned it — Research → Architect → Build → Audit. Quality scales because the process scales.

The 8-Node Orchestrator

At the heart of the pipeline sits the Project Plan Generator — an 8-node LangGraph that turns your ideas into an organized project with actionable tasks.

1️⃣

Chat Router

Classifies the request — simple chat vs. complex agentic task requiring full orchestration.

2️⃣

Architect

Generates a Markdown-based implementation plan with file paths, dependencies, and milestones.

3️⃣

Council Review

Society of Minds — Critic, Safety, and Efficiency voters score the plan and surface concerns.

4️⃣

Plan Revision

If the council rejects, the plan loops back for revision with specific critique attached.

5️⃣

Human Review

The HITL gate — you review the plan, approve or reject, and optionally annotate changes.

6️⃣

Compiler

Converts the approved Markdown plan into executable JSON — the machine-readable action list.

7️⃣

Executor

Runs the compiled plan — creating projects, scheduling tasks, and dispatching fleet workflows.

8️⃣

Glass Box

Broadcasts every artifact and state change over WebSocket for real-time dashboard visibility.

The AI Mesh →