STP HAZMAT: Proving the Condition and Exposing the Doctrine Gap

Why this paper exists

Most doctrine is written for the system people hope will exist. This paper is written for the one that actually shows up.

In many consequence-heavy environments, the decisive early burden of response falls on a small recurring group of people who are already local, already committed, already thinly stretched, and often operating with incomplete information and uneven reinforcement. This paper refers to that condition as STP HAZMAT — the Same Ten People problem. Although the term emerged from hazardous materials teaching, the condition it names extends beyond hazardous materials.

This paper exists for people who have felt this problem in the field, in the EOC, on the fireground, in the hazmat corridor, in continuity planning, in military operations, and in underresourced organizations expected to absorb consequence with less margin than their doctrine admits. If that is not your world, this paper is probably not for you.

The condition is real

The first point is empirical. Current U.S. fire-service data continue to show substantial dependence on volunteer and paid-per-call capacity. The U.S. Fire Administration reports that among active firefighting personnel, 52% are volunteer firefighters and 13% are paid per call. The National Volunteer Fire Council reports that volunteers comprise 62% of the U.S. firefighter workforce, serving as the first line of defense across fire, EMS, vehicle accidents, terrorist and active shooter events, natural disasters, and hazardous materials incidents.

This is not merely a manpower problem. It is a problem of concentrated burden. Thin staffing means the same limited human network is repeatedly exposed to multiple hazard types and continuity demands. When a system must ask whether its own training structure is undermining force generation — as NFPA's Fire Protection Research Foundation explicitly did in 2026 — it is confronting structural strain in the very workforce it depends on.

Disaster sociology adds a second layer. Research on catastrophic events consistently shows that local social structure and immediate survivors often form the actual foundation of early response — not because they are ideally equipped, but because they are already there. The STP condition is not a bug in the system. In many jurisdictions, it is the system.

The doctrine gap

Much prevailing doctrine is organized around scalable coordination, role alignment, and whole-community frameworks. These frameworks are not wrong on their own terms. But they are not consistently built around the recurring burden-bearing local node as their primary design constraint.

When doctrine is written from the center, it tends to assume resources, specialists, handoffs, and information flows that may not materialize. The local adaptive node then has to improvise its way around doctrine that was not built for its actual situation. That improvisation is often invisible, uncompensated, and uncredited — until it fails, at which point doctrine blames the node rather than examining its own design assumptions.

That is the doctrine gap STP HAZMAT names.

The Black Swan position

Black Swan focuses on the small, local, recurring human node that continues to carry consequence when staffing is thin, information is partial, and reinforcement is delayed, degraded, or absent. This is not a niche. In much of the country — and in many international contexts — it is the median response condition, not the edge case.

The purpose of this work is not to market certainty. It is to name field conditions clearly, test ideas in public, and develop doctrine and design assumptions that remain useful under real constraint. This is research and professional writing grounded in operational reality. It is offered to be examined, challenged, refined, and pressure-tested.

If the work holds up, it becomes sharper. If it does not, it should break in public and be rebuilt honestly.

Notes, receipts, and the longer trail

Where this concept connects

The Black Swan Exaptive Spiral: Ethics, Orientation, and Disciplined Improvisation

Section 01 — The problem: adaptation without ethics fails under pressure

The Black Swan Exaptive Spiral began as a practitioner framework for generating coherent action when conditions outstrip standard plans, organizational charts, and narrow technical solutions. Its early architecture emphasized domain awareness, orientation, distributed viability, and exaptive recombination. That architecture was useful, but incomplete. It treated ethics as something adjacent to action rather than something that governs it.

That omission becomes dangerous in complex and chaotic environments. Under pressure, adaptive capacity can just as easily optimize for expedience as for integrity. It can become fast without becoming wise. It can reward fear, ego, concealment, mission tunnel vision, or institutional self-protection while still looking decisive on the surface.

This paper argues that the ethical layer is not decorative. It is the load-bearing core that keeps orientation from collapsing into rationalization under stress. The Black Swan Exaptive Spiral should therefore be understood not as a method for clever improvisation, but as a disciplined operating logic — one that joins the ethical keel, sensemaking, distributed coordination, and exaptive action into a coherent whole.

Section 02 — The ethical keel: four operational functions

The Black Swan Exaptive Spiral uses the metaphor of a keel rather than a foundation. A keel does not freeze a vessel in place. It provides the structural integrity and dynamic stability that allow it to remain oriented while the environment moves. Uncertainty is not a problem to be eliminated but a condition to be navigated.

The ethical keel comprises four operational functions that constrain action when certainty is thin, incentives are distorted, and actors are forced to move before full clarity is available.

Together, these four functions keep adaptation from collapsing into opportunism, keep decentralization from dissolving into fragmentation, and keep disciplined improvisation from degenerating into guesswork dressed up as intuition. The paper does not require familiarity with any particular philosophical tradition. It requires only the willingness to treat character as a control layer rather than decoration.

Section 03 — The architecture: five functional layers

The Spiral can be described as five stacked layers. Each layer answers a distinct question. Each fails in a characteristic way when absent. The term "exaptive" refers to exaptation — the repurposing of an existing capability, resource, or relationship for a function it was never originally designed to serve. In field terms: a transit bus becomes an evacuation asset; a routine inspection habit becomes a rapid signal-detection practice; a school becomes a clean-air shelter.

The sequence is recursive, not linear. Coherent sensemaking is strongest when the ethical keel, shared trust, and sufficient internal variety are already intact. In practice, chaotic conditions may require immediate stabilizing action before that fuller coherence is restored. The keel is not constructed by running the Spiral — it must be built before the Spiral is ever needed.

Section 04 — Domain logic and disciplined improvisation

One of the most persistent operational errors is treating all uncertainty as a license to improvise. The Black Swan Exaptive Spiral distinguishes sharply between procedure, expert adaptation, disciplined improvisation, and stabilizing action — and applies each only in the domain where it belongs.

Section 05 — Iraq vignette: when the map stopped matching the terrain

I want to be honest about where this framework comes from. The Black Swan Exaptive Spiral is not a theory assembled from books and then illustrated with a convenient war story. It began taking shape in 2003, when I was a young lieutenant in Iraq trying to make sense of an environment that kept reclassifying itself faster than our maps, our assumptions, and our command habits could track.

FOB Warhorse sat in Baqubah, the capital of Diyala Province. We moved through combat operations, stability tasks, humanitarian requirements, and emerging counterinsurgency pressures — sometimes within the same week, sometimes within the same day. Each shift demanded more than a new task list. It demanded a different orientation, a different command posture, and often a different ethical emphasis. The doctrine we had inherited was not built for that level of fluidity.

That is where the real problem revealed itself. Planning mattered, but only up to first contact with a reality that refused to stay still. After that, what mattered most was whether leaders and small units could recognize that the domain had shifted, update their mental model before it hardened into a trap, and act without losing their moral bearings.

That same failure pattern — map detached from terrain, adaptation engine running without a moral keel — appears wherever uncertainty, time pressure, technical risk, and moral strain converge. Iraq helped forge this framework. It is not the only domain where it applies.

Section 06 — Applied example: Arkema Crosby, 2017

To test the Black Swan Exaptive Spiral outside combat, this paper uses the 2017 Arkema Crosby, TX, incident: a documented Natech event with a public investigative record, multi-layer failure, and consequences extending beyond the initial physical damage. The analysis draws on the U.S. Chemical Safety Board (CSB) report, court filings, and contemporaneous reporting.

The Arkema facility manufactured and stored organic peroxides that had to be kept below freezing. Its process hazard analysis had never documented flooding as a common-mode failure, even though portions of the site lay within both the 100-year and 500-year floodplains. A 2016 insurer report had already flagged the site's flood risk. Those signals existed. They were not absorbed.

When Hurricane Harvey struck in August 2017, floodwater exceeded six feet at the facility. Primary power failed, then backup generators, then the liquid-nitrogen cooling system. On August 31, two refrigerated trailers ignited. Twenty-one first responders were hospitalized after exposure to decomposition products on U.S. Highway 90, which had been reopened based on telemetry covering only two-thirds of the risk. Over 200 residents were displaced for more than a week.

The incident migrated across Cynefin domains in compressed time. Pre-landfall the problem was complicated — solvable through expert analysis and engineering judgment. Once floodwater exceeded the design envelope, it shifted into chaos. And in the post-evacuation complex phase, three specific ethical failures drove preventable harm: the Highway 90 decision (consequential action taken on incomplete data); refusal to release the chemical inventory (institutional self-protection over community safety); and fragmented distributed cognition (no common operating picture across Arkema, local responders, and county emergency management simultaneously managing Harvey across the entire Houston metro).

Section 07 — Seven field decision prompts

For incident commanders, team leaders, and unit supervisors, the Spiral can be operationalized through seven recurring questions. These are not a replacement for ICS/NIMS — they are a decision logic that runs within that structure for the moments when the coordination architecture is intact, but the terrain has shifted faster than the procedures anticipated. They are not a checklist to be completed in sequence. They are a discipline of judgment to be applied continuously as conditions shift.

That last question is not rhetorical. If a proposed action cannot survive it, the action should not proceed. A team that internalizes these seven prompts does not need to remember the full theoretical architecture in the field. They need to ask the right questions in the right order when the terrain stops cooperating.

Section 09 — Conclusion

The Black Swan Exaptive Spiral is not a celebration of improvisation, and it is not a generic resilience slogan. It is a practitioner framework for generating coherent action in unstable terrain by anchoring adaptation in character and trust, accurately reading the domain, continuously updating orientation, preserving viable distributed coordination, and recombining available resources to extend function without increasing brittleness or moral drift.

The Spiral's contribution is not a new theory of resilience. It is a practitioner-level operating logic, forged in field experience, that integrates existing insights where they are useful and refuses them where they are not. Its test is not theoretical novelty. Its test is whether it gives the person on the scene something they can use when the terrain is shifting, and the inherited script has stopped working.

The framework earns its place one exercise and one after-action review at a time, or it does not earn it at all.

Notes, receipts, and the longer trail

01 — The problem was that the resources were wearing the wrong name

During the 2010–2011 deployment of the 196th Maneuver Enhancement Brigade, I served in the Directorate of Public Works as design engineer and environmental area manager. Camp Phoenix was a major logistics hub in the Kabul Base Cluster, and like many large installations in theater it produced a steady stream of paper, cardboard, wood scraps, and packaging that had to go somewhere. In that environment, “somewhere” often meant a burn pit or a waste stream that created more downstream problems than it solved.

The installation carried two distinct frictions at once: a continuous volume of combustible paper and cardboard pushed toward open-air burning, with all the particulate and toxic effluent that creates; and a large share of garrison personnel who stayed inside the perimeter, busy but disconnected from any visible humanitarian effect. Over a long deployment that detachment quietly erodes morale and the felt sense of purpose.

The Fuel Donut program was an attempt to connect those pieces. The goal was simple: take a waste stream the base already had, convert it into a usable heating fuel, keep the production process low-tech enough to replicate locally, and distribute the finished product through existing outreach channels. The result was a compressed biomass briquette shaped like a donut, made primarily from shredded paper and cardboard mixed with sawdust, water, and ash.

02 — The constraint was the design requirement

One rule governed the whole project: the system had to be simple. If it required complex procurement, it would fail. If it required specialized fabrication, it would fail. If it required a contractor to maintain it, it would fail. If it worked only inside a military camp, it would fail the moment we tried to move the idea into Afghan villages or displaced communities.

The same rule applied to the recipe. Camp Phoenix had shredded paper and sawdust, so that became the first material stream. But Afghanistan is not one uniform operating environment. A solution built on office waste and construction scrap might not survive in a rural area where the available biomass is straw, grass, animal waste, or agricultural residue. So the working question became: what does this location already have too much of, and what does it need more of?

That question is more useful than it sounds. We usually begin by asking what must be brought in from the outside. That is necessary but incomplete. The more useful second question is: what is already here that can be converted? Fuel donuts were one answer — not magic, not universal, but a field-expedient conversion: waste cellulose, plus simple compression, plus drying time, plus an appropriate stove, equals locally usable heat.

03 — The press and the geometry of the donut

To stay clear of the procurement pipeline, soldiers were challenged to build manual compression presses from standard carpentry tools, hand fasteners, and salvaged scrap, using a high-leverage Class-1 lever. Salvaged PVC or heavy metal conduit served as the cylinder wall, perforated low so high-pressure water could escape during compression. A rigid central mandrel anchored to the baseplate formed the hollow core. A fitted plunger let the operator drive the lever and put real mechanical advantage onto the wet mixture.

The donut shape was not a novelty. The hollow core raises the surface-area-to-volume ratio, exposing more of the mass to air, which pulled the solar-drying cycle down from weeks toward a matter of days. When burned, the same hole behaves like a small chimney, driving a natural draft of oxygen into the heart of the fuel — a hotter, more complete burn with less smoke than an open pile of loose paper.

04 — Material composition and regional recipes

The base recipe at Camp Phoenix was built directly from the garrison waste stream — roughly three-fifths shredded cellulose, one-fifth sawdust, and the balance water as binder. To make the idea exportable beyond a base with office waste, the recipe was adapted to what different regions actually have on hand.

Burn-duration figures are practitioner observations from informal field use, not laboratory results.

The point of the table is not the exact percentages. It is the method: read the local material surplus first, then fit the recipe to it.

05 — The human factor mattered as much as the fuel

The program was never only about briquettes. Inside the wire it gave soldiers and volunteers a task with a visible outcome — they could see the waste stream, build the press, produce the fuel, and watch it leave through outreach channels to help families stay warm. In long deployments people become disconnected from the mission; the work can feel abstract and detached from the population it is supposed to serve. A program like this gave people something concrete to do with their hands that connected base operations to humanitarian need.

Completed presses and donuts were handed to the Camp Phoenix Operation Outreach program for distribution to regional orphanages and refugee settlements through the Afghan winter. That closed loop gave isolated soldiers a measurable sense of effect on the population around them. That kind of work changes morale differently than a briefing does. It lets people say, honestly, “this helped someone.”

That does not make the program soft. It makes it operationally useful. Morale, purpose, and agency are not luxuries in sustained operations — they are part of the operating system. It is also why the program outlived my tenure: it did not depend on one person being clever.

06 — From press to stove

A biomass briquette is only as good as the combustion system it goes into. Burned badly, it still throws smoke, soot, carbon monoxide, and wasted heat. Burned well, the same material gives more useful heat with fewer emissions. That led to rocket-stove experimentation, on the same logic as the press: common materials, an understandable design, and adaptation to local constraint. Stoves were built from ammo cans, salvaged sheet metal, and discarded drums, insulated with local sand or wood-ash slurry to hold a hot, directed burn.

Two design features are worth recording. An inclined gravity-feed chute set at roughly 30 to 45 degrees held a column of donuts; as the lowest one burned down and lost integrity, the next slid into the burn bed, so the stove held a more consistent output without constant tending. And insulating the heat riser drove the combustion zone hot enough to gasify the cellulose far more completely than an open fire.

The lesson for practitioners is to refuse half-solutions. A good fuel in a bad stove is half a solution. A good stove with no locally available fuel is also half a solution. The field problem is the whole loop: material source, production, drying, storage, distribution, user training, combustion, safety, and maintenance. Fuel design and stove design have to be developed together.

07 — What was proven, what was observed, and what stayed prototype

Practitioner work loses credibility the moment it blurs what was done, what was watched, and what is merely possible. So, plainly: the core system — compressed fuel donuts from waste cellulose using hand-built manual presses — was constructed, demonstrated, produced, and distributed to Afghan families through Operation Outreach, and the press designs and regional recipes were shared informally with Provincial Reconstruction Team contacts. Rocket stoves were fabricated and run in several configurations.

Thermoelectric generation was a different category. I experimented with using the temperature difference between a hot stove body and cold Kabul air to generate small amounts of electricity — the Seebeck effect — with a later concept adding a fan to improve the temperature differential and force air into the burn. That work was promising and still deserves testing, but it never reached a proven production result during the deployment. It is a future development path, not a pilot outcome.

08 — What it displaced: emissions and logistics

The case for the donut over the burn pit rests on the difference between complete and incomplete combustion. Open-air pits burn cool and oxygen-starved, which maximizes the products you least want. A densified donut burned in an insulated, draft-fed stove burns hot enough to crack many of those fractions before release.

Directional comparison based on combustion chemistry and field observation, not instrumented stack sampling from the pilot.

There is also a logistics argument. Treated as an engineering estimate rather than a measured pilot result: a dried cellulose donut carries roughly 16–17 MJ/kg, comparable to local hardwood at field moisture, so locally processed fuel directly offsets fuel that would otherwise be trucked in. Every metric ton of heating demand met by converting local waste is a metric ton that does not have to move down a hazardous supply corridor. The exact displacement depends on what fuel it replaces, but the direction is not in doubt: local conversion reduces inbound tonnage, and reduced inbound tonnage reduces convoy risk.

09 — Reading it through the Exaptive Spiral

Fuel donuts are a clean worked example of what the Black Swan Exaptive Spiral describes. Exaptation is the repurposing of something for a function it was not made for; the Spiral treats exaptive action as the disciplined recombination of available tools, roles, and relationships when the inherited script no longer fits the terrain. A burn-pit liability became a fuel stream. Scrap lumber became a press. Idle capacity became a production team. A humanitarian outreach program became a distribution network. A morale problem became the signal that people needed useful work tied to visible consequence. None of those parts was invented. They were recognized and rearranged.

In this program the keel was concrete: do not burn what should not be burned, do not ship a heat source without thinking through carbon monoxide and ventilation, do not let a tidy waste-reduction metric mask a new exposure for the population. The keel is what separates a field expedient from a hazard wearing a uniform of usefulness.

It is also a Same-Ten-People story. The pilot was carried by a small, mixed group who happened to be close enough to the problem to see the trapped value, using hand tools and what was lying around. That is the environment the Spiral is built for: thin staffing, incomplete certainty, and the need to act with what is present rather than what the plan imagined.

10 — Monday morning use

A jurisdiction does not need a war zone to apply this. Pick a single recurring waste stream in your community, facility, installation, or response environment — cardboard, pallets, storm debris, yard waste, nonhazardous spoiled biomass, packaging, scrap metal, damaged lumber. Then ask five questions.

Do not begin with the grant. Do not begin with the vendor. Do not begin with the perfect system. Begin with a constraint and a useful conversion. That is where practical resilience starts.

11 — Safety boundaries: the keel in practice

Not every waste stream should become fuel. Do not burn plastics, treated wood, contaminated materials, medical waste, unknown debris, hazardous waste, or chemically contaminated material. Do not assume an improvised stove is safe for indoor use. Do not distribute any heating fuel without working through ventilation, carbon monoxide risk, fire spread, burn injury, user training, and local cultural practice.

The idea works only when the material stream is appropriate, the combustion system is safe enough for the use case, and the people using it understand its limits. If a solution reduces waste but increases exposure, it is not a solution. If it makes heat but hides toxicity, it is not a solution. If it makes responders feel useful while putting the affected population at greater risk, it is not a solution. Resilience is not improvisation without discipline. It is disciplined adaptation under constraint.

12 — Why the story still matters

The Fuel Donut pilot was small. That is part of why it matters. Large systems wait for large solutions; field conditions rarely offer that luxury. Useful capability often begins as a rough prototype built from what is available by people close enough to the problem to see the hidden value. The press was simple. The fuel was humble. The stove designs were rough. The thermoelectric work did not reach production. But the pattern was real: waste became heat, idle capacity became purpose, outreach became distribution, environmental management became humanitarian support, and a base liability became a local resource.

The next useful system may already be sitting in the scrap pile, the burn pile, the debris field, the warehouse corner, or the overlooked routine everyone complains about but no one has reframed.

— References & source notes

Image credits: field photographs from the operational records of the author, 196th MEB, Camp Phoenix, 2010–2011.

01 — Quick start: the first five moves

The plan is long, but you do not need all of it to begin. If you have one person, ninety days, and no budget, you start with five moves and come back for the rest once the first strategy is running.

02 — Why standard CRR plans fail

U.S. fire departments typically spend under three percent of budget on prevention, yet a dollar spent on response after an incident costs roughly twelve to thirty dollars more than a dollar spent on prevention before it. The result is a system that is permanently reactive and structurally unable to reduce the demand it answers. That is not mainly a budget problem; it is cultural and structural, and a plan that ignores it will not survive contact with its own department.

Three failure modes recur: the plan is written for compliance rather than commitment and is filed and forgotten; it counts activities instead of measuring whether risk indicators actually changed; and it is designed for populations that are easy to reach rather than the populations that most need reaching. This plan is built specifically to resist all three.

03 — The Black Swan CRR doctrine

Community risk reduction is exactly the kind of shifting terrain the Black Swan Exaptive Spiral was built for: demographics change, new hazards emerge, resources fluctuate, and trust is earned and lost. The departments that navigate it well are not the ones with the most resources or the most detailed initial plan. They are the ones with the strongest ethical foundation, the clearest picture of the actual terrain, and the ability to repurpose what they already have.

The same ethical keel that anchors the Spiral runs through this plan as four operational functions:

• Inner command — report what the data shows, not what leadership wants to hear, and hold that standard under budget and political pressure.
• Consequence honesty — evaluate programs by whether risk indicators actually changed, not by whether activities were completed. Alarms installed is a process measure; alarms that alert occupants in a real fire is the outcome.
• Terrain sensitivity — design for the community that exists, in its actual languages, cultures, and risk distribution, not the one that is convenient to serve.
• Moral courage without guarantees — act on uncomfortable findings before the politics are settled.

The remaining principles — trust and shared orientation, distributed coordination, domain awareness, exaptive recombination, and treating the plan as scaffolding rather than a fixed framework — are carried through every strategy in the full document.

04 — How the plan is built

The structure is deliberately conventional where convention works and disciplined where most plans drift. A Community Profile establishes the terrain — geography, demographics, hazard inventory, organizational capacity, and a vulnerability summary. A Risk Assessment Methodology turns that profile into prioritized, domain-classified risks with a defined signal pathway and data sources. Five example strategies are then worked end to end, each using the 5 E's (education, engineering, enforcement, economic incentive, and emergency response) with named participants, partners, resources, communications, and — critically — outcome measures. An Implementation Framework and an Evaluation section close the loop by defining who owns the cycle and how the department measures what actually changed.

05 — The five worked strategies

Each strategy is a complete, adaptable template — not a finished answer for any one jurisdiction, but a fully developed example to localize.

06 — What ships in the full plan

Beyond the doctrine and the five strategies, the complete document includes seven working templates — the parts a department fills in to make the plan its own:

• Appendix A — Incident data summary template
• Appendix B — Community demographic data template
• Appendix C — Response profile and hazard risk template
• Appendix D — CRR program budget template
• Appendix E — Strategic partner directory
• Appendix F — Annual program evaluation scorecard
• Appendix G — Strategy development guide