Liberu Automation

Governed workflows and provider-neutral automation capabilities for Liberu applications.

Software · Hosting · Services · Liberu Group

Liberu Automation is a deployable Laravel application for governed workflows, approvals, provider-neutral AI, connectors, media processing, and evaluation. It composes independently released capability and presentation packages while keeping application bootstrapping, environment configuration, panel composition, and cross-package tests in one place.

Key features

• Jetstream authentication, profiles, sessions, two-factor authentication, passkeys, and social login
• Filament admin and account panels assembled from optional presentation modules
• Organisations, teams, roles, permissions, audit trails, settings, and feature flags
• Messaging, notifications, localisation, search, files, webhooks, integrations, analytics, and import/export foundations
• Queue, scheduler, Horizon, Pulse, Telescope, Octane, Reverb, backup, and observability support
• Independently versioned modules installed into tracked /modules directories
• Independently versioned themes installed into tracked /themes directories with inheritance and safe fallback
• Architecture tests for manifests, dependency direction, package ownership, and presentation boundaries
• Governed Automation capabilities covering workflows, rules, approvals, AI gateways, prompts, data processing, media, connectors, and evaluation

Requirements

Quick start

git clone https://github.com/liberusoftware/automation-laravel.git
cd automation-laravel
composer install
cp .env.example .env
php artisan key:generate
npm install
npm run build
php artisan migrate
php artisan serve

Review .env before migrating. Use php artisan migrate --seed only when example data is wanted. The optional interactive install.sh supports local, Docker, and Kubernetes-oriented setup.

Composable package architecture

Each runtime capability is an independent liberusoftware/automation-* Composer package with its own module-automation-* GitHub repository, release lifecycle, manifest, provider, documentation, and tests. Each visual package is an independent liberu-theme. Shared contract packages and the custom installer are normal Composer dependencies under /vendor.

Application composition
├── modules/       # Composer-installed module releases, tracked in Git
├── themes/        # Composer-installed theme releases, tracked in Git
├── app/           # Host-only composition and integration
├── config/        # Enabled modules and application policy
└── tests/         # Cross-package and application tests

Composer is the source of installation and version truth:

# Update all dependencies, including modules and themes
composer update --with-all-dependencies

# Update one capability from its tagged GitHub repository
composer update liberusoftware/search --with-dependencies

The trusted liberusoftware/composer-installer places packages according to type:

modules/ and themes/ are intentionally kept out of .gitignore. Their reproduced contents are committed so deployments and reviews can see the exact installed code, while composer.lock pins each release and source commit. Do not edit an installed module only in this host: contribute the generic change to its package repository, release it, and update the Composer dependency here.

Installation, runtime enablement, authorisation, and commercial entitlement are separate concerns. config/modules.php selects the enabled capability graph; the module manager validates dependencies and orders providers without scanning application classes manually.

Every module also publishes a validated feature catalog in module.json. Hosts can inspect the complete catalog or search it without loading module internals:

php artisan module:features
php artisan module:features health
php artisan module:status search

Module and theme development

A module owns one cohesive capability and communicates through public contracts, actions, events, registries, or stable identifiers. Domain modules do not depend on Filament or themes; optional *-filament, *-api, and *-livewire packages provide presentation adapters.

Every module contains:

composer.json
module.json
README.md
LICENSE.md
CHANGELOG.md
src/
database/ or resources/ when required
tests/

Themes contain composer.json, theme.json, source assets, compatibility metadata, accessibility/fallback expectations, tests, documentation, and asset licensing information. See the module development guide and theme architecture.

Testing and quality

composer validate --strict
vendor/bin/pest
vendor/bin/pint --test
npm run build

The test suite exercises application behaviour and every installed module provider. Package architecture tests verify metadata, declared dependencies, host isolation, UI boundaries, and Composer ownership. Each of the eleven core Automation packages also carries package-local domain tests:

vendor/bin/pest modules/module-automation-*/tests

The release gate measures the owned application executable scope and requires 100% coverage for the application composition scope. The current release passes with 215 tests and 1,122 assertions:

XDEBUG_MODE=coverage php artisan test --coverage-clover=coverage.xml --min=100

Coverage excludes only vendor code, generated files, static assets, and configuration-only paths. PHPStan, module validation, Composer validation, Pint, Docker, and install checks are also required in CI.

Publishing Automation packages

Automation repositories keep the module- prefix on GitHub. Their Composer and Packagist names use liberusoftware/automation-* without that prefix. The publishing helper copies each committed package into its corresponding public repository and never force-pushes existing history.

# Publish or update all 44 Automation package repositories
scripts/publish-automation-packages

# Inspect package-to-repository mappings without submitting to Packagist
php scripts/submit-packagist.php --dry-run

Publishing requires authenticated gh and git access to the organisation. The released packages are tagged independently; the application’s current release is v1.0.1 (the initial major release was v1.0.0).

After the repositories are public, register every Composer package on Packagist:

# Verify all package-to-repository mappings without submitting
php scripts/submit-packagist.php --dry-run

# Obtain the MAIN API token from packagist.org/profile, then bulk register the packages
export PACKAGIST_USERNAME='your-packagist-username'
export PACKAGIST_API_TOKEN='your-packagist-api-token'
php scripts/submit-packagist.php
unset PACKAGIST_API_TOKEN

The submitter skips packages that are already registered and reports individual API failures without printing the configured token.

Documentation

• Module development
• Foundation compliance
• Foundation module matrix
• Theme architecture
• Theme system
• Messaging architecture
• Search architecture
• Localisation
• Notifications

Related Liberu projects

Security

Do not report security vulnerabilities through public GitHub issues. Email security@liberusoftware.com with reproduction details and the affected version so the report can be handled privately.

License

This project is open-source software available under the MIT License. The linked licence text is authoritative; this summary is not legal advice.

Feedback and contributing

Feedback and contributions are welcome. Report reproducible bugs, propose focused enhancements, improve documentation or translations, and submit tested changes. Search existing issues first. Pull requests should explain the problem and approach, remain focused, pass the required checks, and document user-visible or breaking changes. Security reports must follow the private route above.

Contributors

Thank you to everyone who helps improve Liberu. View the contributors graph.