17. 5) P – Population Viability
P · Population Viability = “Do we reliably staff critical posts 24/7 with trained backups and healthy pipelines?” (coverage & time-to-competence) - note: this definition changed overtime, with the approach shown here being the one taken initially.
Population Viability is coverage, not charisma. Posts that are staffed every hour; a training pipeline that keeps tomorrow from eating today; dependency ratios that let families happen without collapsing shifts; droid multipliers counted honestly with their maintenance and QA tax. What moves it is rostering discipline and cross-training matrices that a stranger can read. Proof is 24/7 posts stable through flu weeks, apprenticeships at 10–20% of the technical workforce, and return-to-work medians that hug policy. Failure looks like heroic emails, then silence.
Quick Heuristic: P vs C (Social Cohesion) can be confused. Best analogy: Shift schedule vs team spirit. P keeps posts covered. C keeps people willing and cooperative. Test: Did a metric move because you trained/rostered (P) or because trust/compliance rose (C)?
Cross-pillar ties to P: G succession and lawful continuity require P’s two-deep reality. B surge staffing lives here; S cannot buffer understaffing. R needs second crews who can commission base-kit lines; M needs maintenance techs; E black-start rosters come from P; C reduces churn and incident rates.
Lessons Learnt: Staff posts, not headcount—and design for two-deep coverage. Survival is a roster, not a census. We deleted phantom posts, defined always-on positions, set the 4.5 FTE/post standard (24/7 + leave/training), and tracked time-to-competence like a production KPI. Backups are built with teach-backs, apprenticeships, and childcare; droid multipliers are counted net of maintenance/QA tax.
Misjudged Initially:
Confused headcount with coverage; heroics hid brittle roles.
Underestimated time-to-competence; training seen as a cost center, not a survival line.
Ignored dependency ratios; families and fatigue broke schedules.
Treated biobank as optional; effective population size (including donors) mattered.
Overlooked mental-health access; burnout created silent failure modes.
Qs to Ask:
Which three roles are most brittle, and what’s their coverage ratio today?
How many weeks to bring a novice to safe solo? What fraction of technical FTEs are apprentices (target 10–20%)?
What’s your effective population size (live + bank), and how resilient is storage?
Port Harmonia, Mars (Year 94 Mars Human Era)
Here is an example of Port Harmonia’s Population Viability MIS in the early third century HE:
P=0.30(0.84)+0.20(0.75)+0.15(0.90)+0.15(0.90)+0.15(0.81)+0.05(0.70)≈0.83
Calculations:
Pcov average coverage 0.88, backups 0.70 ⇒ 0.8⋅0.88+0.2⋅0.70 = 0.84
Ppipe two-deep 0.75, throughput 0.60, refresh 0.90 ⇒ 0.4⋅0.75+0.3⋅0.60+0.3⋅0.90 = 0.75
Pdemo fwork = 0.60 ⇒ 0.9; D=0.38 ⇒ 0.9 ⇒ 0.6⋅0.9+0.4⋅0.9 = 0.9.
Prep Nm=900, Nf=1100⇒Nlive^e ≈ 1980; bank D = 300 ⇒ Nbank^e = 150; Neff^e = 2130 ⇒1.0, bank resilience 0.9 ⇒ 0.9.
Phealth ServiceBreadth 0.85, Quality 0.75, Uptime 0.80 ⇒ 0.5⋅0.85+0.25⋅0.75+0.25⋅0.80=0.81
Pfatigue 0.70.
Combine (weights sum to 1)
Suggested starting weights (disclose if tuned). Coverage is king; pipeline keeps it from decaying; demography & reproduction make it multi-decade; healthcare sustains workers; fatigue is an early-warning.
Interpretation:
P < 0.40 — Thin staffing, brittle roles, weak pipeline; high burnout risk.
0.40–0.70 — Adequate coverage with improving pipeline; demography workable; baseline care present.
> 0.70 — Two-deep robustness; healthy age pyramid; strong care; durable retention.