Repository layout

app/
  Domains/          Technical bounded contexts
  Filament/         Admin UI
  Http/             Controllers, middleware, builder endpoints
  Jobs/             Cross-domain orchestration jobs
  Providers/        Service providers

database/migrations/
  landlord/         Platform schema
  tenant/           Tenant schema

packages/
  fapost-foundation Public contracts and DTOs for Core, Solutions, and Plugins
  fapost-support    Shared primitives

resources/js/builder/
                    The Vue flow builder

Domains

Each domain is a bounded context, not a layer: Assistant · Broadcasting · Channels · Contact · Conversation · Flow · Media · Messaging · Presale · Shared · Staff · Tenancy · Webhook Inside one:

Domains/{Domain}/
  Models/        Eloquent models, when the domain needs persistence
  Contracts/     Domain interfaces and stable integration points
  Services/      Business logic
  Jobs/          Asynchronous orchestration within the domain
  Http/          Controllers and requests, without business logic
  Exceptions/

Do not create new base folders — app/Features, app/Solutions, app/Plugins — unless a deliberate decision introduces them. Solutions and Plugins are external packages by design; see the extension model.

Boundaries that are enforced

Domains do not reach into the landlord database. A domain that needs platform-level data takes a contract from Tenancy/Contracts. Direct DB::connection('landlord') stays inside Tenancy infrastructure. The reasoning is in Tenant-aware execution. foundation and support do not depend on Core. No use App\…, no references to concrete Core classes. See Dependency direction. Migrations do not depend on runtime state. See Migration isolation. Only migration isolation has a PHPat rule. The other two are not checked mechanically: foundation and support cannot import App\… because it would not autoload outside Core, and landlord access is caught in review only.

Where a piece of code belongs

It is…	It goes in
A contract external packages build against	`packages/fapost-foundation`
A reusable primitive with no Core dependency	`packages/fapost-support`
Used by one domain and carrying its meaning	That domain in Core
Orchestration across several domains	`app/Jobs`

Business logic lives in services and domain classes. Controllers and jobs orchestrate; they do not decide.

Overview

Development environment

Extension model

Building extensions

Flow nodes

Extension surfaces

Shipping an extension

Core internals

Contributing to Core

Repository layout

Domains

Boundaries that are enforced

Where a piece of code belongs

​Domains

​Boundaries that are enforced

​Where a piece of code belongs

Domains

Boundaries that are enforced

Where a piece of code belongs