Nimbus creative lane
Nimbus Systems
Nimbus is not a generic chat persona in the Command Center. It is a creative/vision lane with story-mode behavior, intake analysis, and future image/story asset handling.
Story Mode Protocol
Surface: mode, not button
Decision: Keep as a request-driven mode; do not force it into the main dashboard as a toggle.
Why: The bridge docs define story mode as an immersive in-world behavior. In the app, it belongs in an explanation page and trigger reference, not as a normal operational control.
Route: /nimbus
Source files
- /opt/data/agent-bridge/nimbus/STORY_MODE_PROTOCOL.md
- /opt/data/agent-bridge/nimbus/NIMBUS_SOUL.md
- /opt/data/agent-bridge/nimbus/NIMBUS_TEAM_PROTOCOL.md
Vision Intake / Watchdog
Surface: page
Decision: Expose as a visible page because it represents real workflow state and helps audit incoming visual assets.
Why: The intake watchdog and vision analyzer are operational systems, not hidden lore. They deserve a direct page and source references.
Route: /nimbus
Source files
- /opt/data/agent-bridge/nimbus/scripts/intake_watchdog.py
- /opt/data/agent-bridge/nimbus/scripts/intake_watchdog_v2.py
- /opt/data/agent-bridge/nimbus/scripts/vision_analyze.py
Image Generator / Story Assets
Surface: page + future button
Decision: Track inside the Nimbus page for now; promote to a button only after the generation flow is clearly defined and approval-gated.
Why: Stufio asked for a front-facing decision surface, but not every system should become a button. Asset generation belongs with story/creative controls and should not be hidden in the general dashboard until it is safe and stable.
Route: /nimbus
Source files
- /opt/data/agent-bridge/nimbus/os/21_VISUAL_DEVELOPMENT/Visual_Development.md
- /opt/data/agent-bridge/nimbus/intake
Cross-Agent Creative Review
Surface: page
Decision: Summarize the creative lane alongside J.A.R.V.I.S., D.E.V., A.C.E., and N.E.X.U.S. context so the Command Center can decide what becomes a UI element and what remains a file or protocol.
Why: The app is the front-facing command center, so it needs a decision surface that explains what is displayed, what is file-only, and what remains approval-gated.
Route: /nimbus
Source files
- /opt/data/agent-bridge/dev-jarvis/
- /opt/data/agent-bridge/ace-jarvis/
- /opt/data/agent-bridge/nimbus/
What becomes UI, what stays file-only
- Story mode is request-driven and immersive.
- Vision intake is operational and should be visible.
- Image-generation decisions should stay approval-gated until the flow is fully defined.
- The Command Center should decide what gets a page, a button, or no display at all.
Source inventory
- /opt/data/agent-bridge/nimbus/STORY_MODE_PROTOCOL.md
- /opt/data/agent-bridge/nimbus/NIMBUS_SOUL.md
- /opt/data/agent-bridge/nimbus/NIMBUS_TEAM_PROTOCOL.md
- /opt/data/agent-bridge/nimbus/scripts/intake_watchdog.py
- /opt/data/agent-bridge/nimbus/scripts/intake_watchdog_v2.py
- /opt/data/agent-bridge/nimbus/scripts/vision_analyze.py
- /opt/data/agent-bridge/nimbus/os/21_VISUAL_DEVELOPMENT/Visual_Development.md
Related command center lanes
The dashboard should surface what matters. If a thing is a mode, keep it a mode. If it is a workflow, give it a page. If it is only a file or protocol, keep it out of the button graveyard.