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.
What This Package Adds
Section titled “What This Package 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.
Developer Notes
Section titled “Developer Notes”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.
Operational Notes
Section titled “Operational Notes”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.
Data And Retention
Section titled “Data And Retention”- 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.
Screenshot Plan
Section titled “Screenshot Plan”- 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.
Pitfalls
Section titled “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.
Verification
Section titled “Verification”- Run
vendor/bin/pest packages/ai-orchestrator/testswhen 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.
Package Manifest
Section titled “Package Manifest”- 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.
Admin Surfaces
Section titled “Admin Surfaces”- None proven in this package directory. This package registers orchestration services and a Layout Builder AI module, but no standalone Filament navigation item.
Commands
Section titled “Commands”- None proven in this package directory.
Routes And Config
Section titled “Routes And Config”- None proven in this package directory.
Permissions And Gates
Section titled “Permissions And Gates”- None proven in this package directory.
Migrations
Section titled “Migrations”- None proven in this package directory.
ERD Excerpt
Section titled “ERD Excerpt”This package has no committed ERD excerpt. Use implementation notes and extension points instead of inventing schema.
Screenshot Automation
Section titled “Screenshot Automation”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.