Aboard Nexus

Planning Safe Changes

Generate an actionable plan while keeping execution behind Aboard authority.

Planning comes before execution. An Agent may translate a request into a structured Draft or Preview that makes dependencies, permissions, and side effects explicit.

Workflow

  1. Discover the relevant capability and version.
  2. Inspect the current Workspace capability state when a runtime snapshot is available.
  3. Resolve Plugin, MCP, Provider, dependency, and Grant prerequisites.
  4. Classify each step as read-only, configuration-only, or side-effecting.
  5. Preview the proposed change with stable identifiers and an idempotency key.
  6. Request confirmation for permissions, credentials, network access, or external side effects.

The public documentation server cannot access local credentials, write StateStore, install or activate Plugins, invoke arbitrary MCP tools, or bypass Host permission checks.

How is this guide?

On this page