Aboard Nexus

Agent Interface Overview

How documentation, capability contracts, machine resources, and authoritative runtimes serve Agents.

Aboard's documentation site is a read-only discovery and planning surface for Agents, not an execution runtime.

Three layers

  1. Human documentation explains concepts, boundaries, workflows, and limitations.
  2. Capability metadata describes IDs, versions, inputs, outputs, permissions, side effects, idempotency, and confirmation.
  3. Runtime handoff lets Aboard Host, Runtime MCP, or Agent Platform confirm availability and execute.
Read docs -> Discover capability -> Obtain runtime context -> Create Draft/Preview -> Review and confirm -> Hand off to authority -> Verify Run, Artifact, and Evidence

Status

  • Implemented: Capability Manifest, Agent Card, Agent Skills, Docs MCP, and read-only Handoff Preview.
  • Partial: runtime capability snapshots and the Host execution loop are still being built.
  • Future reserved: a unified Contract Index, machine-readable Run/Evidence resources, and cross-authority compatibility metadata.

The documentation site cannot install Plugins, access credentials, mutate StateStore, or invoke arbitrary MCP tools. A documented capability is not proof that the current Workspace has installed, activated, configured, or authorized it.

How is this guide?

On this page