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
The programmes
| # | Programme | What it delivers | Status | Window |
|---|---|---|---|---|
| 1 | Foundation and separation | The 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. | DONE | Nov 1 – Nov 10, 2026 (accepted) |
| 2 | API backend and security hardening | A 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.) |
| 3 | Client portal / admin console split | Two clean front-ends born from the current panel: the client portal and the administration console, each talking to the backend only. | PLANNED | after Programme 2 (≈ 1 week, est.) |
| 4 | High availability | Fail-over between engine instances, clustered database, redundant backend — no single point of failure. | PLANNED | after Programme 3 (≈ 1–2 weeks + host provisioning, est.) |
| 5 | Deployment topologies and production cut-over | Installable kits per hosting layout; the production migration plan executed on management's go. | PLANNED | after Programme 4 (≈ 1 week + the cut-over window, est.) |
Programme 2 in detail
| Work package | Status | Note |
|---|---|---|
| Baseline and characterization (every behaviour of the current system recorded as tests) | DONE | hundreds of recorded cases; the regression battery runs them daily |
| Engine hardening (encrypted and authenticated management interface, duplicate-instance safety, protected key material, metrics) | DONE | field-verified on the test server and on staging |
| API backend born (typed boundary to the engine, health and metrics, sessions) | DONE | first vertical slices live behind the panel |
| Ownership-based authorization of client operations (accounts, subscriptions, offers) | DONE | delivered and verified 2026-11-18; negative tests in place |
| Client money operations through the backend | IN PROGRESS | deposits/withdrawals done; subscribe and lifecycle flows next |
| Administration area through the backend (staff, clients, providers, settings, audit) | PLANNED | |
| Notifications and e-mail through the backend | IN PROGRESS | the notification feed served by the backend; e-mail outbox next |
| Panel emptied of direct engine/database access | PLANNED | the closing step of the programme |
| Hosting kit and staging rehearsals | IN PROGRESS | the newest release rehearsed on staging 2026-11-18 (update, trade copy, clean restart) — passed |
Timeline
- Reference frozen; the test harness built and recorded against it.
- Components carved out with history; first full regression batteries; Programme 1 accepted.
- Engine hardening: duplicate-instance safety and the protected management interface, field-verified; first staging rehearsal.
- Security completion cycle: authenticated management interface everywhere; the API backend born; reliability fixes to engine shutdown and synchronisation, proven in the field.
- Client-facing authorization delivered; client money operations through the backend; the newest release verified on staging; engine reliability line merged.
- Reference baseline refresh: the overnight run completed with every engine family green; three defects of the test harness itself that it exposed were traced and fixed the same morning, and the refresh was re-run.
- Subscribe and lifecycle flows through the backend; the backend's own battery and first staging install; then the administration area.
- Programme 3 (portal / admin split) → Programme 4 (high availability) → Programme 5 (deployment and production cut-over, on management's go).
Recent updates
- 2026-11-19 (morning) — The scheduled refresh of the reference baseline ran overnight on the frozen reference release: every engine test family green, including the full-scale scenarios. Three suites read red; each was traced to the test harness rather than to the product — a comparison rule applied to one side only, a test stand-in asking the reference panel for a certificate it never carries, and a baseline older than one of the newer test suites. All three were fixed and verified in isolation the same morning; nothing was re-recorded or relaxed. The refresh was re-run as the morning's second attempt and is in progress.
- 2026-11-18 (evening) — The engine reliability line (clean shutdown and synchronisation fixes) merged after a ten-family field proof. The audit trail of provider-initiated operations on managed accounts now names the provider as the actor: a data-contract revision carried through all four components and proven green across eight field test families (32 scenarios, none failed) and merged into the engine's main line. Tomorrow's scheduled run refreshes the reference baseline.
- 2026-11-18 — Nightly regression battery on the current engine: 37 of 38 suites green (the one red was a bookkeeping omission, corrected the same morning). The client-facing authorization slice delivered with negative tests. Deposits and withdrawals of the managed accounts now go through the API backend with the acting user taken from the verified session. The newest release rehearsed on staging end to end (backup, update, a live trade copy, a clean restart) — passed. An engine reliability line (cleaner shutdown, no duplicate synchronisation work) proven across ten test families and merged. Seven test-harness weaknesses found and fixed.
- 2026-11-17 — The management interface of the engine now requires client certificates everywhere; the API backend born with a typed boundary to the engine; two full batteries run.
- 2026-11-16 — Security completion cycle: the engine's key material protected on disk; the ownership mechanism proven in the field; the regression battery extended.
- 2026-11-12 → 13 — First staging rehearsal of a carved release: update, roll-back, fail-over and outage scenarios exercised on the staging host.
- 2026-11-10 — Programme 1 accepted: all components separated, published and covered by the regression battery.
What is left (high level)
- Programme 2: the remaining engine-facing flows through the backend (subscribe, lifecycle, administration), the e-mail outbox, the panel emptied of direct access, the backend's first staging install.
- Programme 3: the client portal and the administration console as separate applications.
- Programme 4: high availability (engine fail-over, clustered database, redundant backend).
- Programme 5: deployment kits per hosting layout and the production cut-over plan — executed only on management's explicit go.
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.