maniator / maniator/verticopolis

[Feature]: [P2] 1994-style commercial venue inspector detail

Open
#313 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
5
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Imported from the engineering backlog (_bmad-output/implementation-artifacts/backlog.md, story commercial-venue-inspector).
Priority P2 (do-first order) | Severity: med | Status: idea | Epic: SimTower parity | Type: feature-request | Recorded: 2026-07-08

Problem / motivation

Owner observation 2026-07-08 (real game restaurant/cafe inspector). The 1994 inspector for a commercial venue shows data we don't track or surface: a named SUBTYPE ("Chinese Cafe" -- overlaps retail-subtypes), Today's Patronage (a per-venue daily customer count with a colored bar: yellow = average, red = very few), Yesterday's Profit (per-venue $), and REASONING text ("Business is average" / "Very few customers", plus a WEATHER modifier line "Rain might cause fewer customers"). Implies a per-venue model we may lack: daily patronage tracking, per-venue profit history, a business-level tier, and weather affecting commercial traffic (we have WeatherKind; confirm it modulates shop/restaurant/fast-food revenue+patronage). This patronage IS the commercial "population" the finance window counts (see population-census-parity: fast food pop 175). Build a commercial inspector panel + the underlying per-venue patronage/profit/weather model. Complements per-room-eval-parity (same "explain why" reasoning pattern) and finance-1010.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with _bmad-output/implementation-artifacts/backlog.md and the commercial-venue-inspector story, then read the existing WeatherKind and related retail-subtypes and parity issues named in the report. Done means a commercial venue inspector exposes its subtype, today's patronage, yesterday's profit, and reasoning including any weather modifier, backed by the required per-venue behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.