Aboard Nexus

Authority and Permissions

Separate documentation claims, runtime facts, and execution authority.

Aboard uses one authority for each Workspace fact.

Documentation
  declares capabilities
Runtime snapshot
  reports observed state
Host validation
  decides what is allowed now

In local mode, Aboard Host owns Workspace state, Plugin lifecycle, credentials, permissions, and side effects. Workbench presents workflows and requests changes through approved adapters.

A local Workspace and a managed Agent Platform Workspace must never be simultaneous writers of the same fact. Promotion is an explicit authority switch.

The presence of a capability in documentation does not prove that it is installed, active, configured, permitted, or executable.

How is this guide?