The full 936-point backlog built in four 2-week phases using AI-assisted development (Claude Code / Codex) over the existing prototypes. AI compresses the build and test clocks; it does not compress the Bank of Lithuania authorisation. So the platform finishes build-ready in ~8 weeks and waits, proven, for the authorisation grant (Nov 2026–Feb 2027) — which becomes the only gate to go-live.
The headline of this plan: AI speed moves the build off the critical path. Once the build finishes early, the only thing standing between Opalus and live euros is the regulator.
⚙️ Build & test clock — AI-accelerated
~8 weeks
936 pts of code + tests + hardening. Prototypes already exist, design system exists, AI does scaffolding / CRUD / UI / test generation. Senior team reviews-and-integrates. Finishes ~Aug 2026.
🏛️ Authorisation clock — fixed by law
Nov 2026 – Feb 2027
BoL completeness check ≤25 working days (Art 12(4)) + 3-month decision (Art 12(8)). No live investor funds before the grant — regardless of build speed. This is the GA gate.
Build timeline — 8 weeks
Four phases, each folding the original release(s) it replaces so all exit criteria carry over. Phase 1 is front-loaded (foundations + identity, where AI leverage is highest); Phase 2 is lighter to absorb spillover. Milestones (diamonds) show when vendor/hire decisions must land — now in weeks 1–6, not months.
Drawn to a months scale to show the real relationship — the build (hatched navy) finishes long before the decision lands. The platform sits in a launch-ready hold (hatched gold) until the grant.
Test Paris project taken E2E by sophisticated + non-sophisticated investors
GDPR pack + pen test + WCAG 2.1 AA + DR/load targets evidenced
Go-Live gates
External — not closable by code. These gate GA.
Gate GA — regulator/business controlled
ECSP authorisation issued & active — Bank of Lithuania M8 · Nov–Feb
Compliance Officer (& AML Officer) appointed — regulatory prerequisite M5
PSP arrangement executed & aligned with authorisation terms M1/M6
Art 18 passporting notification filed (France) M9
Hard safeguard: live-money mode cannot be enabled in config until a Super Admin sets the authorisation flag. Build-Ready ≠ permission to take funds — taking a euro before M8 is a regulatory breach.
External milestones — now the binding constraint
With the build compressed to 8 weeks, vendor and hiring decisions must be fast-tracked into weeks 1–6 to keep pace. Code is no longer the bottleneck — sandbox access and the Compliance Officer are.
Top compression risk: vendor sandboxes (M1/M2) not ready in Week 1 stalls the integration stories — this is now the #1 schedule risk, ahead of any code estimate. Mitigation: build the provider-agnostic adapter against a mocked surface from day one, and escalate M1/M2 at kickoff. Secondary: senior review is mandatory on every money / audit / dual-control path — AI velocity must not bypass the controls that make this a regulated platform.
