E7A / 04.07
Back to archive

07 / Record

Flagship

2025—present

KS54 Platform — unified college digital platform

Practice

Frontend / platform engineering / architecture / technical leadership

The current culmination of the KS54 digital line: a unified internal platform for educational, administrative, document and integration workflows. The repository started in December 2025 as DocFlow and grew far beyond document management; in September 2026 the overall product became KS54 Platform, with DocFlow retained as one domain inside the system.

Context

DocFlow began as an applied document-workflow layer, then rapidly absorbed educational, administrative and service processes across the college. The task shifted from extending one module to creating a shared platform with explicit domain boundaries.

Solution

The product was divided into independent domains over a common platform layer. The frontend gained shared layout and registry contracts; the backend gained modular routing, RBAC, audit and workers; data and files received dedicated managed boundaries. Architecture decisions are recorded in ADRs and enforced through CI contracts.

Constraints

  • Multiple domains with different life cycles, workflows and roles
  • New modules coexisting with Legacy AIS and external integrations
  • Files, PDFs, background jobs and queues requiring a coherent platform layer
  • Migrations and releases preserving the verifiable history of a live system

What changed

  • DocFlow remains a domain while the overall system is now KS54 Platform
  • Documents, education, contingent, support and electronic queue evolve in one architecture
  • Shared UI contracts reduce divergence across registries and workspaces
  • New migrations are separated from frozen, verifiable legacy history

Case map

Domain platform map

01

Interfaces

  • Workspaces
  • Registries
  • Detail views
  • Public flows
02

Domains

  • DocFlow
  • Education
  • Contingent
  • Support + EQueue
03

Platform core

  • RBAC + audit
  • Workers
  • FileCore
  • API contracts
04

Infrastructure

  • PostgreSQL
  • S3
  • Integrations
  • CI + migrations
An anonymized view of the current layers. It explains the architectural principle without exposing interfaces or internal data.

Scope of work

  1. 01

    Direct development of the Nuxt 4 / Vue 3 frontend: workspaces, registries, detail screens, shared layout and UI contracts

  2. 02

    Document workflows, certificates, order excerpts, tasks and related document processes

  3. 03

    Contingent, attendance, academic journal, education and upbringing workflows

  4. 04

    Admissions, electronic queue, call/voice, support, publications and public interfaces

  5. 05

    PHP 8.3+ backend/API with domain modules, RBAC, audit, workers and background processing

  6. 06

    PostgreSQL/PgBouncer, Phinx migrations and preserved verifiable legacy migration history

  7. 07

    FileCore and Selectel S3, generated files/PDFs, uploads and document artifacts

  8. 08

    MOS, Legacy AIS, VK, MAX, Telegram, mail and other external integrations

  9. 09

    Architecture rules, ADRs, onboarding, testing/CI contracts and operational documentation

Technology chronology

Origin / DocFlow

09.12.2025 → 2026

The platform has been evolving since December 2025: first as DocFlow, then through rapid expansion of the Nuxt frontend and application domains including contingent, support, profession certificates and other modules.

Frontend

Nuxt 4.5 / Vue 3.5 / Pinia 3 / TypeScript 5.9

The current frontend runs on Nuxt 4 and Vue 3 with Pinia, Vue Router, Tabler/Iconify and project-specific UI contracts. The repository codifies shared registry/layout standards, PWA/mobile checks and numerous frontend contract tests.

Backend & platform

PHP 8.3+ / PostgreSQL / PgBouncer / Phinx 0.16

The backend uses a custom Router / RouteRegister and domain modules, PostgreSQL, queues/workers and an increasingly explicit platform layer. New schema changes use Phinx while the legacy SQL history is frozen and verified before the production migration pipeline.

Domain platform

DocFlow + Education + Contingent + Support + EQueue + FileCore + integrations

The platform combines independent domains for documents, education and academic journal, contingent and attendance, tasks, electronic queue, files, support, admissions, publications, certificates and external integrations. DocFlow no longer names the whole system.

Product identity

DocFlow → KS54 Platform / 12.09.2026

ADR-0002 dated September 12, 2026 records the product rename to KS54 Platform because the system had grown beyond document management. DocFlow remains a dedicated domain and legacy technical identifier.

Versions and dates reflect states confirmed by archives, Git history or releases and do not imply that every component was used in every deployment.

Contact
Copied