Start minimal. Add capabilities as the application grows. Keep the same foundation.

/kɔˈrɛtsjɑ/ (ko-RET-si-ya) — from Ukrainian серцевина (core, foundation)

Coretsia is an open-source deterministic PHP 8.4+ application framework built around explicit capability composition, reproducible artifacts, runtime lifecycle safety, and machine-enforced architecture.

It is designed for applications that may begin with a small runtime surface and later add web, worker, asynchronous, integration, and operational capabilities while keeping the same application foundation.

Coretsia treats framework composition and architectural governance as framework responsibilities rather than undocumented conventions.

Application capabilities are selected through mode presets and canonical package metadata.

Those inputs resolve into an explicit deterministic module plan rather than relying on incidental registration order, filesystem scanning, or hidden bootstrap behavior.

Generated framework artifacts are designed to be stable and verifiable:

• deterministic serialization and fingerprints;
• explicit schema identities;
• no timestamps or local absolute paths;
• rerun-no-diff generation;
• validation of artifact structure and semantics.

Coretsia uses a shared Unit-of-Work lifecycle across runtime operations such as HTTP requests, CLI invocations, worker jobs, queue messages, and scheduler ticks.

Runtime-local state is explicitly managed and reset so long-running processes do not silently retain state between operations.

Package boundaries and framework invariants are backed by repository tooling and CI.

Enforcement covers dependency boundaries, package structure, runtime/tooling separation, deterministic generated outputs, public API and DTO policy, security checks, and publishing safety.

Coretsia defines four canonical framework modes:

Modes are capability profiles, not prescribed application architectures.

They do not require MVC, DDD, Clean Architecture, Vertical Slice Architecture, or another application architecture style.

The application architecture remains an owner decision.

Coretsia is in active development.

Current capability tracks:

• Bootstrap & prototypes — implemented. Repository foundations, package tooling, CI and architecture verification, deterministic tooling primitives, and initial CLI foundations are in place.
• Core — implemented. Contracts, Foundation, Kernel, the baseline persistent Worker runtime, and their supporting composition and lifecycle infrastructure are implemented.
• Micro release track — active development. Current work is focused on the remaining infrastructure required for the first complete micro application release.
• Express — planned.
• Hybrid — planned.
• Enterprise extensions — planned.

Coretsia does not yet provide long-term backward compatibility guarantees, stable upgrade guarantees, or a mature third-party package ecosystem.

Coretsia framework packages are developed in the monorepo and published through dedicated split repositories.

Current public package repositories include:

• coretsia/core-contracts — public interfaces, ports, SPIs, and cross-package abstractions;
• coretsia/core-dto-attribute — canonical DTO marker attribute;
• coretsia/core-foundation — shared runtime primitives and Foundation services;
• coretsia/core-kernel — boot, module planning, configuration, artifacts, Unit-of-Work lifecycle, and runtime safety;
• coretsia/platform-worker — long-running worker runtime, supervision, task-source execution, and process lifecycle safety.

Framework packages follow one shared release train rather than independent package version streams.

The current evaluation path is the framework monorepo.

Requirements:

• PHP 8.4 or later;
• Composer 2.x.

git clone https://github.com/coretsia/monorepo.git
cd monorepo

composer setup
composer ci

composer setup prepares the managed development workspace.

composer ci runs the canonical verification pipeline, including tests, architecture rules, deterministic tooling checks, and publishing safety gates.

This is currently a framework-development and architecture-evaluation workflow, not an end-user application installation flow.

• Monorepo
• Website
• Roadmap
• SSoT index
• Repository structure
• Packaging strategy
• Branding
• GitHub Discussions

Coretsia is being built in the open.

At the current stage, technical review is especially useful around:

• architecture and package boundaries;
• consistency between SSoT, implementation, tests, and tooling;
• deterministic behavior;
• runtime lifecycle safety;
• package ownership;
• unclear documentation;
• unnecessary architectural complexity.

The project is not currently seeking production adoption claims or positioning as a replacement for established PHP frameworks.

Start here:

• Contribution guide
• Security policy
• Repository discussions
• Code of Conduct

Coretsia is open-source software licensed under the Apache License 2.0.
See NOTICE for attribution and notices.