Sprint 03
Table of Contents
This page documents a sprint (Sprint 03) of ORE Studio v0. It captures the sprint's mission, current status, and the stories that compose it. For the surrounding context — version goals, sprint order, and product identity — see Version 0.
Mission
Wire the new socket code (from sprint 02's cobalt/comms work) into the Qt UI, and finish the login / account / session surface that the client/server architecture requires.
(Synthesised from the v0 mission: update UI layer to use new socket code + finish login related functionality.)
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent version | Version 0 |
| Previous | Sprint 02 |
| Start | 2025-10-23 |
| End (expected) | 2025-11-07 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Sprint 04 |
| Release Notes | Release notes |
| Last touched | 2025-12-31 |
Achievements
- UI uses the new socket layer end-to-end.
- Accounts and sessions ship as part of v0.
Stories
For the definitions of the themes see Themes.
Infrastructure
| Story | State | Start | End | Description |
|---|---|---|---|---|
| Build stabilisation 3 | DONE | 2025-11-15 | Windows clang-cl, dynamic libraries, vcpkg patches on Windows, Postgres on CI. | |
| Test infrastructure | DONE | 2025-12-01 | separate test DB, split test code, ctest suite-level tests, test data generators. | |
| Postgres-backed currency persistence | DONE | 2025-11-25 | currency repository write path, service command-line DB args. | |
| Logging and observability | DONE | 2025-12-30 | proper Boost.Log usage, Valgrind/leak investigations, code-coverage uplift. |
Product
| Story | State | Start | End | Description |
|---|---|---|---|---|
| Client console and Qt integration | DONE | 2025-12-15 | merge client into console, enable Qt GUI on the new socket layer, locking, Prodigy tags. | |
| Login and sessions | DONE | 2025-12-20 | account and session domain types end-to-end. |
Agile
| Story | State | Start | End | Description |
|---|---|---|---|---|
| Sprint 03 housekeeping | DONE | 2025-12-31 | sprint sundries, backlog refinement, postponed work tracking. |
Charts
Charts generated via sprint_charts cmake target.
PRs & Commits per Day
Dual-axis bar chart. PRs (left axis) and commits (right axis) per day. A high commits-to-PR ratio may indicate scope creep.
Daily Line Churn
Lines added (green) and deleted (red) per day. Building work produces mostly additions; refactoring produces a mix. Days with no churn may indicate blockers.
Cumulative Stories Done
Line chart tracking stories marked DONE during the sprint. Steady upward slope is healthy; plateauing signals a stall.
Retrospective
Filled in retrospect, from the v0 record:
- What worked
- the architecture from sprint 02 absorbed the UI-side wiring cleanly. The risk module's messaging pattern propagated to accounts and sessions without friction.
- What did not
- Windows-specific regressions ate non-trivial time
again. CTest's single-test-per-suite quirk (and OpenSSL leaks under
Valgrind) ended the sprint
BLOCKEDrather than fixed; they carry over to a later sprint. - Carry forward to v2
- blocked items become explicit successors rather than disappearing into retro bullets.