Advanced Coordination
Nexus has been upgraded with structured planning, parallel execution, inter-lim review, and verification gates to handle complex, multi-step projects with higher reliability.
Structured Planning
Before delegating any work, Nexus now decomposes complex requests into a structured plan of 2–5 minute subtasks. Each subtask has a clear scope, expected output, and assigned lim.
Analyze Request
Nexus parses your request and identifies all required deliverables, dependencies, and constraints.
Decompose into Subtasks
The request is broken into discrete, time-boxed subtasks (2–5 minutes each). Each subtask has a single responsible lim and a defined output format.
Map Dependencies
Nexus identifies which subtasks depend on others and which can run in parallel. A dependency graph is built before execution begins.
Present Plan for Approval
Nexus shows you the execution plan before starting. You can approve, modify, or reprioritize subtasks.
Example Structured Plan
Phase 1 (parallel):
• Researcher — Analyze top-performing SaaS launch posts (3 min)
• Content Maker — Draft blog post outline from product brief (4 min)
Phase 2 (parallel, after Phase 1):
• Content Maker — Write full blog post from outline + research (5 min)
• Content Maker — Draft 5-tweet launch sequence for X (3 min)
Phase 3 (sequential):
• Marketer — Schedule tweets at optimal times (2 min)
• Analyst — Verify all deliverables against requirements (2 min)
Shall I proceed?"
Parallel Dispatch
Nexus can now run multiple lims simultaneously on independent subtasks. This dramatically reduces end-to-end completion time for complex projects.
| Feature | Before | Now |
|---|---|---|
| Execution model | Sequential (one lim at a time) | Parallel where dependencies allow |
| 5-subtask project | ~20 minutes | ~8 minutes (with 3 parallel lanes) |
| Resource usage | 1 lim active | Up to 4 lims active simultaneously |
| Dependency awareness | Manual ordering | Automatic dependency graph |
Inter-Lim Review
For critical or high-stakes tasks, Nexus now assigns a second lim to review the first lim's work before presenting it to you. This provides an extra layer of quality assurance.
When Review is Triggered
- Auto-publish content — any content going live without manual approval is reviewed by a second lim
- Code commits — code changes are reviewed by a second Developer lim (or the same lim in a review pass)
- External-facing messages — outreach emails, social replies, and customer communications get a tone and accuracy check
- High-value tasks — any task marked as "critical" in its configuration
Review Flow
Verification Gate
Before marking any task as completed, Nexus now runs a verification check against the original requirements. This ensures nothing is missed or misinterpreted.
What Verification Checks
| Check | Description |
|---|---|
| Completeness | All requested deliverables are present |
| Format compliance | Output matches the expected format (length, structure, file type) |
| Brand alignment | Content adheres to your brand profile and tone guidelines |
| Instruction adherence | Custom lim instructions and forbidden topics were respected |
| Quality threshold | Output meets a minimum quality score based on your Chief Policy settings |
Verification Flow
Configuring Advanced Coordination
These features are enabled by default on all plans (with limits on Free). You can fine-tune behavior in Studio Settings → Chief Policies:
- Planning depth — Simple (fewer subtasks) or Detailed (more granular breakdown)
- Parallel limit — Maximum number of lims running simultaneously (1–4)
- Review threshold — Which task types trigger inter-lim review
- Verification strictness — Lenient (basic checks only) or Strict (full checklist)