Build a read-only, item-focused pricing breakdown #177

New issue

Closed

opened 2026-07-29 06:17:48 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-29 06:17:48 +00:00

Member

Context

The calculator-parity research established that Eco Calc's core player job is not opportunity discovery: it is explaining and setting a defensible price for one selected item. This is the first implementation slice following #173.

What to build

A player selects an item and receives one item-focused price explanation that combines the current recipe cost roll-up with observed market evidence. The page must answer:

What does the item cost to make, and which ingredient paths were bought versus crafted?
What has the item actually traded for, and how liquid or recent is that evidence?
What are current buy and sell offers, if available?
What makes the result trustworthy, incomplete, thin, or stale?

Use Eco App's existing read-only recipe, market, trades, logistics, and item data planes. Link to the existing recipe and trade detail where it adds evidence; do not create a parallel calculator configuration surface.

Acceptance criteria

One item route presents recipe cost, observed price evidence, and live offers in a single explainable view.
Each material value names its source and freshness or confidence state.
Incomplete recipe cost, unpriced inputs, no trades, thin liquidity, unavailable shelves, and upstream failure produce explicit degraded states, never an authoritative-looking price.
The page exposes its key calculation assumptions, including the baseline-recipe limitation and any labour/time rate.
Component and API tests cover a complete result and the degraded states.
docs/FEATURES.md describes the resulting player workflow and its limits.

State and safety boundary

Read game, recipe, market, trade, and store data only.
Do not create player accounts, server-side profiles, preference writes, or store-price writes.
Do not persist user input beyond optional browser-local presentation state.

Non-goals

Rebuilding Eco Calc's manually configured skills, upgrades, ingredient-price, and profit-profile workflow.
Claiming a universal or mandatory price.
Automated store repricing.

## Context The calculator-parity research established that Eco Calc's core player job is not opportunity discovery: it is explaining and setting a defensible price for one selected item. This is the first implementation slice following https://forgejo.coilysiren.me/coilyco-gaming/eco-app/issues/173. ## What to build A player selects an item and receives one item-focused price explanation that combines the current recipe cost roll-up with observed market evidence. The page must answer: - What does the item cost to make, and which ingredient paths were bought versus crafted? - What has the item actually traded for, and how liquid or recent is that evidence? - What are current buy and sell offers, if available? - What makes the result trustworthy, incomplete, thin, or stale? Use Eco App's existing read-only recipe, market, trades, logistics, and item data planes. Link to the existing recipe and trade detail where it adds evidence; do not create a parallel calculator configuration surface. ## Acceptance criteria - [ ] One item route presents recipe cost, observed price evidence, and live offers in a single explainable view. - [ ] Each material value names its source and freshness or confidence state. - [ ] Incomplete recipe cost, unpriced inputs, no trades, thin liquidity, unavailable shelves, and upstream failure produce explicit degraded states, never an authoritative-looking price. - [ ] The page exposes its key calculation assumptions, including the baseline-recipe limitation and any labour/time rate. - [ ] Component and API tests cover a complete result and the degraded states. - [ ] `docs/FEATURES.md` describes the resulting player workflow and its limits. ## State and safety boundary - Read game, recipe, market, trade, and store data only. - Do not create player accounts, server-side profiles, preference writes, or store-price writes. - Do not persist user input beyond optional browser-local presentation state. ## Non-goals - Rebuilding Eco Calc's manually configured skills, upgrades, ingredient-price, and profit-profile workflow. - Claiming a universal or mandatory price. - Automated store repricing.

coilyco-ops referenced this issue

2026-07-29 06:17:59 +00:00

Route production opportunities into the item-pricing explanation #178

coilyco-ops added the

autonomy

headless

priority

labels

2026-07-29 06:18:15 +00:00

coilyco-ops referenced this issue

2026-07-29 06:25:30 +00:00

Resolve a requested item into make, buy, and capable-crafter paths #180