Three-Tier Model

The UNVRSL ecosystem is divided into three logical layers.

Tier 1 — Core Services

The foundational layer: eight dedicated GitHub repositories providing standardized, reusable backend, frontend, and documentation infrastructure across all projects.

Service	Repository	Subdomain

core.console	olivmiron/core.console	core.console.medkronos.com
core.auth	olivmiron/core.auth	auth.medkronos.com
core.storage	olivmiron/core.storage	core.storage.medkronos.com
core.ai	olivmiron/core.ai	core.ai.medkronos.com
core.assets	olivmiron/core.assets	core.assets.medkronos.com
core.hypermedia	olivmiron/core.hypermedia	core.hypermedia.medkronos.com
core.docs	olivmiron/core.docs	core.docs.medkronos.com
core.backend	olivmiron/core.backend	(Client SDK — Composer package)

Tier 2 — Orchestration

The Orchestrator is an automation tool designed to scaffold, provision, and deploy new web projects seamlessly. It reduces setup time to near zero by generating project boilerplate, configuring core service connections, and setting up deployment pipelines.

→ Orchestrator Code Reference

Tier 3 — Application Projects

The actual end-user web applications built using the Orchestrator and powered by the underlying Core Services. Each project is a standalone repository deployed to its own subdomain, but shares authentication, storage, AI, and asset infrastructure with all other projects.

See: End Projects for the full list.

Data Flow

Client / App

    │

    ▼

core.console (API gateway)

    │

    ├── resolves project from API key

    ├── checks security rules (IP/domain, deny-by-default)

    ├── validates API key

    ├── checks project status + service permissions

    ├── enforces quotas

    ├── logs to request_log

    │

    ├──→ core.auth (identity, session)

    ├──→ core.storage (files)

    ├──→ core.ai (LLM calls)

    ├──→ core.hypermedia (media processing)

    └──→ core.assets (UI, branding, JS)

    │

    ▼

Response (via core.console)

Clients talk to core.console exclusively. core.console routes to internal services. Apps integrate via the client SDK (core.backend), which handles API key management and request signing.