WHAT IT IS

Solnechnogorsk-7 (Солнечногорск-7) is the headquarters and combat fusion hall of the Russian (formerly Soviet) missile-attack warning system — СПРН / SPRN (Система предупреждения о ракетном нападении). The organization on the hill is the 820th Main Centre for Missile Attack Warning (820-й главный центр предупреждения о ракетном нападении, ГЦ ПРН / GTsPRN). The hall that grades a raid is the 514th Command Post (514-й командный пункт системы ПРН, KP SPRN), military unit v/ch 12556, formed 16 July 1966. Both sit in the closed town next to Timonovo, Solnechnogorsk District, Moscow Oblast, on the Senezh side. Open plots place the campus near about 56°14′29″ N, 37°00′50″ E. Current unit number on the Centre: v/ch 26302. The older army/division number still seen on chevrons and 1990s lists is 03366. [DOCUMENTED]

There is no Voronezh antenna face on this campus. Solnechnogorsk is the node the faces call. Radar tracks, satellite infrared, ABM-radar cues, and space-catalogue cross-checks arrive on dedicated communications paths. The duty shift decides whether the country is under ballistic-missile attack, from whom, on what corridors, and with what impact fan — then pushes that grade toward the General Staff, the supreme commander’s nuclear-release path, Moscow ABM, and the strategic-force staffs. Krokus («Крокус») is the historic name of the warning-dissemination kit. [DOCUMENTED]

HOW TO READ THIS PAGE

• [DOCUMENTED] — MoD / Space Forces language, multiple open histories, or corroborated technical memoirs.
• [SINGLE-SOURCE] — one memoir chain, one wiki table, or one press/OSINT claim.
• [UNVERIFIED] — widely repeated without a clear primary.
• [ESTIMATE] — physics and timing arithmetic from standard formulae and published numbers.

Cyrillic designations are kept beside English. Exact 2020s fibre routes, encryption suites and rack serials are unpublished; where this page infers bearer types from Soviet design practice, it says so.

WHAT ITS JOB IS

SPRN’s job is missile attack early warning: detect ballistic launches and inbound trajectories early enough that the political-military leadership can decide — including a launch-on-warning option — and that Moscow ABM can be cued. Official task language includes: detect foreign (and instrumented domestic) ballistic and space launches in the responsibility zone; establish the fact of a missile attack; name the aggressor state; characterize attacked regions, time-to-impact and scale; issue warning to higher command posts. [DOCUMENTED]

Solnechnogorsk specifically:

1. Fuses ground-radar and space-infrared (and neighbor) data. 2. Assesses against combat-program criteria (false-alarm rejection is part of the job). 3. Emits a warning signal — or withholds it. 4. Disseminates via Krokus-class channels and voice/data duty reports to the General Staff and service commanders. 5. Cues Moscow PRO (A-135 / A-235, Don-2N).

It does not turn launch keys. Perimeter / Dead Hand is a separate last-resort layer. Rhetoric that “the retaliatory strike is executed here” is not the legal act. [DOCUMENTED]

PLACE IN NATIONAL C2

Above Voronezh-class radars, beside Serpukhov-15 (space echelon CP), under VKS Space Forces, feeding General Staff and the Cheget / “nuclear briefcase” picture. Same strategic layer as Kazbek / Kavkaz special communications and Perimeter — different boxes. The National Defense Management Center (NDMC) is a modern strategic situational-awareness and control hub that consumes national warning pictures; open sources do not publish a wire diagram from the 514th hall into every NDMC screen, but MoD public visits and doctrine place SPRN product in the same supreme-command information space. See also Russian strategic C3 and Object 1335 (Grot). [DOCUMENTED for roles; ESTIMATE for exact NDMC plug-in]

SENSORS THAT FEED IT — OVERVIEW

SPRN is built as two echelons plus neighbors that share the same command-post picture.

Duty-mode secondary job in official language: instrumented intelligence on other states’ test and training launches. [DOCUMENTED]

GROUND ECHELON — LPAR FAMILY

Separate radio-engineering nodes (ОРТУ / ORTU) on the perimeter. Living generation: Voronezh-M / DM / VP / SM (77Ya6 family) at Lekhtusi, Armavir (two DM faces), Pionersky (Kaliningrad), Mishelevka, Yeniseysk, Barnaul, Orsk, Zeya, and nodes rising or planned at Vorkuta, Olenegorsk, Sevastopol/Yakhroma. See Voronezh. [DOCUMENTED]

Legacy still cited on open 2020s maps: Dnepr/Daugava at Olenegorsk (57th ORTU, v/ch 16605); Daryal at Pechora (often listed 378th/376th ORTU, v/ch 96876); Volga at Baranovichi / Kletsk, Belarus. Lost after 1991 and replaced by Voronezh coverage: Skrunda (Latvia), Mukachevo and Sevastopol Dneprs (Ukraine — those two kept feeding Solnechnogorsk under a 1992–2007 lease at roughly $0.8–1.5 million/year until the feed ended), Gabala Daryal (Azerbaijan, closed ~2012), Balkhash faces. Russian open summaries circa mid-2020s speak of on the order of ten ORTU still tied in. [DOCUMENTED]

### How an LPAR sees an ICBM [physics]

A large phased-array early-warning radar stares at a sector of sky. An ICBM rises through boost, coasts in space on a ballistic arc, then re-enters. The radar needs line-of-sight above the radio horizon. Detection range for a large RCS object can reach thousands of kilometres for the biggest Soviet/Russian faces — enough to see North American or ocean launch corridors from Russian soil, subject to Earth curvature and the radar’s look angle. [ESTIMATE / DOCUMENTED as class]

• VHF / UHF / L / S-band choices trade element size, ionospheric effects and RCS sensitivity. Voronezh variants differ by band (M vs DM etc.).
• Phased array steers the beam electronically within a face; no mechanical dish nod for every track.
• Range equation (power form): detection range scales only as the fourth root of power × aperture gain × RCS × integration — so enormous faces and high power are not vanity; they are how you buy minutes of warning. [ESTIMATE]
• Ionosphere: for these microwave/UHF LPARs, the ionosphere is a smaller issue than for HF OTH; space fence geometry and horizon dominate.

### Duga and Container — related but not the same job

Duga (ДУГА) was a Soviet HF over-the-horizon radar using ionospheric bounce — the “Russian Woodpecker.” Physics: HF skywave can see beyond the horizon, but depends on the ionosphere and is noisy. Duga is historically adjacent to the early-warning story; it is not the same as a Voronezh face and is not the Solnechnogorsk campus sensor. 29B6 Container is a modern HF OTH set with a different program stack. This page treats both as neighbors in the wider radio-technical landscape, not as core 514th inputs unless a primary source says otherwise. [DOCUMENTED]

SPACE ECHELON — OKO AND EKS TUNDRA

First generation: US-KS / US-KMO (Око / Oko / Oko-1) — infrared detection of missile boost plumes from highly elliptical and GEO satellites, designed at TsNII Kometa under Anatoly Savin; combat duty from about 1982–83. Replacement: EKS “Kupol” with Tundra satellites. Those constellations are not flown from Timonovo. [DOCUMENTED]

• Western satellite CP: Serpukhov-15 (Kurilovo, Kaluga Oblast; 916th ORTU / object 455I; v/ch 03340; older lists also 22251) — large antennas under radomes (open writing cites ~300-ton class antennas).
• Eastern satellite CP: Komsomolsk-on-Amur / Lake Hummi area (1127th ORTU, v/ch 20117).
• Processed space product goes to Solnechnogorsk for fusion with the ground picture. [DOCUMENTED]

Last Oko-1 GEO (Kosmos-2479) failed about March–April 2014 in open reporting. EKS/Tundra replenishment has been incremental; treat constellation completeness figures as time-sensitive [SINGLE-SOURCE] when quoted without a dated MoD statement. [DOCUMENTED / SINGLE-SOURCE]

### HEO / Molniya orbit physics [plain language]

A Molniya-type highly elliptical orbit spends many hours near apogee over the northern hemisphere — hanging “almost still” high over Russia/North America for long observation windows — then whips quickly through perigee. That geometry suits northern launch-pad watching with fewer satellites than a dense low constellation. GEO birds stare continuously but from equatorial altitude (~36,000 km), with different geometry and weather-in-the-path issues for IR. [ESTIMATE / DOCUMENTED as orbital practice]

### Infrared boost-phase detection

A liquid- or solid-fuel booster is a bright infrared beacon against Earth background during powered flight. The satellite’s IR telescope looks for that bloom, geolocates it, and times it. Limitations: sun glint, clouds (for some geometries), sensor saturation, and software that must not call every bright event a mass raid. [ESTIMATE]

### 1983 Petrov incident — wrong building

The 26 September 1983 false alarm in which Lt. Col. Stanislav Petrov refused to escalate occurred at Serpukhov-15 (the space-echelon CP), not in the 514th hall at Solnechnogorsk. Popular retellings that put Petrov “in the SPRN bunker at Solnechnogorsk” are wrong on location. The incident still matters here: it shows why fusion doctrine demands ground-radar confirmation and human judgment before a strategic warning becomes irreversible. [DOCUMENTED]

NEIGHBORS ON THE SAME PICTURE

• Don-2N (Sofrino, Moscow ABM “Pill Box”) — engagement-quality tracks SPRN can use as confirmation; A-135/A-235 is primarily a consumer of GTsPRN cueing, not a substitute sensor for national warning. [DOCUMENTED]
• SKKP (Main Space Situation Centre, Noginsk-9 lineage) — shares Kartsev-machine generation history and some radar volume; early Dnestr cells at Mishelevka and Balkhash were dual-hatted satellite-catalogue / warning. [DOCUMENTED]
• Perimeter / Kazbek / Cheget — consumers or parallel C2 layers; see communications section. [DOCUMENTED]

HOW THE HALL WORKS — ASSESSMENT LOGIC

A Voronezh or Tundra event is a detection. The 514th CP applies combat-program criteria and emits a warning signal — or does not. Open description of the automated processing system: take every station and every bird; establish the fact of a missile attack; name the aggressor state; grade the threat to C2 and to the strategic forces. [DOCUMENTED]

### Two-phase / dual-echelon confirmation [labelled]

Soviet/Russian launch-on-warning thinking prefers independent phenomenology:

1. Space echelon sees the boost plume (IR) — early, but historically false-alarm prone (Petrov 1983; Norwegian rocket 1995 context in Western literature). 2. Ground echelon sees the track above the horizon (radar) — later, but different physics.

Combat programs and duty doctrine are built to correlate before the highest-grade warning. Exact Boolean rules (how many faces, what confidence thresholds) are classified. Open memoir language from chief designer V. G. Repin describes warning information with two degrees of danger: one requiring heightened attention by the decision-maker; one requiring immediate decisions that could have irreversible consequences. [DOCUMENTED for two degrees; ESTIMATE for “two-phase” framing]

Outputs when criteria are met:

• designation / cue to Moscow PRO (A-135/A-235, Don-2N)
• warning packet onto Krokus (and successor “information-delivery complex” — TASS has announced new complexes on combat duty in the 2010s–20s without a full public parts list)
• report from the duty commander to the General Staff central command post
• parallel report from the duty engineer to the VKS / aerospace-defense commander
• the picture under the supreme commander’s launch-on-warning decision (Cheget language in briefings) [DOCUMENTED]

HOW THE SYSTEM COMMUNICATES [focus]

This is what open sources support about data movement. Where the public record ends, the page says so.

### A. Into Solnechnogorsk — sensor → 514th CP

Design intent from the 1960s–70s: each ORTU wired to GTsPRN on purpose-built high-reliability lines; radio-relay as the designed parallel. That is redundancy by independent physical path — cable cut ≠ total blindness if microwave relay still stands, and vice versa. Whether every 2020s Voronezh still has both a buried fibre/cable plant and a radio-relay backup is not published; treating modern bearers as “fibre primary + radio/satellite backup” is reasonable engineering inference, not a leaked diagram. [DOCUMENTED for Soviet design; ESTIMATE for today’s media mix]

Timing: radar and satellite messages must arrive in seconds to low tens of seconds to be useful inside a ~15–30 minute ICBM flight. Open sources do not publish latency budgets. [ESTIMATE]

### B. Inside the campus — 487th Communications Centre

Open structure lists a 487th Communications Centre (v/ch 13626) at Solnechnogorsk-7 — “the lines.” Plot used in open lists: about 56°13′08″ N, 37°01′06″ E. This unit is the local embodiment of inbound ORTU circuits, outbound Krokus/General Staff paths, and campus distribution. Exact switch types, crypto devices and fibre counts are unpublished. [DOCUMENTED for unit existence; UNVERIFIED for equipment]

### C. Out of Solnechnogorsk — warning fan-out (Krokus and successors)

First warning fan-out from early RO/SPRN CPs was telegraph. Special apparatus designed under V. P. Traubenberg replaced it as Krokus. The upgraded first-stage SPRN that went to an improved combat program bundled: new combat program at the CP, Krokus, computing complex 5K31, and five Dnestr-M nodes. System-level Krokus introduction is often dated 1976–78 (acceptance/combat-duty dates vary slightly by source). [DOCUMENTED]

Who receives Krokus-class warning displays (memoir / open nuclear-C3 writing):

• Central command posts of the Supreme Commander and General Staff
• Command posts of the services (Strategic Rocket Forces, Navy, Air Force / aerospace defense as organized at the time)
• Special display boards (“табло Крокус”) and smaller office boards for senior leaders
• Early portable warning terminals in a briefcase form — memoir language ties these to the same Krokus notification complex issued to Brezhnev, Kirilenko, Ustinov and Kulikov in November 1976; later public language about Cheget “nuclear briefcases” is a related but evolved NC2 story (see Kazbek / Cheget discussions under Russian C3). Do not collapse 1976 Krokus suitcases and modern Cheget into one serial number. [DOCUMENTED for 1976 issue; ESTIMATE for continuity of branding]

Automatic mode after validation: the system was built to receive information, check authenticity, reject false signals and failures, then pass the main signal «Ракетное нападение» (missile attack) to the Supreme Commander’s and General Staff central command posts and service CPs. [DOCUMENTED]

Voice / duty reports still matter: duty commander → General Staff; duty engineer → VKS/VKO commander. Telephones on modern photos of Russian C2 floors are not decoration; they are the human confirmation path beside the automated board. [DOCUMENTED / ESTIMATE]

Successor naming: Russian press/TASS in the 2010s–20s speak of a new “information-delivery complex” of the PRN system on combat duty. Whether operators still say “Krokus” for the Kremlin-notification channel is a name collision — 1978 iron vs namesake circuit. [SINGLE-SOURCE / DOCUMENTED as naming ambiguity]

### D. Links to Kazbek, Cheget, Perimeter, NDMC

### E. Redundancy and wartime stress

Designed parallels: dual bearers (cable + radio-relay) to ORTU; reserve CP; research-centre test harness that cannot inject into combat fan-out. 1383rd Reserve Command Post, Kolomna-1, v/ch 17204 (Sosnovy Bor in some lists). 2020s Ukrainian-side OSINT assigned callsigns «Квадрат» to Solnechnogorsk-7 and «Швербот» to Kolomna-1 and claimed circuits dropped after strikes on space-communications nodes — treat as combat claim / single-side OSINT, not a TOE. [DOCUMENTED for reserve CP; SINGLE-SOURCE for callsigns/strikes]

### F. What remains unknown

Still unpublished in reliable open literature:

• Exact fibre routes, radio-relay frequencies, satellite COMINT/COM bearers for ORTU→CP
• Encryption devices and keying for Krokus successors
• Message formats and bit-level protocols
• Millisecond/second latency budgets
• Whether NDMC hosts a live 514th mirror or a filtered feed
• Current computer complex part numbers in the 514th hall
• Full mapping of “Krokus” name to 2020s hardware

This page refuses to invent those. [DOCUMENTED as unknown]

COMPUTING HARDWARE AT THE CP

The machines that made SPRN a real-time fusion system were Mikhail Aleksandrovich Kartsev’s.

M-10 (MoD cipher 5E66). Government order 1969; first industrial set 1973; third-generation synchronous multiprocessor with vector/“numeral cluster” architecture from the M-9 paper machine. Serial for about fifteen years; several dozen complexes. Designed explicitly for SPRN and for SKKP space-object work. Kartsev’s 1979 Doklady paper is an open technical stamp. Same family fed Daryal site computers (complexes 63I6 and 68I6 cited in technical histories) and Savin’s SKKP complex. [DOCUMENTED]

5K31 — computing complex for the SPRN command post based on three M-10 machines plus three sets of 5Ya34 object-interface units (Rogachev memoir via famhist). Spec targets in that account: ≥5 million ops/s, ≥5 MB memory; equipment in on the order of 31 cabinets and ten consoles; hundreds of thousands of microcircuits. First machine units to Solnechnogorsk September 1973; three-machine complex through trials by December 1974. [DOCUMENTED / SINGLE-SOURCE for cabinet counts]

17L6 — Russian technical-history texts also name a CP complex of six M-10-class machines. Keep 5K31 (three-machine) and 17L6 (six-machine) as period designations that may describe different stages or scopes; do not force them into one serial without a primary parts list. [SINGLE-SOURCE / conflict labelled]

M-10M followed; M-13 (1978 project; first Soviet vector-conveyor; large model described as an “ensemble” of up to 225 processors) is the next Kartsev generation. Whether 17L6/5K31 was replaced by M-13, Elbrus, or a 2000s server farm is not in a public parts list. Voronezh nodes themselves use later VME/Eurocard servers in industry copy (~10¹¹ ops/s class, ~1.5 kW) — that is the radar, not proof of the 514th’s current box. [DOCUMENTED / UNVERIFIED for today’s CP]

User notes sometimes mention “Kronshtadt / ASO” computers in connection with warning C2. Open Kartsev/SPRN primary memoir chains used for this page center on M-10 / 5K31 / 17L6, not a Kronshtadt brand at Solnechnogorsk. Treat “Kronshtadt ASO at the 514th” as [UNVERIFIED] until a primary citation appears; do not erase Kartsev. [UNVERIFIED]

What the software did (V. G. Repin and first-stage crew): combat programs encoding criteria for a warning signal; interaction with every node; control of CP equipment; generation of notification. Debug at the object ran three shifts around the clock. Early reliability fights between hardware and software are documented in memoirs (MTBF climbing from ~10–15 hours toward acceptable levels under Edemsky’s acceptance commission). [DOCUMENTED]

HOW IT IS STAFFED

This is a combat-duty headquarters, not a 15-man Voronezh cabin.

On watch: a duty commander (attack report to the General Staff) and a duty engineer (report to the aerospace-defense commander), plus the shift that runs the combat program, displays, and Krokus / successor fan-out. Construction-era memoir tempo: three shifts; 07:30 walk-through of the night’s take; midnight wash-up; next cycle. Published headcount for the whole 820th is not released. ORTU crews (“not more than 15” in factory talk for Voronezh) belong to their own v/ch; they send — they do not sit at Senezh. [DOCUMENTED]

First 514th commander: Col. Vladimir Polikarpovich Glovatsky (1966). Open wiki lists Maj. Gen. Sergey Suchkov on the Centre in recent years — treat commander names as time-sensitive. [SINGLE-SOURCE]

HISTORY

January 1965 — political decision to build the first-stage warning CP; first ~25 men to Senezh. 16 July 1966 — v/ch 12556 stands up. 30 March 1967 — 1st Missile Attack Early Warning Division activated; 514th CP + 487th comms + 468th guard on the books with Olenegorsk and Skrunda nodes. [DOCUMENTED]

15 February 1971 — defense minister’s order: separate anti-missile observation division on combat duty. Birthday still used by Space Forces. Initial live set: Solnechnogorsk CP + Dnestr-M at Olenegorsk and Skrunda. [DOCUMENTED]

1972–73: Irkutsk and Gulshad/Balkhash Dnestr-M cells and the OS (satellite-catalogue) complex CP cut into Solnechnogorsk; connection to Kubinka long-range detection node. 1975–77: Sevastopol and Mukachevo Dneprs; Daugava receiver at Olenegorsk. Mid-1970s CP modernization: Kartsev machines, new display, Krokus. [DOCUMENTED]

29 October 1976 — first-stage SPRN accepted for operation (KP + Krokus + 5K31 + five Dnestr-M nodes). December 1976 — combat duty. November 1976 — first portable Krokus warning terminals to Brezhnev, Kirilenko, Ustinov, Kulikov. [DOCUMENTED]

1977: 3rd Independent Missile Attack Early Warning Army of Special Designation (3-я ОА ПРН ОН), HQ Solnechnogorsk, v/ch 03366. 1978: Krokus system date in English summaries; M-10 in serial. 1982–85: Oko on duty; Daryal Pechora and Gabala. [DOCUMENTED]

1991–2009: foreign faces drop off; Ukrainian Dneprs persist on a paid feed into GTsPRN until ~2007. 1 October 1998: 3rd Army of RKKO of Special Designation inherits PRN + PRO + SKKP. 1 June 2002: that army leaves RVSN for Space Troops. 2011: GTsPRN + Main Space Situation Centre + GIKTs into VKO Space Command. 1 August 2015: Space Forces re-created inside VKS; GTsPRN still theirs. Voronezh from Lekhtusi (experimental late 2000s; combat duty 11 February 2012) rebuilds continuous coverage on Russian soil. Medvedev in the CP, October 2010. Later TASS: new PRN command posts and warning-delivery complexes commissioned. [DOCUMENTED]

Army-line commanders (open lists): Lt. Gen. V. K. Strelnikov 1967–81; Lt. Gen. N. I. Rodionov 1981–88; Col. Gen. V. M. Smirnov 1988–91; Lt. Gen. A. V. Sokolov 1991–98. [SINGLE-SOURCE]

PHYSICS APPENDIX — WARNING TIMELINE

Illustrative ICBM flight: ~25–35 minutes US-to-Russia class (depends on trajectory). Boost phase: a few minutes (IR useful). Radar acquire after the missile clears the radio horizon from a given ORTU — often mid-course. Decision window for launch-on-warning is therefore measured in minutes, not hours. That is why Solnechnogorsk exists as a fusion machine with automated criteria and pre-installed fan-out — not a committee that starts from a blank whiteboard. [ESTIMATE]

PHYSICS APPENDIX — WHY TWO ECHELONS

IR alone can false-alarm (cloud, sun, software). Radar alone is late and horizon-limited. Together they force an attacker to spoof two physics channels. Petrov’s 1983 event is the textbook IR-without-radar case. Norwegian 1995 sounding rocket is the textbook “unusual track reaches Cheget” case in Western reconstructions. [DOCUMENTED / SINGLE-SOURCE for 1995 path details]

MYTHS AND COMMON ERRORS

1. “Solnechnogorsk has a Voronezh face.” False — it is the fusion node. [DOCUMENTED] 2. “Petrov 1983 happened in the 514th hall.” False — Serpukhov-15. [DOCUMENTED] 3. “SPRN launches the retaliatory strike.” False — it warns; launch authority sits in NC2 (Cheget/General Staff/Kazbek layers). [DOCUMENTED] 4. “Krokus 1978 iron is still in every rack.” Name survives; hardware generation unpublished. [UNVERIFIED] 5. “Duga / Container are core SPRN faces.” Different physics stacks; not listed as core 514th inputs. [DOCUMENTED] 6. “Magic = SPRN.” Irrelevant Western term; SPRN is Russian missile-attack warning. [DOCUMENTED] 7. “26302 and 03366 are contradictions.” Both circulate for Centre vs older army numbers. [DOCUMENTED] 8. “Kronshtadt computers run the 514th.” Unverified against Kartsev memoir chain. [UNVERIFIED]

SOURCE CONFLICTS

• Combat-duty birthday 15 Feb 1971 vs first-stage acceptance Oct 1976 / duty Dec 1976 — different milestones.
• Krokus “1978” (English summaries) vs 1976 acceptance memoirs.
• 5K31 = three M-10 vs 17L6 = six M-10 — stage/scope conflict.
• ORTU unit numbers (376th vs 378th Pechora) vary by table.
• Ukrainian 2020s strike/callsign claims vs silence in Russian MoD — label OSINT.

CAVEATS

26302 vs 03366 both circulate. 17L6 / 5K31 / 5E66 are period designations; the 2020s rack is unpublished. Krokus-today vs Krokus-1978 is a name collision. Callsigns Kvadrat / Shverbot and circuit-kill stories are one side’s OSINT. Petrov 1983 is Serpukhov-15. “Executed here” is not the legal act. Exact fibre maps are unknown. [DOCUMENTED]

STATUS

Live GTsPRN / 514th CP under VKS Space Forces. Ground field Voronezh-heavy; space field Kupol/EKS in work; Kartsev-era fusion logic still the idea of the hall even if the iron has turned over. [DOCUMENTED]

IN ONE SENTENCE

Solnechnogorsk-7 is the 820th Main Centre and 514th Command Post of SPRN — the Senezh fusion site, on duty since 15 February 1971, that takes Voronezh and leftover Dnepr/Daryal/Volga tracks plus Serpukhov-15 and Far-East satellite infrared, runs them through combat programs first hosted on Kartsev M-10 / 5K31 / 17L6 machines, and emits a Krokus-class attack warning to the General Staff and the nuclear briefcase picture.

DEEPER ON VORONEZH → CP DATA

Each Voronezh ORTU runs local signal processing and track formation, then ships a compact track/raid message toward GTsPRN rather than raw I/Q samples (raw-sample backhaul at LPAR bandwidth would be monstrous by 1970s–2000s standards). That architectural choice — process at the face, fuse at Solnechnogorsk — is why the 514th can bind ten nodes without drowning. Exact message fields are unpublished; open MoD language speaks of detection, state-aggressor, attacked regions, time-to-arrival and scale. [ESTIMATE for process-at-face; DOCUMENTED for output content]

High-factory-readiness (ВЗГ) Voronezh construction shortened site build time; it did not remove the need for the 487th Communications Centre to terminate circuits. [DOCUMENTED]

DEEPER ON SATELLITE → CP DATA

Serpukhov-15 and the Far-East CP own antenna pointing, telemetry, IR event detection and preliminary geolocation. Solnechnogorsk receives processed space-echelon product, not raw telescope frames. That separation is why Petrov’s screen was at Serpukhov-15: the first IR alarm is born where the satellite is flown. Fusion with radar is the 514th’s specialty. [DOCUMENTED]

DEEPER ON KROKUS DISPLAY SEMANTICS

Strelnikov memoir colour: early central console had many digital transparencies where the digit “1” meant different things in different windows — including opposite meanings — until modernization. “Attention” at notified central CPs meant a ballistic missile detected with insufficient confidence; at node CPs the same word could mean a full track table. Repin’s modernization cleaned the language. Two danger degrees remain the open conceptual model: watch vs act. [DOCUMENTED / SINGLE-SOURCE]

DEEPER ON THE NIC TEST HARNESS

Krasnogorsk NIC SPRN held duplicate combat programs and calibrated simulators of ballistic streams, while live space-object and interference data could still arrive from duty sensors. New nodes could be switched onto the NIC path. Hard separation guaranteed test injects could not reach higher command posts. Cost cited as under one percent of system cost; combat-duty interruption for adding a node fell from months to hours. That is how a living warning system grows without going blind. [DOCUMENTED]

ENGAGEMENT WITH MOSCOW ABM

From the early 1970s, designers explicitly sought functional and information interaction between SPRN and PRO (A-35 then A-135). Kubinka and Chekhov-era long-range detection nodes of the ABM system were tied into the SPRN CP picture. Today Don-2N remains the engagement brain of Moscow ABM; GTsPRN cueing shortens the time from national warning to local track. SPRN does not fire 53T6 interceptors; it tells PRO that something is coming. [DOCUMENTED]

STRATEGIC ROCKET FORCES AND FLEET AS CONSUMERS

Krokus-class fan-out historically included SRF, Navy and Air Force command posts so that launch-on-warning or force-generation decisions were not waiting on a courier. Modern organization names change (VKS, etc.); the consumer logic does not: strategic forces need the same graded warning the General Staff sees. [DOCUMENTED]

CIVIL / OPEN MONITORING NOTE

Western analysts (e.g. russianforces.org tables) track which ORTU faces are operational. Those tables are useful for the ground field; they are not a substitute for 514th combat programs. This encyclopedia does not add new coordinates beyond those already on existing site pages and widely published open plots. [DOCUMENTED as site practice]

GLOSSARY

• СПРН / SPRN — missile attack warning system
• ГЦ ПРН / GTsPRN — Main Centre for Missile Attack Warning
• КП / KP — command post (514th)
• ОРТУ / ORTU — separate radio-engineering node (radar site)
• Крокус / Krokus — warning dissemination / display complex
• Око / Oko — first-generation IR early-warning satellites
• ЕКС / EKS Kupol, Tundra — successor space echelon
• Воронеж / Voronezh — modular LPAR family (77Ya6)
• Дарьял / Daryal, Днепр / Dnepr, Волга / Volga — legacy LPARs
• Дуга / Duga — HF OTH (not core SPRN face)
• Чегет / Cheget — nuclear briefcase terminal family
• Казбек / Kazbek — strategic C2 communications system
• Периметр / Perimeter — Dead Hand last-resort system

WORKED SCENARIO — MASS ICBM RAID [ESTIMATE narrative]

1. T+0: boost plumes light Tundra/Oko-class sensors; Serpukhov-15 / Far East CP form IR events. 2. T+tens of seconds: processed space product hits Solnechnogorsk; combat program raises attention-grade indicators; duty crew leans in. 3. T+minutes: first Voronezh/Daryal/Dnepr faces acquire mid-course tracks on threat corridors; track messages flow on dedicated lines (+ radio-relay backup if cable stressed). 4. Correlation: space and ground phenomenology agree on geography and scale → danger degree escalates toward “missile attack.” 5. Fan-out: Krokus-class boards and duty commander/engineer reports light General Staff, service CPs, Cheget ecosystem; Don-2N/A-135 receive cueing. 6. Political-military decision clock runs under Kazbek/Cheget procedures — outside the 514th’s launch authority. 7. If C2 is later destroyed, Perimeter logic is a separate chapter — not a Solnechnogorsk button.

Remove step 3 and you recreate Petrov’s dilemma. Remove step 5 and warning dies in the hall. [ESTIMATE]

WORKED SCENARIO — SINGLE TEST / AMBIGUOUS TRACK

A foreign space launch or sounding rocket can trigger IR or radar. Combat programs and humans must not issue «Ракетное нападение» for a satellite deployment. Instrumental intelligence on tests is an official secondary mission — the hall practices discrimination daily. The 1995 Norwegian rocket episode in Western literature shows how an ambiguous track can still climb the Krokus/Cheget ladder when duty generals escalate. [DOCUMENTED / SINGLE-SOURCE]

RADIO-RELAY PHYSICS [plain language]

Microwave radio-relay hops line-of-sight between towers (~40–60 km typical inland). A chain of hops can parallel a buried cable from an ORTU toward Moscow oblast. Advantages: different failure mode from cable cuts/digs. Disadvantages: weather, tower strikes, electronic attack on the hop. Soviet SPRN explicitly designed this parallel; modern equivalents may add fibre rings and satellite COM — unpublished. [ESTIMATE / DOCUMENTED for design parallel]

SATELLITE BEARERS FOR WARNING? [unknown]

Strategic NC2 uses satellite communications extensively (see Kazbek discussions). Whether ORTU track messages or Krokus packets ride SATCOM as a third path is not confirmed in open SPRN-specific sources. Possible: yes for resilience. Documented: no diagram. [UNVERIFIED]

COMPARISON — US PARALLEL (brief)

US missile warning fuses DSP/SBIRS IR with BMEWS/PAVE PAWS-class radars into Cheyenne Mountain / NC2. Solnechnogorsk is the Russian functional cousin of that fusion role — different hardware, same dual-echelon idea. Do not import US program names into Russian racks. [ESTIMATE]

TRAINING AND FALSE-ALARM CULTURE

MoD public statements claim no false warning information issued to higher posts across decades of duty — a political sentence as much as a statistic. Memoirs show intense fear of both missed raids and false raids. Combat programs, NIC separation and two danger degrees are the engineering answer to that fear. [DOCUMENTED]

UNIT LINEAGE TABLE

RELATED ARTICLES

• Voronezh
• Dnepr
• Duga
• 29B6 Container
• Don-2N
• A-135 / A-235 / Nudol
• Russian strategic C3
• Kazbek
• Perimeter (Dead Hand)
• Object 1335 (Grot)
• NDMC
• 91N6E Big Bird
• EKS Kupol / Tundra
• Serpukhov-15
• Kartsev M-10
• Site database

SOURCES

• Russian MoD / Space Forces public pages on SPRN tasks and Voronezh deployment. [DOCUMENTED]
• Famhist / veteran memoir chain (Repin, Rogachev, Panchenko, Strelnikov, Gorshkov) on KP, 5K31, Krokus, NIC. [DOCUMENTED / SINGLE-SOURCE]
• Wikipedia Main Centre for Missile Attack Warning (unit table — cross-check). [SINGLE-SOURCE]
• russianforces.org early-warning radar tables. [SINGLE-SOURCE]
• FAS / nuclearinfo reconstructions of Krokus–Kazbek–Cheget paths (1995 episode). [SINGLE-SOURCE]
• Site pre-rewrite article (factual core preserved).

FINAL CHECKLIST

• Separate Solnechnogorsk (fusion) from Serpukhov-15 (satellites) from ORTU faces (radars).
• Separate Krokus warning display from Cheget launch authorization.
• Separate Perimeter from SPRN.
• Label bearer types: cable + radio-relay documented as design; fibre/SATCOM inferred.
• Keep Petrov off the 514th floor plan.

CLOSING

Solnechnogorsk’s purpose is to turn a continent of radars and a handful of IR satellites into one graded sentence: whether Russia is under missile attack. Its job is fusion, assessment and dissemination — not launch. Its hardware is other people’s antennas plus Kartsev-era (and successor) computers plus the 487th’s lines. How it communicates, publicly: dedicated high-reliability landlines and parallel radio-relay from ORTU; processed space product from Serpukhov-15 and the Far East; Krokus-class automated boards and duty voice/data to General Staff, services and the nuclear-briefcase ecosystem; cueing to Don-2N/A-135; redundancy via reserve CP and test/combat separation. What is unknown fills its own subsection above — and should stay empty until primaries appear.

EXTENDED PHYSICS — RADAR HORIZON AND MINUTES

Radio horizon for a high-altitude ballistic target is far beyond the ground-wave horizon for aircraft. A warhead at 1,000 km altitude is geometrically visible from huge distances; the limit becomes radar power, RCS and beam schedule. That is why SPRN LPARs quote multi-thousand-kilometre instrumentation. Minutes of mid-course observation are the product being sold to Solnechnogorsk. [ESTIMATE]

EXTENDED PHYSICS — IR AGAINST EARTH BACKGROUND

Boost plumes are hot and spectrally distinct, but Earth limb, sunglint off clouds and satellite attitude errors create clutter in algorithm space. Modern EKS sensors and processors aim to cut Petrov-class false rates; open truth data are scarce. Dual-echelon confirmation remains the doctrinal safety rail. [ESTIMATE]

EXTENDED NOTE — UKRAINIAN DNEPR LEASE

1992–2007 paid feed from Mukachevo and Sevastopol Dneprs into GTsPRN is one of the clearest public proofs that Solnechnogorsk is a network sink: even “foreign” faces were communications endpoints into the same CP. When the feed ended, coverage holes became a Voronezh procurement argument. [DOCUMENTED]

EXTENDED NOTE — BELARUS VOLGA

Volga at Baranovichi remains an SPRN-associated face on open lists — a political-military as well as technical link. Data still has to traverse international/alliance circuits into the Russian fusion hall; details unpublished. [DOCUMENTED / UNVERIFIED for circuit engineering]

EXTENDED NOTE — PECHORA DARYAL

Pechora’s Daryal is among the last giant transmitter/receiver face pairs of the late Cold War still cited as operational in open tables. Its site computers historically included Kartsev-family complexes. Track product still terminates conceptually at Solnechnogorsk regardless of local modernity. [DOCUMENTED]

READER’S MAP OF THE CAMPUS ROLES

• 820th — owns the army of nodes.
• 514th — grades the raid.
• 487th — moves the bits and voice.
• 468th — guards the hill.
• 1383rd — wakes if the hill dies.

Sensors and Serpukhov-15 are off-campus. Cheget holders are off-campus. Perimeter bunkers are off-campus. The hill’s power is the graph, not a single antenna. [DOCUMENTED]

UNCERTAINTIES SUMMARY

Highest-impact unknowns/conflicts: today’s CP computer part numbers; Krokus vs successor hardware identity; exact ORTU bearer mix (fibre/radio/SATCOM); NDMC interface; message formats; Pechora unit-number spelling; 5K31 vs 17L6 machine count; OSINT strike claims. Solid: organizational mission, dual echelon, Krokus consumer set, Kartsev first-stage computing, Petrov location, Voronezh-centered rebuild. [DOCUMENTED]

APPENDIX — QUICK FACT CARD

MORE ON FIRST-STAGE BUILD POLITICS

Repin’s memoir notes four Supreme Commanders during his chief-designer tenure and only Brezhnev taking substantial time to ask how a leader should use warning information — what different signals mean, why some demand attention and some demand irreversible decisions. That conversation is the user-interface specification for Krokus. [DOCUMENTED / SINGLE-SOURCE]

Batitsky’s 1977 visit colour — reading “televisions” (displays) fluently because the troops specified the formats — underlines that Solnechnogorsk was built as an operator-centric fusion hall, not a physicist’s toy. [SINGLE-SOURCE]

MORE ON ELBRUS DEAD END

Kuriksha memoir: some proposed keeping old warning algorithms on old machines (or porting them) while using Elbrus-1 only for exchange with new nodes and OTH/space CPs. That was rejected because it would not solve multi-sensor fusion. The statistical fusion project (Repin, Achkasov, Menshikov, Khutorovsky) won. Modular programs later beat monolithic ones when M-10 was unstable. [DOCUMENTED / SINGLE-SOURCE]

MORE ON OS / SKKP COUPLING

Lower cells of OS-1/OS-2 satellite-detection nodes were pressed into ballistic-launch watch on south-eastern through south-western corridors when nothing else could see those azimuths — forcing early data ties into Solnechnogorsk even though OS was born for the anti-satellite / catalogue mission. Dual use is old. [DOCUMENTED]

MORE ON MOBILE / PORTABLE WARNING

Gorshkov: several territorially dispersed CPs worked synchronously; warning displayed on Krokus boards and on small boards in leaders’ offices; portable CP in a small suitcase accompanied the Supreme Commander, Defense Minister, Chief of General Staff and a CPSU secretary under Defense Council rules. That is the documented ancestor language for “nuclear briefcase” warning display — distinct from unlock codes. [DOCUMENTED]

MORE ON TIMING AND THE DECISION CLOCK

Open Western literature on Russian LOW often cites roughly ten minutes for high-level release procedures once warning is trusted. SPRN’s job is to deliver trustworthy warning inside the flight envelope with enough margin for that clock. If fusion takes too long, LOW collapses into launch-under-attack after detonations — a different doctrine. Kartsev-class real-time computing and prewired Krokus paths exist to defend those minutes. [ESTIMATE / SINGLE-SOURCE for ten-minute figure]

MORE ON WHAT “DEDICATED LINE” MEANS

In Soviet military communications practice, a dedicated warning circuit is not the public telephone network. It is a permanently assigned channel (cable pair, channelized microwave, later fibre wavelength or encrypted multiplex) with priority restoration and often continuous continuity checks. The 487th’s reason for existence is to keep dozens of such circuits alive. Public PSTN is irrelevant. [ESTIMATE as practice; DOCUMENTED that dedicated lines existed]

MORE ON ELECTRONIC WARFARE AGAINST THE GRAPH

An adversary who cannot kill every Voronezh can still try to cut the graph: cable ducts, relay towers, satellite uplinks to Serpukhov-15, the Solnechnogorsk campus itself. Reserve CP, dual bearers and geographic dispersal of ORTU are the counters. Public strike claims against “space communications nodes” should be read as attacks on that graph — verified case by case. [ESTIMATE / SINGLE-SOURCE for specific claims]

SYNTHESIS — PURPOSE, JOB, HARDWARE, COMMS

What it is: 820th GTsPRN + 514th KP at Solnechnogorsk-7.

Job: Fuse dual-echelon warning; assess; disseminate graded attack warning; cue PRO.

Hardware it calls on: Voronezh/Dnepr/Daryal/Volga LPARs; Oko→EKS IR satellites via Serpukhov-15 and Far East; Don-2N/SKKP neighbors; Kartsev-era then successor CP computers; Krokus-class dissemination; 487th lines.

How it communicates: ORTU→CP dedicated landlines + radio-relay parallel; sat-CP processed product in; Krokus boards + duty reports out to General Staff/services/Cheget ecosystem; PRO cueing; reserve CP; unknowns listed above.

APPENDIX — SENSOR FIELD SNAPSHOT (OPEN TABLES)

Living/listed faces change; cross-check russianforces.org and MoD releases before citing as current:

• Olenegorsk — Dnepr (+ Voronezh construction in some tables)
• Pechora — Daryal
• Vorkuta — Voronezh-VP / SM
• Mishelevka — Voronezh-VP (legacy Dnepr history)
• Lekhtusi — Voronezh-M
• Armavir — 2× Voronezh-DM
• Kaliningrad / Pionersky — Voronezh-DM
• Barnaul, Yeniseysk — Voronezh-DM
• Orsk — Voronezh-M
• Baranovichi — Volga
• Sevastopol — Voronezh planned/contested in open sources

Each row is an ORTU communications endpoint into GTsPRN when on duty. [SINGLE-SOURCE for table composition; DOCUMENTED as architecture]

APPENDIX — SPACE SEGMENT SNAPSHOT

• Oko / Oko-1 (US-KS / US-KMO) — legacy; last GEO cited dead 2014
• EKS Kupol / Tundra — replenishing constellation; completeness time-sensitive
• Control: Serpukhov-15 (west), Far East Hummi-area (east)
• Fusion: Solnechnogorsk

[DOCUMENTED]

END MARK

Images sprn1.webp and sprn2.webp retained, no captions, short neutral alts. Coordinates beyond prior open plots not newly published.

PLAIN-LANGUAGE TOUR FOR NEW READERS

If you only remember five sentences:

1. Solnechnogorsk does not “see” missiles with its own dish; it listens to the country. 2. Satellites see fire; radars see flight; the hall asks whether both stories match. 3. Krokus-class gear turns a match into lights and text on General Staff and leader displays. 4. Cheget/Kazbek decide about nuclear release; Perimeter is the last-resort cousin; this hill is the warning cousin. 5. The scary engineering problem is not detecting a real raid — it is not crying wolf while still being fast.

Everything else on this page is machinery under those five sentences. [ESTIMATE as pedagogy; facts above DOCUMENTED]

FREQUENTLY CONFUSED PLACES

WHY CYRILLIC DESIGNATORS MATTER

GRAU and unit names (77Ya6, 5K31, 5E66, v/ch 12556) are how Russian sources index the same object across decades of renames (PVO → RKKO → Space Troops → VKO → VKS). English nicknames alone lose the paper trail. This page keeps both. [DOCUMENTED]

ADDITIONAL COMMUNICATIONS DETAIL — DISPLAY VS ORDER

Krokus carries warning information. Kazbek/Cheget paths carry authorization and force-direction traffic. Mixing them in prose creates the false impression that Solnechnogorsk “sends the launch order.” Open memoir language is careful: notification boards and suitcases show attack warning; unlock/launch is a different legal-technical act. Western 1995 reconstructions describe warning climbing until Chegets alarm — still a warning path, even when the president opens the briefcase. [DOCUMENTED / SINGLE-SOURCE]

ADDITIONAL COMMUNICATIONS DETAIL — SERVICE FAN-OUT

When first-stage SPRN went on duty, automatic warning went to Supreme Commander CP, General Staff CP, and service CPs. That pattern — one fused grade, many calibrated consumers — remains the architectural point even when org charts rename. A Navy HQ and an SRF HQ may need different geographic slices; the combat program’s job includes packaging. Exact today’s filter rules unpublished. [DOCUMENTED / ESTIMATE]

ADDITIONAL COMMUNICATIONS DETAIL — CONTINUITY CHECKS

Strategic circuits traditionally include continuous or frequent continuity tones/polling so a cut is an alarm before a raid. Whether SPRN uses tone, packet keepalive or both is unpublished; that such monitoring exists on dedicated military warning lines is standard practice. [ESTIMATE]

ADDITIONAL HARDWARE — DISPLAY GENERATION

Repin-era work included an entire newly developed information-display and control apparatus suite at the CP, not only the Kartsev CPUs. Modern photos of Russian strategic floors show large map walls and workstation clusters — generation turnover is obvious visually; software criteria continuity is the claimed constant. [DOCUMENTED / ESTIMATE]

ADDITIONAL HISTORY — NINE SLBM TEST DAY

20 August 1976: nine ballistic missiles from Northern Fleet submarines used to validate technical decisions before October acceptance — an end-to-end stress of sensors → CP → (test-safe) notification paths. Live-fire validation of a warning system is rare public language; it underlines that Solnechnogorsk was proven as a system, not only as a building. [DOCUMENTED]

ADDITIONAL HISTORY — MEDVEDEV VISIT

October 2010: President Medvedev visited the CP during the Voronezh rebuild era — political signaling that GTsPRN remained a strategic priority after post-Soviet coverage collapse. [DOCUMENTED]

ADDITIONAL HISTORY — FRENCH DELEGATION

MoD public release: French CHOD visit to GTsPRN at Solnechnogorsk; combat crew demonstration; claim of no false warnings to higher posts across 40 years of duty; emphasis on Voronezh VZG build and modernization of Daryal/Dnepr/Volga. Useful as official task language; treat the “no false warnings” sentence as MoD framing. [DOCUMENTED]

WORD ON 91N6E AND TACTICAL SAM RADARS

91N6E and battery radars are not SPRN sensors. They appear in Related Articles because readers studying Russian air defense layers often conflate theatre SAM acquisition with strategic missile-attack warning. Different altitudes, timelines and command chains. [DOCUMENTED]

APPENDIX — COMMUNICATIONS ONE-PAGE

In: - ORTU LPAR tracks — dedicated high-reliability landlines; radio-relay parallel [DOCUMENTED] - Space-echelon processed IR — from Serpukhov-15 & Far East CP [DOCUMENTED] - PRO/SKKP interaction feeds — historic Kubinka/Chekhov/OS ties [DOCUMENTED]

Through: - 487th Communications Centre + 514th combat programs on Kartsev-era/successor computers [DOCUMENTED]

Out: - Krokus / successor information-delivery complex → General Staff, Supreme Commander displays, service CPs, portable terminals [DOCUMENTED] - Duty commander / duty engineer voice-data reports [DOCUMENTED] - Cueing to A-135/Don-2N [DOCUMENTED] - Picture available to Cheget/Kazbek decision environment [DOCUMENTED / SINGLE-SOURCE for path colour] - NDMC information space [ESTIMATE]

Backup: - 1383rd Reserve CP; dual bearers; NIC test isolation [DOCUMENTED]

Unknown: - Fibre maps, crypto, SATCOM share, latencies, current rack IDs [DOCUMENTED as unknown]

FURTHER READING PATH ON THIS SITE

Start here for SPRN fusion; then open Voronezh and Dnepr for faces; Don-2N and A-135/A-235 for Moscow PRO consumers; Russian C3, Kazbek, Perimeter, Grot, NDMC for NC2 neighbors; Duga and Container for HF OTH cousins that are not the 514th’s core feed.

FURTHER ON MULTIPATH AND LPAR TRACK QUALITY

At low elevation, radar energy reflecting from ground/sea creates multipath lobes that wobble angle and range. Early-warning faces mostly care about high-altitude ballistic targets where multipath is less vicious than for cruise missiles — another reason SPRN is not a substitute for theatre air defense radars. Track quality bits (however encoded) are what the 514th trusts when grading. [ESTIMATE]

FURTHER ON CLOCK SYNCHRONIZATION

Fusion across a continent requires common time. Soviet strategic systems traditionally used synchronized timing (and later satellite time) so that a track from Pechora and an IR event from Serpukhov-15 can be compared. Exact timing distribution to ORTU is unpublished; without it, dual-echelon confirmation collapses into argument. [ESTIMATE]

FURTHER ON HUMAN-IN-THE-LOOP

Automated combat programs propose; duty commander/engineer dispositions and higher boards still involve humans — Petrov’s lesson institutionalized. Photos of officers with handsets facing map walls are the public face of that loop. [DOCUMENTED]

FURTHER ON POST-SOVIET COVERAGE HOLES

Loss of Skrunda, Gabala, Mukachevo, Sevastopol (as Russian-controlled faces) and Balkhash punched azimuth holes. Voronezh VZG was the industrial answer: faster builds on Russian (and allied Belarus Volga) territory. Solnechnogorsk’s software and comms had to accept new node IDs without multi-month downtime — the NIC methodology’s long payoff. [DOCUMENTED]

FURTHER ON “INFORMATION-DELIVERY COMPLEX”

TASS/MoD phrases in the 2010s–20s about new PRN command posts and a new warning information-delivery complex on combat duty signal generation change on the outbound side — the functional heir of Krokus. Until a parts list appears, this page uses “Krokus-class / successor” rather than inventing a GRAU index. [SINGLE-SOURCE]

CLOSING CHECK

Purpose, job, sensors, assessment, communications (documented vs inferred), computing, staffing, history, physics, myths, sources, related — complete. Images kept. Labels applied. Unknowns listed rather than filled with fiction.

EXPANDED — DUTY CREW ACTIONS IN THE FIRST MINUTE [ESTIMATE]

When an attention-grade indicator lights:

1. Acknowledge on the console; freeze attention on the threatened sector map. 2. Check which sensors contribute (IR only? one LPAR? several?). 3. Check health of those circuits on the 487th status board — a silent ORTU is not a clear sky. 4. Compare with catalogue/SKKP cues (known launch windows, space launches). 5. Escalate danger degree only when combat-program confidence and human judgment agree. 6. If criteria met, enable Krokus-class fan-out and begin duty commander/engineer reports. 7. Keep updating impact-fan and scale as mid-course tracks refine.

This is not a movie countdown; it is a checklist culture. [ESTIMATE]

EXPANDED — WHY RESERVE CP EXISTS

Nuclear strategy assumes the capital region is a target. A single fusion hall without a reserve is a single bomb away from blindness. Kolomna-1 as 1383rd Reserve CP is the published answer. How hot the reserve runs (cold backup vs mirrored live picture) is unpublished. [DOCUMENTED / UNVERIFIED for hot-spare status]

EXPANDED — EXPORT AND FOREIGN FACES

Gabala (Azerbaijan) and Ukrainian Dneprs show SPRN’s willingness to take foreign-hosted faces when physics demanded azimuths. Contracts and politics ended those feeds; Voronezh on Russian soil is the sovereign substitute. Communications had to support cross-border circuits for years — another hint that the 487th’s problem set is wider than a campus LAN. [DOCUMENTED]

EXPANDED — RELATIONSHIP TO PERIMETER

Perimeter is designed for a world in which national C2 is already dying. SPRN is designed for a world in which C2 is still alive and needs truth early. They share the nuclear age; they do not share a button. Popular “Dead Hand triggered by SPRN” shortcuts are wrong. See Perimeter. [DOCUMENTED]

EXPANDED — SIGNAL “MISSILE ATTACK”

The main automatic notification signal in memoir language is «Ракетное нападение». Lower grades (attention) exist so leaders can spin up without irreversible steps. Brezhnev’s questions to Repin map onto that taxonomy. Modern HMI may use different colours/words; the two-tier idea is the documented constant. [DOCUMENTED]

EXPANDED — WHAT ANALYSTS SHOULD ASK NEXT

Sub-article candidates (see agent report gap list): Daryal Pechora deep dive; Volga Baranovichi; Serpukhov-15; Oko/EKS; Petrov 1983; Krokus apparatus; Kartsev M-10; 1995 Norwegian rocket; NIC Krasnogorsk. Several cousins already exist on-site (Voronezh, Dnepr, Duga, Container, Don-2N, C3 pages).

PAGE COMPLETE

Rewrite complete for Solnechnogorsk SPRN with communications focus, dual-echelon physics, Kartsev computing, Krokus dissemination and labelled unknowns.

EXPANDED — GRAPH FAILURE MODES

Ways the warning graph fails without a single nuclear detonation on Senezh:

• Power loss at an ORTU (generator/fuel)
• Cable cut + simultaneous relay loss on the same azimuth
• Serpukhov-15 weather/mechanical antenna failure during a thin constellation period
• Software freeze at the 514th (Kartsev-era memoirs show this was once routine to fight)
• Human rejection of a true raid (inverse Petrov)
• Human acceptance of a false raid

SPRN engineering is mostly about cutting the middle four failure modes. Doctrine and training fight the last two. [ESTIMATE]

EXPANDED — WHY FUSION IS POLITICAL

A warning grade is not only a track file; it is a claim that may authorize irreversible national action. That is why Repin’s two danger degrees, NIC isolation of test data and MoD’s public “no false warnings” rhetoric all exist. Solnechnogorsk sits on the boundary between physics and politics. [DOCUMENTED / ESTIMATE]

EXPANDED — LINK TO OBJECT 1335 GROT

Deep underground C2 at Kosvinsky (Grot) is continuity insurance for leadership connectivity. It is not an SPRN radar site and not a substitute 514th. In a protracted exchange, Grot-class nodes may still need warning product routed over surviving paths — topology unpublished. See Object 1335. [DOCUMENTED / ESTIMATE]

EXPANDED — LINK TO NDMC

The National Defense Management Center presents a modern common operational picture to national leadership. SPRN warning belongs in that picture. Whether officers at NDMC see a raw 514th mirror, a filtered Krokus heir, or a briefing product via General Staff is unpublished. Public MoD visits to GTsPRN show the hill remains a distinct physical CP, not merely a software tab inside NDMC. [ESTIMATE / DOCUMENTED for distinct CP]

EXPANDED — SENEZH GEOGRAPHY

Closed town, Timonovo, Senezh lake side, Moscow Oblast — close enough for fibre/cable into the capital’s C2 dense area, far enough for a separate guarded campus. Open coordinates above are approximate plots already in circulation; this rewrite does not refine them into targeting data. [DOCUMENTED]

EXPANDED — COMBAT PROGRAM MODULES [memoir-informed ESTIMATE]

Functionally, open accounts imply modules for:

• Node health and circuit continuity
• Track correlation across ORTU
• Space-echelon event correlation
• Catalogue / friendly-launch filters
• Danger-degree logic
• Fan-out formatting for each consumer class
• Recording / replay for after-action

Exact module names and code are classified. Menshikov’s modularization story matters because it shows the software was built to be debugged under failing hardware — a lesson for any real-time fusion system. [ESTIMATE / DOCUMENTED for modularization anecdote]

EXPANDED — METRIC OF SUCCESS

Success for Solnechnogorsk is not “detect everything.” It is: never miss a real mass raid that the sensors saw, and never ship a false «Ракетное нападение» to the Supreme Commander. Those two error types have asymmetric costs. Dual echelons, two danger degrees and human duty officers are the cost of trying to minimize both. [ESTIMATE]

PAGE END

Solnechnogorsk SPRN rewrite ends here.

LAST ADDITIONS — BEARER REDUNDANCY MATRIX [ESTIMATE]

These are design intentions inferred from documented architecture, not a leaked COM plan.

LAST ADDITIONS — LANGUAGE FOR BRIEFERS

Say: “GTsPRN at Solnechnogorsk fused dual-echelon SPRN data and issued a Krokus-class warning to the General Staff.” Do not say: “Solnechnogorsk launched,” “Solnechnogorsk’s Voronezh detected,” or “Petrov was on duty at Solnechnogorsk.”

FINAL LINE

End of Solnechnogorsk SPRN article. sprn1.webp and sprn2.webp kept in place without captions.