LAB / 02 — SYSTEM
One core.
Explicit responsibilities.
Keep domain decisions close to the operational record. Keep external providers and user interfaces behind clear boundaries.
A modular monolith
The current architectural direction is a Laravel core with a primary transactional database and Redis for queues, cache, locks, sessions and rate limits. Filament provides the operator interface; a separate Next.js cabinet consumes the customer API.
The useful boundaries
- Customer context
- Customer API access is scoped to an authenticated customer. Public UUIDs identify resources; they are not authorization.
- External providers
- Payment, tracking and notification integrations depend on configured provider credentials and deployment-specific validation. A driver in the source is not proof of an activated service.
- AI assistance
- The source includes a provider-independent gateway and human-owned review mechanisms. Sensitive decisions and external communication require the configured operator controls. This public website runs no AI service.
- Auditability
- Record the action and decision alongside the affected operational objects. Do not infer success from a queued job or an interface message alone.
Built in distinct phases
Named AltaPost planning and workflow work existed in 2018. The retained legacy implementation starts in 2019. The legacy platform combined product direction, workflow design and implementation by multiple developers over time.
The current Core is an AI-assisted Laravel / Filament rebuild of the operational domain.
No infrastructure inventory, internal admin links, production shipment data or secrets are published in this lab. This architectural overview is based on source documentation reviewed October 27, 2026.