The Model-Way
Nexus is a structured operating partner. The "Model-Way" transforms unstructured chat into intent-led business work by separating goal, phase, decision, and execution.
Audience: Users who want to turn conversations into structured, repeatable work.
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
Users who want to turn conversations into structured, repeatable work.
The Model-Way
Nexus is a structured operating partner. The "Model-Way" transforms unstructured chat into intent-led business work by separating goal, phase, decision, and execution.
Philosophy
Nexus should not behave like endless chat. It starts with intent, moves through Discovery, Synthesis, Decision, and Execution, and preserves the resulting context so the business can reuse what it learned.
Technically Managed By
- Intent pickers categorize the goal before the first prompt is sent.
- Phases (Discovery -> Synthesis -> Decision -> Execution) guide the agent journey.
- State is preserved across phases to prevent "memory drift" common in raw chat.
How Users Should Use and Manage It
- 1Choose the right Intent (Brainstorm, Solve, etc.) to set the agent's behavior.
- 2Follow the Phase indicators to know where you are in the work cycle.
- 3Provide context during Discovery; review structure during Synthesis.
How It Fits in Nexus
- The Model-Way is the primary interaction engine of Nexus.
- It makes high-value business work feel like a standard, repeatable operating skill.
- It is the bridge between human intent and machine execution.
What Matters
- Intent pickers: Brainstorm, Solve, Write, Decide, Learn.
- Structured Phases: No more "endless chat" without a goal.
- Governed output: The system follows your context, constraints, and approval path.
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.