UNVRSL Framework
UNVRSL Framework
UNVRSL is a custom multi-repository PHP framework for building, deploying, and scaling web applications. It follows a three-tier architecture — Core Services provide the foundation, the Orchestrator scaffolds new projects, and Application Projects are the end-user products built on top.
Core Services (Tier 1)
Seven dedicated repositories providing reusable backend, frontend, and documentation infrastructure:
| Service | Purpose |
| core.auth | Authentication, sessions, user access, multi-app identity |
| core.storage | S3 storage, file tracking, object management |
| core.ai | LLM wrappers, conversational data, AI integration |
| core.assets | CDN-like shared PHP/JS utilities, stylesheets, branding |
| core.hypermedia | Media/document processing, conversion, compression |
| core.docs | Living documentation hub (this site) |
| core.backend | Composer package: HTML template init, reusable PHP helpers |
Orchestration (Tier 2)
The Orchestrator scaffolds, provisions, and deploys new application projects, reducing setup time to near zero.
Application Projects (Tier 3)
End-user web applications built on the Core Services via the Orchestrator.
Documentation Layers
All documentation in core.docs is organized into four interconnected layers:
L1 — Scope — The "what and why." Project goals, feature definitions, ecosystem overview, and the end-projects roadmap. This is the stable north star that rarely changes.
L2 — Architecture — The "how" at the system level. Data models, auth flows, service contracts, deployment pipeline, quota systems. Changes when architectural decisions are made, but not frequently.
L3 — Roadmap — The "what's next." Living task lists, priorities, and local scopes per core service and per application project. This layer evolves weekly.
L4 — Code — The "what exists." Code-level documentation mirroring the actual repositories — class references, API signatures, usage examples. Lives closest to the code it describes.
Each layer links to related pages in other layers, creating an interconnected map of the entire framework from vision down to implementation.
Infrastructure
- VPS with Plesk Obsidian on Ubuntu 24.04
- Each core service = dedicated subdomain (e.g.
core.ai.medkronos.com) - Webhook-based auto-deploy from GitHub to Plesk subdomains
- SSH key authentication between VPS and GitHub