Jobs view: show which jobs are not covered by active and long-term players #312

New issue

Open

opened 2026-08-20 05:00:20 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-20 05:00:20 +00:00

Member

Filed from the Sirens Discord #suggestions-feedback-bugs forum.

Source // https://discord.com/channels/1300204416229441587/1531689282606207178
Raised by // Kai, 2026-07-28
Forum tags // mods (webapp)
Signal // 1 reply

What was asked

Add a section to https://eco-app.coilysiren.me/jobs that surfaces coverage gaps: which jobs nobody currently active or long-term is filling.

This is the same resilience concern that drives the star-gain argument, made visible. A missing smelter is worse than a missing material, and right now nobody can see the gap until progress stalls.

Constraint Kai attached

restrict to only jobs that have been unlocked

via however you get that info?

So the view should not report an unstaffed job that no one could take yet, since that is noise rather than a gap. The trailing question mark is Kai's, and it is the open part: the unlock state may not be directly available from the current data path.

What needs establishing before building

Where unlocked-job state comes from, if anywhere. This is the acknowledged unknown.
How "active" and "long-term" get defined as queryable predicates. The server reports total versus active player counts, but long-term is a retention judgment that likely needs its own definition.
Whether a job with exactly one holder should read as covered or as at-risk. The resilience framing suggests single-holder coverage is the interesting signal, not zero-holder coverage.

The broader feature inventory for this site is tracked separately, filed from https://discord.com/channels/1300204416229441587/1531686534997213275

Filed from the Sirens Discord `#suggestions-feedback-bugs` forum. **Source** // https://discord.com/channels/1300204416229441587/1531689282606207178 **Raised by** // Kai, 2026-07-28 **Forum tags** // mods (webapp) **Signal** // 1 reply ## What was asked Add a section to https://eco-app.coilysiren.me/jobs that surfaces coverage gaps: which jobs nobody currently active or long-term is filling. This is the same resilience concern that drives the star-gain argument, made visible. A missing smelter is worse than a missing material, and right now nobody can see the gap until progress stalls. ## Constraint Kai attached > restrict to only jobs that have been unlocked > > via however you get that info? So the view should not report an unstaffed job that no one could take yet, since that is noise rather than a gap. The trailing question mark is Kai's, and it is the open part: the unlock state may not be directly available from the current data path. ## What needs establishing before building 1. Where unlocked-job state comes from, if anywhere. This is the acknowledged unknown. 2. How "active" and "long-term" get defined as queryable predicates. The server reports total versus active player counts, but long-term is a retention judgment that likely needs its own definition. 3. Whether a job with exactly one holder should read as covered or as at-risk. The resilience framing suggests single-holder coverage is the interesting signal, not zero-holder coverage. ## Related The broader feature inventory for this site is tracked separately, filed from https://discord.com/channels/1300204416229441587/1531686534997213275

coilyco-ops added the

labels

2026-08-20 05:00:20 +00:00