Strategy Command Centre
Strategy pages convert verified mechanics and the completed service guides into practical planning models. Recommendations state their assumptions and are never presented as immutable game rules.
Completed programmes
Section titled “Completed programmes”Stage 38 — Cross-Service Account Progression
Section titled “Stage 38 — Cross-Service Account Progression”- Cross-Service Account Progression — expansion gates, readiness states, service sequencing, cross-service dependencies, major-incident resilience and account archetypes;
- Station Placement and Coverage — route, destination, access, response-cluster, specialist-hub and relief-base planning.
Stage 39 — Alliance Operations
Section titled “Stage 39 — Alliance Operations”- Alliance Operations — member, dispatcher and administrator modes; onboarding; roles; contributions; mutual support; major incidents; events; moderation; reporting and external-tool boundaries.
Stage 40 — Account Readiness Planning Suite
Section titled “Stage 40 — Account Readiness Planning Suite”- Account Readiness Planner — local-only mission scenarios, protected reserve, capacity-aware alternative allocation, personnel thresholds, towing/carrier checks and reversible browser storage.
Stage 41 — Guide UX, Accessibility and Navigation
Section titled “Stage 41 — Guide UX, Accessibility and Navigation”- mature Getting Started and Game Systems guides replace the remaining framework pages;
- long pages expose accessible, collapsed section navigation;
- tables and code blocks scroll within the content column on narrow screens;
- keyboard focus remains visible across links, controls and disclosure summaries;
- the complete programme route set is covered by desktop, iPhone and iPad viewport acceptance;
- critical WCAG A/AA checks cover the primary command, service, strategy, alliance and tool surfaces.
Operating sequence
Section titled “Operating sequence”- Verify current mission pressure in Mission Lookup.
- Build representative concurrent incidents in the Account Readiness Planner.
- Enter only correctly staffed and deployable inventory, then protect routine and specialist reserve.
- Identify the narrowest exact gap or unresolved evidence field.
- Review the relevant service guide.
- Compare candidate resources using Resource Comparison.
- Use Station Placement for route, access and destination constraints.
- Activate one controlled expansion.
- Observe the changed mission mix and recover to Ready before repeating.
- Use alliance support as documented contingency rather than an unbounded substitute for local capability.
Strategy pillars
Section titled “Strategy pillars”| Pillar | Planning question |
|---|---|
| Readiness | Can the current network handle its representative incidents with reserve? |
| Evidence | Is the proposed capability backed by current canonical mission pressure? |
| Geography | Will the resource reach its intended incidents, access points and destinations? |
| Personnel | Are the required qualifications and roles concurrently available? |
| Cross-service integration | Are every hard partner service and handoff ready? |
| Throughput | Can patients, prisoners, recovery assets and returning vehicles complete the full cycle? |
| Resilience | Can another incident occur without regional collapse? |
| Alliance contingency | Can support be requested without emptying donor networks or hiding local gaps? |
| Recovery | Does the network return to useful positions before more generation activates? |
Account models
Section titled “Account models”Foundation
Section titled “Foundation”- routine Fire, Police and Ambulance response;
- useful local reserve;
- practical station geography;
- first specialists commissioned only against measured demand.
Developing
Section titled “Developing”- independently functional response clusters;
- trained specialist and replacement cohorts;
- patient, custody and recovery throughput measured;
- command and support no longer single points of failure.
Regional
Section titled “Regional”- service specialisation aligned with cross-service dependencies;
- relief bases and strategic reserve;
- urban, rural, coastal, airport and railway geography treated explicitly;
- several representative incidents tested together.
Mature
Section titled “Mature”- independently dispatchable regions;
- major-incident and recovery doctrine;
- alliance support used as contingency;
- new game content enters through the evidence workflow rather than assumptions.
Strategy boundaries
Section titled “Strategy boundaries”The strategy programme does not:
- invent universal unlock thresholds;
- turn missing costs or capacities into zero;
- assume every account should buy services in one fixed order;
- merge guaranteed, alternative, conditional or probabilistic requirements;
- convert patient, prisoner or recovery ranges into fictional resource rows;
- treat alliance support as guaranteed local capacity;
- present community administration policies as game-enforced mechanics;
- optimise only for visual map symmetry;
- scrape or mutate a MissionChief account.
Next programme
Section titled “Next programme”The next programme is Stage 42 — Versioned Guide Release and Completion Report, reconciling the completed Stage 37–41 operational estate into the compatible v1.4.0 production release.