Doctrine as Organizational Memory

Start with the definitional mess, because it is instructive. Jackson opens by noting that "doctrine" has been defined so many ways it has become "thoroughly ill-defined": it is "what is written down, usually at the highest levels, for dissemination throughout an army … to instruct and standardize" (Johnston); it "stands for an institutional culture of conceptual thinking on the nature of conflict and the best conduct of warfare" (Mäder); it "is regarded as the foundation of military professional knowledge. Doctrine is to soldiers what blueprints are to architects or briefs to lawyers" (Evans). The definition Jackson builds on — Drew and Snow's "what we believe about the best way to conduct military affairs" — points at the definition he adopts: doctrine is the most visible expression of a military's institutional belief system, the accepted paradigms by which the institution understands, prepares for, and (at least in theory) conducts warfare, and, at one remove, its perception of its own role and legitimacy within society.

Three caveats discipline that definition, and each matters for us. First, doctrine is institutional: the writings of individual thinkers, from Sun Tzu forward, are not doctrine until a military formally adopts them — memory here is organizational, not personal. Second, doctrine as conceived today takes written form, though for most of Western military history doctrine was oral, informal, and personalized. Third, doctrine is cognitive — the product of "examination and interpretation of the available evidence," a process of knowledge acquisition. Put those together and Jackson has described, in his own vocabulary, exactly what Walsh & Ungson (1991) call organizational memory: stored information from an organization's history, bearing on present decisions. The distinctive move is that this institution's memory is engineered — deliberately written, hierarchically approved, formally promulgated, and periodically revised. Culture drifts; individuals retire; procedures ossify silently. Doctrine is the one retention bin you can diff.

But you can only diff editions that survive to be compared, and for most of this institution's history the norm was the opposite — the superseded edition was to be destroyed. The clearest surviving statement of that norm sits in the letter of promulgation of the Navy's wartime War Instructions, 1944, signed by Fleet Admiral E. J. King:

Read as a memory operation, that sentence is stark: doctrine revision is not only the writing of a new memory but the physical annihilation of the old one. The superseded edition is not archived, footnoted, or marked "deprecated"; it is burned, and no receipt is kept. Organizational memory as engineered here is a current memory by design — the institution holds one authoritative version and destroys its predecessors, precisely to prevent the confusion of two coexisting "truths" in the fleet. This makes our controlled comparison a lucky accident of a later, more archival era: the reason we can lay 1994, 2010, and 2020 side by side is that the modern promulgation norm changed from burning to bloodless supersession. The 2010 edition retires its predecessor in a single unceremonious line — "The previous edition of NDP 1 is superseded" — with no fire and no order to destroy. The seminar should notice that the shift from destroying prior memory to merely superseding it is itself a change in how the institution relates to its own past, and one worth holding against Session 03's account of the doctrine-production system.

Knox, writing in 1915, states the functional theory of doctrine this seminar will keep testing: doctrine is pre-positioned shared understanding — "due preparation of the minds" — that substitutes for communication when communication fails. Session 01 derived the same requirement from Galbraith: when the environment attacks your information channels, you reduce the need for information processing by loading common premises in advance. Doctrine is the load mechanism, and "a common meeting ground of beliefs" is as clean a definition of organizational memory's coordination function as anything in the 1991 literature.

Now the official definition, which all three editions of NDP 1 carry unchanged — the 2010 glossary reproduces it verbatim — and which Jackson subjects to sustained analysis:

Read as knowledge management, the two sentences are doing opposed work on purpose. "Fundamental principles … guide their actions" is a codification claim: knowledge about warfighting can be extracted from experience, generalized, written down, and reused — Hansen, Nohria & Tierney's (1999) people-to-documents strategy, whose economics depend on the same problem recurring. "Requires judgment in application" is a personalization claim: the written principle is incomplete without a competent human who carries what the document cannot — Polanyi's tacit dimension, the knowing that exceeds the telling. The clause is seemingly paradoxical (Jackson calls it exactly that), but it is better read as a boundary marker: the institution codifies up to the tacit–explicit boundary and then explicitly labels the remainder, instead of pretending the remainder does not exist (pure codification) or refusing to write anything down (pure personalization). The escape clause itself has a small three-point history worth tracking, since it is this session's central object. The 1994 and 2010 editions both carry the bare Joint Pub definition — "authoritative but requires judgment in application" — but the 2010 introduction already glosses it toward a stronger claim: "doctrine is a shared way of thinking that is authoritative, but not directive in nature." The 2020 edition then folds that gloss into the marker itself: "Like all doctrine publications, NDP 1 is authoritative but not prescriptive, and requires judgment in application." Across the sequence the institution moved from stating the tacit-boundary caveat, to explaining it, to building the explanation into the caveat — externalization tightening on its own escape clause.

One more definitional pair, because sections 03–04 depend on it. Jackson analyzes doctrine with two tools uncommon in military writing: ontology, the construction of taxonomies — the categories through which the institution carves up reality (delineating "irregular" from "conventional" warfare is ontology); and epistemology, the theory of how knowledge is acquired and warranted — the cognitive process by which the institution decides a concept deserves inclusion (evaluating a war and assigning it to a category is epistemology). Inclusion in doctrine is an epistemological act with ontological consequences: a concept printed in a manual has been institutionally accepted as valid knowledge, and the taxonomy it carries becomes the lens through which the institution perceives. In memory terms: ontology is the schema of the archive; epistemology is its admissions policy.

The archive did not appear whole. It accreted, and the accretion pattern is theoretically legible: each school emerges when the institution's environment demands that a new layer of previously tacit or personal knowledge be externalized. Three factors delineate the schools: the scope and audience broadens from system operators to legislatures and the public; the mode of application shifts from instruction manual to training aid to guidance to instrument for analysis; and the relationship to institutional ontology moves from absent, to implicit, to explicit, to inquisitive — by the fourth school, manuals are the medium in which the institution asks itself what it is for.

1. 01 Technical manual school · from 1607
   Procedures, externalized. The lineage begins with the "first modern drill book," Wapenhandlingen van Roers, Musqetten, Ende Spiessen (Amsterdam, 1607) — weapon employment broken into numbered component steps, each tied to a verbal command, published one year after Europe's first modern military academy opened at Sedan. Manuals in this school are instruction manuals: narrow, absolute, delineating correct from incorrect "in absolute and inflexible terms." Ontology is absent — a technical manual tells a soldier how to use his weapon, never when. It has never existed alone: what surrounded it for centuries was unwritten, personalized doctrine. Occasionally the micro goes macro: the US Army's 1970s "training revolution" under Gorman decomposed whole missions into task lists with mandated performance steps and annual evaluation — first-school method at institutional scale.
2. 02 Tactical manual school · late 18th–19th century
   Battle, standardized. The 1779 Regulations for the Order and Discipline of the Troops of the United States — approved by Washington and by Congress — is among the first official doctrine manuals; the school proliferates through the 19th century as post-Napoleonic professionalization replaces aristocratic birthright with merit and study (Jomini explaining Napoleon's method to everyone else). Applied as training aids, these manuals carry an implicit ontology: they assume a battlefield, assume state adversaries, assume battle outcomes decide wars — and concentrate on winning within those assumptions. The risk Jackson flags is dissonance between tactical means and strategic ends: doctrine that answers the wrong question confidently. The US war in Vietnam, on Krepinevich's account, is the canonical case.
3. 03 Operational manual school · 1982
   The institution's ontology, made explicit. Catalyzed by defeat: after Vietnam, the Army rebuilt itself around doctrine — TRADOC founded 1973; DePuy's controversial 1976 FM 100-5 ("win the first battle of the next war"); then the 1982 edition, which did two unprecedented things. It asserted an operational level of war between tactics and strategy (present in Prussian/German and Soviet doctrine for a century, new to English-speaking militaries), and it made the Army's ontology explicit: subordinate to policy in Clausewitz's sense, built to defeat the conventional forces of other states, entrusted with operations once policymakers set objectives — Huntington's "normal" theory of civil–military relations, written into the manual. The other services followed: FMFM 1 Warfighting (1989, maneuver warfare), AFM 1-1 (1992, two volumes, the second all essays), and NDP 1 (1994) — the Navy's brief flirtation, of which more below (NDP 1, 1994). Applied as guidance, taught in newly founded schools (SAMS, 1983).
4. 04 Military strategic school · 1990s
   The archive turns inquisitive. The Cold War's end dissolved the third school's ontological clarity: what were Western militaries for, in a world of peace enforcement, budget cuts, and no Soviet threat? Capstone manuals emerged as the medium of the institution's self-examination — philosophical documents establishing "fundamental principles or a core conceptual framework that is intended to describe, categorize, and justify military activities as much as guide" them. Applied as instruments for analysis; addressed, uniquely, to outsiders as much as insiders (the 2005 FM 1 names the Executive Branch, Congress, other Services, and Army civilians as its audience) — doctrine as declaration of institutional strategy, lobbying platform, and public-relations instrument. Joint doctrine arrives in the same wave, but by legislative force: Goldwater-Nichols (1986) → JP 1 (1991). And the era's ontological uncertainty is legible in its concept churn: RMA, EBO, NCW, MOOTW, SASO, RDO.

Two features of this history do theoretical work. First, the schools accumulate rather than replace. Kuhn predicts old paradigms die; Jackson finds instead that each school persists alongside its successors, in the manner of Bousquet's scientific "regimes" (mechanistic, thermodynamic, cybernetic, chaoplexic — the clock, the engine, the computer, the network), each leaving a permanent conceptual sediment. The archive is stratified, not overwritten — which is exactly how Walsh & Ungson describe organizational memory, and exactly unlike a rationalized knowledge base. Today's doctrine hierarchy contains all four schools simultaneously, from torpedo maintenance procedures to capstone philosophy, with a single fourth-school manual normally sitting atop a pyramid of operational, tactical, and technical ones.

Second, what stayed unwritten is as instructive as what got written. For most of its history the British Army kept its doctrine in the personalization bin on principle:

Jackson reports the same pattern in the US and Commonwealth navies and the US and Canadian air forces "right up until the latter part of the 20th century" — and the argument around it is Hansen's trade-off stated eighty years early: champions of unwritten doctrine "cited its flexibility as its key strength," while opponents "attacked the erratic success rate that has resulted from its reliance on the abilities of individual commanders." Flexibility versus scale; tacit richness versus turnover-vulnerability. Commonwealth navies would not even call their written manuals "doctrine" until the 1990s — they were "procedural manuals" or "fleet instructions," a naming choice that kept real doctrine, by definition, in people.

One more mechanism deserves note before we leave the history: memory here is not bounded by the single organization. Applying Fleck's "thought collectives" to Canada's adoption of the operational level of war, Coombs found that Canadian doctrine writers underwent no domestic debate at all — "it had already occurred in the United States," and the Canadians "implicitly viewed [themselves] as part of a single community of practice that extended across the continent." Jackson generalizes: an international thought collective with US doctrine writers at the inner circle and allied militaries in outer rings, flowing ideas outward far more strongly than back (he finds only a handful of reverse cases, such as US borrowing from Australia's Complex Warfighting in 2005), which makes it also an epistemic community in Haas's sense. Smaller allies effectively outsource part of their organizational memory to the hegemon's doctrine shop — with interoperability, not independent validation, as the binding constraint.

If ontology is the archive's schema, epistemology is its admissions policy — and Jackson's central historical finding is that the policy barely changed from the 17th century to the 20th. Doctrine's traditional epistemology is positivism: Enlightenment-rooted, Comtean in method — observe the subject from a neutral viewpoint, assess rationally, extract the universal laws governing the relationships, then apply the laws to manipulate reality toward a desired end (victory). Underneath sits an equally constant ontological realism: reality is structured and tangible whether or not anyone labels it — an understandable commitment, Jackson notes dryly, for practitioners who can be killed by relationships they have not yet conceptualized. The resulting belief system, in his formulation: "warranted knowledge is that which can be mathematically measured when a subject is assessed from a neutral viewpoint."

Paparone's typology (which Jackson adopts as nearly the only extant analysis of doctrinal epistemology) splits the positivist archive in two. Highly positivist doctrine expresses remedies as predetermined tasks and standards — weapon qualification, where effectiveness is assessed "using mathematical probabilities and measures of effectiveness" and a "trade school" suffices to transmit it. Moderately positivist doctrine "prescribes processes rather than preset solutions" — planning methods, mission analysis, templated campaign design — requiring practitioners with "specialized and practiced analytical skills" formed in professional schools. The Navy's clearest early exemplar of this mode long predates its capstone doctrine: the Naval War College's Sound Military Decision (1942) codified an "estimate of the situation" — a repeatable procedure for reaching a decision under uncertainty — rather than any catalog of correct decisions, and taught it at Newport to the officers who would carry it into the fleets of World War II. Procedural memory of exactly this kind is what the 2010 NDP 1 still teaches under "the planning process." The first maps to Jackson's technical school; the second describes "the vast majority of manuals" in the tactical, operational, and strategic schools. Note what both share: the codification premise. Knowledge is context-free enough to write down; the document plus a trained user equals capability. Even the judgment clause does not break the frame — Jackson reads it as "a nod to post-Enlightenment intellectual trends" that "does not alter the definition's underlying positivism, as the sound application of judgment presumes the conduct of rational thinking as a prerequisite." (His footnote is worth the price of the monograph: "A more cynical observer might be forgiven for thinking that the caveat has been included as a disclaimer, in case the application of doctrine goes awry.")

The challenge arrived on two vectors. The first was intellectual: chaos theory and complexity science, seeping into military thought from the late 1980s (Boyd's decision cycle; Mann's 1992 warning that "the provocative doctrines of the last century have become the confining dogmas of this one," and that classical strategy "compels us to reduce highly complex situations down to a few major variables"). The Marine Corps moved first and deliberately: announcing the MCDP series in 1996, Lieutenant General Van Riper promised manuals that "will not simply codify conventional military wisdom but will expand the boundaries of doctrine by incorporating lessons from other disciplines including the new sciences … the implications of chaos and complexity theory" — incorporated subtly, Bassford records, to avoid "sales resistance." The second vector was failure: the initial inadequacy of positivist doctrine for the wars in Iraq and Afghanistan, which converted an academic current into an institutional crisis — junior-officer dissent (Yingling: "a private who loses a rifle suffers far greater consequences than a general who loses a war"), the "revolt of the generals," and then the Petraeus–Mattis response, run through the doctrine system itself: the 2006 FM 3-24 / MCWP 3-33.5 Counterinsurgency, drafted by a team under the retired officer-academic Conrad Crane with unprecedented civilian participation, dual-badged into two services' hierarchies, and downloaded 1.5 million times in the month after posting — reviewed everywhere from the New York Times to jihadist websites. It is possibly the widest-circulated doctrine manual ever published: an organizational memory artifact that briefly became a public document of record.

Epistemologically, the manual's deepest novelty was the concept of design, which contrasts itself against planning in terms any knowledge theorist will recognize:

Anti-positivism denies the neutral observer: social phenomena — and warfare is one — "can only be understood from the point of view of the individuals who are directly involved," so understanding is inherently subjective, perspectival, and unstable. A doctrine written on that premise cannot store solutions; it can only store methods of inquiry. In Hansen's terms, this is a different codification product altogether: the positivist archive codifies answers for reuse; design doctrine codifies a procedure for generating situated understanding — codified inquiry rather than codified answers. In Nonaka & Takeuchi's terms, it relocates the archive's center of gravity from combination (recombining explicit knowledge) toward supported externalization (helping practitioners articulate the problem they are actually inside of). Design spread quickly — FM 3-0 (2008), FM 5-0 (2010), MCWP 5-1 (2010), and, decisively for institutional acceptance, the joint JP 5-0 (2011).

Jackson's judgment on all this is carefully hedged, and the hedges are data. He calls the shift "arguably the most pervasive paradigm shift to have occurred in 400 years of doctrinal history" — pervasive precisely because it is epistemological rather than ontological, questioning the admissions policy of all four schools at once. But he catalogs the ways it may fail: the detractors who find it vacuous (Owen: "good old wine in shabby new bottles") or unworkable (Vego, prosecuting the IDF's Systemic Operational Design after Lebanon 2006); the sympathizers who fear tactical misapplication (Elkus & Burke) or paralysis-through-analysis in conventional war (Vohr); the "comprehension gap" (users unaware of the concepts' epistemological roots) and "application gap" (anti-positivist ideas bolted onto the front of positivist planning processes); and the possibility that the whole episode is a wartime flirtation — he notes that as US attention turned to the Pacific, the Navy–Air Force "AirSea Battle" concept sat "very comfortably within the third school" with an epistemology "unquestionably positivist." Keep that hedge in hand: the 2020 NDP 1 we are about to read contains Boyd, complexity-adjacent language about chaos and uncertainty — and no design chapter at all.

Why call this a controlled comparison? Because nearly everything except time is held fixed: the same institution, writing the same capstone document (NDP 1, Naval Warfare), in the same genre (fourth-school self-description: who we are, what we do, how we fight), for the same declared purpose (a foundation "every naval professional" / "every member of the Naval Service" must understand). What varies is the strategic environment — 1994's unipolar moment, through 2010's hedge ("war with another great power strikes many as improbable," yet "demands that it be actively deterred"), to 2020's "re-emergence of long-term strategic competition" — and a quarter century of institutional life. Whatever differs between the editions is therefore evidence about how this institution edits its memory when the world moves; whatever survives is evidence about what it considers load-bearing. The March 2010 edition is the crucial addition: it converts a two-point bracket into a three-point trajectory, so that for each change we can now ask not just whether the institution edited the memory but when. One caveat governs its use throughout: the recovered file is an ~80% excerpt — foreword, introduction, Chapters Two and Three, and glossary — and the body of Chapter One is missing, so wherever a comparison dimension lives in "Who We Are," the 2010 value cannot be read and is marked as such.

First, the 1994 edition on its own terms, because its context is unusual. It was produced fast, by a new organization — the Naval Doctrine Command, established 1993, disestablished 1998, its functions dispersed — to translate the 1992 White Paper … From the Sea "into doctrinal reality," announcing a six-publication capstone series (NDP 1 through 6: warfare, intelligence, operations, logistics, planning, command and control). Its strategic frame is explicit: force redirected "toward regional contingencies and political persuasion, moving away from the prospect of all-or-nothing global war with another superpower," with a new emphasis on littoral operations. Its identity chapter names four qualities — readiness, flexibility, self-sustainability, mobility — that make naval forces "expeditionary." Its warfighting chapter teaches the attrition-versus-maneuver dichotomy and takes a side: "Maneuver warfare, based on the twin pillars of decisiveness and rapidity, is our preferred style of warfighting" — a commitment Jackson notes was "quite deliberately" borrowed to align the Navy with the Marine Corps's FMFM 1, Warfighting (1989) — the maneuver-warfare manifesto that itself became a same-document revision pair when the Marines reissued it as MCDP 1, Warfighting (1997), whose foreword states the general editing principle this whole section illustrates ("Military doctrine cannot be allowed to stagnate"). That the concept the Navy borrowed in 1994 was, by 2010, gone from NDP 1 while the Marines kept refining it in their own line is a small controlled experiment in how borrowed memory decays faster than native memory. And NDP 1's theory of doctrine itself is stated with a clarity worth quoting whole:

Jackson's verdict on the 1994 edition is part of the data: it was "notably shorter and far less detailed" than its Army, Marine Corps, or Air Force equivalents, the product of a service that "has generally been dismissive of doctrine development" — and the fourth school "has not emerged at all within the USN," which achieved capstone-like functions instead through non-doctrinal strategy papers (… From the Sea; Forward … From the Sea; Anytime, Anywhere) that Hattendorf judged to "lie between doctrine and strategy as strictly defined." Add Jackson's cross-national finding about service cultures — army doctrine faces downwards (guiding operations), navy doctrine faces upwards (justifying force structure to government), air force doctrine faces inwards (educating airmen about air power) — and a hypothesis forms that the seminar should hold onto: the Navy is the personalization-leaning service, whose deepest memory lives in ships, wardrooms, and commanders rather than manuals, and whose capstone documents are partly external-legitimation artifacts in Meyer & Rowan's sense. The 2020 edition, notably, begins by re-arguing from first principles why the nation needs a navy at all — an odd thing to have to tell one's own sailors, and exactly the thing one tells Congress.

Was that first edition actually absorbed? We have a measurement. In 1996, two years after promulgation, Anne Westerfield's Naval Postgraduate School thesis — advised by Wayne P. Hughes, whose "attack effectively first" the 2020 edition would later cite — evaluated NDP 1 against its own stated purpose of "provid[ing] a framework for detailed Navy and Marine Corps doctrine" and found it wanting: NDP 1 "contains several weaknesses that detract from its stated purpose," its ties to the subordinate publications "are weaker" than the joint publications' internal ties, and, tellingly for a memory artifact, its "beliefs and core values … are difficult to discern," submerged in the text rather than highlighted — Westerfield's specific recommendation was that Chapter One should "discourse on shared core values." This is memory uptake measured, not assumed, and it sets up a striking observation about the middle edition: the 2010 NDP 1 opens Chapter One with an explicit section on naval and guardian core values and ethos — honor, courage, commitment, and the naval ethos named outright — exactly the surfacing of core values the 1994 edition lacked and Westerfield had flagged. We should not read this as cause and effect (there is no evidence the drafters read an NPS thesis), but as parallel evidence: an independent 1996 critique and the institution's own 2010 revision converged on the same defect. Note the honesty limit — the 2010 core-values section is visible only through the recovered table of contents and its first paragraphs; the body of that chapter is part of the missing 20%.

The 2010 edition is best read as the hinge. Its strategic frame still carries the 1994 posture almost verbatim — forces directed "toward securing the United States and its allies," "moving away from the prospect of an all-or-nothing global war with another adversary" — yet it has already installed the machinery the 2020 edition would run on: the tri-service "Naval Service" identity (tri-signed by the CNO, the Commandant of the Marine Corps, and the Commandant of the Coast Guard), A Cooperative Strategy for 21st Century Seapower as the governing maritime strategy, a six-phase campaign model (Shape, Deter, Seize the Initiative, Dominate, Stabilize, Enable Civil Authority), and — decisively for the memory story — sea control restored to the center of the archive, six years before the 2020 refrain "Sea control enables all other naval functions":

What 2010 had not yet done is equally instructive. It never uses the phrase "mission command" — the command philosophy is present as commander's intent and decentralized execution, but unnamed and untheorized, the labeling still a decade away. And its account of the principles moves the other direction from 2020: where 1994 taught the nine principles of war and 2020 returns to "the nine principles of war," the 2010 edition frames them as twelve — the "principles of joint operations," the historic nine plus restraint, perseverance, and legitimacy, three additions "born out of recent experience across the range of military operations." The joint-twelve framing was a mid-period import that the 2020 edition quietly dropped, reverting to the classic nine. That non-monotonic wobble is a reminder that memory does not only accrete and prune in one direction; the institution can adopt a framing and then un-adopt it.

Now the diff. Read the table as three memory strata with different half-lives, and read left-to-right as a trajectory — the 2010 column tells you where each change had reached by the midpoint:

What does the diff teach, theoretically? Walsh & Ungson insist that organizational memory is not passive storage: retrieval is selective, reconstruction is active, and what is remembered serves present decision premises. The NDP 1 trajectory shows the layering of that process with unusual precision, and the 2010 midpoint sharpens the timing. The container (chapter triptych, principles list, vignette genre, the judgment clause itself) has a half-life measured in generations — and the one container change, dropping the futures chapter, we can now pin to 2010 or earlier rather than 2020. The middle stratum — named operational concepts — churns roughly per strategic era, but not in lockstep: maneuver warfare was out by 2010, whereas sea control's restoration was also complete by 2010, so the concept the institution unlearned and the concept it re-remembered moved on the same clock, not sequentially. Battlespace dominance out, sea control back in — a concept that is in fact the older memory, restored (Corbett and Mahan were in the 1994 reading list too). The surface stratum — the environment model — is rewritten across the sequence, and here 2010 catches the pivot half-made: the great-power threat had re-entered as a named imperative while the unipolar language of moving away from all-or-nothing global war still stood, a genuine mid-edit snapshot. One framing even reverses: the principles went nine (1994) → joint-twelve (2010) → nine again (2020), memory adopted and then un-adopted. And one detail resists every category: the mutating 99% statistic — a memory slot so stable that the institution kept the number while replacing what it counts (though its 2010 value is lost with the missing Chapter One). If you want a single exhibit for the claim that organizational memory is schema-first and fact-second, that is it.

Hansen and colleagues studied consulting, healthcare, and software firms and concluded that effective knowledge strategy is roughly 80/20 one way or the other: codify and reuse (Andersen, Ernst & Young), or cultivate person-to-person transfer (McKinsey, Bain), but do not straddle — the economics, incentives, and IT of the two strategies undermine each other. The military, on its face, is a monumental counterexample: a vast codification apparatus (four schools of manuals, hierarchies of publications, a dictionary that defines "doctrine" itself) fused to an equally vast personalization apparatus (professional military education, staff rides, war games, commander apprenticeship, unit cohesion). Why does the straddle hold?

Because it is not one knowledge market. The straddle decomposes by knowledge type, and the sources give us the decomposition directly. Where problems recur identically across thousands of units — weapon employment, signals, reporting formats, replenishment procedures — Hansen's reuse economics apply in full, and the institution codifies absolutely (first-school doctrine tolerates no judgment clause). Where problems are novel, situated, and adversarial — command decisions under uncertainty — the institution personalizes, and always has. The 1994 NDP 1 describes the personalization channel with a candor no knowledge-management consultant could improve upon: Nelson and Burke "rarely issued detailed instructions to their subordinate commanders. Instead, they frequently gathered their captains to discuss a variety of tactical problems. Because of these informal discussions, the captains became aware of what their commanders expected to accomplish … Thus prepared, they later were able to act independently, following their commanders' intent, even though formal orders either were brief or nonexistent." That is socialization in Nonaka & Takeuchi's strict sense — tacit-to-tacit transfer through shared experience — and it is described inside the codified document, as doctrine about when not to rely on doctrine. Twenty-six years later the 2020 edition canonizes the same two commanders for the same lesson. The exemplar pair is itself among the most stable items in the institution's memory.

Mapping the whole system onto Walsh & Ungson's retention bins shows what doctrine is actually for:

Against that map, doctrine's role clarifies: it is not the memory so much as the index and integrator of the memory — the one artifact that names the concepts, fixes the vocabulary, ranks the functions, and tells members which bin to consult for what ("Naval doctrine forms a bridge between the naval component of our nation's military strategy and our tactics, techniques and procedures," 1994). The SECI spiral runs through it on a loop:

The proof-of-function story for the whole system — memory substituting for communication under exactly the degraded conditions Session 01 established — is the quotation with which the 2020 edition chooses to end, a 1948 reflection on the Pacific war:

Notice what Carney does not credit: manuals. He credits inculcation — principles made "second nature," internalized past the point of needing the document. That is the mature form of the military's answer to Hansen: codification is not the terminal store of knowledge but the transmission format between generations of practitioners, with the real operational memory intended to reside, at the moment of use, in people. The written archive exists so that "due preparation of the minds" (Knox, 1915) can happen at scale and survive turnover; the judgment clause exists because the archive knows it is a means. And the standing risk is the fable in Jackson's foreword — the Soviet general's complaint that "it is impossible to plan against the Americans because they don't follow their own doctrine," which American officers repeat with pride. An adversary cannot exploit a codified memory its owners hold loosely; but an institution whose members do not know its doctrine (the very gap Colonel Hanson's foreword laments in the officer corps) is running on bins 1 and 2 alone — personalization by neglect rather than by design.

1. The clause on trial. Jackson's cynical footnote reads "authoritative but requires judgment in application" as a liability disclaimer; this session read it as a principled boundary marker for tacit knowledge. Both readings fit the text. What evidence would distinguish them — in how deviations from doctrine are treated after failure, in how the clause is taught, in whether "judgment" is ever assessed? Note that the 2020 edition strengthened the clause ("authoritative but not prescriptive"). Which reading does that revision support?
2. Hansen's warning, revisited. The military straddles codification and personalization by layering them by knowledge type. But the Soviet general's fable and Colonel Hanson's foreword (officers who don't know their own doctrine) suggest the layers leak. Is the straddle actually working — or is the US military two knowledge regimes (a codified one for procedures, an oral-cultural one for command) that merely share a letterhead? What observation would settle it?
3. The reluctant codifier. The Navy's capstone doctrine came late, thin, from a doctrine command that lived five years; its fourth-school functions ran through strategy white papers; Codner says navy doctrine faces "upwards" toward funders. Apply Meyer & Rowan: is NDP 1 load-bearing organizational memory, or ceremonial structure adopted for legitimacy while the real memory stays in ships and wardrooms? Use the 2020 edition's own features (re-arguing the case for sea power from first principles; footnoting civilian scholars) as evidence either way.
4. Forgetting versus editing. Between 1994 and 2020 the Navy deleted "maneuver warfare … is our preferred style of warfighting" — a commitment Jackson says was borrowed from the Marine Corps in the first place. Is this organizational forgetting (memory decay), deliberate unlearning (Hedberg's term), or the correction of a memory that was never authentically the institution's own? What does your answer imply about whether doctrine records belief or produces it?
5. Paradigm shift or flirtation? Jackson calls the positivist-to-anti-positivist turn "arguably the most pervasive paradigm shift … in 400 years," then hedges: design may be recaptured as checklist, AirSea Battle is comfortably positivist, and the shift may end with the wars that caused it. The 2020 NDP 1 — written nine years after JP 5-0 canonized design — contains Boyd and complexity language but no design chapter. Adjudicate: did the paradigm shift happen? What counts as evidence for a paradigm shift in an archive that historically accretes paradigms rather than replacing them?
6. Stories in the manual. Both editions teach through vignettes — Midway and Inchon in 1994; Taffy 3 and Guadalcanal in 2020. Nonaka & Takeuchi say socialization requires shared experience, which a printed story cannot provide. So what do the vignettes actually transfer — tacit judgment, values, identity, or merely the feeling of tacitness? Compare Carney's claim that principles were "second nature": can narrative inculcate, or only signal what inculcation should produce?
7. The deletion test. Suppose every doctrine publication vanished overnight but people, culture, structures, and training continued. Carney implies the fleet would fight on — the memory that matters is in commanders. What, concretely, would degrade, and on what timescale? (Consider: interoperability with allies, the thought collective, new-officer formation, the Navy–Congress interface, joint operations with services that are doctrine-based.) Use your answer to state precisely which organizational functions written memory serves that embodied memory cannot.
8. The transfer test. Take a knowledge-intensive organization you know — an engineering org with runbooks and design docs, a hospital with protocols, a law firm with precedent files. Where is its tacit–explicit boundary, and does anything mark it the way the judgment clause does? Draft the "authoritative but requires judgment" sentence for that organization's most important document, and identify what would have to change — in training, blame allocation, and versioning practice — for the sentence to be true rather than decorative.