The VA Doesn't Give Credit for What You Remember.
I'm Making Sure Operation Epic Fury Veterans Have Something Better Than Memory.
The Gist
The VA claims system has a documentation problem that has existed since Vietnam and has never been fixed. Veterans come home, years pass, conditions worsen — and when they try to file, the records that would prove what happened to them are gone. I wasn’t going to let that happen to veterans of Operation Epic Fury.
Thirty-four days into OEF2026, I built epicfury.hadit.com — a real-time evidence archive that documents every confirmed event in the theater, sourced against a strict tier hierarchy, and mapped directly to 38 CFR diagnostic codes. Named casualties serve as Living Anchors: if you were in the same unit, same base, same date, you can anchor your proof of location to that record.
There’s also a critical acronym conflict that is going to cause widespread improper denials if the veterans community doesn’t address it now. OEF2026 is not OEF. OEF is Afghanistan. Every VSO, every veterans law attorney, and every advocate reading this needs to know that.
This is a one-veteran mission. I’m open to collaboration. I’m open to feedback. Getting it right matters more than anything else.
The paper trail should fight for them when they get home.
Thirty-four days ago, the United States commenced Operation Epic Fury — a massive kinetic campaign against Iran, executed alongside Israel’s Operation Roaring Lion. American service members are dying, being wounded, and being exposed to blast overpressure, acoustic trauma, toxic combustion byproducts, and sustained psychological stress on a scale the region hasn’t seen in a generation.
The VA claims system is not ready for them.
That’s not a criticism of the people who work at the VA. It’s a description of a structural problem that has existed for every conflict since Vietnam and has never been adequately addressed: the VA adjudicates disability claims based on contemporaneous documentation that the military has no systemic obligation to create, and that veterans have no systemic support to preserve.
We know how this plays out. The veteran gets home. Life takes over. Five years pass, or ten, or twenty. A condition that began in a drone strike on a logistics base in Kuwait is now a chronic disability. The veteran files. The VA asks for proof of the event. Proof of location. Proof of exposure. And the records — the unit logs, the base attack reports, the sick call records, the buddy statements — are either classified, destroyed, inaccessible, or were simply never created in a form the VA can use.
This is not an edge case. It is the dominant experience of post-9/11 veterans. It is the reason HadIt.com has existed for twenty-nine years.
What I built
Three days after Operation Epic Fury commenced, I launched epicfury.hadit.com — a real-time, publicly sourced documentation archive designed specifically to close this gap.
Every confirmed event in the OEF2026 theater is documented before the sources go offline, the press releases get archived, and the witnesses scatter. Each entry is sourced against a strict three-tier hierarchy — Tier 1 being official DOW/CENTCOM/service branch releases, DVIDS records with VIRIN numbers, and Federal Register entries; Tier 2 being a curated list of approved defense publications; Tier 3 being rejected outright. Every entry is mapped to the specific 38 CFR diagnostic codes a veteran will need when they file.
The Living Anchors doctrine is the core innovation. Named personnel — confirmed present at a specific location on a specific date via Tier 1 sources — serve as evidentiary anchors for all unnamed personnel in the same command structure. If you were in the same unit as someone named in this archive on the date of a documented event, you can anchor your Proof of Location claim to that record. That’s how the system works. Now veterans of this conflict will have the tools to work it.
The archive runs on weekly intelligence sweeps, structured fact-checks, and a source discipline that I’d put against any VSO’s claims packet review. It currently covers February 28 through April 2, 2026. Thirteen confirmed combat KIA are named and sourced. The legal authority triad — Presidential announcement, DFARS contingency designation, Congressional Record War Powers notification — is fully documented.
The companion forum
community.hadit.com/forum/199-oef2026-operation-epic-fury is where the archive meets the community. First-hand accounts, buddy statement coordination, claims questions — veteran to veteran. The forum cannot contribute to the archive directly. Source discipline is non-negotiable. But it can generate research leads that future sweeps can chase down and elevate, and it gives veterans a place to connect their experience to the documented record.
The systemic issue nobody is talking about
There is an acronym conflict that is going to cause widespread improper denials if it isn’t addressed now, and I am going to say it as loudly and as often as I can until the VA formally acknowledges it.
OEF2026 is not OEF.
“OEF” is the established abbreviation for Operation Enduring Freedom — the Afghanistan conflict, 2001 to 2014. It has its own presumptive periods, its own benefit rules, its own adjudication standards. Operation Epic Fury is a distinct 2026 military operation that has not yet received a formal congressional AUMF — itself an unresolved legal authority gap I am actively researching.
When veterans of Operation Epic Fury begin filing claims, many of them, their VSOs, and potentially VA adjudicators will use the bare “OEF” acronym out of habit. Claims will be routed to the Afghanistan conflict designation. Adjudicators will look for service dates between 2001 and 2014. Claims will be denied. Veterans will appeal. Years will be wasted.
The fix is simple and it needs to start now: Operation Epic Fury (OEF2026) on every form, every buddy statement, every nexus letter, every claim. The archive uses OEF2026 exclusively and I am asking every VSO, every veterans law attorney, and every advocacy organization reading this to do the same.
Where things stand and what I’m asking for
This is a one-veteran mission. I am under no illusions about the limits of that. The archive is methodologically sound, the pipeline is functioning, and the source discipline is rigorous — but there is a ceiling on what one person can sustain while also running HadIt.com and everything else that comes with this work.
If you are in veterans advocacy, VA claims law, military journalism, or policy research and you see value in what I’m building — I’m open to a conversation about collaboration. I am not looking for anyone to take over or redirect this work. I am looking for people who understand why it matters and want to help make it better.
And if you see something in the archive that is wrong, missing, or should be documented differently, I want to know. This is a living record. Getting it right matters more than anything else.
The paper trail should fight for them when they get home. Right now, for veterans of Operation Epic Fury, it does.
🔗 Archive: epicfury.hadit.com
🔗 Community: community.hadit.com/forum/199-oef2026-operation-epic-fury
— Theresa M. Aldrich “Tbird”
Founder, HadIt.com | Creator, Tbird’s Quiet Fight | USN Veteran