Roadmap FEATURE-39 · In progress · Feature
Account career record and notable hauls
Confirmed account career ledger and minimum rank display implemented locally September 26. The transaction-bound ledger preserves exact gem composition, confirmed credits, event-time sponsor, discovery identity, revisions and versioned rank awards; retries cannot double-award and unknown historical composition is not invented. Local backend 44/44 tests, real HTTP lost-response/reconnect/other-sponsor coverage, and display lifecycle checks passed. See docs/plans/career-ledger-implementation.md. Full live acceptance and release/wallet environment isolation remain open. Remaining: durable haul IDs, deposit membership/finalization and late-receipt recovery (TASK-8), notable outcomes and career review/public read API. September 27 recognition/leaderboard additions remain proposals in docs/plans/career-recognition-and-leaderboards.md. Hauls, not flights, are counted: a docking visit with bulk cargo starts at berth capture and ends when empty, or on earlier undock/death/disconnect. Wallet backpressure does not end it; empty docking is not a haul; artifact trade is a separate recovery. Value is confirmed deposits within the visit, size is units unloaded. No historical haul reconstruction from aggregate amounts.
0 blitzers supported · Updated
Activity
Account career record and notable hauls: title updated, summary updated. [MCP] Mike requested Flight Operations reconciliation on 2026-09-30. Updated against dated repository implementation/verification evidence; retained unverified acceptance and proposal boundaries. No publication, priority, slice or release change.
Account career record and notable flights: In progress to In progress. [MCP] Record Mike's 2026-09-17 haul boundary decision from docs/plans/steam-stats-achievements.md; finalization mechanics remain TASK-8.
Account career record and notable flights: In progress to In progress. [MCP] Owner-requested verification and enrichment of the Steam stats/achievements proposal. Source-audited local game/Coldboot code and official Steam documentation; linked detailed gap tasks with acceptance criteria. Preserve publication and workflow status. No implementation, deployment, Steamworks mutation or live acceptance.
Account career record and notable flights: In progress to In progress. [MCP] Discovery sprint continuation committed locally on codex/discovery-recovery: game d59282e; Coldboot c3102b3 (after foundation 41d9ab7/d560a21). First playable experiment now connects west-field clues, one four-cell Rift Relic, death/drop/reclaim, 900 m carrier signature, North Exchange exclusive recovery, account credits/discovery/recovery count and same-allocation recovery journal. Ordinary bulk banking remains intact. Checks: 37 backend tests; lost-response HTTP retry and rejoin under another syndicate; local journal restart; four peers at 150 ms added RTT and 2% loss; 720p/1080p cockpit/chase renders. Source 19.149/protocol 19; no push, export, live migration or deployment. Broader catalog/selectable goals/career-haul work and human acceptance remain; not shipped. Managed-container disk retention/destruction behavior remains a release review gate. Human test procedure is tests/discovery-recovery-playtest.md in the game repository.
Account career record and notable flights: Next up to In progress. [MCP] Owner started discovery/recovery sprint on codex/discovery-recovery in game and Coldboot repositories. First foundation commits: game 41d9ab7 (typed cargo definitions/hold, multi-cell capacity, exclusive buyer filtering, no silent replacement, atomic snapshot rejection); backend d560a21 (authenticated transactional artifact credits, discovery and career receipts). Local cargo checks and all 37 backend tests pass. Not yet connected to live ship cargo, specialist buyer, hunt, HUD or persistent escrow/recovery transport. No live schema migration, build, push or deployment. Sprint requirements: tasks/prd-discovery-recovery.md. Do not mark complete or testing.
Account career record and notable flights: Awaiting review to Next up. [MCP] Owner requested recording and backlog refinement of the cargo/discovery discussion. Confirmed work is queued after current slice; optional designs remain under consideration for feedback. Dependencies and unresolved choices are explicit; no implementation or acceptance claimed.