Define Eco Gnome / Eco Calc parity target for Eco App #173

Closed
opened 2026-07-29 05:57:30 +00:00 by coilyco-ops · 0 comments
Member

Outcome

Define the Eco Gnome / Eco Calc parity target for eco-app.coilysiren.me: the player jobs worth matching, the current capability gap, and the ordered product slices that justify implementation.

This is a successor to the self-hosting work in #40 and the practical-usefulness design in #98. It does not presume that Eco App should copy either product's UI or every feature.

Scope

  • Compare the player-facing workflows offered by Eco Gnome and Eco Calc with the current Sirens Eco App.
  • Separate parity candidates into: already covered, reusable upstream capability, Eco App-native opportunity, blocked by data, and deliberately out of scope.
  • Establish a prioritised parity matrix with evidence, including data provenance and ownership.
  • Recommend only bounded follow-up issues that improve a specific player outcome.

Acceptance

  • A source-backed parity matrix covers the material calculator workflows.
  • Each gap has a recommended disposition and an identified data/ownership dependency.
  • The parent records a proposed first slice, success evidence, and explicit non-goals.
  • Implementation work is created only after the matrix supports it.

Non-goals

  • No fork, redesign, or replacement of Eco Gnome is assumed.
  • No UI cloning, production deployment, mod rollout, or new data exporter is performed here.
  • This does not reopen completed #40 or #98 work.

Context

Research plan

Lane Issue Purpose Sequence
Incumbent capabilities #174 Evidence for Eco Gnome/Eco Calc workflows and reuse constraints. Starts now.
Eco App baseline #175 Verified current capability/data inventory. Starts now.
Sirens demand #176 Community evidence and prioritisation inputs. Starts now.
Parity decision This issue Reconcile evidence into a matrix and select the first justified slice. After #174–#176.

The lanes are independent. This parent must explicitly mark each candidate as adopt, integrate, build, defer, or reject before new implementation issues are created.

## Outcome Define the Eco Gnome / Eco Calc parity target for `eco-app.coilysiren.me`: the player jobs worth matching, the current capability gap, and the ordered product slices that justify implementation. This is a successor to the self-hosting work in #40 and the practical-usefulness design in #98. It does not presume that Eco App should copy either product's UI or every feature. ## Scope - Compare the player-facing workflows offered by Eco Gnome and Eco Calc with the current Sirens Eco App. - Separate parity candidates into: already covered, reusable upstream capability, Eco App-native opportunity, blocked by data, and deliberately out of scope. - Establish a prioritised parity matrix with evidence, including data provenance and ownership. - Recommend only bounded follow-up issues that improve a specific player outcome. ## Acceptance - A source-backed parity matrix covers the material calculator workflows. - Each gap has a recommended disposition and an identified data/ownership dependency. - The parent records a proposed first slice, success evidence, and explicit non-goals. - Implementation work is created only after the matrix supports it. ## Non-goals - No fork, redesign, or replacement of Eco Gnome is assumed. - No UI cloning, production deployment, mod rollout, or new data exporter is performed here. - This does not reopen completed #40 or #98 work. ## Context - #40 — self-hosted Eco Gnome - #98 — practical-usefulness design and prior completed implementation graph - #165 — historical price/bell-curve backlog - Discord: [eco-app.coilysiren.me feature inventory](https://discord.com/channels/1300204416229441587/1531686534997213275/1531686534997213275) ## Research plan | Lane | Issue | Purpose | Sequence | | --- | --- | --- | --- | | Incumbent capabilities | #174 | Evidence for Eco Gnome/Eco Calc workflows and reuse constraints. | Starts now. | | Eco App baseline | #175 | Verified current capability/data inventory. | Starts now. | | Sirens demand | #176 | Community evidence and prioritisation inputs. | Starts now. | | Parity decision | This issue | Reconcile evidence into a matrix and select the first justified slice. | After #174–#176. | The lanes are independent. This parent must explicitly mark each candidate as adopt, integrate, build, defer, or reject before new implementation issues are created.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-gaming/eco-app#173
No description provided.