Skip to main content

Control Plane

The control plane is the Ecosystem workflow that turns compiled and bound artifacts into deterministic orchestration and generation outputs.

It does not replace runtime execution. It complements capability binding by answering: what needs to change outside the runtime before activation, and what integration artifacts can be generated safely from current contracts.

Inputs and outputs​

Control-plane workflows consume:

  • CompiledEntrypointBundle
  • capability binding lockfile
  • adapter manifests and loaded adapters

They produce typed artifacts for deterministic review and CI gating:

  • report: adapter and contract coverage diagnostics
  • plan: ordered capability resource operations
  • apply: typed execution results for planned operations
  • drift: missing/unexpected/mismatched operation deltas
  • generate: integration artifact sets (for example query/router clients and scaffold metadata)

CLI workflow​

# 1) Validate adapter coverage and contract compatibility
gooi marketplace control-plane report --input -

# 2) Build deterministic operation plan
gooi marketplace control-plane plan --input -

# 3) Generate integration artifacts from requested surfaces/targets
gooi marketplace control-plane generate --input -

# 4) Optionally execute supported operations
gooi marketplace control-plane apply --input -

# 5) Detect drift (advisory by default; strict fails CI)
gooi marketplace control-plane drift --input - --strict

Determinism and safety boundaries​

  • Identical inputs produce identical plan and artifact hashes.
  • Missing required adapter support returns typed diagnostics; there are no implicit fallbacks.
  • drift is advisory by default in v1; use --strict for release gates.
  • Adapter translation is provider-owned. Gooi core owns ordering, diagnostics, and contract enforcement.

Terraform relationship​

Control plane is Terraform-complementary. It is capability-aware orchestration and generation over Gooi contracts, not a Terraform replacement.

What's next​