AI Orchestrator

Package docs status

This page is generated from public package documentation in capell-4/packages and the package manifest checked into the source repository.

Field	Value
Composer package	capell-app/ai-orchestrator
Package slug	ai-orchestrator
Product group	Capell Commercial
Tier	premium
Bundle	commercial
Runtime contexts	admin
Capell version	^4.0
Source repository	capell-app/packages
Source path	packages/ai-orchestrator
Docs source	packages/ai-orchestrator/docs
Manifest	capell.json

AI Orchestrator coordinates AI providers, prompts, structured requests, and package integrations that need AI-assisted workflows.

At A Glance

• Package: capell-app/ai-orchestrator
• Namespace: Capell\AIOrchestrator\
• Service providers: packages/ai-orchestrator/src/Providers/AIOrchestratorServiceProvider.php
• Capell dependencies: capell-app/admin, capell-app/core
• Third-party dependencies: lorisleiva/laravel-actions, spatie/laravel-data, spatie/laravel-package-tools

Why It Helps Your Capell Workflow

• Centralizes provider orchestration so AI-enabled Capell packages do not each invent prompt, provider, and execution plumbing.
• Gives developers a shared place to add AI capabilities while keeping package features decoupled from a single vendor.
• Helps owners introduce AI features gradually because consuming packages can depend on a common orchestration layer.

Best Used With

• Media AI
• SEO Suite
• Agent Bridge

What It Adds

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.

Why It Matters

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

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

Built With

This package makes its Composer dependencies visible because they are part of the value proposition, not just plumbing. When an upstream package has a public repository, its linked preview card points readers back to the maintainers so their work gets proper credit.

Capell packages used here

• Capell Admin
• Capell Core

Open-source packages used here

• Laravel Actions - single-purpose action classes that keep package workflows out of controllers and Filament resources.
• Spatie Laravel Data - typed data objects for package boundaries, form state, settings, and structured results.
• Spatie Laravel Package Tools - Laravel package bootstrapping for config, migrations, commands, translations, and service provider setup.

Linked package previews

Screens And Workflow

Screenshots are generated from docs/screenshots.json during package deployment.

• 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.

Technical Shape

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

Code Map

Area	Path	Purpose
Actions	packages/ai-orchestrator/src/Actions	Domain operations. Test these directly where possible.
Data	packages/ai-orchestrator/src/Data	Structured payloads, form state, view models, and integration data.
Enums	packages/ai-orchestrator/src/Enums	Persisted states and Filament option values.
Providers	packages/ai-orchestrator/src/Providers	Registration, extension hooks, routes, migrations, and resources.
Resources	packages/ai-orchestrator/resources	Views, translations, assets, and package resources.
Tests	packages/ai-orchestrator/tests	Package-level Pest coverage.

Data And Persistence

• 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.

• Data objects live in src/Data/; use them for payloads, form state, and view models.

Extension Points

• Contracts: AIOrchestratorModule, AIOrchestratorProviderConnector.
• Register Capell extension points, routes, migrations, settings, render hooks, and resources from service providers.

Install Impact

• Adds ai-orchestrator service bindings and module registry.
• No migrations.
• No routes in this package.
• No Filament resource is registered by this package alone.

Install And Setup

• Install with composer require capell-app/ai-orchestrator in the host Capell application.
• In this repository, verify package changes with vendor/bin/pest; do not use php artisan.

Admin And Access

• None proven in this package directory.

• None proven in this package directory.

Common Pitfalls

• 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.

Docs

• docs index
• credits-and-acknowledgements.md
• overview.md

Testing

Run package tests from the repository root:

vendor/bin/pest packages/ai-orchestrator/tests --configuration=phpunit.xml

Maintenance Notes

• Put behaviour changes in src/Actions/; UI classes, commands, and controllers should call actions instead of owning domain logic.
• Use package Data classes at boundaries instead of passing anonymous arrays between layers.
• Use backed enums for persisted values and enum labels for Filament options.