Gabriel AlmirPTExplicit errors
Result and Option make failure and absence part of the contract.
dossier / implemented
Maybe
Errors and absence become explicit states, adopted gradually at the edges of PHP 7.4 systems.
01 / Context
Legacy systems mix null, false, exceptions, and validation. Maybe explores an incremental transition without requiring a rewrite.
- PHP 7.4 compatibility.
- Gradual adoption in existing code.
- Process concurrency with clear security boundaries.
02 / Architecture map
Architecture map
- 01null / false / throw
Competing semantics in legacy code.
- 02Schema + DTO
Data gains shape at the boundary.
- 03Result + Option
Error and absence enter the contract.
- 04Isolated Async
Processes with explicit timeout and serialization.
03 / Decisions
Decisions
Adopt at the edges
Schema and DTO enter first where external data crosses the system.
Async as a process boundary
The core stays synchronous; concurrency, timeout, and serialization belong to their own boundary.
04 / quality
Quality attributes
CompatibilityPHP 7.4-compatible API.A declared project constraint.
SafetyValidation before crossing processes.Schema, DTO, and explicit contracts.
EvolvabilitySchema → DTO → Result → Option → Async.Layers can be adopted incrementally.
Evidence
- Public APIVersioned types and examples in the repository.
- Async boundarySerialization, timeout, and isolation are observable responsibilities.
Known limits
- Async does not replace durable queues or operational supervision.
- The application remains responsible for idempotency, resources, and recovery.
- License and source commit await pinning after audit.