Skip to content
IPBJune 19, 2026 · 2 min read

Korea-Axis Doctrine — Why Allied Operators Should Inherit, Not Re-implement

50-theater pipeline reach is the design intent, not the side effect. Encoding four centuries of IPB primitives once means every NATO/JP-doctrine ally inherits them.

byPark Moojin

The "50-theater pipeline reach" line on our website looks like a marketing claim. It is the design intent.

This note explains why.

Encoding once, inheriting everywhere

The four-century arc — Myeongnyang (1597) → Fu-Go (1944) → Muan (2024) → DPRK low-altitude (2024-25) — repeats the same handful of primitives. Environmental telemetry as decisive force. Low-altitude airspace as contested medium. Doctrine-tagged source citation as audit obligation.

Encoding those primitives in the Lattice catalog once means every allied operator who has signed onto NATO ATP-2.1.1 + JP 2-01.3 inherits them. We do not have to convince fifty CBRN cells that the primitives matter. The cells are already running on the doctrine; we ship the primitives that doctrine expects.

The re-implementation tax

Without a partner namespace, every allied operator who wants Korea-axis depth has to re-implement it. Hire analysts who can read the four-century arc. Build their own habitat profile engine. Maintain their own doctrine-reference tags. Every one of those re-implementations will be slightly inconsistent with every other one, and the inconsistency surfaces during incidents.

We want allied operators to refuse to pay the re-implementation tax. The way to make them refuse is to ship something cleaner than re-implementation: a documented, doctrine-audited, replayable namespace. That is the partner-namespace argument from a different angle.

Why "Korea-axis" is the right framing

The phrase reads parochial. The substance is the opposite. Korean theater is the case study for the four-century arc — it has all four anchor events, all four repetitions of the primitive set. An allied operator who runs this theater well is, by transferable analogy, running every other low-altitude theater well.

We do not promise to encode every theater's specifics. We promise to encode the primitives — and to ship them through a namespace that allied operators can audit against their own doctrine without our participation.

Encoding is force-multiplication

The traditional answer to "we need allies to operate at this depth" is to train more analysts. The Korea-axis doctrine is to encode the depth so the analyst headcount stays linear and the inheritance is n-way.

Six people at UAMKT cannot run fifty theaters. Six people can encode the primitives that fifty theaters inherit. The headcount math only works at the schema layer.

Inquiries: ceo@uamkt.com

Primary reference: NATO ATP-2.1.1 — Intelligence Procedures · JP 2-01.3 — Joint Intelligence Preparation of the Operational Environment.

Tags
IPBNATO ATP-2.1.1JP 2-01.350-theater
Newsletter

Doctrine, encoded — once a fortnight.

Each issue ties one allied-doctrine reference to one Korea-axis case. Average length: 5 minutes. Unsubscribe in one click.