Built in theater. Written into doctrine later.

What is and is not being claimed

The rated officer does not assert that he authored FM 6-02 or any other doctrinal publication. The claim recorded here is narrower: that the architecture, methods, and coalition-integration practices he executed in Kandahar and at FOB Farah in 2011–2012 were later reflected in formal U.S. Army Signal Corps doctrine and training publications that did not yet exist when those operations were conducted.

The argument is framed as a sequence of facts: (1) pre-arrival impossibility — the relevant manuals had not yet been published; (2) in-theater execution — the operations are documented in OERs, public-government record, and sworn narrative; and (3) post-arrival codification — FM 6-02 and related publications appeared eighteen months to eight years later with language and functions that match those earlier field methods.

Records that anchor the doctrinal claim

Three categories of contemporaneous record underwrite this chapter. The Officer Evaluation Report covering the deployment is described as one hundred percent Afghanistan-derived and records the five-FOB Direct Signal Support Team scope, the FOB Farah Technical Control Facility responsibilities, Regional Command South and West coverage, and coalition-integration duties. The DVIDS and Lions Roar coverage is the public-government record of the Kandahar resourcing turnaround, naming 1LT Jason Schnatterle and preserving the "back door deals" and "acquire as much stuff as possible" language that matches the nonstandard sustainment methods later mapped to doctrine. The Operational Narrative connects the events: failed rotations at Kandahar, lateral acquisition, reassignment to Farah, asset-control transfer, hardened TCF SOP, Italian fiber integration, and Provincial Reconstruction Team arrival, in chronological order.

The subject's Cisco credential stack — CCNP Routing & Switching, CCNA Routing & Switching, CCNA Voice, A+, Network+, Security+ — recorded in Block 6 of OER #1, is offered as context for why a first lieutenant held the depth of network-engineering knowledge necessary to build the architectures later described in doctrine. The Army's own Signal Corps career-model document identifies A+, Network+, Security+, and a single CCNA as the common baseline for the grade; the stack recorded on the OER sits well above that baseline, and multi-vendor certification stacking of the kind reflected on the OER was described by the Army in November 2013 — inside the OER window — as a newly promoted opportunity rather than an established norm.

Operational function crosswalk

The table below summarizes the precedence argument at the level of function. The left column identifies what was done in theater; the middle names the contemporaneous record that anchors that description; the right column identifies where that function later appears in doctrine or training publications.

Doctrinal register used in this chapter

The publications listed below form the doctrinal frame used in the subject's analysis. Titles and first-publication dates are stated as verified against the U.S. Army Publishing Directorate and public mirrors of the Army's files. The relevance column describes how each publication is treated in the mapping, as a matter of the subject's analysis, not as a claim of authorship.

The temporal claim can be read directly from the "First published" column: the rated officer's deployment closed in mid-2012. Every capstone or techniques publication cited below carries a first-publication date that falls after that redeployment, and in several cases years after — the specific gaps FM 6-02 and its ATP family later filled were being executed in the field first.

FM 6-02 paragraphs and the operational narrative

FM 6-02, returned under FOIA in May 2026, carries Distribution Restriction "Approved for public release; distribution is unlimited" and is dated 22 January 2014. The table below lines up selected paragraphs from that manual with passages from the Operational Narrative and the contemporaneous record that documents those passages. The intent is to show timing and correspondence, not to reproduce the manual in full.

Why FM 6-02 is cited but not hosted. FM 6-02 is approved for public release and was provided under FOIA; this archive references it by title, paragraph, and date rather than reposting the Army's file. That approach allows independent verification while keeping the archive's handling of doctrinal material conservative. A public mirror of the 22 January 2014 edition is maintained by external archives — a link is provided in the "Sources for doctrinal publications" block below for readers who wish to check paragraph text directly. The same approach is used for the ATP 6-02.x series and other publications listed above.

Independent corroboration of the doctrinal gap

The most direct outside corroboration of the timing claim comes from the RAND Corporation's 2014 study of the Afghan Mission Network. That report — produced by the RAND Arroyo Center for the U.S. Army — records that developing coalition-network integration in Afghanistan "required doctrine, leadership, training, and planning," explicitly frames doctrine as one of the elements still being built out, and specifically thanks Regional Command (West) CJ6 staff among the personnel who informed the study. That is an independent, U.S.-Army-sponsored, contemporaneous statement that the doctrinal territory this chapter maps was still under construction at the moment FM 6-02 was being drafted and published. See RAND RR-302, Networks and Network Analysis for Defence and Security (Arroyo Center, 2014).

A second, earlier corroboration comes from within the Signal branch's own professional literature. The Armed Forces Communications and Electronics Association's Signal magazine — the Signal Corps Regimental Association's professional publication — ran a field report from Kandahar in April 2011, five months before the rated officer's arrival in theater, in which the Regional Command South CJ-6 staff described multinational-coalition signal interference as "one of the most time-consuming problems of their deployment." The article documents CENTRIXS-ISAF as the practical, in-theater workaround being used at the time — the same workaround pattern that FM 6-02 would later formalize in its coalition-integration paragraphs. See AFCEA Signal, "On the Ground in Kandahar," April 2011.

Traceability ratio and limits of the claim

The most concrete metric used in this chapter is a 5-of-7, or 71 percent, FM 6-02 traceability ratio — five of seven core operational functions executed in theater correspond directly to specific paragraphs in FM 6-02 as published on 22 January 2014. The temporal gaps identified are an approximately eighteen-month gap from execution to FM 6-02 publication and a six-to-seven-year gap to TC 6-02.1, TRADOC Pamphlet 525-3-1, and the Signal Captains Career Course redesign.

The broader estimate that approximately 80–90 percent of the Signal Captains Career Course curriculum touches on functions the subject had already executed in Afghanistan is recorded here as his analysis and assertion, pending any formal review by doctrine-development authorities. The 71 percent FM 6-02 traceability figure, grounded in paragraph-level comparison, is treated as the primary evidentiary metric in this archive.

Reading this chapter alongside the others

This chapter is intended to be read in sequence with Kandahar, FOB Farah, and Coalition. Those chapters set out what was done, when, and under what conditions. This chapter then sets out what doctrine later said about those same functions, and how the timing and content of the manuals relate to the already-documented record. The goal is not to elevate opinion but to show dates, publications, and records together so that any reader — or reviewing body — can make an independent assessment of doctrinal impact.