maniator / maniator/verticopolis

[Parity]: [P2] Verify the Classic rent ladders and full-per-quarter office cadence against a primary or genuinely independent source

Open
#575 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 owner's review on PR #574 (spec-classic-economy-canon-cadence-2026-07-22, backlog row classic-rent-primary-source-verification).

The Classic rent dollar ladders (office, condo, hotel nightly) and the full-lump-per-quarter office cadence currently rest on the Relentless Optimizer fan reference plus search-result snippets of the GameFAQs FAQ lineage (BStuart, furdude2, Aristotle47). The pages themselves could not be read in-session, and mirrors or descendants of one lineage are not independent corroboration, so every confidence note stays explicitly provisional.

Work: establish the values from a primary or genuinely independent source. Candidate paths: read the FAQ pages directly (not snippets) and establish their independence from the fan reference; OCR the archive.org manual if it becomes readable; or, definitively, read the office rent lumps and hotel nightly charges directly in the retail game via the Wine harness (the house method that settled stairs willingness and the calendar phase). On confirmation, upgrade the provenance notes in src/engine/pricing.ts and the pricing GDD; on contradiction, re-open the pricing GDD Decision 2 and the cadence spec's ruling.

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 src/engine/pricing.ts, the pricing GDD, and the cadence spec to identify the provisional rent and office-cadence notes. Verify the values from directly read FAQ pages, a readable archive.org manual, or the retail game through the Wine harness. Done means provenance is upgraded when confirmed, or the pricing GDD Decision 2 and cadence ruling are reopened when contradicted.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
game-dev
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.