Engineering the platform for safer releases, resilient services and global scale.
V15 builds above V14 with Redis/session readiness, cache abstraction, transactional outbox delivery, signed webhooks, protected object storage, deployment channels, tenant-level rollouts, worker heartbeats, incidents, public status, maintenance controls and executable platform self-tests.
Release safely. Process asynchronously. Observe continuously.
Maintenance Switch
A file-backed maintenance flag can move incoming traffic to a proper HTTP 503 maintenance response while leaving the public status route available.
Tenant Rollouts
New capabilities can be piloted with specific institutions rather than enabled globally at once.
Worker Heartbeats
Background workers publish their last-seen time so failed or stale processing becomes visible.
Migration Runner
MySQL/MariaDB deployments can apply versioned SQL migrations with transaction rollback on failure.
Platform Self-Test
An executable CLI test checks storage, cache, release manifest and required PHP extensions before deployment.
Global Fresh Deployment
V15 continues release-specific hashed assets and a release manifest to prevent old front-end assets being silently reused.
The next constraint is no longer features—it is reliability.
RCI can continue adding educational and commercial capabilities, but V15 deliberately concentrates on how those systems are released, monitored, recovered, integrated and scaled.