Chat Control Plane
Nexus Chat is the intake and authoring surface. Users describe goals in plain English, and the platform compiles that intent into structured work the rest of the system can manage.
Audience: Anyone creating workflows, asking for action, or refining operating context.
Current Version
1.0
Documentation aligned to the current operational build of Chat, Automations, Contacts, and workflow runtime.
Scope
1
A standalone documentation page with a stable URL you can share directly.
Quick Start
How the system is meant to be used
Step 1
Read the platform overview first so you understand how Chat, apps, and runtime work together.
Step 2
Start your first conversation in Chat with a real business outcome, not just a general prompt.
Step 3
Let Nexus turn that intent into a durable record, workflow, or next-step artifact.
Step 4
Connect the systems required for context, communication, and execution as setup requires.
Step 5
Move into the relevant app surface to review, manage, approve, and operate the resulting work.
Operating Principle
Chat compiles. Apps operate. Runtime executes.
Nexus is not a chatbot that happens to call tools. It is a structured operating system where conversational intent is translated into durable records, validated state, and auditable actions.
This docs site is the product-level reference for how that model works today and how the current 1.0 surfaces fit together.
Audience
Anyone creating workflows, asking for action, or refining operating context.
Chat Control Plane
Nexus Chat is the intake and authoring surface. Users describe goals in plain English, and the platform compiles that intent into structured work the rest of the system can manage.
Philosophy
Chat is not meant to be the final resting place of work. It is the place where intent becomes structure, blockers are clarified, and the system decides what durable object needs to exist next.
Technically Managed By
- The chat layer receives intent and routes it through orchestration logic.
- It can create or update structured artifacts such as workflow records, setup tasks, and contextual operating objects.
- Execution should happen through governed runtime tools and app surfaces, not direct raw prompt output.
How Users Should Use and Manage It
- 1Use Chat to initiate outcomes, ask for help, or compile work into structure.
- 2Answer only the blocker questions required to move the work forward.
- 3Once Nexus creates a durable artifact, continue operating that work in the relevant app.
How It Fits in Nexus
- Chat is the intake and authoring plane for the whole system.
- It connects user intent to Automations, Contacts, Inbox, Calendar, and future structured workflows.
- It is the first step in the Nexus pattern: describe, compile, manage, execute.
What Matters
- Chat is where intent becomes structure.
- The orchestration layer routes work into durable records instead of leaving it trapped in conversation.
- Chat is best for initiation, refinement, and troubleshooting, not as the long-term source of truth.
Reference Notes
Next Step
Use the docs as the product contract.
As new apps and runtime behaviors ship, extend this documentation hub first so users and internal teams have one clear reference for how Nexus is supposed to work.