Overlay relevant specialty unlocks on item price history #199

New issue

Closed

opened 2026-08-01 18:01:02 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-01 18:01:02 +00:00

Member

What to build

Help players interpret a selected item's price history by marking when the server first gained the specialties needed to produce that item. Join the existing recipe graph to the existing progression events, convert each relevant first-observed specialty gain to cycle day, and overlay those markers on the item market-history surface introduced by #198.

This first slice covers the current cycle. It establishes cycle-relative marker semantics without claiming that older cycles with different star or progression rules are directly comparable.

Acceptance criteria

For a selected item, resolve every specialty required by its known recipe variants from the existing recipe graph.
For each required specialty, derive the first observed server-wide gain from the existing progression action data and express it as cycle day.
The item market-history presentation overlays those specialty markers without obscuring price, volume, or distribution evidence.
Missing recipes, missing progression exports, no observed unlock, and multiple recipe variants produce explicit, non-misleading states.
Historical cycles with incompatible progression rules are excluded or version-labeled rather than silently averaged together.
The backend contract and frontend tests cover one complete join, multiple variants, and each degraded state.
docs/FEATURES.md documents the new interpretation layer and its current-cycle limit.

Blocked by

Blocked by #198.

Source

Public-safe synthesis of Sirens Discord community discussion during the week ending 2026-08-01. Players wanted price movements aligned with cycle day and the arrival of relevant production capabilities.

## What to build Help players interpret a selected item's price history by marking when the server first gained the specialties needed to produce that item. Join the existing recipe graph to the existing progression events, convert each relevant first-observed specialty gain to cycle day, and overlay those markers on the item market-history surface introduced by #198. This first slice covers the current cycle. It establishes cycle-relative marker semantics without claiming that older cycles with different star or progression rules are directly comparable. ## Acceptance criteria - [ ] For a selected item, resolve every specialty required by its known recipe variants from the existing recipe graph. - [ ] For each required specialty, derive the first observed server-wide gain from the existing progression action data and express it as cycle day. - [ ] The item market-history presentation overlays those specialty markers without obscuring price, volume, or distribution evidence. - [ ] Missing recipes, missing progression exports, no observed unlock, and multiple recipe variants produce explicit, non-misleading states. - [ ] Historical cycles with incompatible progression rules are excluded or version-labeled rather than silently averaged together. - [ ] The backend contract and frontend tests cover one complete join, multiple variants, and each degraded state. - [ ] docs/FEATURES.md documents the new interpretation layer and its current-cycle limit. ## Blocked by - Blocked by #198. ## Source Public-safe synthesis of Sirens Discord community discussion during the week ending 2026-08-01. Players wanted price movements aligned with cycle day and the arrival of relevant production capabilities.

coilyco-ops added the

priority

autonomy

headless

labels

2026-08-01 18:01:02 +00:00

~~coilyco-ops referenced this issue from coilyco-gaming/.github 2026-08-01 18:01:39 +00:00~~

Define the gaming-wide portfolio triage pattern #3

coilyco-ops referenced this issue from a commit

2026-08-01 19:25:15 +00:00

feat: add skill trees and price history closes #195 closes #197 closes #198 closes #199

coilyco-ops closed this issue