Skip to content
Capell CMS

AI Orchestrator Credits And Acknowledgements

AI Orchestrator is part of the Capell package set. This page names the main frameworks, packages, authors, and services this package leans on, with a short note about what they make possible here. It is intentionally shorter than the repository-wide credits page and closer to the package itself.

Package role: Capell AIOrchestrator orchestration package

Shared Foundations

Section titled “Shared Foundations”
  • Laravel, created by Taylor Otwell, gives this package routing, service providers, Eloquent, validation, queues, events, auth, caching, and the normal Laravel testing surface.
  • Filament and the Filament project give this package admin resources, pages, widgets, forms, tables, actions, and panel integration.
  • Composer, Packagist, and GitHub make the package install, split, and release workflow possible. Composer and Packagist deserve a special nod because Capell packages live and update through Composer metadata.
  • Pest, Orchestra Testbench, PHPStan, Larastan, Laravel Pint, and Rector keep this package easier to test, review, and update when bugs are fixed.

Capell Packages Used Here

Section titled “Capell Packages Used Here”
  • Capell Admin supplies the Capell-side contracts, surfaces, or runtime that AI Orchestrator builds on.
  • Capell Core supplies the Capell-side contracts, surfaces, or runtime that AI Orchestrator builds on.

Open-source Packages And Authors

Section titled “Open-source Packages And Authors”
  • Laravel Actions, by Loris Leiva, keeps package behaviour in small action classes instead of burying it in pages, commands, or controllers.
  • Spatie Laravel Data, by Ruben Van Assche and Spatie, keeps request state, settings, and package results typed at the boundaries.
  • Spatie Laravel Package Tools, by Freek Van der Herten and Spatie, keeps service provider setup, config publishing, migrations, and command registration predictable.

What We Especially Appreciate

Section titled “What We Especially Appreciate”

The strongest bit is the approval-aware workflow. Capabilities can plan, review, and require approval before execution, which means AI help can be useful without becoming a blind mutation path.

Keeping This Page Current

Section titled “Keeping This Page Current”

When AI Orchestrator adds a new framework, service, or third-party package that becomes part of the user-facing workflow, update this page and the package README together. Credits should explain the practical help we get from a dependency, not just list a package name.