Download the PHP package fapost/foundation without Composer
On this page you can find all versions of the php package fapost/foundation. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download fapost/foundation
More information about fapost/foundation
Files in fapost/foundation
Package foundation
Short Description FaPost public contract layer for Solutions, Plugins and external integrations
License Apache-2.0
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package foundation
FaPost Foundation
fapost/foundation is the public contract layer of the FaPost platform. It holds the
interfaces, DTOs, enums and value objects that Core, Solutions and Plugins agree on. It is the
only package a Solution or Plugin is allowed to depend on to integrate with the platform.
Design rules
- No dependency on Core.
use App\...is forbidden here. Foundation never references concrete Core classes; the implementations live in Core and are bound to these contracts at runtime. - Contracts, not logic. Everything here is an interface, a DTO, an enum, or a small value object. No business logic, no persistence, no framework wiring.
- If a contract is needed by an external Solution/Plugin, it belongs here. A pure, reusable
primitive with no Core coupling belongs in
fapost/support. Domain-specific code stays in Core.
Requirements
- PHP
^8.4 illuminate/support^11 || ^12psr/http-message,spatie/laravel-data
Namespace
What's inside
| Area | Namespace | Purpose |
|---|---|---|
| Extension lifecycle | Contracts, Lifecycle, Manifest, Support |
Register and validate Solutions/Plugins against the platform |
| Flow engine | Flow\*, Contracts\NodeHandlerInterface, Contracts\DataAccessorInterface |
Node handlers, expression engine, triggers, contact writes, scoped state |
| Messaging | Messaging\* |
Outbound message senders, delivery results, typing/processing indicators |
| Channels | Channel\* |
Channel adapters and webhook registration |
| Media | Media\* |
Channel media upload/download contracts and DTOs |
| RAG | Contracts\RagAdapterInterface, DTO\*Rag* |
Retrieval-augmented generation adapters |
| Analytics | Analytics\* |
Analytics event DTO, writer contract, event types |
| Inbound/outbound DTOs | DTO\* |
Incoming/outgoing messages, media, webhook payloads, execution results |
Extension entry point
An extension never touches Route, Schedule or Migrations directly. It declares intent
through CoreRegistrarInterface, whose implementation lives in Core:
- Solution — an external composer package with niche domain logic (HR, Recruitment).
Extend
Lifecycle\AbstractSolutionServiceProvider. - Plugin — extends platform capabilities without domain logic (a new channel adapter, a new
RAG provider). Extend
Lifecycle\AbstractPluginServiceProvider.
Both declare a Manifest\SolutionManifest used for boot-time validation, capability compatibility
checks and degraded-state detection:
Flow node handlers
NodeHandlerInterface is the contract for flow-engine nodes. The engine resolves a handler by
(type, version) from an in-memory registry — no DB queries. Versioning rules:
- backward-compatible change (new field with default) →
version()unchanged; - breaking change →
version()++, old handlers stay registered so existing flow definitions keep running; - remove a handler only when no active flow references it.
Handlers must be graph-unaware (return a sourceHandle, not the next node id) and safe to retry.
Flow\Handlers\AbstractVersionedHandler provides a base for versioned handlers.
Testing
License
Licensed under the Apache License 2.0.
All versions of foundation with dependencies
illuminate/support Version ^11.0 || ^12.0
psr/http-message Version ^1.1 || ^2.0
spatie/laravel-data Version ^4.0