Built in theater. Written into doctrine later.
FM 6-02, Signal Support to Operations, and related publications were issued after the 2011–2012 deployment. This chapter sets out how the subject’s documented field methods at Kandahar and FOB Farah align with those later manuals and training materials, and how that alignment is framed as a temporal, evidentiary claim rather than an authorship claim.
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. FM 6-02 and its related materials were provided to the subject through Senator Patty Murray's office on 28 May 2026, allowing this side-by-side comparison against the existing deployment record.
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 Capps 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.
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.
| In-theater execution | Record anchor | Later doctrinal reflection |
|---|---|---|
| Distributed DSST coverage across Forward Operating Bases Nathan Smith, Stone, Pasab, Farah, and Lagman | OER #1 duties; Doctrinal Nexus Analysis | FM 6-02 ¶ 3-5 and ¶ 3-6 on LandWarNet / hub-node architecture (22 Jan 2014) |
| Services pushed to the forward edge by DSST / TCF roles rather than held at the hub | OER #1; FOB Farah narrative | FM 6-02 ¶ 3-8 on services at the point of need (22 Jan 2014) |
| NetOps run as a commander-support function tied to CJTF-82, RC-South, and RC-West requirements | OER #1; Nexus Analysis | FM 6-02 ¶ 3-31 on commander-focused NetOps (22 Jan 2014) |
| Theater-level NOSC behavior performed from a FOB-level billet through the hardened TCF | OER #1; Nexus Analysis | FM 6-02 ¶ 3-33 on theater NOSC architecture (22 Jan 2014) |
| Coalition integration of Italian and other NATO partners at Farah onto the U.S. backbone | Farah and Coalition chapters; operational narrative; OER-linked nexus | FM 6-02 ¶ 2-13 and ¶ 2-42; ATP 6-02.45 coalition / multinational integration language (post-2014, 2019) |
| Recovery under failed supply conditions using lateral acquisition and nonstandard resourcing | DVIDS / Lions Roar quotes; Kandahar and Farah narrative | TC 6-02.1 “creative and unorthodox” Signal Soldier attribute (2018) |
| Distributed communications in a degraded, combat environment with FOB-level strategic nodes | Operational narrative; Farah chapter | TRADOC Pamphlet 525-3-1, The U.S. Army in Multi-Domain Operations 2028 (6 Dec 2018) |
Doctrinal register used in this chapter
The publications listed below form the doctrinal frame used in the subject’s analysis. Titles and dates are stated as verified in the public Army Publishing record. 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.
| Publication | Verified title | Relevance (subject’s analysis) |
|---|---|---|
| FM 6-02 | Signal Support to Operations | Capstone Signal doctrine; primary reference for the 5-of-7 / 71 percent traceability analysis |
| ATP 6-02.71 | Techniques for Department of Defense Information Network Operations | DODIN / NetOps techniques; linked to DSST and TCF operations |
| ATP 6-02.12 | Department of Defense Information Network–Army Planning Techniques | Planning and PACE techniques; used as a planning analogue to the in-theater work |
| ATP 6-02.53 | Techniques for Tactical Radios and Retransmission | Tactical-radio baseline; provides context for the tactical layer under the strategic build |
| ATP 6-02.54 | Techniques for Satellite Communications | SATCOM planning; relevant to backhaul from FOB-level nodes |
| ATP 6-02.60 | Techniques for Warfighter Information Network–Tactical (WIN-T) | WIN-T techniques; overlaps with the TCF and hub-node behaviors in Farah |
| TC 6-02.1 | The U.S. Army Signal Corps Training Strategy | Training doctrine; includes the “creative and unorthodox” attribute referenced in the narrative |
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.
| FM 6-02 paragraph (22 Jan 2014) | Operational narrative passage | Contemporaneous record |
|---|---|---|
| ¶ 2-33 / 2-34 — Tactical Installation and Networking-Enhanced Company (TIN-E): description of deploying to install and hand off network infrastructure, enabling transition from tactical to semi-permanent support for Army and coalition headquarters. | Narrative § III — Resourcing under constraint: lateral reconnaissance, identification of excess equipment, direct negotiation, and rapid acquisition to build the infrastructure needed for DSST and TCF functions within days rather than months. | OER #1 duties (230th Signal Co (TIN), 25th Signal Bn); DVIDS / Lions Roar article naming 1LT Capps and quoting the resourcing approach. |
| ¶ 2-40 / 2-41 — Expeditionary Signal Battalion (ESB): description of engineering, installing, operating, maintaining, and defending nodal and extension communications that carry voice, data, and special circuits over multiple transmission systems. | Narrative § I and § V: DSST coverage at five FOBs and the establishment of the first hardened TCF in Regional Command West, shifting communications at Farah from fragmented, unit-level tactical systems to integrated strategic architecture. | OER #1 (five-FOB DSST scope, TCF responsibility); deployment orders; FOB Farah chapter. |
| ¶ 2-42 — Theater Tactical Signal Brigade: supervision of installation, operation, and maintenance of nodal communications in support of Theater Army and coalition organizations. | Narrative § VI — Coalition integration: planning and execution of the Italian fiber integration at Farah, including trenching, splicing, and bringing the Italian command post on to the U.S. strategic backbone while preserving separate security postures. | OER #1 (160th Signal Brigade higher headquarters; RC-S / RC-W coverage); Coalition chapter. |
| ¶ 2-65 — Signal Command (Theater) (SC(T)): planning, engineering, and managing signal systems and interfaces with joint and multinational systems. | Narrative § V — FOB Farah and the Technical Control Facility: consolidation of asset control at Farah, hardening of the TCF, standardized access and routing procedures, and integration of multiple user communities into a single strategic node. | OER #1 (TCF OIC, FOB Farah); asset-transfer narrative in the Farah chapter. |
| ¶ 3-5 / 3-6 — LandWarNet hub-and-node architecture: description of how services are extended from theater backbones to forward nodes. | Narrative § II and § V: movement from non-functional DSST teams and absent infrastructure at the forward sites to a five-node DSST laydown anchored by the Farah TCF as a hub. | OER #1 duties; Kandahar and Farah chapters. |
| ¶ 3-8 — Services at the point of need: description of pushing services forward to where commanders operate. | Narrative § V: transfer of communications control to the DSST at Farah, relocation of soldiers into hardened structures, and daily coordination with area DSST teams to push SOPs and services forward. | OER #1 (DSST and TCF responsibilities); Farah chapter. |
| ¶ 3-23 / 3-25 — Network transport and information services: emphasis on interoperability and end-to-end connectivity involving joint, coalition, and commercial components. | Narrative § V and § VI: tactical users, the Italian enclave, and commercial fiber backhaul converging at the Farah TCF as a single, managed node. | OER #1 (network-interface duties); Coalition chapter. |
| ¶ 3-31 — Commander-focused NetOps: NetOps executed in support of commander’s intent and mission requirements. | Narrative § V: NetOps tied to Combined Joint Task Force-82 and Regional Command requirements, with daily coordination to keep services aligned with the supported commander. | OER #1 (NetOps tied to CJTF-82, RC-S, RC-W); Meritorious Service Medal citation (PO 12-130-05, 9 May 2012). |
| ¶ 3-33 — Theater Network Operations and Security Center (NOSC): centralization of network operations and security at theater level. | Narrative § V: Farah TCF functioning as the practical NetOps and security center for Regional Command West, from a FOB-level billet, before the manual codified that behavior. | OER #1 (TCF OIC); MSM citation; Farah chapter. |
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. The same approach is used for the ATP 6-02.x series and other publications listed above.
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.