Runtime flows

How work moves through Nexus end-to-end. Three flows cover the system:

• Task lifecycle — from a goal to drafted, approved, ready tasks.
• Agent run — from a leased task to an isolated Kubernetes execution and back.
• Board sync — how the internal board projects to Plane.

The whole loop in one screen

Telegram / UI            Nexus Core              MongoDB / NATS         Kubernetes
─────────────            ──────────              ──────────────         ──────────
/nexus create goal  ──▶  decompose into   ──▶    goals + tasks
                         tasks (draft)           persisted

operator approves   ──▶  tasks → ready    ──▶    tasks updated
in UI                                            event: task.ready

                         scheduler leases ──▶    task → leased    ──▶   create Job
                         + builds run cfg         run created            (agent runner)

                                          ◀──    events stream     ◀──   pod reports
                         update board     ──▶    board_items             progress
                         sync to Plane    ──▶    board_links

                         run done         ──▶    task → done /
                                                 waiting_review

Each arrow is mediated by Nexus Core — the only authority over state.