Roadmap FEATURE-36 · In progress · Feature
Typed cargo and capacity-based hold
Confirmed updated direction: cargo cells measure physical capacity; six inventory slots hold and select identifiable objects/stacks. Bulk minerals occupy cells without consuming slots. Artifacts and future supplies/deployables consume one slot per object/stack plus their physical capacity cost. Exact future capacities and stack limits remain design decisions. The first live prototype uses Mike's 3D artifact model and alpha inventory icon, one four-cell relic and deliberate trade; six slots are now functional in the local branch, superseding the earlier placeholder-equipment interpretation. Item definitions, per-instance identity/quantity/charges/condition, slot ownership and action capabilities are separate. Selection alone never sells, consumes or activates. Future repair items, missiles, grenades, mines and buffs need their own authoritative behaviors and tests; metadata is not implementation. Acceptance: server-authoritative slot/capacity limits, stable identity through pickup/drop/transfer/sale, atomic invalid-manifest rejection, readable cockpit/chase icons and replay-safe actions. No across-sector cargo persistence assumed.
0 blitzers supported · Updated
Activity
Deferred from current slice: Moving
Typed cargo and capacity-based hold: In progress to In progress. [MCP] Owner-approved inventory refactor committed locally as 71b1013 on codex/discovery-recovery. Replaces special artifact storage with six slots, typed item instances, definition resources, quantity/charges/condition, action capabilities and world pickup adapter. Mike's artifact1.glb and alpha icon are wired. Keys 1–6 select; T acts; D-pad left/right selects and up acts. Docking/selection never sells slotted items; explicit server-validated Trade at the specialist uses existing retry-safe recovery. Source 20.150/protocol 20. Inventory, real client/server action/replay, wallet HTTP, bulk banking and rendered 720p/1080p checks pass. Four-peer latency regression passed on isolated rerun (one earlier concurrent run missed departure timing). No push/export/deployment. Future supplies, missiles, mines, buffs and multi-item world orchestration are not implemented. Editable resources and extension steps: design/inventory-foundation.md. Human acceptance remains pending.
Typed cargo and capacity-based hold: 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.
Typed cargo and capacity-based hold: 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.
Typed cargo and capacity-based hold: 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.