maniator / maniator/verticopolis

[Parity]: [P3] Verify the 1994 maintenance dollar table and decide Classic's charge cadence (full per canon period vs the 1/10 rescale)

Open
#573 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

From the classic-economy-canon party and source sweep of 2026-07-22 (_bmad-output/planning-artifacts/design/spec-classic-economy-canon-cadence-2026-07-22.md §3.4 and §6, backlog row canon-maintenance-table).

The 1994 original charged maintenance in full amounts per quarter (the FAQ lineage lists per-quarter figures per facility). Verticopolis charges modern-tuned monthly values (ECON.maintenancePerCarMonthly, serviceMaintenanceMonthly) rescaled to 1/10 per canon 3-day period (income-invariant, arch-classic-calendar-parity §3). With office rent now collecting the full canon lump each canon quarter (spec above), Classic upkeep is the remaining economy line still on the invariant rescale.

Work: verify the canon maintenance dollar table against period sources (the FAQ maintenance chart, and the manual if it ever becomes readable), then decide whether Classic charges the full canon amounts each canon period through the same quarterlyRentScale-style seam, replacing the 1/10 rescale for Classic only. Modern keeps the rescale regardless.

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/planning-artifacts/design/spec-classic-economy-canon-cadence-2026-07-22.md, especially §§3.4 and 6 and the canon-maintenance-table backlog row. Verify the 1994 maintenance figures against the FAQ maintenance chart and the manual if readable, then inspect ECON.maintenancePerCarMonthly, serviceMaintenanceMonthly, and the quarterlyRentScale-style seam. Done means the canon table is verified, Classic’s cadence is decided and reflected, and Modern retains its rescale.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.