Skip to main content
The qxctl maestro ... grammar surfaces Maestro presence evidence. Maestro is the presence authority; qxctl merely reads and inspects what Maestro records. Neither creates docking relationships on its own.

​
Inventory

Maestro inventory
qxctl maestro inventory presents Maestro’s complete, derived, read-only inventory of authenticated vector-engine docking relationships per TOPS and receptor. Additional qxctl leaves expose Maestro-related administration:
  • Status and inspection of docking evidence
  • Recovery routes bounded by Maestro’s own contracts
  • Foundational lifecycle enrollment and native supervision for Maestro itself
Every mutation route goes through the exact module-owned adapter. qxctl never renders Maestro descriptors from internal parsing or invokes an implicit newest version.
Maestro does not start, schedule, supervise, or invoke engines. qxctl maestro inventory is read-only. Binding, reconciliation, session coordination, or a lifecycle plan alone does not establish Maestro presence.

Maestro

Presence authority contract and boundaries.

qxctl engines

Engine binding registry (bindings are not docking).

qxctl session

Authenticated sessions used to record presence.

Engines overview

Independently installable vector engines that dock with Maestro.
Last modified on September 24, 2026