Skip to content

AIOrchestrator

Status: Available, no schema impact · Kind: package · Tier: premium · Bundle: commercial · Contexts: admin · Product group: Capell Commercial

This page is the consolidated implementation overview for the AIOrchestrator package. It is extracted from the package README, service providers, migrations, config files, routes, resources, models, actions, and the shared Capell ERD notes where available.

AIOrchestrator provides the orchestration layer for Capell ai-orchestrator modules and capability execution.

  • AIOrchestrator module registry.
  • Contracts for modules and provider connectors.
  • Actions for listing, registering, and running capabilities.
  • core layout builder integration module for layout planning preview.

Defines the module and capability contracts other packages can use without putting AI workflow logic into resources or controllers.

  • AIOrchestratorServiceProvider registers ai-orchestrator services.
  • Contracts: AIOrchestratorModule and AIOrchestratorProviderConnector.
  • Actions: ListAIOrchestratorCapabilitiesAction, RegisterAIOrchestratorModuleAction, RunAIOrchestratorCapabilityAction.
  • Data objects describe capabilities and runs.
  • Enums model approval level.

Lets Capell installations add assisted workflows while keeping approvals and capability boundaries explicit.

  • Adds ai-orchestrator service bindings and module registry.
  • No migrations.
  • No routes in this package.
  • No Filament resource is registered by this package alone.
  • This package does not own database tables.
  • State is passed through data objects and consuming package integrations.
  • Persistence, if needed, belongs to the package that runs the capability.
  • Capability list or prompt surface where provided by a consuming package.
  • core layout builder preview workflow when the integration is enabled.
  • Approval state where a capability requires review.
  • Install the package that supplies the ai-orchestrator surface before expecting UI.
  • Treat capability output as reviewable draft data unless the consuming package proves otherwise.
  • Provider connector configuration belongs to the consuming ai-orchestrator integration.
  • Run vendor/bin/pest packages/ai-orchestrator/tests when package tests exist.
  • Run the relevant host-app migration or package install flow in a disposable database.
  • Open the listed admin or frontend surface and compare it with the screenshot plan.
  • Composer name: capell-app/ai-orchestrator
  • Product group: Capell Commercial
  • Kind: package
  • Tier: premium
  • Bundle: commercial
  • Contexts: admin
  • Requires: capell-app/admin, capell-app/core, capell-app/layout-builder
  • Optional dependencies: None listed.
  • None proven in this package directory. This package registers orchestration services and a Layout Builder AI module, but no standalone Filament navigation item.
  • None proven in this package directory.
  • None proven in this package directory.
  • None proven in this package directory.
  • None proven in this package directory.

This package has no committed ERD excerpt. Use implementation notes and extension points instead of inventing schema.

Deployment should read screenshots.json, install the package with demo data, resolve each admin surface or frontend URL, and write images to public/docs/screenshots/packages/ai-orchestrator.

  • Capability list or prompt surface where provided by a consuming package.
  • core layout builder preview workflow when the integration is enabled.
  • Approval state where a capability requires review.