Game Pillars¶
Seven core principles that guide every design decision in Manifest Rail. When a design call is ambiguous, it gets resolved by which pillar it best honors. When a proposed mechanic conflicts with a pillar, that's a red flag worth addressing before committing.
→ Parent: GDD.md
1. The Player Is an Executive, Not an Engineer¶
The player commissions projects; staff executes them. The player decides what to build, when to commission it, how to fund it, and who to put on it — but never lays track tile by tile, never schedules individual trains beyond fleet allocation, never overrides a plan's line items.
Red flag: any mechanic that pulls the player into operational micromanagement (per-mile track placement, per-train scheduling, individual freight-car coupling).
Examples in the design: project commissioning with abstracted planning (ProjectManagement); the player commissions a feasibility study and the Surveyor plans the route — the player never lays the route themselves, and the surveyor's competence (not the player's hand) shapes its length and grade (Feasibility Studies); fleet allocation as the tactile layer rather than per-train scheduling (Procurement Fleet Capacity); maintenance as a regional lever rather than per-asset upkeep (Operations).
2. Reputation Always Matters¶
Every decision moves goodwill on multiple axes. Every relationship is tracked. Counterparty leverage and reputation substitute for each other but neither is fully ignorable — a reviled-but-dominant operator can still extract sweetheart deals on volume, but goodwill always moves the margins.
Red flag: any mechanic that bypasses reputation entirely, or any "always works" outcome regardless of the player's standing.
Examples in the design: contract acquisition is relationship-weighted, not rate-bidding (Contracts); hostile takeovers depend on regional reputation, not just direct ownership (Company Stock); procurement terms key off goodwill via the leverage model (Goodwill, Volume, and Procurement Terms); even labor sourcing carries reputation — importing outside workers over willing locals, or bringing them into a strong-union county, damages company standing (Goodwill Effects on Labor).
3. The World Is a Constellation of Named Entities¶
The player character, the companies the player leads or holds, owned subsidiaries, named individuals, suppliers, customers, AI competitors, and the named settlements that grow and decline along the network — each is a first-class entity with its own reputation, traits, and history. Cross-entity interactions (a tarnished company drags down its subsidiaries; a sterling executive lifts the company that hires them; a respected supplier extends preferred terms) are the texture of strategic play.
Red flag: any mechanic that treats the world as a single undifferentiated mass ("the market"), or that aggregates entities away into an opaque score.
Examples in the design: per-entity reputation tracks across player, company, subsidiaries, named staff (Reputation Tracks); named suppliers (Pullman, Baldwin, etc.) with their own reputations (Suppliers); construction subsidiaries with regional reputations independent of the parent (Subsidiary Independent Reputation).
4. Time and Information Have Texture¶
Daily simulation tick. Era-specific information lag (post → telegraph → telephone). Distant events arrive late, sometimes already past their decision deadlines. The simulation is not neutral about distance and time — the player's geographic position and the era's communication tech materially shape what they know and when.
Red flag: any mechanic that flattens time or distance, makes information instantly available, or removes the lag-decay of decision options.
Examples in the design: information lag through three eras (Three Communication Eras); event option decay as deadlines tick down (Time Pressure); rail infrastructure shortens information distance, creating a feedback loop with construction (Rail Speeds Migration / Information).
5. Management-Sim Depth, Not Train-Simulator Detail¶
Rich management mechanics — contracts, bonds, equity, procurement, populations, reputation, scenarios — presented through menus and data in the lineage of Out of the Park, Football Manager, and Motorsport Manager, but no per-train micromanagement. The game is not real-time: the player advances a day at a time or sims to a stopping point (no pause-and-resume clock — see UIArchitecture — Time Controls). Players who want a tactile layer get fleet allocation; players who want depth get the boardroom. The hand-drawn map is a view the player consults, not the surface they operate through.
Red flag: any drift toward train-simulator territory (route-by-route train scheduling, per-locomotive consist editing, real-time train control); any mechanic that makes the map the mandatory site of an action that belongs in a menu.
Examples in the design: per-route timetables driven by simulation, with the player allocating equipment to slots rather than dispatching trains (Per-Route Timetables); operational maintenance as an abstracted regional cost rather than a per-asset chore (Operations Concept); commodity flows driven by economic conditions, not by player-routed shipments (Per-Region, Per-Commodity Pricing).
6. The Player Sets Their Own Depth¶
The player decides how much to handle personally. Any operational layer — fleet allocation, maintenance, routine procurement, even the running of an entire owned company — can be delegated to hired staff, who act according to their own competence and priorities. A player can micromanage one railroad to the last contract while a second runs on its managers, or oversee a whole portfolio at arm's length. Depth is opt-in; the game never forces minutiae on a player who wants to operate at altitude, and never withholds it from one who wants to dig in.
Red flag: any system that forces the player to engage at a single fixed altitude — a mechanic that can't be delegated to staff, or one that can't be drilled into for a player who wants the detail. Also: delegation that's a black box (the player can't see why the staff made a call) — delegated outcomes must trace back to the staff's traits and competence.
Examples in the design: fleet allocation defaulting to auto-allocation with player override (Fleet Allocation); contract triage governed by player-set priority policies the simulation resolves automatically (The Hybrid Model); maintenance funding as a per-region lever (Operations); whole-company delegation through the named-staff system (Staff and Labor); the authority-and-engagement model that lets the player lead one company and delegate others (Multiple Companies).
7. The Railroad Shapes the World¶
The network is not laid over a static board — it builds and transforms the world. A stop planted in open country can grow a town around it; a station draws migration and the jobs that hold the people it attracts; a connected county's industry and population swell while a bypassed one withers. Cause runs both ways: the economy shapes where the player builds, and where the player builds reshapes the economy. The map at the end of a scenario is one the player made, not one they merely traversed. This is the "Manifest" in Manifest Rail — the railroad as the maker of places, markets, and movement.
Red flag: any mechanic that treats the map as a fixed board the player only connects — settlements that can't be created or grown, counties inert to rail access, a world that looks the same whether the player built a continental trunk line or nothing at all.
Examples in the design: stations creating settlements from open country and growing them by through-traffic + local jobs (Settlement Growth); migration weighted by station tier (Migration); rail access shortening information distance, a feedback loop with construction (Information & Communication); population growth feeding back into commodity demand, and a connected settlement generating its own freight demand that reinvests toward the next build (Connection-Driven Demand).
When in doubt, choose the option that best honors the pillars.