Skip to content

Adaptors

Adaptors

Gemba pairs exactly one WorkPlane adaptor (the data plane — work tracker) with at most one OrchestrationPlane adaptor (the agent runtime). Each adaptor declares a capability manifest at boot; the SPA renders only what the manifest exposes.

Authoring guides

  • WorkPlane authoring guide — the core surface every WorkPlane adaptor must implement, plus the conformance harness an adaptor passes to be considered ready.
  • OrchestrationPlane authoring guide — the scope-bounded session lifecycle and the optional capability axes every OrchestrationPlane adaptor declares.

Reference adaptors

  • Beads — the out-of-the-box WorkPlane adaptor (bd CLI
  • Native — the bundled OrchestrationPlane that drives tmux / iTerm2 / Terminal.app sessions directly without an external daemon.
  • Gas Town — optional OrchestrationPlane wrapping the Gas Town agent runtime. Conformance report.

Where next

  • Architectural decisions about plane boundaries: see Design.
  • The capability manifest contract is in the SPA spec: see UI spec.