Framework vs Starter Kit

EvoLayer Base separates its framework logic from its application boilerplate using two repositories. This guarantees a safe upgrade path while giving you a batteries-included starting point.

The Package: xuple/evolayer-base

The package is the true "framework." It is installed via Composer into the vendor/ directory and contains:

• The compiled PHP logic for the ontology cache.
• The evolayer:* Artisan commands.
• The underlying AI streaming infrastructure.
• The pristine React component stubs (published on install).

The package handles the heavy lifting safely out of sight, keeping your application codebase incredibly clean.

The Host: xuple/evolayer-base-starter

The Starter Kit is a thin, consumable shell. It is a standard Laravel 13 application that requires the EvoLayer Base package.

When you use composer create-project, you are cloning the Starter Kit. It contains:

• Your .env and configuration files.
• Your database migrations and seeders.
• The React frontend components (which the package copied in during installation).

You own your app code, configuration, and branding. Meanwhile, the framework acts as a silent partner, managing the complex AI runtime, UI blocks, and example surfaces behind the scenes.

These managed surfaces are safely updated via composer evolayer:resync. Whenever you're ready to deeply customize a managed surface and take full control, you can easily eject it into your own codebase.