Nexus Docs

Philosophy

Nexus is designed so users do not have to master disconnected tools to get meaningful work done. Natural language starts the work, structured product surfaces manage it, and runtime services execute it safely.

Technically Managed By

• Chat acts as the intake plane where intent is captured.
• Structured apps hold durable state for workflows, relationships, communication, and work management.
• Runtime services and integrations execute actions, enforce policy, and preserve auditability.

How Users Should Use and Manage It

1. 1Start in Chat when you need to initiate, clarify, or compile work.
2. 2Move into app surfaces when the work needs to be reviewed, managed, or operated over time.
3. 3Treat structured records and operational apps as the durable source of truth.

How It Fits in Nexus

• Platform Overview explains the operating model behind every Nexus feature.
• It connects Chat, Automations, Contacts, Inbox, Calendar, and runtime services into one system.
• It is the anchor document for understanding how Nexus is supposed to behave.

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

1. 1Choose the right Intent (Brainstorm, Solve, etc.) to set the agent's behavior.
2. 2Follow the Phase indicators to know where you are in the work cycle.
3. 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.

Philosophy

Onboarding is not just setup. It connects identity, provisioning, and the operating model so users can move from first access to first structured outcome.

Technically Managed By

• Tier 1: Marcoby Account Hub (identity.marcoby.com).
• Tier 2: Nexus Service Activation (Provisioning).
• PlaybookService: Auto-assigns the "Nexus Business Onboarding" journey.

How Users Should Use and Manage It

1. 1Start by reading the Platform Overview so the rest of the product makes sense.
2. 2Complete account activation and any required onboarding steps before expecting automation to run.
3. 3Use Chat for your first real outcome, then move into the app surface that holds the resulting work.

How It Fits in Nexus

• Getting Started connects the global identity hub to your private instance.
• It ensures every user starts with the same baseline operating model.
• It is the foundation of the sovereign "Silo" architecture.

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

1. 1Use Chat to initiate outcomes, ask for help, or compile work into structure.
2. 2Answer only the blocker questions required to move the work forward.
3. 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.

Philosophy

A dashboard should not be a static archive of yesterday's database counts. It should be an active control center that shows thinking, sensing, and executing in real time, built with premium aesthetics like glassmorphism and animated gradients.

Technically Managed By

• Trinity Navigation: THINK (blue), SEE (purple), and ACT (indigo) semantic layers.
• Glassmorphism UI: Custom CSS backdrop-blur and border overlays mapping live system state.
• Active Event Feeds: Live activity streams connected directly to recent conversation rollups and background jobs.

How Users Should Use and Manage It

1. 1Use the THINK metrics to track collaborative sessions and new idea generation.
2. 2Use the SEE indicators to review real-time anomaly alerts and business intelligence syncs.
3. 3Use the ACT widgets to monitor time savings, workflow run success, and ROI calculations.

How It Fits in Nexus

• Unifies all downstream telemetry from Chat, Automations, Contacts, and Integrations into one aesthetic cockpit.

Philosophy

Relationships should not be fragmented across inboxes, CRMs, calendars, and notes. Nexus treats a contact as a canonical operating object that other parts of the system can reliably reference.

Technically Managed By

• Contacts unify source identities from connected systems into canonical person and company records.
• Timeline events, merge candidates, sync jobs, and linked records create the relationship graph.
• Other surfaces can use contacts as shared context rather than storing disconnected copies of relationship state.

How Users Should Use and Manage It

1. 1Use Contacts to review and manage the canonical record for a person or company.
2. 2Resolve duplicates and check linked identities when records come from multiple systems.
3. 3Treat Contacts as the shared relationship layer for communication, workflows, and follow-up.

How It Fits in Nexus

• Contacts are the identity and relationship layer of Nexus.
• Inbox, Calendar, Integrations, and Automations all become more useful when they resolve back to canonical contacts.
• This is one of the core systems that makes Nexus feel unified rather than app-by-app.

Philosophy

Communication and time are not side data. They are core operating context. Nexus treats inbox and calendar as active work surfaces that should inform follow-up, relationships, and automation.

Technically Managed By

• Inbox and Calendar aggregate communication and scheduling context from connected providers.
• Messages and events should resolve back to canonical contacts and workflow context where possible.
• These surfaces provide live inputs that other parts of the system can use for drafting, follow-up, and automation.

How Users Should Use and Manage It

1. 1Review messages and meetings in context instead of as isolated events.
2. 2Use Chat when you want summaries, follow-up help, or action extracted from communication history.
3. 3Use these surfaces as operational context sources for Contacts and Automations.

How It Fits in Nexus

• Inbox and Calendar are the communications and commitments layer of Nexus.
• They enrich Contacts, inform Chat, and create operational triggers for workflows.
• They help turn Nexus into a live operating system instead of a static dashboard.

Philosophy

Nexus should feel like one operating system, not a collection of disconnected app logins. Integrations are how external systems become usable context and executable capability inside the platform.

Technically Managed By

• Integrations manage account connections, credentials, scopes, and connector health.
• Connected systems feed Chat, Contacts, Inbox, Calendar, and Automations with live context and execution capability.
• Workflow readiness depends on whether the required integrations and bindings are present and healthy.

How Users Should Use and Manage It

1. 1Connect the systems you want Nexus to see, reason over, or act through.
2. 2Review scopes, health, and connection status before relying on an integration in automation.
3. 3Reconnect or reauthorize stale integrations before troubleshooting downstream workflow issues.

How It Fits in Nexus

• Integrations are the connectivity layer of Nexus.
• They make external tools part of the operating system instead of separate silos.
• They are a prerequisite for many workflows, communication features, and identity resolution behaviors.

Philosophy

The AI should never have "black box" access. Every capability is an explicit, described tool that maps back to a specific integration, operation, and security scope.

Technically Managed By

• Core Tools: Identity context, connection status, and model orchestration.
• Connectors: Platform-specific tools for Google, Microsoft, GitHub, Slack, HubSpot, etc.
• Governed Access: Every tool call is logged, traceable, and subject to user-authorized scopes.

How Users Should Use and Manage It

1. 1Refer to this catalog to understand what the AI can help with.
2. 2Check your integration status in Settings if the AI reports a connection issue.
3. 3Use the chat traces to see exactly which tools the AI is calling during a task.

How It Fits in Nexus

• The Capability Catalog is the "hand-eye coordination" of the Nexus OS.
• It defines the boundary between conversational reasoning and physical execution.
• It ensures broad platform transparency across all connected services.

Philosophy

Automation in Nexus should be understandable, resumable, and operable by humans. AI may help author the workflow, but structured workflow state is what makes automation trustworthy.

Technically Managed By

• Workflow definitions are stored as durable records with setup state, runtime state, and execution history.
• Integrations, validation, approvals, and execution policies are attached to the automation rather than hidden in chat.
• The server compiles and versions workflow specifications before execution occurs.

How Users Should Use and Manage It

1. 1Review new automation requests in the Automations surface before activating them.
2. 2Resolve setup blockers such as integrations, required inputs, and validation rules.
3. 3Use run history and workflow status to manage the automation after creation.

How It Fits in Nexus

• Automations are the execution layer of Nexus.
• They turn conversational requests and operating needs into repeatable, governed system behavior.
• They depend on Chat for intake, Integrations for connectivity, and Runtime and Safety for execution control.

Philosophy

A shared workflow template prevents automation from becoming improvisation. The point is not just to generate steps, but to generate a stable, inspectable contract for execution.

Technically Managed By

• Each workflow follows the same canonical structure: trigger, inputs, integrations, actions, validation, outputs, and runtime policy.
• This structure supports compilation, validation, management, and execution across the platform.
• Missing requirements are modeled explicitly instead of failing silently during runtime.

How Users Should Use and Manage It

1. 1Use this model when configuring or reviewing advanced automations.
2. 2Confirm the trigger, inputs, integrations, actions, and approval rules before activation.
3. 3Treat the workflow template as the operational contract behind the automation.

How It Fits in Nexus

• Workflow Template sits underneath Automation Workflows as the canonical schema.
• It helps Nexus keep AI-authored workflows predictable and manageable.
• It is most useful for advanced users, operators, and internal product/engineering teams.

Philosophy

Treat CMS publishing as an explicit, auditable capability: generation, preview, and publish are distinct, reviewable steps.

Technically Managed By

• OAuth-authorized Ghost integration that issues publish credentials
• Draft/preview → approve → publish workflow with content/html payloads
• Media registration and binary upload for images and attachments
• Post metadata management (tags, authors, visibility, scheduling)

How Users Should Use and Manage It

1. 1Connect Ghost in Integrations and verify site permissions before publishing.
2. 2Use the Assistant to generate draft content, then open the draft for human review.
3. 3Preview rendered HTML before publishing to avoid formatting regressions.
4. 4Schedule or set visibility on publish if you need delayed release or member-only posts.

How It Fits in Nexus

• Enables AI-assisted content creation while preserving editorial review.
• Publishes content under the operator’s authorized account and retains audit traces.
• Supports newsletters and posts as durable artifacts surfaced in Automations or Inbox.

Philosophy

The image upload tool handles the entire binary transfer internally, returning the required asset URN immediately.

Technically Managed By

• Direct workspace file access reads local image paths or URLs.
• Handles LinkedIn upload registration and binary push internally in a single step.
• Returns a stable asset URN (e.g., urn:li:share:123) for post composition.

How Users Should Use and Manage It

1. 1Verify that the target file path exists in your workspace before calling the tool.
2. 2Provide the returned URN as the media attachment in nexus_linkedin_post.

How It Fits in Nexus

• Supplies the URN for post attachments, making image sharing seamless.

Philosophy

File creation must be safe, atomic, and scoped entirely within the user's private workspace.

Technically Managed By

• Write target filename and raw content to the secure user workspace.
• Optional encoding parameter supports base64 for binaries or standard utf-8 for text.
• Sanitizes paths to prevent directory traversal and system file overrides.

How Users Should Use and Manage It

1. 1Specify a clear filename and content body.
2. 2Use base64 encoding if you are persisting binary files (e.g. images or pdfs).

How It Fits in Nexus

• Saves Assistant-generated outputs, structured summaries, or scripts into your active storage.

Philosophy

Provide instantaneous publishing to X, ensuring text length constraints are validated beforehand.

Technically Managed By

• OAuth-authenticated client credentials authorize the publish request.
• Supports replyToTweetId parameter to chain replies or construct threads.
• Limits post text to standard 280 characters with prompt-time validation.

How Users Should Use and Manage It

1. 1Draft and preview the post content in Chat first.
2. 2Provide a replyToTweetId if you are replying to an existing conversation thread.

How It Fits in Nexus

• Allows the Assistant to act as an active publisher on social channels under human oversight.

Philosophy

Your workspace should be everywhere you are. The Nexus client-hub is the central web gateway that makes your sovereign "silos" feel like a single, unified experience.

Technically Managed By

• Unified Identity: Redirects automatically to the correct instance using Marcoby Identity.
• Identity Bridge: Mediates OAuth sessions between the Hub and private instances.
• Multi-instance routing: One login, many workspaces.

How Users Should Use and Manage It

1. 1Access the client-hub via identity.marcoby.com.
2. 2Log in to your Marcoby account to see all your active instances.
3. 3Switch between environments seamlessly without re-authenticating.

How It Fits in Nexus

• The client-hub is the "Operating System" browser for your Nexus instances.
• It is the primary way users interact with the platform on a daily basis.
• It bridges the gap between web-based silos and a unified user experience.

Philosophy

Nexus should be trustworthy before it is impressive. AI is allowed to assist with authoring and reasoning, but execution has to remain controlled, inspectable, and resumable.

Technically Managed By

• Workflow execution is governed by stored specs, validation rules, approval gates, and runtime policies.
• Run history, traces, paused states, and outputs are stored as durable records.
• The runtime model prevents raw conversational intent from becoming ungoverned execution.

How Users Should Use and Manage It

1. 1Treat workflow safety as something that must be configured and verified, not assumed.
2. 2Check missing inputs, approvals, validation rules, and integration state before activation.
3. 3Use traces, paused states, and stored outputs as the primary debugging and audit surfaces.

How It Fits in Nexus

• Runtime and Safety is the governance layer behind the whole platform.
• It enables Chat, Automations, and Integrations to work together without sacrificing control.
• It is what turns Nexus from an AI assistant into an operable business system.

Philosophy

You shouldn't have to trade privacy for intelligence. Nexus is designed to run on your infrastructure, using your keys, under your rules. We call this "Sovereign Intelligence."

Technically Managed By

• Self-hosted Agent Runtime (OpenClaw) via Docker/Coolify.
• Isolated "Silos": Your data never leaves your instance unless you allow it.
• BYOK (Bring Your Own Key): You control the relationship with the LLM providers.

How Users Should Use and Manage It

1. 1Deploy using our Coolify/Docker templates for the fastest setup.
2. 2Configure your own API keys in the Advanced Settings.
3. 3Treat your Nexus instance as a secure, private room for your business thinking.

How It Fits in Nexus

• Sovereign Setup is the core promise of the Nexus architecture.
• It distinguishes Nexus from SaaS "black boxes" by providing full auditability.
• It scales from a single server to enterprise-grade private clouds.

Philosophy

AI capability should be a secure, private utility that you control. You shouldn't have to trade context or data privacy for intelligence; your keys, your profiles, and your models stay strictly inside your instance.

Technically Managed By

• Bring Your Own Key (BYOK): Secure connection of Google, OpenAI, Anthropic, or OpenRouter.
• Sovereign Sandboxing: Dynamic credential injection ensures keys never leave your secure host.
• AI Profiles: Purpose-built operating profiles mapping model selection to active goals.
• Auto-Refreshed OAuth: Real-time background token sync prevents session expiration.

How Users Should Use and Manage It

1. 1Navigate to Settings > AI Configurations to connect your preferred provider keys.
2. 2Select a designated AI Profile (Quality, Speed, Coding) to tune the system's defaults.
3. 3Enable Advanced Override to select specific individual models for advanced streams.

How It Fits in Nexus

• The AI Model System is the cognitive engine of your Nexus instance.
• It coordinates with OpenClaw to safely run reasoning chains, tools, and actions.
• It respects your billing tier and feature gates to keep operations governed and predictable.