Nexus and parallel work
Described transcript
On screen: A dark space. Thin amber rays streak in from the edges, converge on a point and flare into a bright star. The caption “Nexus” appears first and is replaced by “Independent tasks”.
Narration: Nexus coordinates the work of the other roles. It looks for independent tasks, the ones that touch no shared file.
On screen: Two terminal panes side by side. On the left, the command bmad-plus nexus create --plan nexus-plan.json is typed. It prints “Nexus run demo — durable task coordination” and one line for each of two tasks, “value” and “notes”, each ending “not started; verification=pending; acceptance=pending”. Then bmad-plus nexus inspect demo prints the same summary with the line “Start when dependencies have current accepted evidence.” The right pane shows nexus-plan.json: a run with “id”: “demo” and “maxParallel”: 2, and two tasks. The first, “value”, has the objective “Write the value 7 into src/value.json.” The second, “notes”, has the objective “Write the release notes into docs/notes.md.”, an acceptance line (“docs/notes.md exists and is not empty.”), empty “dependsOn”, “scope”: [“docs/notes.md”] (outlined), “artifacts”, “resources”, a “checks” entry that runs a node script, “maxAttempts”: 2 and “idempotent”: true.
Narration: Each task gets its own write scope, and scopes may not overlap.
On screen: A network of glass spheres joined by thin amber lines hangs in a dark, starry sky with an amber glow. It grows from a loose scatter into a connected mesh. The caption reads “Parallelism comes from the host”.
Narration: Parallel agents come from your host tool. Without them, the tasks run in sequence.
On screen: A terminal. The command bmad-plus nexus launch demo value shows the task “running”, with an attempt id and a process id. Then bmad-plus nexus collect demo value --input attempt.json shows it “completed”, still with “verification=pending; acceptance=pending”. bmad-plus nexus verify demo value; echo “exit code: $?” changes the line to “verification=passed” (outlined) and prints “exit code: 0”. A long command, bmad-plus nexus inspect demo --json filtered with grep, sed and awk, lists the check that ran: “command”: “/usr/local/bin/node”, “policy”: “minimal-local-v1” (outlined), “exitCode”: 0 and “stdout”: “value.json holds 7\n”. Finally bmad-plus nexus accept demo value is typed, and the status line ends “verification=passed; acceptance=accepted”, with “acceptance=accepted” outlined.
Narration: Nexus can also launch a planned local command or a Codex CLI process, under a foreground supervisor. It records the real result, then runs independent checks before anything is accepted.
On screen: A tangled knot of thin amber lines straightens, line by line, into a square grid with a bright point at its centre. The caption reads “No background scheduler”.
Narration: There is no background scheduler, and host permissions still apply.
On screen: A dim blue haze with a glowing horizon that slowly brightens. The caption reads “Discovery · Build · Ship”.
Narration: In autopilot, the same pipeline runs from idea to delivery, with the checkpoints you configure.