STPAMM Platform — Modernisation Programme

Progress and timeline of the platform's restructuring. Updated by the engineering side after every verified step. Last updated: 2026-11-19 07:45 (Istanbul)

Where we are

2 of 5programmes complete or in progress (Programme 1 done, Programme 2 under way)
~45%overall estimated completion (weighted by planned effort)
Dailyautomated regression battery on the new code (the gate every change passes before it merges)
Stagingthe newest release verified on the staging environment on 2026-11-18
Overall: estimated 45% — Programme 1 (100%), Programme 2 (about 55%), Programmes 3–5 not started. Estimates, not commitments; they move as work is verified.

The programmes

#ProgrammeWhat it deliversStatusWindow
1Foundation and separationThe platform split into independently versioned components (trading engine, web panel, data contract, deployment kit, test harness) with an automated regression battery recorded against the production-equivalent reference, and every component published to the private code hosting.DONENov 1 – Nov 10, 2026 (accepted)
2API backend and security hardeningA dedicated API backend between the web panel and the trading engine; hardened engine management interface (encrypted, authenticated); execution safety against duplicate instances; ownership-based authorization of every client-facing operation; the panel's engine-facing operations moved behind the backend step by step.IN PROGRESS ~55%Nov 11 – late Nov 2026 (est.)
3Client portal / admin console splitTwo clean front-ends born from the current panel: the client portal and the administration console, each talking to the backend only.PLANNEDafter Programme 2 (≈ 1 week, est.)
4High availabilityFail-over between engine instances, clustered database, redundant backend — no single point of failure.PLANNEDafter Programme 3 (≈ 1–2 weeks + host provisioning, est.)
5Deployment topologies and production cut-overInstallable kits per hosting layout; the production migration plan executed on management's go.PLANNEDafter Programme 4 (≈ 1 week + the cut-over window, est.)

Programme 2 in detail

Work packageStatusNote
Baseline and characterization (every behaviour of the current system recorded as tests)DONEhundreds of recorded cases; the regression battery runs them daily
Engine hardening (encrypted and authenticated management interface, duplicate-instance safety, protected key material, metrics)DONEfield-verified on the test server and on staging
API backend born (typed boundary to the engine, health and metrics, sessions)DONEfirst vertical slices live behind the panel
Ownership-based authorization of client operations (accounts, subscriptions, offers)DONEdelivered and verified 2026-11-18; negative tests in place
Client money operations through the backendIN PROGRESSdeposits/withdrawals done; subscribe and lifecycle flows next
Administration area through the backend (staff, clients, providers, settings, audit)PLANNED
Notifications and e-mail through the backendIN PROGRESSthe notification feed served by the backend; e-mail outbox next
Panel emptied of direct engine/database accessPLANNEDthe closing step of the programme
Hosting kit and staging rehearsalsIN PROGRESSthe newest release rehearsed on staging 2026-11-18 (update, trade copy, clean restart) — passed

Timeline

Recent updates

What is left (high level)

Production is untouched by this programme until the cut-over decision; every change is verified by the automated battery and, where relevant, rehearsed on staging first. This page contains no technical or operational detail of the systems themselves.