Constraint Satisfaction Blueprint

The Sentinel Papers

A Constraint Satisfaction Blueprint for the LGM-35A Sentinel ICBM Program

Seven analytical spokes specifying what must be encoded, measured, built, funded, tested, and certified for the Sentinel program to succeed — and what happens to the nuclear deterrent if it doesn't. Each spoke is an independent technical architecture. Together they form a closed feasibility envelope with 63 testable acceptance criteria.

UNCLASSIFIED March 2026 7 Spokes · 63 Acceptance Criteria All claims source-verified Zenodo DOI

The Blueprint

The Sentinel program's January 2024 critical Nunn-McCurdy breach — 81% PAUC growth to $140.9 billion — exposed constraints the 2020 baseline failed to encode. The February 2026 restructure (450 new modular silos, early-2030s IOC) addresses the construction strategy. It does not address the coupled constraints across workforce, supply chain, propellant chemistry, guidance depletion, NC3 synchronization, and security certification that together determine whether the program — and the Minuteman III force it depends on during transition — remains viable.

This blueprint identifies six actions that must occur within specific windows for all constraints to be simultaneously satisfiable. These are not recommendations. They are the boundary conditions of a mathematical existence proof — the Threaded Continuity Regime — derived from the coupled constraint analysis across all seven spokes.

1. PRP-2 by ~2028

Second Propulsion Replacement Program. Hybrid repour/new-case approach for Minuteman III solid rocket motors aging past viability thresholds. Estimated $8–12B. The Air Force's own 2050 feasibility assessment identifies this as necessary.

● Currently unfunded. No program of record.

2. NS50 Recapitalization

Guidance system recapitalization or equivalent sustainment initiated by the late 2020s. NS-50 spares trending toward zero. Test launch frequency already reduced to conserve inventory.

● Currently unfunded. No program of record.

3. Certification Pathway

Physical Security Systems Test Facility restart or accepted alternative verification method under AFMAN 91-118/119. Without this, Sentinel Operational Certification is blocked regardless of hardware readiness.

● PSSTF suspended. No schedule. No alternative identified.

4. Sentinel Slip ≤ 5 Years

IOC slip from post-restructure baseline must be bounded. Beyond 5 years, hard cliffs engage for a significant portion of the Minuteman III fleet. No feasible configuration exists past that threshold.

● Baseline not yet established. MS-B expected end of 2026.

5. Security Forces +15–20%

Manning increase for concurrent Minuteman III guard, Sentinel construction security, decommissioning, and approximately 800 nuclear convoys over 9 years. AFGSC currently plans 5%.

● GAO recommends Manpower Estimate Report by 2027.

6. Software Workforce at 3–4× Nominal

Nuclear-critical software hiring must account for NSCCA independent verification overhead (~2×) and cleared workforce churn (~50–60% efficiency). Combined multiplier on naive FTE estimates.

● No published workforce plan reflects this multiplier.

These six conditions define the Threaded Continuity Regime — the bounded region within which all constraints can be simultaneously satisfied. Each condition is independently achievable. The question is whether all are funded and initiated within the required windows. That is a policy decision, not a technical constraint.

The evidence supporting each condition is documented across the seven analytical spokes below, with full source chains to primary documents: GAO reports, statutory text, military standards, DoD press releases, congressional testimony, and peer-reviewed technical literature.

Constraint convergence architecture. Seven independent analytical spokes converge on a bounded feasibility envelope (center). Red boundary indicates hard cliff deadlines. Connecting arcs show constraint propagation chains across domains. All six conditions in the feasible path must be satisfied simultaneously.

The Seven Spokes

Each spoke is an independent analytical kernel specifying what must be encoded, measured, or verified for a specific constraint surface. Together they form the closed feasibility envelope.

SPK-01 · Measurement

Unit-Cost & Breach Computability Kernel

Nunn-McCurdy compliance relies on manually compiled spreadsheets that cannot be independently reproduced. GAO found programmatic adjustments masked ~50% of breaches (2001–2003). UC-BCK specifies how to transform breach determination into computationally reproducible, auditable analysis from FlexFile source data — ensuring the next baseline is measurable.
$140.9B 81% PAUC
SPK-02 · Validation

Schedule-Index Coupling Kernel

The 2020 baseline permitted concurrent design and construction because no dependency was encoded between missile design freeze and silo geometry lock. The physics required that dependency; the schedule didn't. SI-CK specifies what the re-baselined IMS must contain — including the statutory 400-ICBM floor as a schedule-level constraint that rejects infeasible conversion proposals.
400 Floor 50 Offline Max
SPK-03 · Construction Feasibility

Ground Infrastructure Production Closure Kernel

At Minot (binding constraint): 5-month season × mud-season blackout × cold productivity × remote logistics × security overhead = ~14% effective capacity. The 1960s built 1,000 silos in 5 years with 21,796 unclearanced workers and no environmental compliance. Sentinel attempts half the scope with one-third the workforce under dramatically more restrictive conditions. GI-PCK specifies how to compute whether any proposed build rate is physically achievable.
14% Capacity 5-Month Season
SPK-04 · Integration

NC3 Interface Boundary Kernel

The EMP Commission recommends hardening to 85 V/km — an order of magnitude beyond the 8 V/km commercial standard. Modern 1.2V electronics have noise margins one-quarter of the systems the shielding specs were designed for. NC3-IBK specifies the boundary contract where presidential authority becomes physical action, across a dual-stack transition with Minuteman III lasting potentially two decades.
85 V/km Dual-Stack
SPK-05 · Assurance

Cyber-Surety Joint Rules Kernel

December 2024: DoDI 3150.02 elevated cybersecurity to a Nuclear Surety Standard — "by physical or digital means." The Update Paradox: patch the system and violate nuclear certification, or don't patch and violate ATO. CSJ-K specifies how to resolve this through explicit bifurcation of frozen surety-core and agile surfaces with pre-classified change pathways.
Update Paradox FROZEN/AGILE
SPK-06 · Verification

Test & Evaluation Adequacy Kernel

DOT&E warns that digital twins "aid but do not obviate" live testing. No flight test data exists — trajectory models are unvalidated. The security test facility is suspended with no schedule. Operational Certification cannot close without it. TEA-K specifies how to make "adequate testing" a computed state derived from evidence, not an assertion.
PSSTF Blocked No Flight Data
SPK-07 · Resource Limits

Workforce, Supply Chain & Transition Continuity Kernel

Three hard cliffs: propellant aging out chemically, guidance spares trending to zero, security certification pathway undefined. The Air Force's own 2050 feasibility assessment identifies motor and guidance replacement as necessary — but neither program exists. WST-K specifies the Threaded Continuity Regime: the bounded feasibility envelope where all constraints can be simultaneously satisfied, and proves 2028 is the decision point.
Hard Cliffs 2028 Deadline

The Coupled Constraints

The Air Force has people working on construction, workforce, propellant sustainment, NC3, and cybersecurity certification independently. What the constraint satisfaction analysis reveals is what happens when these constraints interact simultaneously — when a delay in one domain creates demand in another that exceeds capacity, triggering further delays. Individual constraints are manageable. Coupled constraints that propagate across domains are where programs fail.

Schedule–Cost Spiral

Sentinel slip → extended MMIII sustainment → workforce and parts demand increase → PRP-2 and NS50_RECAP required ($8–12B+ unfunded) → cost either inflates Sentinel baseline (toward another Nunn-McCurdy breach) or competes for the same budget.

SPK-02 → SPK-07 → SPK-01

Construction–Workforce Paradox

Winter shutdown → workforce disperses to warmer jobs → clearance pipeline takes 5–12 months for replacements → spring reconstitution incomplete → peak capacity only 8–12 weeks per season → program extends → more winter cycles → more attrition. The attempted solution creates the problem.

SPK-03 → SPK-07 → SPK-03

Propellant–Industrial Base Chain

Motor age-out → PRP-2 required → PRP-2 needs nozzle ablatives → nozzles need rayon/CRP → legacy rayon stockpile depleting → DPA new-source not yet qualified for strategic applications. A chemistry constraint propagates through materials, industrial base, and acquisition.

SPK-07 (CISG++)

NC3 Synchronization Risk

ESS IOC (FY2032) ≈ Sentinel IOC (early 2030s) — but no formal dependency exists between programs. If Sentinel fields before ESS: the most advanced ICBM relies on aging AEHF for protected command. NC3 fiber runs through same corridors as ground infrastructure — subject to same 5-month seasons and mud-season blackouts.

SPK-04 → SPK-03 → SPK-02

NSCCA Triple Bottleneck

Only finally-cleared engineers touch nuclear code (CNWDI). A completely separate organization must independently verify the same code (NSCCA). Half the hires leave before peak productivity. Three independent constraints compound on the same talent pool: ~3–4× naive FTE requirement.

SPK-05 → SPK-07 → SPK-06

Certification Blockage

PSSTF suspended → security certification pathway undefined → Sentinel Operational Certification blocked → IOC impossible regardless of hardware readiness → MMIII must operate longer → extends into propellant cliff zone.

SPK-06 → SPK-07 → SPK-02

The Hard Cliffs

Unlike schedule delays that can theoretically be recovered, three constraint surfaces create deadlines that no funding decision after the fact can reverse. Propellant ages on a chemical timeline. Guidance spares deplete with each test launch and field failure. The certification pathway must exist before it's needed. These are not risks with probabilities — they are physical deadlines.

CliffEarliestLatestStatus
Propellant oldest (HTPB scenario)~2023~2030May already be binding
NS-50 guidance exhaustion~2028~2035Test frequency already reduced
Propellant oldest (PBAN scenario)~2028~2040PRP-2 by 2028 prudent under any scenario
Security certification needed~2031~2032PSSTF suspended, no alternative
Propellant youngest (any binder)~2034~2049Fleet-wide viability boundary

The Air Force's own 2050 feasibility assessment identifies propulsion replacement and guidance replacement as necessary conditions for continued Minuteman III operation. Neither program of record exists. Neither is funded. The Air Force acknowledges the requirement and has not acted upon it.

What Happens Outside the Feasible Region

If PRP-2 is not funded: motors age out. Fleet viability decreases monotonically. The operational ICBM count drops below the statutory floor of 400 — not by policy choice, but by chemistry. If NS50_RECAP is not funded: guidance inventory reaches zero. Operational missiles cannot be maintained. If the certification pathway is not resolved: Sentinel IOC is blocked indefinitely. If slip exceeds 5 years from the new baseline: multiple hard cliffs engage simultaneously. No configuration satisfies all constraints. The deterrent degrades not because of strategic decision, but because physics does not wait for budget cycles.

The Decision Timeline

Now — March 2026

Sentinel restructure announced. Prototype silo groundbreaking (Feb 13). No new cost estimate published. No new Integrated Master Schedule. Milestone B re-certification expected end of 2026. The window during which the constraint architecture can inform the new baseline is open now.

2027 — First Flight Test

Air Force target for Sentinel first launch from pad (GAO projects no earlier than March 2028). Until this occurs, trajectory and reentry models are unvalidated. All downstream certification gates depend on this date.

2028 — The Decision Point

PRP-2 must be initiated. NS50_RECAP must be underway. The security certification pathway must be resolved. Under any plausible propellant binder scenario, the oldest motors approach viability thresholds by this date. After 2028, the propellant cliff becomes inevitable — not because of management failure, but because of chemistry. This is the last point at which the coupled constraints can be jointly satisfied.

Early 2030s — IOC Target

Plausible at F.E. Warren (longest construction season, first wing) if modular construction delivers and clearance pipelines scale. Full Operational Capability across all three wings: structurally a late-2030s outcome under the physical constraints documented in the seven spokes.

What This Analysis Is

This is a constraint satisfaction blueprint — a set of technical specifications identifying what must be encoded, measured, built, funded, tested, and certified for the Sentinel program to succeed. It does not argue that Sentinel is unnecessary or that the nuclear deterrent should be abandoned. It demonstrates, through sourced evidence and multiplicative constraint modeling, that a feasible path exists but requires specific actions within specific windows.

Every factual claim has been source-verified against primary documents: DoD press releases, GAO reports, statutory text (10 U.S.C. §§ 4371–4376, §9062(n)), military standards (MIL-STD-188-125-1, MIL-HDBK-189C, MIL-STD-881F), DFARS clauses, CRREL cold-weather research, EMP Commission technical reports, Air Force career field education and training plans, DoD Inspector General audits, and peer-reviewed technical literature.

The seven spokes are independent analytical kernels that share data interfaces and cross-reference each other's constraint surfaces. Each spoke defines acceptance criteria — 63 testable pass/fail conditions in total — that transform narrative assertions into computable states. Either the constraints are real or they aren't. Either the boundary conditions are satisfied or they aren't. The architecture exists to help the program succeed by making the coupled constraints visible before they manifest as the next breach.

The window is open. The Sentinel program is in restructuring. A new baseline has not been approved. Milestone B re-certification locks at the end of 2026. The constraint architecture documented here can inform that baseline — ensuring it encodes the physical dependencies, resource limits, and hard cliffs that the 2020 baseline omitted. Once a new baseline is approved without these constraints, the opportunity closes until the next breach forces another review.