Skip to main content
The qxctl knowledge engines ... grammar manages the protected user-scope default binding profile for Symphony’s vector engines. It binds selected content for later reconciliation. It does not install, invoke, activate, dock, authenticate, authorize, or apply an engine.

​
Commands

Engines grammar
Supply absent for the first v2 registry mutation or the exact digest reported by list for later mutations. Every mutation is compare-and-swap against that digest.

​
v1 to v2 migration

Valid v1 registry state remains readable. Migration to v2 is a separate exact compare-and-swap and is never a version-selection operation. Do not treat migration as an upgrade path for engine selection.
  • list and inspect continue to work on v1 evidence.
  • migrate produces a linked v2 generation without discarding v1 truth.
  • After migration, use v2 digests for future mutations.

​
What a bind is

A bind selects exact content for later reconciliation by the coordinator. It:
  • Does not install an engine
  • Does not invoke or activate an engine
  • Does not dock an engine with Maestro
  • Does not authenticate a caller
  • Does not authorize apply

qxctl reconcile

Reconcile bound content with a coordinator.

qxctl lifecycle

Lifecycle plans that use bound engines.

Maestro

Presence authority that records docking, not bindings.

Engines overview

Independently installable vector engines.
Last modified on September 24, 2026